Flexible BGP Communities
draft-lange-flexible-bgp-communities-03

Document Type Expired Internet-Draft (individual)
Last updated 2010-08-02
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-lange-flexible-bgp-communities-03.txt

Abstract

This document defines a new attribute for BGP called the Flexible Community attribute. Flexible Communities build on the experience and utility of the standard BGP community, and the extended BGP community attributes. This attribute allows operators to associate structured information with a route or set of routes. This information can be then be used to execute routing policy. An enhanced version of communities is necessary to accommodate IPv6, 4-byte ASN's, and introduce a more extensible and flexible policy expression. This document also introduces the concept of Neighbor Classes. A Neighbor Class is applied to a group of BGP neighbors who share certain attributes. For example, the PEER Neighbor Class could be applied to BGP sessions between ASN X and other networks with which ASN X has a non-transit peering relationship.

Authors

Andrew Lange (andrew.lange@alcatel-lucent.com)
Jeffrey Haas (jhaas@pfrc.org)
Keyur Patel (keyupate@cisco.com)
Shane Amante (shane@castlepoint.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)