[Idr] I-D Action: draft-ietf-idr-bgp-attribute-announcement-01.txt

internet-drafts@ietf.org Fri, 19 May 2017 15:40 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: idr@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149520844486.30807.5431009493565553853@ietfa.amsl.com>
Date: Fri, 19 May 2017 08:40:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_or8qdmvw1LdAr8TtRRt_0TZbbE>
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-attribute-announcement-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing of the IETF.

        Title           : Constrain Attribute announcement within BGP
        Authors         : Keyur Patel
                          James Uttaro
                          Bruno Decraene
                          Wim Henderickx
                          Jeff Haas
	Filename        : draft-ietf-idr-bgp-attribute-announcement-01.txt
	Pages           : 9
	Date            : 2017-05-18

Abstract:
   [RFC4271] defines four different categories of BGP Path attributes.
   The different Path attribute categories can be identified by the
   attribute flag values.  These flags help identify if an attribute is
   optional or well-known, Transitive or non-Transitive, Partial, or of
   an Extended length type.  BGP attribute announcement depends on
   whether an attribute is a well-known or optional, and whether an
   attribute is a transitive or non-transitive.  BGP implementations
   MUST recognize all well-known attributes.  The well-known attributes
   are always Transitive.  It is not required for BGP implementations to
   recognise all the Optional attributes.  The Optional attributes could
   be Transitive or Non-Transitive.  BGP implementations MUST store and
   forward any Unknown Optional Transitive attributes and ignore and
   drop any Unknown Optional Non-Transitive attributes.

   Currently, there is no way to confine the scope of Path attributes
   within a given Autonomous System (AS) or a given BGP member-AS in
   Confederation.  This draft defines attribute extensions that help
   confine the scope of Optional attributes within a given AS or a given
   BGP member-AS in Confederation


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-attribute-announcement/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-idr-bgp-attribute-announcement-01
https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-attribute-announcement-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-attribute-announcement-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[Idr] I-D Action: draft-ietf-idr-bgp-attribute-an… internet-drafts