IPv4-mapped IPv6 Instance IDs in OSPFv3
draft-boucadair-ospf-v4v6-ospfv3-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 OSPFv3 [RFC2740]). These new Instance IDs [I-D.ietf-ospf-af-alt] are meant to instantiate distinct OSPFv3 instances to convey routing information which is specific to IPv4-mapped IPv6 address Address Family [I-D.ietf-behave-address-format]. The goal of running separate instances for IPv4-mapped IPv6 is to distinguish the native IPv6 routing topology from the IPv4 routing topology. Separate instances are also meant to prevent any overload of the native IPv6 routing tables by IPv4-mapped IPv6 routes. This isolation is motivated also from an operational perspective to enforce 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.)