An Application of the BGP Community Attribute in Multi-home Routing
draft-ietf-idr-community-00
Document | Type |
Expired Internet-Draft
(idr WG)
Expired & archived
|
|
---|---|---|---|
Authors | Enke Chen , Tony J. Bates | ||
Last updated | 2024-08-23 (Latest revision 1996-03-13) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Dead 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
This document presents an application of the BGP community attribute [2] in simplifying the implementation and configuration of routing policies in the multi-provider Internet. It shows how the community based configuration can be used to replace the AS-based customization of the BGP 'LOCAL_PREF' attribute, a common method used today. Not only does the technique presented simplifies configuration and management at the provider level, it also represents a paradigm shift in that it gives the potential for the customer to control its own routing policy with respect to its service provider, as well as providing the ability for policy configuration to be done at a prefix based granularity rather than the more common AS based granularity.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)