AD review of draft-ietf-ips-iscsi-nodearch-key-02
Lars Eggert <[email protected]>
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <[email protected]> |
Section 1.2., paragraph 3: > The key is sent during operational parameter negotiation of an iSCSI > session's login phase. The intended use of this key is to provide > enhanced logging and support capabilities, and to enable collection > of iSCSI implementation and usage information. Functional behavior > of the iSCSI node (this includes the iSCSI protocol logic -- the > SCSI, iSCSI, and TCP/IP protocols) MUST NOT depend on the presence, > absence, or content of the key. The key MUST NOT be used by iSCSI > nodes for interoperability, or exclusion of other nodes. To ensure > proper use, key values SHOULD be set by the node itself, and there > SHOULD NOT be provisions for the key values to contain user- defined > text. Suggest to move the text starting with "Functional behavior..." to Section 3 (Overview is not the place for this.) Finally - why is this going for Informational and not PS? PS seems appropriate. Lars -- Lars Eggert NEC Network Laboratories _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips
smime.p7s
(application/pkcs7-signature, 3.6 KB) - not displayed