idnits 2.17.1 draft-ietf-idr-last-as-reservation-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC1930, but the abstract doesn't seem to directly say this. It does mention RFC1930 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC1930, updated by this document, for RFC5378 checks: 1996-03-01) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 21, 2014) is 3627 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR J. Haas 3 Internet-Draft Juniper Networks 4 Updates: 1930 (if approved) J. Mitchell 5 Intended status: Best Current Practice Microsoft Corporation 6 Expires: November 22, 2014 May 21, 2014 8 Reservation of Last Autonomous System (AS) Numbers 9 draft-ietf-idr-last-as-reservation-07 11 Abstract 13 This document reserves two Autonomous System numbers (ASNs) at the 14 end of the 16 bit and 32 bit ranges, described in this document as 15 "Last ASNs" and provides guidance to implementers and operators on 16 their use. This document updates section 10 of RFC 1930. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on November 22, 2014. 35 Copyright Notice 37 Copyright (c) 2014 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 1. Introduction 52 IANA has reserved the last Autonomous System Number (ASN), 65535, of 53 the 16 bit autonomous system number range for over a decade with the 54 intention that it not be used by network operators running BGP 55 [RFC4271]. Since the introduction of BGP Support for Four-Octet AS 56 Number Space [RFC6793], IANA has also reserved the last ASN of the 32 57 bit autonomous system number range, 4294967295. This reservation has 58 been documented in the IANA Autonomous System Numbers Registry 59 [IANA.AS]. Although these "Last ASNs" border on Private Use ASN 60 [RFC6996] ranges, they are not defined or reserved as Private Use 61 ASNs by [IANA.AS]. This document describes the reasoning for 62 reserving these Last ASNs and provides guidance both to operators and 63 to implementers on their use. 65 2. Requirements Language 67 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 68 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 69 document are to be interpreted as described in RFC 2119 [RFC2119]. 71 3. Reasons for Last ASNs Reservation 73 A subset of the BGP communities of ASN 65535, the last ASN of the 16 74 bit range, are reserved for use by Well-known communities as 75 described in [RFC1997] and [IANA.WK]. Although this is not currently 76 true of ASN 4294967295, if there is a future need for another Special 77 Use ASN that is not designed to be globally routable, or the 78 associated BGP communities of such an ASN, ASN 4294967295 could be a 79 valid candidate for such purpose. This document does not prescribe 80 any such Special Use to this ASN at the time of publication. 82 4. Operational Considerations 84 Operators SHOULD NOT use these Last ASNs for any other purpose or as 85 Private Use ASNs. Operational use of these Last ASNs could have 86 undesirable results. For example; use of AS 65535 as if it were a 87 Private Use ASN, may result in inadvertent use of BGP Well-known 88 Community values [IANA.WK], causing undesirable routing behavior. 90 These last ASNs MUST NOT be advertised to the global Internet within 91 AS_PATH or AS4_PATH attributes. Operators SHOULD filter Last ASNs 92 within the AS_PATH and AS4_PATH attributes. 94 5. Implementation Considerations 96 While these Last ASNs are reserved, they remain valid ASNs from a BGP 97 protocol perspective. Therefore, implementations of BGP [RFC4271] 98 SHOULD NOT treat the use of these Last ASNs as any type of protocol 99 error. However, implementations MAY generate a local warning message 100 indicating improper use of a reserved ASN. 102 Implementations that provide tools that filter Private Use ASNs 103 within the AS_PATH and AS4_PATH attributes MAY also include these 104 Last ASNs. 106 6. IANA Considerations 108 [Note to IANA, TO BE REMOVED BEFORE PUBLICATION: IANA please update 109 the reservations for values 65535 and 4294967295 in the registries 110 mentioned below to reference this document.] 112 IANA has reserved last Autonomous System number 65535 from the 113 "16-bit Autonomous System Numbers" registry for the reasons described 114 in this document. 116 IANA has also reserved last Autonomous System number 4294967295 from 117 the "32-bit Autonomous System Numbers" registry for the reasons 118 described in this document. 120 These reservations have been documented in the IANA Autonomous System 121 Numbers Registry [IANA.AS] and the IANA Special-Purpose AS Numbers 122 Registry [IANA.SpecialAS]. 124 7. Security Considerations 126 This document does not introduce any additional security concerns in 127 regards to usage of Last ASNs. Although the BGP protocol is designed 128 to allow usage of these Last ASNs, security issues related to BGP 129 implementation errors could be triggered by Last ASN usage. 131 8. References 133 8.1. Normative References 135 [IANA.AS] IANA, , "Autonomous System (AS) Numbers", May 2014, 136 . 138 [IANA.SpecialAS] 139 IANA, , "Special-Purpose Autonomous System (AS) Numbers", 140 May 2014, . 143 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 144 Requirement Levels", BCP 14, RFC 2119, March 1997. 146 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 147 Protocol 4 (BGP-4)", RFC 4271, January 2006. 149 [RFC6793] Vohra, Q. and E. Chen, "BGP Support for Four-Octet 150 Autonomous System (AS) Number Space", RFC 6793, December 151 2012. 153 8.2. Informative References 155 [IANA.WK] IANA, , "Border Gateway Protocol (BGP) Well-known 156 Communities", May 2014, . 159 [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP 160 Communities Attribute", RFC 1997, August 1996. 162 [RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for 163 Private Use", BCP 6, RFC 6996, July 2013. 165 Appendix A. Acknowledgments 167 The authors would like to thank Michelle Cotton and Elwyn Davis for 168 encouraging the proper documentation of the reservation of these ASNs 169 and David Farmer for his contributions to the document. 171 Authors' Addresses 173 Jeffrey Haas 174 Juniper Networks 176 Email: jhaas@juniper.net 178 Jon Mitchell 179 Microsoft Corporation 180 One Microsoft Way 181 Redmond, WA 98052 182 USA 184 Email: Jon.Mitchell@microsoft.com