datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Codification of AS 0 processing.
draft-ietf-idr-as0-06

Document type: Active Internet-Draft (idr WG)
Document stream: IETF
Last updated: 2013-02-21 (latest revision 2012-08-26)
Intended RFC status: Proposed Standard
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: Susan Hares

IESG State: RFC Ed Queue
RFC Editor State: MISSREF
Responsible AD: Alia Atlas
IESG Note: John Scudder (jgs@juniper.net) is the Document Shepherd.
Send notices to: idr-chairs@tools.ietf.org, draft-ietf-idr-as0@tools.ietf.org

idr                                                            W. Kumari
Internet-Draft                                                    Google
Updates: 4271 (if approved)                                      R. Bush
Intended status: Standards Track               Internet Initiative Japan
Expires: February 27, 2013                                   H. Schiller
                                                                 Verizon
                                                                K. Patel
                                                           Cisco Systems
                                                         August 26, 2012

                    Codification of AS 0 processing.
                         draft-ietf-idr-as0-06

Abstract

   This document updates RFC 4271 and proscribes the use of Autonomous
   System (AS) 0 in the Border Gateway Protocol (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.

   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 February 27, 2013.

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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Kumari, et al.          Expires February 27, 2013               [Page 1]
Internet-Draft               as0-processing                  August 2012

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Requirements notation . . . . . . . . . . . . . . . . . . . 3
   2.  Behavior  . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 5
   Appendix A.  Changes / Author Notes.  . . . . . . . . . . . . . . . 5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6

Kumari, et al.          Expires February 27, 2013               [Page 2]
Internet-Draft               as0-processing                  August 2012

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 Route Origin Attestation
   (ROA) is used to mark a prefix and all its more specific prefixes as
   not to be used in a routing context.  This allows a resource holder
   to signal that a prefix (and the more specifics) should not be routed
   by publishing a ROA listing AS0 as the only origin.  To respond to
   this signal requres that BGP implementations do not accept or
   propagate routes containing AS0.

   No clear statement that AS 0 was proscribed could be found in any BGP
   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] Sections 6.2 and 6.3
   by specifying the behavior in the presence of AS0.

   At least two implementations discard routes containing AS 0, and this
   document codifies this behavior.

1.1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

[include full document text]