idnits 2.17.00 (12 Aug 2021) /tmp/idnits47592/draft-ietf-idr-as0-04.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 7, 2012) is 3666 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '5668' on line 210 == Outdated reference: draft-ietf-idr-error-handling has been published as RFC 7606 == Outdated reference: draft-ietf-idr-rfc4893bis has been published as RFC 6793 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 idr W. Kumari 3 Internet-Draft Google 4 Updates: 4271 (if approved) R. Bush 5 Intended status: Standards Track Internet Initiative Japan 6 Expires: November 8, 2012 H. Schiller 7 Verizon 8 K. Patel 9 Cisco Systems 10 May 7, 2012 12 Codification of AS 0 processing. 13 draft-ietf-idr-as0-04 15 Abstract 17 This document updates RFC 4271 and proscribes the use of AS 0 in BGP 18 OPEN and AS_PATH / AS4_PATH BGP attribute. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on November 8, 2012. 37 Copyright Notice 39 Copyright (c) 2012 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.1. Requirements notation . . . . . . . . . . . . . . . . . . . 3 56 2. Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 59 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 60 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 62 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 63 Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . . 5 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 Autonomous System 0 is listed in the IANA Autonomous System Number 69 Registry as "Reserved - May be use to identify non-routed networks" 70 ([IANA.AS_Numbers]). 72 [RFC6491] specifies that AS number zero in a ROA is used to mark an 73 NLRI which is to be marked as Invalid. 75 No clear statement that AS 0 was proscribed could be found in any BGP 76 specification. 78 As at least two implementations discard routes containing AS 0, and 79 to allow approaches such as the above, this document codifies this 80 behavior. 82 1.1. Requirements notation 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 86 document are to be interpreted as described in [RFC2119]. 88 2. Behavior 90 A BGP speaker MUST NOT originate or propagate a route with an AS 91 number of zero in the AS_PATH, AS4_PATH, AGGREGATOR or AS4_AGGREGATOR 92 attributes. 94 An UPDATE message that contains the AS number of zero in the AS_PATH 95 or AGGREGATOR attribute MUST be considered as malformed, and be 96 handled by the procedures specified in [I-D.ietf-idr-error-handling]. 98 An UPDATE message that contains the AS number of zero in the AS4_PATH 99 or AS4_AGGREGATOR attribute MUST be considered as malformed, and be 100 handled by the procedures specified in [I-D.ietf-idr-rfc4893bis]. 102 If a BGP speaker receives zero as the peer AS in an OPEN message, it 103 MUST abort the connection and send a NOTIFICATION with Error Code 104 "OPEN Message Error" and subcode "Bad Peer AS" (see [RFC4271] Section 105 6.2). A router MUST NOT initiate a connection claiming to be AS 106 number zero. 108 Authors of future protocol extensions that carry the Autonomous 109 System number are encouraged keep in mind that AS number zero is 110 reserved and to provide clear direction on how to handle AS number 111 zero. 113 3. IANA Considerations 115 The IANA is requested to update the Reference for number 0 in the 116 "Autonomous System (AS) Numbers" registry to reference this document. 118 4. Security Considerations 120 By allowing a RPKI resource holder to issue a ROA saying that AS 0 is 121 the only valid origin for a route, we allow them to state that a 122 particular address resource is not in use. By ensuring that all 123 implementations that see AS 0 in a route ignore that route, we 124 prevent a malicious party from announcing routes containing AS 0 in 125 an attempt to hijack those resources. 127 In addition, by standardizing the behavior upon reception of an 128 AS_PATH (or AS4_PATH) containing AS 0, this document makes the 129 behavior better defined, and security gotchas often lurk in the 130 undefined spaces. 132 5. Acknowledgements 134 The authors wish to thank Enke Chen, Brian Dickson, Bruno Decraene, 135 Robert Raszuk, Jakob Heitz, Danny McPherson, Chris Morrow, iLya, John 136 Scudder, Jeff Tantsura, Daniel Ginsburg and Susan Hares. Apologies 137 to those we may have missed, it was not intentional. 139 6. References 141 6.1. Normative References 143 [I-D.ietf-idr-error-handling] 144 Scudder, J., Chen, E., Mohapatra, P., and K. Patel, 145 "Revised Error Handling for BGP UPDATE Messages", 146 draft-ietf-idr-error-handling-01 (work in progress), 147 December 2011. 149 [I-D.ietf-idr-rfc4893bis] 150 Vohra, Q. and E. Chen, "BGP Support for Four-octet AS 151 Number Space", draft-ietf-idr-rfc4893bis-06 (work in 152 progress), April 2012. 154 [IANA.AS_Numbers] 155 IANA, "Autonomous System (AS) Numbers", 156 . 158 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 159 Requirement Levels", BCP 14, RFC 2119, March 1997. 161 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 162 Protocol 4 (BGP-4)", RFC 4271, January 2006. 164 6.2. Informative References 166 [RFC6491] Manderson, T., Vegoda, L., and S. Kent, "Resource Public 167 Key Infrastructure (RPKI) Objects Issued by IANA", 168 RFC 6491, February 2012. 170 Appendix A. Changes / Author Notes. 172 [RFC Editor: Please remove this section before publication ] 174 Draft accepted as IDR Doc, notes reset. Please see notes for 175 draft-wkumari-idr-as0.xml for prior comments. 177 Changes -00. 179 o Added AS4_PATH -- Robert Raszuk. 180 o Change "bgp listener" to "bgp speaker" -- Enke Chen 181 o Consistent use of AS_PATH (v., AS-PATH and AS PATH) -- Danny 182 McPherson 183 o New text for Sec 2 P1 -- Enke / Keyur / Scudder, 184 http://www.ietf.org/mail-archive/web/idr/current/msg05786.html 185 o I made a boo boo -- I had the file open in 2 editors, made changes 186 in one and overwrote them by saving on the "other, then checked 187 the broken one into SVN. Apologies to all whose comments I may 188 have missed... 190 Changes -01 192 o The WG thread 193 http://www.ietf.org/mail-archive/web/idr/current/msg05685.html 194 showed a very strong preference for separating the error 195 definition and handling -- the chairs also showed a prefernce to 196 Publish this and point to the error handling that Enke will write. 197 o The originally suggested text ("An UPDATE message that contains 198 the AS number of zero in the AS-PATH attribute MUST be...") only 199 referenced the AS-PATH, readded AS4_PATH, *AGGREGATOR as suggested 200 by Robert Raszak and Danny. 202 Changes -02 203 o Fixed the reference for *AGGREGATOR. This required breaking it 204 out into two sentences / clauses. 205 o Added text on other places where an AS can show up (e.g: "4-Octet 206 AS specific Extended Community" [5668]) -- thanks to Keyur. 208 Changes - 03 209 o Removed text on other places where an AS can show up (e.g: 210 "4-Octet AS specific Extended Community" [5668]). 211 o Added *very* generic "Authors of future protocol extensions..." 212 text 214 Changes -04 216 o Looks like the draft needs an 'Updates: RFC 4271' header. Can you 217 make the change? -- JGS. 218 o "You have things a bit scrambled in these two paragraphs" -- JGS 219 (whoops!). 220 o Editorial: I suggest dropping the parentheses in... JGS. 221 o Added "This document updates rfc 4271" to keep IDNITs happy... 222 o Bumped refs: draft-ietf-sidr-iana-objects has been published as 223 RFC 6491, idr-error is now -01, 4893bis is now -06 225 Authors' Addresses 227 Warren Kumari 228 Google 229 1600 Amphitheatre Parkway 230 Mountain View, CA 94043 231 US 233 Email: warren@kumari.net 235 Randy Bush 236 Internet Initiative Japan 237 5147 Crystal Springs 238 Bainbridge Island, WA 98110 239 US 241 Email: randy@psg.com 242 Heather Schiller 243 Verizon 244 22001 Loudoun County Parkway 245 Ashburn 20147 246 US 248 Email: heather.schiller@verizon.com 250 Keyur Patel 251 Cisco Systems 252 170 W. Tasman Drive 253 San Jose, CA 95134 254 USA 256 Phone: 257 Fax: 258 Email: keyupate@cisco.com 259 URI: