RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

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

Source of RFC: pwe3 (int)

Errata ID: 1852
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2009-09-08
Held for Document Update by: Stewart Bryant
Date Held: 2011-11-12

Section 12, pg.27 says:

  pwLastChange OBJECT-TYPE
|    SYNTAX        TimeTicks
     MAX-ACCESS    read-only
     STATUS        current
     DESCRIPTION
        "The value of sysUpTime at the time the PW entered
         its current operational state.  If the current state was
         entered prior to the last re-initialization of the local
         network management subsystem, then this object contains a
         zero value."
     ::= { pwEntry 36 }

It should say:

  pwLastChange OBJECT-TYPE
|    SYNTAX        TimeStamp
     MAX-ACCESS    read-only
     STATUS        current
     DESCRIPTION
        "The value of sysUpTime at the time the PW entered
         its current operational state.  If the current state was
         entered prior to the last re-initialization of the local
         network management subsystem, then this object contains a
         zero value."
     ::= { pwEntry 36 }

Notes:

[[ Location is bottom of page 27 ]]

Like any other object intended to keep a snapshot of sysUpTime,
this object must have the corrresponding SYNTAX of TimeStamp
(cf. pwCreateTime, on mid-page 27); a SYNTAX of TimeTicks is
appropriate on;y for 'running clocks' started at a particular
event (like pwUpTime, also on pg. 27, just above pwLastChange).


Although technically correct that the SYNTAX should be TimeStamp, this
is safe because the SYNTAX of TimeStamp is TimeTicks.

Report New Errata



Advanced Search