idnits 2.17.1 draft-wkumari-idr-as0-01.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 (October 23, 2011) is 4569 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: April 25, 2012 Internet Initiative Japan 6 H. Schiller 7 Verizon 8 October 23, 2011 10 Codification of AS 0 processing. 11 draft-wkumari-idr-as0-01 13 Abstract 15 This document proscribes the use of AS 0 in BGP OPEN and AS-PATH BGP 16 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 April 25, 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 propapate an announcement with an AS number of zero, and a BGP 90 listener MUST NOT accept an announcement which has an AS number of 91 zero in the AS-PATH attribute, and SHOULD log the fact that it has 92 done so. 94 In addition if a BGP listener recives zero as the peer AS in an OPEN 95 message, it MUST abort the connection and send a NOTIFICATION with 96 Error Code "OPEN Message Error" and subcode "Bad Peer AS" (see 97 [RFC4271] Section 6.2). Obviosuly enough, a router MUST NOT 98 initialte a connection claiming to be AS number zero. 100 3. IANA Considerations 102 The IANA is requested to update the Reference for number 0 in the 103 "Autonomous System (AS) Numbers" registry to refernce this document. 105 4. Security Considerations 107 By allowing resource holders to say that AS 0 is the only valid 108 origin for a route, we allow them to state that a particular address 109 resource is not in use. By ensuring that all implementations that 110 see AS 0 in a route ignore that route, we prevent a malicious party 111 from announcing routes containing AS 0 in an attempt to hijack those 112 resources. 114 In addition, by standardizing the behavior upon reception of an AS 115 PATH containing AS 0, this document makes the behavior better 116 defined, and security gotchas often lurk in the undefined spaces. 118 5. Acknowledgements 120 The authors wish to thank the BGPsec design team, and especially 121 Randy Bush for providing most of the text. 123 6. References 125 6.1. Normative References 127 [IANA.AS_Numbers] 128 IANA, "Autonomous System (AS) Numbers", 129 . 131 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 132 Requirement Levels", BCP 14, RFC 2119, March 1997. 134 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 135 Protocol 4 (BGP-4)", RFC 4271, January 2006. 137 6.2. Informative References 139 [I-D.ietf-sidr-iana-objects] 140 Manderson, T., Vegoda, L., and S. Kent, "RPKI Objects 141 issued by IANA", draft-ietf-sidr-iana-objects-03 (work in 142 progress), May 2011. 144 Appendix A. Changes / Author Notes. 146 [RFC Editor: Please remove this section before publication ] 148 From -00 to -01. 150 o Forgot to change Informational to Std. 152 Authors' Addresses 154 Warren Kumari 155 Google 156 1600 Amphitheatre Parkway 157 Mountain View, CA 94043 158 US 160 Email: warren@kumari.net 162 Randy Bush 163 Internet Initiative Japan 164 5147 Crystal Springs 165 Bainbridge Island, WA 98110 166 US 168 Email: randy@psg.com 170 Heather Schiller 171 Verizon 172 22001 Loudoun County Parkway 173 Ashburn 20147 174 US 176 Email: heather.schiller@verizon.com