--- 1/draft-ietf-idr-as0-04.txt 2012-05-28 12:14:39.705427258 +0200 +++ 2/draft-ietf-idr-as0-05.txt 2012-05-28 12:14:39.717425568 +0200 @@ -1,23 +1,23 @@ idr W. Kumari Internet-Draft Google Updates: 4271 (if approved) R. Bush Intended status: Standards Track Internet Initiative Japan -Expires: November 8, 2012 H. Schiller +Expires: November 23, 2012 H. Schiller Verizon K. Patel Cisco Systems - May 7, 2012 + May 22, 2012 Codification of AS 0 processing. - draft-ietf-idr-as0-04 + draft-ietf-idr-as0-05 Abstract This document updates RFC 4271 and proscribes the use of AS 0 in BGP OPEN and AS_PATH / AS4_PATH BGP attribute. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -25,21 +25,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -66,21 +66,23 @@ 1. Introduction Autonomous System 0 is listed in the IANA Autonomous System Number Registry as "Reserved - May be use to identify non-routed networks" ([IANA.AS_Numbers]). [RFC6491] specifies that AS number zero in a ROA is used to mark an NLRI which is to be marked as Invalid. 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 to allow approaches such as the above, this document codifies this behavior. 1.1. Requirements notation The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. @@ -215,37 +218,42 @@ o Looks like the draft needs an 'Updates: RFC 4271' header. Can you make the change? -- JGS. o "You have things a bit scrambled in these two paragraphs" -- JGS (whoops!). o Editorial: I suggest dropping the parentheses in... JGS. o Added "This document updates rfc 4271" to keep IDNITs happy... o Bumped refs: draft-ietf-sidr-iana-objects has been published as 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 Warren Kumari Google 1600 Amphitheatre Parkway Mountain View, CA 94043 US Email: warren@kumari.net - Randy Bush Internet Initiative Japan 5147 Crystal Springs Bainbridge Island, WA 98110 US Email: randy@psg.com + Heather Schiller Verizon 22001 Loudoun County Parkway Ashburn 20147 US Email: heather.schiller@verizon.com Keyur Patel Cisco Systems