draft-ietf-idr-as0-04.txt   draft-ietf-idr-as0-05.txt 
idr W. Kumari idr W. Kumari
Internet-Draft Google Internet-Draft Google
Updates: 4271 (if approved) R. Bush Updates: 4271 (if approved) R. Bush
Intended status: Standards Track Internet Initiative Japan Intended status: Standards Track Internet Initiative Japan
Expires: November 8, 2012 H. Schiller Expires: November 23, 2012 H. Schiller
Verizon Verizon
K. Patel K. Patel
Cisco Systems Cisco Systems
May 7, 2012 May 22, 2012
Codification of AS 0 processing. Codification of AS 0 processing.
draft-ietf-idr-as0-04 draft-ietf-idr-as0-05
Abstract Abstract
This document updates RFC 4271 and proscribes the use of AS 0 in BGP This document updates RFC 4271 and proscribes the use of AS 0 in BGP
OPEN and AS_PATH / AS4_PATH BGP attribute. OPEN and AS_PATH / 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 36 skipping to change at page 1, line 36
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 November 8, 2012. This Internet-Draft will expire on November 23, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 3, line 15 skipping to change at page 3, line 15
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]).
[RFC6491] specifies that AS number zero in a ROA is used to mark an [RFC6491] specifies that AS number zero in a ROA is used to mark an
NLRI which is to be marked as Invalid. NLRI which is to be marked as Invalid.
No clear statement that AS 0 was proscribed could be found in any BGP No clear statement that AS 0 was proscribed could be found in any BGP
specification. specification. This document corrects this omission, most
importantly in the case of the AS_PATH. This represents an update to
the error handling procedures given in [RFC4271].
As at least two implementations discard routes containing AS 0, and As at least two implementations discard routes containing AS 0, and
to allow approaches such as the above, this document codifies this to allow approaches such as the above, this document codifies this
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].
skipping to change at page 6, line 26 skipping to change at page 6, line 29
o Looks like the draft needs an 'Updates: RFC 4271' header. Can you o Looks like the draft needs an 'Updates: RFC 4271' header. Can you
make the change? -- JGS. make the change? -- JGS.
o "You have things a bit scrambled in these two paragraphs" -- JGS o "You have things a bit scrambled in these two paragraphs" -- JGS
(whoops!). (whoops!).
o Editorial: I suggest dropping the parentheses in... JGS. o Editorial: I suggest dropping the parentheses in... JGS.
o Added "This document updates rfc 4271" to keep IDNITs happy... o Added "This document updates rfc 4271" to keep IDNITs happy...
o Bumped refs: draft-ietf-sidr-iana-objects has been published as o Bumped refs: draft-ietf-sidr-iana-objects has been published as
RFC 6491, idr-error is now -01, 4893bis is now -06 RFC 6491, idr-error is now -01, 4893bis is now -06
Changes - 05
o Added something to the intro saying what we update and why. This
was in the abstract, but I didn't have it in the intro. Stupid.
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
22001 Loudoun County Parkway 22001 Loudoun County Parkway
Ashburn 20147 Ashburn 20147
US US
Email: heather.schiller@verizon.com Email: heather.schiller@verizon.com
Keyur Patel Keyur Patel
Cisco Systems Cisco Systems
 End of changes. 8 change blocks. 
6 lines changed or deleted 13 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/