The IESG wrote:
The IESG has received a request from the Pseudo Wire Emulation Edge to Edge WG to consider the following document: - 'IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3) ' <draft-ietf-pwe3-iana-allocation-12.txt> as a BCP
This draft reserves a number of ranges not be allocated by IANA, for example in Pseudowire type (2.1. Pseudowire Type) it says: "PW Type values 1025 through 4096, and 32768 are reserved for future use, and are not to be allocated by IANA." (32768 was a typo and should have been 32767). It has been suggested that we should change this to: "PW Type values 1025 through 4096, and 32767 are allocated through the IETF Consensus Process" Similarly for other ranges in the draft in which similar "not to be allocated by IANA" text is used. The rational is as follows. There is no TECHNICAL reason not to use these values - they do not for example clash with other protocols - the PWE3 WG was simply reserving them for the future with a significant barrier to their allocation. With the existing text, if we did ever need them we would need to issue an instruction to IANA to release them, but would also have to check that no one had done anything on the basis that they were not to be issued by IANA. By making them available through the IETF Consensus Process, we retain them as a range that we can use in the future, but set a barrier to use, such that they will be issued only if the IETF considers the proposed use to be valid. I believe that the proposed change executes the intent of the PWE3 WG, but is administratively simpler. - Stewart _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf