RFC 8287, "Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes", December 2017

Note: This RFC has been updated by RFC 8690, RFC 9214

Errata ID: 6101
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alexander ("Sasha") Vainshtein
Date Reported: 2020-04-13
Held for Document Update by: Deborah Brungard
Date Held: 2020-04-30

Section 7.2 says:

   The network node that advertised the Node Segment ID is responsible
   for generating a FEC Stack Change sub-TLV with the Post Office
   Protocol (POP) operation type for the Node Segment ID, regardless of
   whether or not Penultimate Hop Popping (PHP) is enabled.

   The network node that is immediately downstream of the node that
   advertised the Adjacency Segment ID is responsible for generating the
   FEC Stack Change sub-TLV for POP operation for the Adjacency Segment
   ID.

It should say:

   The network node that advertised the Node Segment ID is responsible
   for generating a FEC Stack Change sub-TLV with the pop operation type for 
   the Node Segment ID, regardless of whether or not penultimate hop popping 
   (PHP) is enabled.

   The network node that is immediately downstream of the node that
   advertised the Adjacency Segment ID is responsible for generating the
   FEC Stack Change sub-TLV for pop operation for the Adjacency Segment
   ID.

Notes:

Expansion of POP to "Post Office Protocol" in the context of this document is wrong. It should not be capitalized, it is not an abbreviation, simply the verb, pop. In addition, expansion for PHP should not be with caps.

Report New Errata