RFC 5586, "MPLS Generic Associated Channel", June 2009Source of RFC: mpls (rtg)
See Also: RFC 5586 w/ inline errata
Errata ID: 1940
Publication Format(s) : TEXT
Reported By: Matthew Bocci
Date Reported: 2009-11-03
Verifier Name: Adrian Farrel
Date Verified: 2009-12-02
Section 10 says:
In order to support this requirement, IANA has changed the code point allocation scheme for the PW Associated Channel Type be changed as follows: 0 - 32751 : IETF Review 32760 - 32767 : Experimental
It should say:
In order to support this requirement, IANA has changed the code point allocation scheme for the PW Associated Channel Type be changed as follows: 0 - 32759 : IETF Review 32760 - 32767 : Experimental 32768 - 65535 : IETF Review
There are some gaps in the specified allocation policy for some parts of the ACH channel type range (32752 to 32759 and 32768 to 65535). The channel type is a 16-bit value, and the IANA considerations section of RFC5586 should be updated to reflect this.
The correction should be to clarify that the allocation policy for the code points that have been left out of RFC5586 is IETF review (which reflects the WG consensus at the time of publication), and to leave the Experimental range where it is to avoid impacting current implementations.
This also requires an update by IANA to the PW ACH Channel Type registry.