RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 4872, "RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery", May 2007

Source of RFC: ccamp (rtg)

Errata ID: 931
Status: Verified
Type: Editorial

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

Section 15.2 says:

   An empty PPRO with no subobjects is considered illegal.  If there is
   no first subobject, the corresponding Path message is also in error,
   and the receiving node SHOULD return a PathErr message with the new
   error code/sub-code "Routing Problem/Bad PRIMARY_PATH_ROUTE object".

It should say:

   An empty PPRO has no subobjects and is considered illegal.  A node
   receiving a Path message containing an empty PPRO SHOULD return a
   PathErr message with the new error code/sub-code "Routing Problem/
   Bad PRIMARY_PATH_ROUTE object".

Notes:

The original problem report said...

According to the text, PPROs are only admitted in Path messages.
PPROs "with no first subobject" carry no subobjects at all.
It is unclear why the text tries to distinguish these 'too cases'
and uses the word, "also", in the second sentence.

Something significant might have been lost in the text,
which cannot be concluded from the context.
In this case, please supply the missing clues.
Otherwise, the RFC should read unambiguously as supplied above.

...and proposed the text...

An empty PPRO with no subobjects is considered illegal. A node
receiving an empty PPRO SHOULD return a PathErr message with the new
error code/sub-code "Routing Problem/Bad PRIMARY_PATH_ROUTE object".

This proposal is rejected in favor of the corrected text because it lost some of the meaning.

Report New Errata