BGP Extended Community for Identifying the Target Node
draft-dong-idr-node-target-ext-comm-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jie Dong , Shunwan Zhuang , Gunter Van de Velde | ||
| Last updated | 2020-09-10 (Latest revision 2020-03-09) | ||
| Replaced by | draft-ietf-idr-node-target-ext-comm | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 [RFC4271] has been used to distribute different types of routing and policy information in the network. In some cases, the information distributed may be only intended for one or several particular receiving BGP nodes in the network. However, BGP does not have a general mechanism of designating the receiving node of the routing information. This document defines a new type of BGP Extended Community called "Node Target". The mechanism of using the Node Target Extended Community to steer BGP route distribution to particular BGP nodes is specified.
Authors
Jie Dong
Shunwan Zhuang
Gunter Van de Velde
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)