IPv4-mapped IPv6 Instance IDs in IS-IS
draft-boucadair-isis-v4v6-mi-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohamed Boucadair , Christian Jacquenet , Dean Cheng , Yiu Lee | ||
| Last updated | 2009-10-20 | ||
| 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
This memo defines two new Instance Identifiers (Instance IDs) in IS-IS [RFC1195]). These new Instance IDs [I-D.ietf-isis-mi] are meant to instantiate distinct IS-IS instances to convey routing information which is restricted to IPv4-mapped IPv6 addresses [I-D.ietf-behave-address-format]. The ultimate goal of running separate instances for IPv4-mapped IPv6 routes is to isolate the IPv6 routing table from the IPv4 routing table, and to avoid any overload due to the population of the table by IPv4-mapped IPv6 routes. This isolation is motivated also from an operational perspective to allow the enforcement of specific routing policies for each topology.
Authors
Mohamed Boucadair
Christian Jacquenet
Dean Cheng
Yiu Lee
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)