BGP Communities use for the prefix origination tagging
draft-teplov-grow-rfc4384-bis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Matvey Teplov | ||
| Last updated | 2008-06-17 | ||
| 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
BGP communities [RFC 1997] are 64-bit values that are used to tag the originated or traversing prefixes for the different purposes, such as origination tagging or policy application purposes. These values can be displayed in a new and old format, which notes different representation of the same 64-bit value. This document defines the way of tagging prefixes based upon their geographical origination to assist in development of geographically-based policies that, ideally, will result in RTD (Round Trip Delay) value improvements, as optimized paths can be established.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)