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

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2012-05-07
Replaces draft-wkumari-idr-as0
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
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
                                                                 Verizon
                                                                K. Patel
                                                           Cisco Systems
                                                             May 7, 2012

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

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.

   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.

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
   include Simplified BSD License text as described in Section 4.e of

Kumari, et al.          Expires November 8, 2012                [Page 1]
Internet-Draft               as0-processing                     May 2012

   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 November 8, 2012                [Page 2]
Internet-Draft               as0-processing                     May 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 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.

   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].

2.  Behavior

   A BGP speaker MUST NOT originate or propagate a route with an AS
   number of zero in the AS_PATH, AS4_PATH, AGGREGATOR or AS4_AGGREGATOR
   attributes.

   An UPDATE message that contains the AS number of zero in the AS_PATH
   or AGGREGATOR attribute MUST be considered as malformed, and be
   handled by the procedures specified in [I-D.ietf-idr-error-handling].

   An UPDATE message that contains the AS number of zero in the AS4_PATH
Show full document text