Providing Next External Hop Path Information to End Hosts
draft-jaufeerally-nexthop-path-info-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rayhaan Jaufeerally | ||
| Last updated | 2019-06-13 (Latest revision 2018-12-10) | ||
| 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
The aim of this document is to define an interface through which an Autonomous System (AS) can disseminate information about forwarding of packets to the next hop outside the AS, to devices within its network. This information can be used to make path aware routing decisions, either by being aware of the default route packets will take when traversing the AS, or by using other mechanisms to control the path packets which is out of the scope of this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)