Search RFCs

RFC Editor

Found 2 records.

Status:Verified (2)

RFC 4133, "Entity MIB (Version 3)", August 2005

Note: This RFC has been obsoleted byRFC 6933

Errata ID:183
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2005-09-22
Verifier Name: Dan Romascanu
Date Verified: 2009-02-18

Section 2.12.1 says:

     For example, the entPhysicalUris object may be used to encode a URI     containing a Common Language Equipment Identifier (CLEI) URN for     the managed physical entity.  The URN name space for CLEIs is     defined in [RFCYYYY], and the CLEI format is defined in     [T1.213][T1.213a].  For example, an entPhysicalUris instance may     have the value of        URN:CLEI:D4CE18B7AA     [RFC3986] and [RFCYYYY] identify this as a URI in the CLEI URN name     space.  The specific CLEI code, D4CE18B7AA, is based on the example     provided in [T1.213a].

It should say:

     For example, the entPhysicalUris object may be used to encode a URI     containing a Common Language Equipment Identifier (CLEI) URN for     the managed physical entity.  The URN name space for CLEIs is     defined in [RFC4152], and the CLEI format is defined in     [T1.213][T1.213a].  For example, an entPhysicalUris instance may     have the value of        URN:CLEI:D4CE18B7AA     [RFC3986] and [RFC4152] identify this as a URI in the CLEI URN name     space.  The specific CLEI code, D4CE18B7AA, is based on the example     provided in [T1.213a].

Errata ID:779
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2005-09-22
Verifier Name: Ron Bonica
Date Verified: 2009-09-03

Section 8.2 says:

 [RFCYYYY]     Tesink, K. and R. Fox, "A Uniform Resource Name (URN)                Namespace for the CLEI Code", RFC YYYY, August 2005.

It should say:

 [RFC4152]     Tesink, K. and R. Fox, "A Uniform Resource Name (URN)               Namespace for the CLEI Code", RFC 4152, August 2005.

Report New Errata