RFC Errata
Found 6 records.
Status: Verified (6)
RFC 5601, "Pseudowire (PW) Management Information Base (MIB)", July 2009
Source of RFC: pwe3 (int)
Errata ID: 4069
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alexander ("Sasha") Vainshtein
Date Reported: 2014-08-05
Verifier Name: Brian Haberman
Date Verified: 2014-08-06
Section 12 says:
pwAttachedPwIndex OBJECT-TYPE
SYNTAX PwIndexOrZeroType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the PW is attached to another PW instead of a local
native service, this item indicates the pwIndex of the
attached PW. Otherwise, this object MUST
be set to zero. Attachment to another PW will have no
PW specific entry in any of the service MIB modules."
DEFVAL { 0 }
::= { pwEntry 10 }
It should say:
pwAttachedPwIndex OBJECT-TYPE
SYNTAX PwIndexOrZeroType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the PW is attached to another PW instead of a local
native service, this item indicates the pwIndex of the
attached PW. Otherwise, this object MUST
be set to zero. Attachment to another PW will have no
PW specific entry in any of the service MIB modules.
This object may be modified only when the value of
the associated pwAdminStatus object is down(2), and
the associated pwOperStatus object has value down(2)
or notPresent(5) such that the row in the pwTable
represents an inactive PW."
DEFVAL { 0 }
::= { pwEntry 10 }
Notes:
Description of the pwEntry object in the same RFC states that "The read-create objects in this table are divided into
three categories:
1) Objects that MUST NOT be changed after row activation.
These are objects that define basic properties of the
PW (for example type, destination, etc.).
2) Objects that MAY be changed when the PW is
defined as not active. A change of these objects involves
re-signaling of the PW or it might be traffic affecting.
PW not active is defined as one of the following
conditions:
a) The pwRowStatus is notInService(2).
b) The pwRowStatus is notReady(3).
c) The pwAdminStatus is down(2).
If the operator needs to change one of the values for an
active row, the operator can either set the pwRowStatus to
notInService(2) or set pwAdminStatus to down(2).
Signaling (or traffic) is initiated again upon setting
the pwRowStatus to active(1) or setting the pwAdminStatus
to up(1) or testing(3), respectively.
3) Objects that MAY be changed at any time."
In further states (in tthe same description) that "By default, all the read-create objects MUST NOT be changed after row activation, unless specifically indicated in the individual object description."
pwAttachedPwIndex object is used to stitch a couple of PWs represented by two different rows in the pwTable, with the pwAttachedPwIndex value in the row representing one of them set to the pwIndex of the other one and vice versa.
Since there is no way in the SMIv2 paradigm to create two rows in the same table
in a single atomic operation, setting a this attribute in a pair of rows is only
possible when both are created. In order to do that, read-create access mode of
the pwAttachedPwIndex object has to be interpreted as ability to set its value
when the row represents an inactive PW.
In accordance with the quoted description, such an interpretation must be
explicitly specified in the description of this object.
Such a specification is missing in the current text, hence the default
interpretation of the read-create access mode is holds.
Proposed text fixes this problem.
Errata ID: 1859
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2009-09-09
Verifier Name: Stewart Bryant
Date Verified: 2011-11-12
Section 12, pg.25 says:
[[ DESCRIPTION clause for pwFcsRetentionCfg OBJECT-TYPE ]]
"The local configuration of Frame Check Sequence (FCS)
retention for this PW. FCS retention can be configured for
PW types High-Level Data Link Control (HDLC), Point-to-Point
Protocol (PPP), and Ethernet only. If the implementation
| does not support FCS retention, an error MUST be reported in
pwFcsRetentionStatus. This object MAY be changed only if
the PW is not active."
It should say:
"The local configuration of Frame Check Sequence (FCS)
retention for this PW. FCS retention can be configured for
PW types High-Level Data Link Control (HDLC), Point-to-Point
Protocol (PPP), and Ethernet only. If this object is set to
fcsRetentionEnable(2) and the implementation does not support
the FCS retention for this PW, an error MUST be indicated by
setting pwFcsRetentionStatus to localFcsRetentionCfgErr(4).
This object can be changed only if the PW is not active."
Notes:
Rationale:
The original DESCRIPTION indicated unconditional signaling of an error, whether
the activation of unsupported FCS retention is requested or not.
This is contrary to the DESCRIPTION for pwFcsRetentionStatus.
Errata ID: 3030
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Stewart Bryant
Date Reported: 2011-11-12
Verifier Name: Stewart Bryant
Date Verified: 2011-11-12
Section 12, page 37 says:
pwPerf1DayIntervalTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwPerf1DayIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides per-PW performance information for
the current day's measurement and the previous day's
interval."
It should say:
DESCRIPTION
"This table provides per-PW performance information for
the current day's measurement and the previous day's
measurement."
Errata ID: 1861
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2009-09-09
Verifier Name: Stewart Bryant
Date Verified: 2011-11-12
Section 12, pg.34 says:
pwPerfIntervalEntry OBJECT-TYPE
SYNTAX PwPerfIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by the agent for every
| PW."
It should say:
pwPerfIntervalEntry OBJECT-TYPE
SYNTAX PwPerfIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by the agent for every
monitored interval for each monitored PW."
Errata ID: 1862
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2009-09-09
Verifier Name: Stewart Bryant
Date Verified: 2011-11-12
Section 12, pg.38 says:
pwPerf1DayIntervalEntry OBJECT-TYPE
SYNTAX PwPerf1DayIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by the agent for every
| PW."
It should say:
pwPerf1DayIntervalEntry OBJECT-TYPE
SYNTAX PwPerf1DayIntervalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by the agent for every
monitored day for each monitored PW."
Errata ID: 2815
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Daniel Cohn
Date Reported: 2011-05-24
Verifier Name: Stewart Bryant
Date Verified: 2011-11-12
Section Daniel says:
pwOperStatus OBJECT-TYPE
SYNTAX PwOperStatusTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the operational status of the PW; it
does not reflect the status of the Customer Edge (CE) bound
interface. It is set to down only if pwNotForwarding,
psnFacingPwRxFault, or psnFacingPwTxFault indications are
set in pwLocalStatus or pwRemoteStatus.
It indicates 'lowerLayerDown' if the only reason for
not being in the 'up' state is that either the outer tunnel
or physical layer of the network side is in the 'down'
state.
All other states are declared based on the description
of the PwOperStatusTC.
"
::= { pwEntry 38 }
It should say:
pwOperStatus OBJECT-TYPE
SYNTAX PwOperStatusTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the operational status of the PW; it
does not reflect the status of the Customer Edge (CE) bound
interface. It is set to down only if pwNotForwarding,
psnPwRxFault, or psnPwTxFault indications are
set in pwLocalStatus or pwRemoteStatus.
It indicates 'lowerLayerDown' if the only reason for
not being in the 'up' state is that either the outer tunnel
or physical layer of the network side is in the 'down'
state.
All other states are declared based on the description
of the PwOperStatusTC.
"
::= { pwEntry 38 }
Notes:
psnFacingPwRxFault and psnFacingPwTxFault were replaced in RFC 5542 by psnPwRxFault and psnPwTxFault respectively