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: 2486
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 10.2 says:

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

(6)  Section 10.2 -- clarification including mismatched angle
                     brackets, word omissions, and punctuation

Within Section 10.2, the third paragraph on page 26 says:

   [...]
|  A newly received Path message that matches SESSION object and Sender
   Tunnel Address, LSP ID, Sub-Group Originator ID> with existing Path
|  state carrying the same or different Sub-Group_ID, referred to Sub-
|  Group_ID(n) is processed as follows:

It should say:

|  A newly received Path message with SESSION object and <Sender Tunnel
|  Address, LSP ID, Sub-Group Originator ID> tuple matching existing
|  Path state carrying the same or a different Sub-Group_ID, referred to
|  as Sub-Group_ID(n), is processed as follows:

Report New Errata