The IESG is considering the situation with IANA allocation of the RSVP FLOWSPEC and SENDER_TSPEC C-Types for ietf-ccamp-gmpls-sonet-sdh that has been recently approved by the IESG for publication as an RFC. While the long-term measures to prevent similar situations in future are being discussed, the issue at hand needs to be quickly resolved. The proposed solution is to change the assignment of the above C-Types from value 3 (currently assigned by IANA) to 4, and mark value 3 as "reserved". The IESG would like to solicit comments on the proposed solution from the community. More details are given below. Please send your comments by January 22nd, 2004. Description of the situation with IANA assignments for ietf-ccamp-gmpls-sonet-sdh: 1. After the approval of the document by the IESG, an IANA action has been performed for the document, in which IANA correctly picked the next available C-Type value (3) in the FLOWSPEC and SENDER_TSPEC ranges and assigned it to the document. 2. However, the CCAMP WG has been informed that value 3 is being used by implementations of an another (expired) Internet draft that also picked next available value in the same ranges. Because the draft never progressed, these values have never been formally allocated by IANA within the RSVP registry. 3. Because implementations of the expired Internet draft have been deployed, assigning value 3 to ietf-ccamp-gmpls-sonet-sdh would create interoperability problems. 4. An implementation survey performed in the CCAMP WG showed that most early implementations of ietf-ccamp-gmpls-sonet-sdh use value 4, and those few that use the IANA-assigned value 3 would be willing to change it to 4 to avoid interoperability problems.
