RFC 4873, "GMPLS Segment Recovery", May 2007

Note: This RFC has been updated by RFC 9270

Errata ID: 936
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-05-08
Rejected by: Adrian Farrel
Date Rejected: 2010-10-30

Section 4.2.3 says:

  In general, objects in a recovery LSP are created based on the
  corresponding objects in the LSP being protected.  [...]

It should say:

[not submitted]

Notes:

IMHO makes use of too sluggish language; talking about
"objects in a recovery LSP" or "objects in the LSP being protected"
should be avoided because it messes up the essentials of [G]MPLS,
the separation of the data plane carrying arbitrary labeled data
packets and the control plane (with RSVP-TE carrying the TE objects).
Unfortunately, similar language recurs at other places in the RFC;
for the sake of brevity, I refrain from listing all those instances
below.

I would appreciate very much future derived and/or related work to
return to a more precise language.

from pending
--VERIFIER NOTES--
There has long been a conflation of "LSP" to mean the data plane entity (connection) and the also the control plane state necessary to maintain the data plane entity. The body of people working in the MPLS and CCAMP working groups are used to this and can readily deduce which meaning is intended. Additional text is added when the author believes it is important to make an explicity distinction.

Since this Erratum is not specifically actionable on this RFC, it is rejected.

Report New Errata