Controlling the redistribution of BGP routes
draft-ietf-grow-bgp-redistribution-00
| Document | Type | Expired Internet-Draft (grow WG) | |
|---|---|---|---|
| Last updated | 2003-06-02 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-grow-bgp-redistribution-00.txt
Abstract
This document proposes the redistribution extended community. This new extended community allows a router to influence how a specific route should be redistributed towards a specified set of eBGP speakers. Several types of redistribution communities are proposed. The first type may be used to indicate that a specific route should not be announced over a specified set of eBGP sessions. The second type may be used to indicate that the attached route should only be announced with the NO_EXPORT community over the specified set of eBGP sessions and the third type may be used to indicate that the attached route should be prepended n times when announced over a specified set of eBGP sessions.
Authors
Olivier Bonaventure (olivier.bonaventure@info.fundp.ac.be)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)