Multi-Topology/Multi-Instance OSPFv3 for IPv4-Embedded IPv6
draft-boucadair-ospf-v4v6-ospfv3-mt-02

Document Type Expired Internet-Draft (individual)
Authors Mohamed Boucadair  , Christian Jacquenet  , Dean Cheng  , Yiu Lee 
Last updated 2010-02-11 (latest revision 2009-10-20)
Stream (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-boucadair-ospf-v4v6-ospfv3-mt-02.txt

Abstract

This memo defines two new Multi Topology Routing Identifiers (MT IDs), based on [I-D.ietf-ospf-mt-ospfv3] and two new Instance Identifiers (MI IDs), based on [I-D.ietf-ospf-af-alt], respectively, in OSPFv3. With these identifiers, an IPv4-Embedded IPv6 topology is maintained for both IPv6 unicast and multicast traffic. The purpose of running separate instances or topologies for IPv4- Embedded IPv6 traffic is to distinguish from the native IPv6 routing topology, and the topology that is used for routing IPv4-Embedded IPv6 datagrams only. Separate instances/topologies are also meant to prevent any overload of the native IPv6 routing tables by IPv4-Embedded IPv6 routes.

Authors

Mohamed Boucadair (mohamed.boucadair@orange-ftgroup.com)
Christian Jacquenet (christian.jacquenet@orange-ftgroup.com)
Dean Cheng (Chengd@huawei.com)
Yiu Lee (yiu_lee@cable.comcast.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)