RFC 5601, "Pseudowire (PW) Management Information Base (MIB)", July 2009

Errata ID: 1858
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2009-09-09
Rejected by: Stewart Bryant
Date Rejected: 2011-08-03

Section 12, pg.19/20 says:

a)  [[ DESCRIPTION clause for pwLocalAttachmentID OBJECT-TYPE,
       at the bottom of page 19: ]]

         "This object is an octet string representing the local
          forwarder attachment individual identifier (AII) to be
          used by this PW.  It is used as the Source AII (SAII) for
|         outgoing signaling messages and the Target AII (TAII) in
          the incoming messages from the peer.  Applicable if
          pwOwner equal 'genFecSignaling'."


b)  [[ DESCRIPTION clause for pwRemoteAttachmentID OBJECT-TYPE,
       on top of page 20: ]]
 
         "This object is an octet string representing the remote
          forwarder attachment individual identifier (AII) to be
          used by this PW.  It is used as the TAII for outgoing
|         signaling messages and the SAII in the incoming messages
          from the peer.
          Applicable if pwOwner equals 'genFecSignaling'."

It should say:

a)
         "This object is an octet string representing the local
          forwarder attachment individual identifier (AII) to be
          used by this PW.  It is used as the Source AII (SAII) for
|         outgoing signaling messages and expected as the Target
          AII (TAII) in the incoming messages from the peer.
          Applicable if pwOwner equal 'genFecSignaling'."

b)
         "This object is an octet string representing the remote
          forwarder attachment individual identifier (AII) to be
          used by this PW.  It is used as the TAII for outgoing
|         signaling messages and expected as the SAII in the
          incoming messages from the peer.
          Applicable if pwOwner equals 'genFecSignaling'."

Notes:

Rationale:
The phrase talking about "use" of a value in an incoming message
is potentially misleading. The insertion of "expected as" should
cure the issue, with minimal footprint.
--VERIFIER NOTES--
The original text clearly states the use of the object.

Report New Errata