Subject: [PWE3] [Technical Errata Reported] RFC5601 (1856)

From: RFC Errata System <[email-masked]>
Date: Wed, 9 Sep 2009 00:19:47 -0700 (PDT)

The following errata report has been submitted for RFC5601,
"Pseudowire (PW) Management Information Base (MIB)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5601&eid=1856

--------------------------------------
Type: Technical
Reported by: Alfred Hoenes <[email-masked]>

Section: 12, pg.18

Original Text
-------------
  pwPeerAddrType OBJECT-TYPE
     SYNTAX        InetAddressType
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
          "Denotes the address type of the peer node.  It should be
           set to 'unknown' if PE/PW maintenance protocol is not used
           and the address is unknown."
     DEFVAL { ipv4 }
     ::= { pwEntry 8 }

  pwPeerAddr OBJECT-TYPE
     SYNTAX        InetAddress
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
          "This object contains the value of the peer node address
           of the PW/PE maintenance protocol entity.  This object
           SHOULD contain a value of all zeroes if not applicable
           (pwPeerAddrType is 'unknown')."
     ::= { pwEntry 9 }

Corrected Text
--------------
  pwPeerAddrType OBJECT-TYPE
     SYNTAX        InetAddressType
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
|         "Denotes the address type of the peer node stored in
|          pwPeerAddr.  It should be set to 'unknown' if PE/PW
           maintenance protocol is not used and the address is
           unknown."
     DEFVAL { ipv4 }
     ::= { pwEntry 8 }

  pwPeerAddr OBJECT-TYPE
     SYNTAX        InetAddress
     MAX-ACCESS    read-create
     STATUS        current
     DESCRIPTION
          "This object contains the value of the peer node address
|          of the PW/PE maintenance protocol entity. The type of this
|          object is determined by the corresponding pwPeerAddr object.
|          This object MUST contain a zero-lenght octet string if not
           applicable (pwPeerAddrType is 'unknown')."
     ::= { pwEntry 9 }

Notes
-----
Rationale:

a) RFC 4001 requests that every use of InetAddressType and
   InetAddress makes explicit the coupling between the objects.
   Hence, the DESCRIPTION clause(s) need to be amended.
   For clarity, the Corrected text does so for both objects.

b) RFC 4001 (pg. 6) specifies that an InetAddressType object of
   value unknown(0) correspond to an InetAddress object
   that is a zero-length string, unless unknown(0) is used to
   indicate an internet address type not (yet) known (at the time
   of publication of RFC 4001). All Standards Track MIB modules
   making use of InetAddressType so far couple the value unknown(0)
   with an InetAddress of size 0, because an unknown IP address
   of a (known) specific type can be represented by the
   "unspecified address" of that address format.
   Hence, the original text should be changed.
   This has been done in the perceived spirit of the conformance
   specification for pwPeerAddr on mid-page 51 and page 54.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5601 (draft-ietf-pwe3-pw-mib-14)
--------------------------------------
Title               : Pseudowire (PW) Management Information Base (MIB)
Publication Date    : July 2009
Author(s)           : T. Nadeau, Ed., D. Zelig, Ed.
Category            : PROPOSED STANDARD
Source              : Pseudo Wire Emulation Edge to Edge
Area                : Internet
Stream              : IETF
Verifying Party     : IESG