[Idr] I-D Action: draft-ietf-idr-wide-bgp-communities-04.txt

internet-drafts@ietf.org Thu, 02 March 2017 13:47 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A2BC312998B; Thu, 2 Mar 2017 05:47:58 -0800 (PST)
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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148846247866.19611.17441167304517620418.idtracker@ietfa.amsl.com>
Date: Thu, 02 Mar 2017 05:47:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/tdfVPWvvXSBGnIrxdOwURwa3sr4>
Cc: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-wide-bgp-communities-04.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Mar 2017 13:47:59 -0000

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           : BGP Community Container Attribute
        Authors         : Robert Raszuk
                          Jeffrey Haas
                          Andrew Lange
                          Bruno Decraene
                          Shane Amante
                          Paul Jakma
	Filename        : draft-ietf-idr-wide-bgp-communities-04.txt
	Pages           : 25
	Date            : 2017-03-02

Abstract:
   Route tagging plays an important role in external BGP [RFC4271]
   relations, in communicating various routing policies between peers.
   It is also a very common best practice among operators to propagate
   various additional information about routes intra-domain.  The most
   common tool used today to attach various information about routes is
   through the use of BGP communities [RFC1997].

   This document defines a new encoding which will enhance and simplify
   what can be accomplished today with the use of BGP communities.  The
   most important addition this specification makes over currently
   defined BGP communities is the ability to specify, carry as well as
   use for execution an operator's defined set of parameters.  It also
   provides an extensible platform for any new community encoding needs
   in the future.



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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-wide-bgp-communities-04

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


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/