Registered Wide BGP Community Values
draft-ietf-idr-registered-wide-bgp-communities-02
| Document | Type |
Expired Internet-Draft
(idr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Robert Raszuk , Jeffrey Haas | ||
| Last updated | 2016-12-02 (Latest revision 2016-05-31) | ||
| Replaces | draft-raszuk-registered-wide-bgp-communities | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Communicating various routing policies via route tagging plays an important role in external BGP peering relations. The most common tool used today to attach various information about routes is realized with the use of BGP communities. Such information is important for the peering AS to perform some mutually agreed actions without the need to maintain a separate offline database for each pair of prefix and an associated with it requested set of action entries. This document proposes to establish a new IANA maintained registry of most commonly used Wide BGP Communities by network operators. Such public registry will allow for easy refernece and clear interpretation of the actions associated with received community values.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)