Record NEXTHOP_PATH ATTIBUTE for BGP
draft-hares-idr-nexthop-path-record-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Susan Hares , Zhenbin Li , Li Zhang | ||
| Last updated | 2015-12-31 (Latest revision 2015-06-29) | ||
| 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
In some BGP deployments, BGP next hops may use a set or tunnels or run across converged networks such as seamless MPLS. This document describes a new optional transitive path attribute, NEXTHOP_PATH ATTRIBUTE for BGP that records the next hop path which can be used by BGP network management to monitor and manage the BGP infrastructure via management interfaces (such as I2RS).
Authors
Susan Hares
Zhenbin Li
Li Zhang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)