Border Gateway Protocol NEXT-HOP-SNPA Attribute
draft-ietf-bgp-nexthop-01
| Document | Type |
Expired Internet-Draft
(idr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | |||
| Last updated | 2024-08-23 (Latest revision 1991-10-24) | ||
| 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
The purpose of the NEXT-HOP attribute is for one border gateway A to tell another border gateway B which border gateway C (where C might equal A) should be used as the next hop on the path to the destinations advertised in the UPDATE containing the NEXT-HOP attribute.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)