NOPEER community for BGP route scope control
draft-huston-nopeer-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Geoff Huston | ||
| Last updated | 2001-08-13 | ||
| 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
This document proposes the use of a scope control BGP community. This new well-known advisory transitive community is intended to allow an origin AS to specify the extent to which a specific route should be externally propagated. In particular this community, termed here as NOPEER, allows the origin AS to specify that a route with this attribute need not be advertised across bilateral peer connections.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)