Wide BGP Communities update (-04) - input solicited

Jeffrey Haas jhaas at pfrc.org
Thu Feb 13 21:29:17 UTC 2014

The authors of the Wide BGP Communities Internet-draft would like to solicit
your feedback on the current version of the draft.  The intended purpose of
the feature is to provide for next-generation BGP communities.

Why "next-generation"?  A few motivations:
- BGP Path Attribute code space is limited.  We want to stop burning new
  code points for such features when the underlying "mark a route" behavior
  is the same.
- Each time we add something with new encoding, we get deployment lag from
  needing new code to handle it.
- While it's done the job for a number of years, existing communities force
  operators to go through a lot of convoluted policy to do anything from
  very common things to subtle things.

The accompanying use case document will be updated soon, but not prior to
the upcoming IETF.  Most of our attention the last few weeks has been on
getting the details of the encoding right.

In recognition to a very common use case desired here, note Section 5.  A
wide community is being registered with no further semantics than "here's a
list of AS numbers".  This permits the desired AS4:AS4 semantic.

-- Jeff

----- Forwarded message from internet-drafts at ietf.org -----

Date: Thu, 13 Feb 2014 12:55:54 -0800
From: internet-drafts at ietf.org
To: i-d-announce at ietf.org
Subject: I-D Action: draft-raszuk-wide-bgp-communities-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

        Title           : Wide BGP Communities Attribute
        Authors         : Robert Raszuk
                          Jeffrey Haas
                          Andrew Lange
                          Shane Amante
                          Bruno Decraene
                          Paul Jakma
                          Richard A Steenbergen
	Filename        : draft-raszuk-wide-bgp-communities-04.txt
	Pages           : 24
	Date            : 2014-02-13

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

   Such information is important to allow BGP speakers to perform some
   mutually agreed actions without the need to maintain a separate
   offline database for each tuple of prefix and associated set of
   action entries.

   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:

There's also a htmlized version available at:

A diff from the previous version is available at:

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:

I-D-Announce mailing list
I-D-Announce at ietf.org
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

----- End forwarded message -----

More information about the NANOG mailing list