RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 4 records.

Status: Verified (4)

RFC 4873, "GMPLS Segment Recovery", May 2007

Note: This RFC has been updated by RFC 9270

Source of RFC: ccamp (rtg)

Errata ID: 1797
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: David McWalter
Date Reported: 2009-06-23
Verifier Name: Adrian Farrel
Date Verified: 2010-08-20

Section 5.2 says:

The collection of SRROs is controlled via the
segment-recording-desired flag in the SESSION_ATTRIBUTE object.  This
flag MAY be set even when SEROs are not used.

It should say:

   The collection of SRROs is controlled via the
   presence of an RRO in the message being processed.

Notes:

No request was made to IANA to assign a value for the segment-recording-desired flag.

As reported in the Errata, the segment-recording-desired flag is
unassigned. The flag is unassigned and therefore cannot be used.
As agreed to on the CCAMP mail list and the Stockholm (IETF 75)
working group meeting the the collection of SRROs should be
controlled based on the presence of an RRO in the message being
processed. That is, the segment-recording-desired flag should be
considered to be set when an RRO is present in the message being
processed.

Errata ID: 937
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2007-05-08
Verifier Name: Adrian Farrel
Date Verified: 2010-10-30

Section 4.2.4 says:

   Recovery LSP removal follows standard procedures defined in [RFC3209]
   and [RFC3473].  This includes with and without setting the
   administrative status.

It should say:

   Recovery LSP removal follows standard procedures defined in [RFC3209]
   and [RFC3473].  These procedures include LSP removal with and without
   setting the administrative status flags described in Section 7 of
   [RFC3473].

Errata ID: 939
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2007-05-08
Verifier Name: Adrian Farrel
Date Verified: 2010-10-30

Section 4.3.1 says:

   o new text:
      If a message contains multiple NOTIFY_REQUEST objects, only the
      first object used is in notification.  Subsequent NOTIFY_REQUEST
      objects MUST be propagated in the order received.

It should say:

   o new text:
      If a message contains multiple NOTIFY_REQUEST objects, only the
      first object is used to supply the information used to build and
      send a notification. Subsequent NOTIFY_REQUEST objects MUST be
      propagated in the order received.

Notes:

The original proposed text (below) is rejected because the presence of the NOTIFY_REQUEST object is not a trigger.
o new text:
If a message contains multiple NOTIFY_REQUEST objects, only the
first object is used to potentially trigger a notification.
Subsequent NOTIFY_REQUEST objects MUST be propagated in the order
received.

Errata ID: 943
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2007-05-08
Verifier Name: Adrian Farrel
Date Verified: 2010-10-30

Section 6.1 says:

   LSP Segment Recovery Flags are carried in the PROTECTION object of
   the same C-Type defined in [RFC4872].  The format of the flags are:

It should say:

   LSP Segment Recovery Flags are carried in the PROTECTION object of
   C-Type 2 defined in [RFC4872].  The format of the modifed PROTECTION
   object carrying these flags is:

Notes:

The subsequent diagram depicts the full object, not only the (new) flags.

Report New Errata



Advanced Search