RFC Errata
RFC 4544, "Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI)", May 2006
Note: This RFC has been obsoleted by RFC 7147
Source of RFC: ips (tsv)See Also: RFC 4544 w/ inline errata
Errata ID: 1636
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-07-04
Verifier Name: Lars Eggert
Date Verified: 2008-12-19
The DESCRIPTION clause of the iscsiHdrIntegrityNone OBJECT-IDENTITY, DESCRIPTION "The authoritative identifier when no integrity | scheme (for either the header or data) is being <<page break>> used." should better say: DESCRIPTION "The authoritative identifier when no integrity | scheme for the header is being used." The DESCRIPTION clause of the iscsiHdrIntegrityCrc32c OBJECT-IDENTITY, DESCRIPTION "The authoritative identifier when the integrity | scheme (for either the header or data) is CRC32c." should better say: DESCRIPTION "The authoritative identifier when the integrity | scheme for the header is CRC32c." The DESCRIPTION clause of the iscsiDataIntegrityNone OBJECT-IDENTITY, DESCRIPTION "The authoritative identifier when no integrity | scheme (for either the header or data) is being used." should better say: DESCRIPTION "The authoritative identifier when no integrity | scheme for the data is being used." The DESCRIPTION clause of the iscsiDataIntegrityCrc32c OBJECT-IDENTITY, DESCRIPTION "The authoritative identifier when the integrity | scheme (for either the header or data) is CRC32c." should better say: DESCRIPTION "The authoritative identifier when the integrity | scheme for the data is CRC32c."
Notes:
The iscsiDescriptors OBJECT-IDENTITY declarations, on page 16/17
of the RFC, unfortunately contain pairwise identical DESCRIPTION
clauses, making Header and Data Integrity identifiers
indistinguishable.