A survey of the utilization of the BGP community attribute
draft-quoitin-bgp-comm-survey-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bruno Quoitin , Olivier Bonaventure | ||
| Last updated | 2002-03-21 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
In this document, we describe the two most common utilizations of the BGP community attribute, namely to tag routes and indicate how a route should be redistributed by external peers. We then discuss how often these two types of community attribute are used on the basis of the RIPE whois database and of BGP table dumps.
Authors
Bruno Quoitin
Olivier Bonaventure
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)