draft-ietf-idr-as-private-reservation-01.txt   draft-ietf-idr-as-private-reservation-02.txt 
Network Working Group J. Mitchell Network Working Group J. Mitchell
Internet-Draft Microsoft Corporation Internet-Draft Microsoft Corporation
Updates: 1930 (if approved) December 20, 2012 Updates: 1930 (if approved) December 21, 2012
Intended status: Informational Intended status: BCP
Expires: June 23, 2013 Expires: June 24, 2013
Autonomous System (AS) Reservation for Private Use Autonomous System (AS) Reservation for Private Use
draft-ietf-idr-as-private-reservation-01 draft-ietf-idr-as-private-reservation-02
Abstract Abstract
This document describes the reservation of Autonomous System numbers This document describes the reservation of Autonomous System numbers
(ASNs) that are for Private Use only and should not be advertised to (ASNs) that are for Private Use only and MUST NOT be advertised to
the Internet, known as Private Use ASNs. This document enlarges the the Internet, known as Private Use ASNs. This document enlarges the
total space available for Private Use ASNs by documenting the total space available for Private Use ASNs by documenting the
reservation of a second, larger range and updates RFC 1930 by reservation of a second, larger range and updates RFC 1930 by
replacing Section 10. replacing Section 10.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 June 23, 2013. This Internet-Draft will expire on June 24, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 2, line 38 skipping to change at page 2, line 38
Since the introduction of BGP Support for Four-octet AS Number Space Since the introduction of BGP Support for Four-octet AS Number Space
[RFC6793], the total size of the ASN space has increased [RFC6793], the total size of the ASN space has increased
dramatically, and a larger subset of the space should be available to dramatically, and a larger subset of the space should be available to
network operators to deploy in Private Use cases. The existing range network operators to deploy in Private Use cases. The existing range
of Private Use ASNs is widely deployed and the ability to renumber of Private Use ASNs is widely deployed and the ability to renumber
this resource in existing networks cannot be coordinated given these this resource in existing networks cannot be coordinated given these
ASNs by definition are not registered. Therefore this documents the ASNs by definition are not registered. Therefore this documents the
existing Private Use ASN reservation, while also introducing a existing Private Use ASN reservation, while also introducing a
second, larger range that can also be utilized. second, larger range that can also be utilized.
2. Private Use ASNs 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. Private Use ASNs
To allow the continued growth of usage of the BGP protocol in To allow the continued growth of usage of the BGP protocol in
networks that utilize Private Use ASNs, two ranges of ASNs are networks that utilize Private Use ASNs, two ranges of ASNs are
reserved by this document in Section 5. The first which was reserved by this document in Section 6. The first which was
previously defined in [RFC1930] out of the original 16-bit Autonomous previously defined in [RFC1930] out of the original 16-bit Autonomous
System range and a second, larger range out of the higher part of the System range and a second, larger range out of the higher part of the
Four-Octet AS Number Space [RFC6793]. Four-Octet AS Number Space [RFC6793].
3. Operational Considerations 4. Operational Considerations
If Private Use ASNs are used and prefixes are originated from these If Private Use ASNs are used and prefixes are originated from these
ASNs which are destined to the Internet, Private Use ASNs must be ASNs which are destined to the Internet, Private Use ASNs MUST be
removed from the AS_PATH before being advertised to the global removed from the AS_PATH before being advertised to the global
Internet. Operators are cautioned to ensure any implementation Internet. Operators are cautioned to ensure any implementation
specific features that recognize Private Use ASNs have been updated specific features that recognize Private Use ASNs have been updated
to recognize both ranges prior to making use of the newer, to recognize both ranges prior to making use of the newer,
numerically higher range of Private Use ASNs. Some implementations numerically higher range of Private Use ASNs. Some existing
of such features will fail to remove any Private Use ASNs from the implementations that remove Private Use ASNs from the AS_PATH may
AS_PATH if the AS_PATH contains a mix of Private Use and non-Private fail to remove Private Use ASNs if the AS_PATH contains a mixture of
Use ASNs and if these implementations are not updated, the newer Private Use and Non-Private Use ASNs. If such implementations have
range may be classified as the later. Normal AS_PATH filtering may not been updated to recognize the new range of ASNs in this document
also be used to limit prefixes originating from Private Use ASNs from and a mix of old and new range Private Use ASNs exist in the path,
being advertised to the global Internet and can help in transition these implementations may cease to remove any Private Use ASNs from
scenarios until the implementation specific features that manipulate the AS_PATH. Normal AS_PATH filtering may be used to prevent
AS_PATH are updated. prefixes originating from Private Use ASNs from being advertised to
the global Internet. Using AS_PATH filtering to filter the new range
of Private Use ASNs on a network may also mitigate the leaking of
Private Use ASNs to the global Internet in certain cases. These
cases include the case where a network is reliant on AS_PATH
manipulation features that have not been updated to recognize the new
range as described above.
4. Acknowledgements 5. Acknowledgements
The author would like to acknowledge Christopher Morrow, Jason The author would like to acknowledge Christopher Morrow, Jason
Schiller, and John Scudder for their advice on how to pursue this Schiller, and John Scudder for their advice on how to pursue this
change. The author would also like to thank Brian Dickson, David change. The author would also like to thank Brian Dickson, David
Farmer, Jeffrey Haas, Nick Hilliard, Warren Kumari, and Jeff Wheeler Farmer, Jeffrey Haas, Nick Hilliard, Warren Kumari, and Jeff Wheeler
for their comments and suggestions. for their comments and suggestions.
5. IANA Considerations 6. IANA Considerations
[Note to IANA, NOT for publication: The IANA should update the "16- [Note to IANA, NOT for publication: The IANA should update the "16-
bit Autonomous System Numbers" registry to reference this RFC (when bit Autonomous System Numbers" registry to reference this RFC (when
published) for the existing Private Use reservation. Further, to published) for the existing Private Use reservation. Further, to
maintain consistency from an operator standpoint, it is suggested maintain consistency from an operator standpoint, it is suggested
that the end of the "32-bit Autonomous System Numbers" range be that the end of the "32-bit Autonomous System Numbers" range be
reserved for Private Use, and a size of 94,967,295 (value to replace reserved for Private Use, and a size of 94,967,295 (value to replace
TBD1 below) is suggested corresponding to the range of 4200000000 TBD1 below) is suggested corresponding to the range of 4200000000
(value to replace TBD2 below) to 4294967294 (value to replace TBD3 (value to replace TBD2 below) to 4294967294 (value to replace TBD3
below).] below).]
skipping to change at page 4, line 8 skipping to change at page 4, line 18
Autonomous System numbers from the "16-bit Autonomous System Numbers" Autonomous System numbers from the "16-bit Autonomous System Numbers"
registry, namely 64512 - 65534 inclusive. registry, namely 64512 - 65534 inclusive.
IANA has also reserved, for Private Use, a contiguous block of TBD1 IANA has also reserved, for Private Use, a contiguous block of TBD1
Autonomous System numbers from the "32-bit Autonomous System Numbers" Autonomous System numbers from the "32-bit Autonomous System Numbers"
registry, namely TBD2 - TBD3 inclusive. registry, namely TBD2 - TBD3 inclusive.
These reservations have been documented in the IANA Autonomous System These reservations have been documented in the IANA Autonomous System
Numbers Registry [IANA.AS]. Numbers Registry [IANA.AS].
6. Security Considerations 7. Security Considerations
This document does not introduce any additional security concerns in This document does not introduce any additional security concerns in
regards to Private Use ASNs. regards to Private Use ASNs.
7. References 8. References
7.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
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, Autonomous System (AS) Number Space", RFC 6793,
December 2012. December 2012.
7.2. Informative References 8.2. Informative References
[IANA.AS] IANA, "Autonomous System (AS) Numbers", December 2012, [IANA.AS] IANA, "Autonomous System (AS) Numbers", December 2012,
<http://www.iana.org/assignments/as-numbers/>. <http://www.iana.org/assignments/as-numbers/>.
[RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation,
selection, and registration of an Autonomous System (AS)", selection, and registration of an Autonomous System (AS)",
BCP 6, RFC 1930, March 1996. BCP 6, RFC 1930, March 1996.
Author's Address Author's Address
 End of changes. 15 change blocks. 
25 lines changed or deleted 40 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/