idnits 2.17.1 draft-ietf-idr-as0-00.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 (November 29, 2011) is 4531 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 idr W. Kumari 3 Internet-Draft Google 4 Intended status: Standards Track R. Bush 5 Expires: June 1, 2012 Internet Initiative Japan 6 H. Schiller 7 Verizon 8 November 29, 2011 10 Codification of AS 0 processing. 11 draft-ietf-idr-as0-00 13 Abstract 15 This document proscribes the use of AS 0 in BGP OPEN and AS_PATH / 16 AS4_PATH BGP attribute. 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 June 1, 2012. 35 Copyright Notice 37 Copyright (c) 2011 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 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.1. Requirements notation . . . . . . . . . . . . . . . . . . . 3 54 2. Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 57 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 60 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 61 Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . . 4 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 64 1. Introduction 66 Autonomous System 0 is listed in the IANA Autonomous System Number 67 Registry as "Reserved - May be use to identify non-routed networks" 68 ([IANA.AS_Numbers]). 70 [I-D.ietf-sidr-iana-objects] specifies that AS number zero in a ROA 71 is used to mark an NLRI which is to be marked as Invalid. 73 No clear statement that AS 0 was proscribed could be found in any BGP 74 specification. 76 As at least two implementations discard routes containing AS 0 (and 77 to allow approaches such as the above) this document codifies this 78 behavior. 80 1.1. Requirements notation 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 84 document are to be interpreted as described in [RFC2119]. 86 2. Behavior 88 This document specifies that a BGP speaker MUST NOT originate or 89 propagate a route with an AS number of zero. If a BGP speaker 90 receives a route which has an AS number of zero in the AS_PATH (or 91 AS4_PATH) attribute, it SHOULD be logged and treated as a WITHDRAW. 92 This same behavior applies to routes containing zero as the 93 Aggregator or AS4 Aggregator. 95 In addition if a BGP speaker receives zero as the peer AS in an OPEN 96 message, it MUST abort the connection and send a NOTIFICATION with 97 Error Code "OPEN Message Error" and subcode "Bad Peer AS" (see 98 [RFC4271] Section 6.2). Obviously enough, a router MUST NOT initiate 99 a connection claiming to be AS number zero. 101 3. IANA Considerations 103 The IANA is requested to update the Reference for number 0 in the 104 "Autonomous System (AS) Numbers" registry to reference this document. 106 4. Security Considerations 108 By allowing resource holders to say that AS 0 is the only valid 109 origin for a route, we allow them to state that a particular address 110 resource is not in use. By ensuring that all implementations that 111 see AS 0 in a route ignore that route, we prevent a malicious party 112 from announcing routes containing AS 0 in an attempt to hijack those 113 resources. 115 In addition, by standardizing the behavior upon reception of an 116 AS_PATH (or AS4_PATH) containing AS 0, this document makes the 117 behavior better defined, and security gotchas often lurk in the 118 undefined spaces. 120 5. Acknowledgements 122 The authors wish to thank Enke Chen, Robert Raszuk, Danny McPherson, 123 Keyur Patel, John Scudder. Apologies to those we may have missed, it 124 was not intentional. 126 6. References 128 6.1. Normative References 130 [IANA.AS_Numbers] 131 IANA, "Autonomous System (AS) Numbers", 132 . 134 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 135 Requirement Levels", BCP 14, RFC 2119, March 1997. 137 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 138 Protocol 4 (BGP-4)", RFC 4271, January 2006. 140 6.2. Informative References 142 [I-D.ietf-sidr-iana-objects] 143 Manderson, T., Vegoda, L., and S. Kent, "RPKI Objects 144 issued by IANA", draft-ietf-sidr-iana-objects-03 (work in 145 progress), May 2011. 147 Appendix A. Changes / Author Notes. 149 [RFC Editor: Please remove this section before publication ] 151 Draft accepted as IDR Doc, notes reset. Please see notes for 152 draft-wkumari-idr-as0.xml for prior comments. 154 Changes -00. 156 o Added AS4_PATH -- Robert Raszuk. 157 o Change "bgp listener" to "bgp speaker" -- Enke Chen 158 o Consistent use of AS_PATH (v., AS-PATH and AS PATH) -- Danny 159 McPherson 160 o New text for Sec 2 P1 -- Enke / Keyur / Scudder, 161 http://www.ietf.org/mail-archive/web/idr/current/msg05786.html 162 o I made a boo boo -- I had the file open in 2 editors, made changes 163 in one and overwrote them by saving on the other, then checked the 164 broken one into SVN. Apologies to all whose comments I may have 165 missed... 167 Authors' Addresses 169 Warren Kumari 170 Google 171 1600 Amphitheatre Parkway 172 Mountain View, CA 94043 173 US 175 Email: warren@kumari.net 177 Randy Bush 178 Internet Initiative Japan 179 5147 Crystal Springs 180 Bainbridge Island, WA 98110 181 US 183 Email: randy@psg.com 185 Heather Schiller 186 Verizon 187 22001 Loudoun County Parkway 188 Ashburn 20147 189 US 191 Email: heather.schiller@verizon.com