Hi all, again :-)
RFC 7249, fresh off the presses, instantiates an IANA registry for
"Special-Purpose AS Numbers".
The initial registry contents are:
AS Numbers Reason for Reservation
--------------------- -------------------------------------------
0 Reserved by [AS0-PROCESS]
23456 AS_TRANS; reserved by [RFC6793]
64496-64511 For documentation and sample code; reserved
by [RFC5398]
64512-65534 For private use; reserved by [RFC6996]
65535 Reserved by [RFC1930]
65536-65551 For documentation and sample code; reserved
by [RFC5398]
4200000000-4294967294 For private use; reserved by [RFC6996]
4294967295 Reserved by [LAST-AS-RES]
7249 describes this registry as follows:
Some special-purpose AS numbers have been reserved. Section 3 of
this document establishes an IANA registry for special-purpose AS
Numbers that have already been reserved. Future additions to this
registry can be made through "IETF Review" as defined in [RFC5226].
Once a reservation is approved, it is recorded in the special-purpose
AS numbers registry with a reference to the IESG-approved RFC that
documents the reservation.
William and I have heard the suggestion that we should add 112 to this
registry. A convenient mechanism for doing so would be to add some IANA
considerations to rfc6304bis.
7249 is not particularly clear on what "special" means. AS 112 is not special
from a protocol perspective; it's just another origination point for prefixes
on the Internet, and in that sense is the same as AS 701, etc.
On the other hand, AS 112 *is* special in the sense that it corresponds to a
specific architecture service that has been described in the IETF, and one
which is not controlled operationally by any single entity, and AS 112 really
shouldn't be used for anything else.
So, same basic question as before: given that rfc6304bis is already in wglc, do
we think it's worthwhile adding a sentence to the text to request the IANA to
add 112 to the "Special-Purpose AS Numbers" registry?
Joe
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
