draft-ietf-idr-as0-00.txt   draft-ietf-idr-as0-01.txt 
idr W. Kumari idr W. Kumari
Internet-Draft Google Internet-Draft Google
Intended status: Standards Track R. Bush Intended status: Standards Track R. Bush
Expires: June 1, 2012 Internet Initiative Japan Expires: June 18, 2012 Internet Initiative Japan
H. Schiller H. Schiller
Verizon Verizon
November 29, 2011 December 16, 2011
Codification of AS 0 processing. Codification of AS 0 processing.
draft-ietf-idr-as0-00 draft-ietf-idr-as0-01
Abstract Abstract
This document proscribes the use of AS 0 in BGP OPEN and AS_PATH / This document proscribes the use of AS 0 in BGP OPEN and AS_PATH /
AS4_PATH BGP attribute. AS4_PATH BGP attribute.
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.
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 1, 2012. This Internet-Draft will expire on June 18, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 11 skipping to change at page 2, line 11
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements notation . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements notation . . . . . . . . . . . . . . . . . . . 3
2. Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . . 4 6.2. Informative References . . . . . . . . . . . . . . . . . . 4
Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . . 4 Appendix A. Changes / Author Notes. . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
Autonomous System 0 is listed in the IANA Autonomous System Number Autonomous System 0 is listed in the IANA Autonomous System Number
Registry as "Reserved - May be use to identify non-routed networks" Registry as "Reserved - May be use to identify non-routed networks"
([IANA.AS_Numbers]). ([IANA.AS_Numbers]).
[I-D.ietf-sidr-iana-objects] specifies that AS number zero in a ROA [I-D.ietf-sidr-iana-objects] specifies that AS number zero in a ROA
is used to mark an NLRI which is to be marked as Invalid. is used to mark an NLRI which is to be marked as Invalid.
skipping to change at page 3, line 29 skipping to change at page 3, line 29
behavior. behavior.
1.1. Requirements notation 1.1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Behavior 2. Behavior
This document specifies that a BGP speaker MUST NOT originate or A BGP speaker MUST NOT originate or propagate a route with an AS
propagate a route with an AS number of zero. If a BGP speaker number of zero.
receives a route which has an AS number of zero in the AS_PATH (or
AS4_PATH) attribute, it SHOULD be logged and treated as a WITHDRAW.
This same behavior applies to routes containing zero as the
Aggregator or AS4 Aggregator.
In addition if a BGP speaker receives zero as the peer AS in an OPEN An UPDATE message that contains the AS number of zero in the AS_PATH,
message, it MUST abort the connection and send a NOTIFICATION with AS4_PATH, AGGREGATOR or AS4_AGGREGATOR attribute MUST be considered
Error Code "OPEN Message Error" and subcode "Bad Peer AS" (see as malformed, and be handled by the procedures specified in
[RFC4271] Section 6.2). Obviously enough, a router MUST NOT initiate [I-D.ietf-idr-error-handling].
a connection claiming to be AS number zero.
If a BGP speaker receives zero as the peer AS in an OPEN message, it
MUST abort the connection and send a NOTIFICATION with Error Code
"OPEN Message Error" and subcode "Bad Peer AS" (see [RFC4271] Section
6.2). A router MUST NOT initiate a connection claiming to be AS
number zero.
3. IANA Considerations 3. IANA Considerations
The IANA is requested to update the Reference for number 0 in the The IANA is requested to update the Reference for number 0 in the
"Autonomous System (AS) Numbers" registry to reference this document. "Autonomous System (AS) Numbers" registry to reference this document.
4. Security Considerations 4. Security Considerations
By allowing resource holders to say that AS 0 is the only valid By allowing resource holders to say that AS 0 is the only valid
origin for a route, we allow them to state that a particular address origin for a route, we allow them to state that a particular address
skipping to change at page 4, line 17 skipping to change at page 4, line 21
from announcing routes containing AS 0 in an attempt to hijack those from announcing routes containing AS 0 in an attempt to hijack those
resources. resources.
In addition, by standardizing the behavior upon reception of an In addition, by standardizing the behavior upon reception of an
AS_PATH (or AS4_PATH) containing AS 0, this document makes the AS_PATH (or AS4_PATH) containing AS 0, this document makes the
behavior better defined, and security gotchas often lurk in the behavior better defined, and security gotchas often lurk in the
undefined spaces. undefined spaces.
5. Acknowledgements 5. Acknowledgements
The authors wish to thank Enke Chen, Robert Raszuk, Danny McPherson, The authors wish to thank Enke Chen, Brian Dickson, Bruno Decraene,
Keyur Patel, John Scudder. Apologies to those we may have missed, it Robert Raszuk, Jakob Heitz, Danny McPherson, Chris Morrow, iLya,
was not intentional. Keyur Patel, John Scudder, Jeff Tantsura, Daniel Ginsburg and Susan
Hares. Apologies to those we may have missed, it was not
intentional.
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-idr-error-handling]
Scudder, J., Chen, E., Mohapatra, P., and K. Patel,
"Revised Error Handling for BGP UPDATE Messages",
draft-ietf-idr-error-handling-00 (work in progress),
November 2011.
[IANA.AS_Numbers] [IANA.AS_Numbers]
IANA, "Autonomous System (AS) Numbers", IANA, "Autonomous System (AS) Numbers",
<http://www.iana.org/assignments/as-numbers>. <http://www.iana.org/assignments/as-numbers>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. 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.
skipping to change at page 5, line 18 skipping to change at page 5, line 27
o Change "bgp listener" to "bgp speaker" -- Enke Chen o Change "bgp listener" to "bgp speaker" -- Enke Chen
o Consistent use of AS_PATH (v., AS-PATH and AS PATH) -- Danny o Consistent use of AS_PATH (v., AS-PATH and AS PATH) -- Danny
McPherson McPherson
o New text for Sec 2 P1 -- Enke / Keyur / Scudder, o New text for Sec 2 P1 -- Enke / Keyur / Scudder,
http://www.ietf.org/mail-archive/web/idr/current/msg05786.html http://www.ietf.org/mail-archive/web/idr/current/msg05786.html
o I made a boo boo -- I had the file open in 2 editors, made changes o I made a boo boo -- I had the file open in 2 editors, made changes
in one and overwrote them by saving on the other, then checked the in one and overwrote them by saving on the other, then checked the
broken one into SVN. Apologies to all whose comments I may have broken one into SVN. Apologies to all whose comments I may have
missed... missed...
Changes -01
o The WG thread
http://www.ietf.org/mail-archive/web/idr/current/msg05685.html
showed a very strong preference for separating the error
definition and handling -- the chairs also showed a prefernce to
Publish this and point to the error handling that Enke will write.
o The originally suggested text ("An UPDATE message that contains
the AS number of zero in the AS-PATH attribute MUST be...") only
referenced the AS-PATH, readded AS4_PATH, *AGGREGATOR as suggested
by Robert Raszak and Danny.
Authors' Addresses Authors' Addresses
Warren Kumari Warren Kumari
Google Google
1600 Amphitheatre Parkway 1600 Amphitheatre Parkway
Mountain View, CA 94043 Mountain View, CA 94043
US US
Email: warren@kumari.net Email: warren@kumari.net
Randy Bush Randy Bush
Internet Initiative Japan Internet Initiative Japan
5147 Crystal Springs 5147 Crystal Springs
Bainbridge Island, WA 98110 Bainbridge Island, WA 98110
US US
Email: randy@psg.com Email: randy@psg.com
Heather Schiller Heather Schiller
Verizon Verizon
 End of changes. 12 change blocks. 
21 lines changed or deleted 41 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/