IPv6 Source/Destination Routing using IS-IS
draft-baker-ipv6-isis-dst-src-routing-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Baker | ||
| Last updated | 2013-08-21 (Latest revision 2013-02-17) | ||
| Replaced by | draft-ietf-isis-ipv6-dst-src-routing | ||
| RFC stream | (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 note describes the changes necessary for IS-IS to route classes of IPv6 traffic that are defined by a source prefix and a destination prefix. This implies not routing "to a destination", but "traffic matching a classification tuple". The obvious application is egress routing - routing traffic using a given prefix to an upstream network that will not drop traffic using that prefix using BCP 38 filters.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)