RFC 4875, "Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)", May 2007

Note: This RFC has been updated by RFC 6510

Errata ID: 2485
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-05-15
Held for Document Update by: Adrian Farrel
Date Held: 2010-08-21

Section 8.2 says:

Erratum created by duplication from multipart Erratum 961 raised by Alfred Hoenes.

(5)  Section 8.2 -- text duplication and inconsistency

The second paragraph of Section 8.2 (on page 23),

   A transit LSR sets the Sub-Group Originator ID in the FILTER_SPEC
   object(s) of a Resv message to the value that was received in the
   corresponding Path message.  If any of the incoming Resv messages
   corresponding to a single Path message carry a RESV_CONFIRM object,
   then the LSR MUST include a RESV_CONFIRM object in the corresponding
   Resv message that it sends upstream.  If the Sub-Group Originator ID
   is its own address, then it MUST set the receiver address in the
   RESV_CONFIRM object to this address, else it MUST propagate the
   object unchanged.

should be deleted entirely !

Rationale:
  The first two sentences in this paragraph are repeated almost
  literally in the subsequent (third) paragraph of the section.
  The third (last) sentence above essentially is superseeded, in
  a more precise manner, by the second and the third bullet at the
  bottom of page 23.
  But, perhaps most importantly, the first bullet there handles a
  subcase not covered by, and hence mis-specified, by that sentence!

  Apparently, the lower half of page 23 is a revised revision of
  the quoted second paragraph, which should have been deleted.

Report New Errata