draft-ietf-idr-last-as-reservation-03.txt   draft-ietf-idr-last-as-reservation-04.txt 
IDR J. Haas IDR J. Haas
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Informational J. Mitchell Intended status: Informational J. Mitchell
Expires: September 15, 2014 Microsoft Corporation Expires: September 21, 2014 Microsoft Corporation
March 14, 2014 March 20, 2014
Reservation of Last Autonomous System (AS) Numbers Reservation of Last Autonomous System (AS) Numbers
draft-ietf-idr-last-as-reservation-03 draft-ietf-idr-last-as-reservation-04
Abstract Abstract
This document reserves two Autonomous System numbers (ASNs) at the This document reserves two Autonomous System numbers (ASNs) at the
end of the 16 bit and 32 bit ranges, described in this document as end of the 16 bit and 32 bit ranges, described in this document as
"Last ASNs" and provides guidance to implementers and operators on "Last ASNs" and provides guidance to implementers and operators on
their use. their use.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 15, 2014. This Internet-Draft will expire on September 21, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 19 skipping to change at page 3, line 19
SHOULD NOT treat the use of these Last ASNs as any type of protocol SHOULD NOT treat the use of these Last ASNs as any type of protocol
error. However, implementations MAY generate a local warning message error. However, implementations MAY generate a local warning message
indicating improper use of a reserved ASN. indicating improper use of a reserved ASN.
Implementations that provide tools that filter Private Use ASNs Implementations that provide tools that filter Private Use ASNs
within the AS_PATH and AS4_PATH attributes MAY also include these within the AS_PATH and AS4_PATH attributes MAY also include these
Last ASNs. Last ASNs.
6. IANA Considerations 6. IANA Considerations
[Note to IANA, TO BE REMOVED BEFORE PUBLICATION: IANA please update
the reservations for values 65535 and 4294967295 in the three
registries mentioned below to reference this document. Please note
at the time of this comment the "Special-Purpose AS Numbers registry"
has not yet been created but should be before publication of this
document.]
IANA has reserved last Autonomous System number 65535 from the
"16-bit Autonomous System Numbers" registry for the reasons described
in this document.
IANA has reserved last Autonomous System number 65535 from the IANA has reserved last Autonomous System number 65535 from the
"16-bit Autonomous System Numbers" registry for the reasons described "16-bit Autonomous System Numbers" registry for the reasons described
in this document. in this document.
IANA has also reserved last Autonomous System number 4294967295 from IANA has also reserved last Autonomous System number 4294967295 from
the "32-bit Autonomous System Numbers" registry for the reasons the "32-bit Autonomous System Numbers" registry for the reasons
described in this document. described in this document.
This reservation has been documented in the IANA Autonomous System This reservation has been documented in the IANA Autonomous System
Numbers Registry [IANA.AS]. Numbers Registry [IANA.AS].
skipping to change at page 3, line 48 skipping to change at page 4, line 13
implementation errors could be triggered by Last ASN usage. implementation errors could be triggered by Last ASN usage.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.housley-number-registries] [I-D.housley-number-registries]
Housley, R., "Internet Numbers Registries", draft-housley- Housley, R., "Internet Numbers Registries", draft-housley-
number-registries-04 (work in progress), February 2014. number-registries-04 (work in progress), February 2014.
[IANA.AS] IANA, , "Autonomous System (AS) Numbers", February 2014, [IANA.AS] IANA, , "Autonomous System (AS) Numbers", March 2014,
<http://www.iana.org/assignments/as-numbers/>. <http://www.iana.org/assignments/as-numbers/>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet
Autonomous System (AS) Number Space", RFC 6793, December Autonomous System (AS) Number Space", RFC 6793, December
2012. 2012.
8.2. Informative References 8.2. Informative References
[IANA.WK] IANA, , "Border Gateway Protocol (BGP) Well-known [IANA.WK] IANA, , "Border Gateway Protocol (BGP) Well-known
Communities", February 2014, <http://www.iana.org/ Communities", March 2014, <http://www.iana.org/assignments
assignments/bgp-well-known-communities/>. /bgp-well-known-communities/>.
[RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP
Communities Attribute", RFC 1997, August 1996. Communities Attribute", RFC 1997, August 1996.
[RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for [RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for
Private Use", BCP 6, RFC 6996, July 2013. Private Use", BCP 6, RFC 6996, July 2013.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors would like to thank Michelle Cotton and Elwyn Davis for The authors would like to thank Michelle Cotton and Elwyn Davis for
 End of changes. 6 change blocks. 
7 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/