RFC Errata
RFC 5654, "Requirements of an MPLS Transport Profile", September 2009
Source of RFC: mpls (rtg)
Errata ID: 2073
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Eric Gray
Date Reported: 2010-03-12
Held for Document Update by: Adrian Farrel
Section 2.5.4 says:
83 The external controls as defined in [RFC4427] MUST be supported. A. External controls overruled by higher priority requests (e.g., administrative requests and requests due to link/node failures) or unable to be signaled to the remote end (e.g., due to a coordination failure of the protection state) MUST be dropped.
It should say:
83 The external controls as defined in [RFC4427] MUST be supported. A. External controls overruled by higher priority requests (e.g., administrative requests and requests due to link/node failures) or unable to be signaled to the remote end (e.g., due to a coordination failure of the protection state) MUST be ignored.
Notes:
Dropping a control is meaningless. The original intent may have been to say "control messages", but this requirement is stated in the section "Management-Plane Operation of Protection and Restoration"
In any case, using "ignored" instead of "dropped" fixes the problem regardless of the original intention.