Multi-Topology/Multi-Instance ISIS for IPv4-Embedded IPv6
draft-boucadair-isis-v4v6-mt-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mohamed Boucadair , Christian Jacquenet , Dean Cheng , Yiu Lee | ||
Last updated | 2010-02-23 | ||
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 document defines two new Multi Topology Routing Identifiers (MT IDs), based on [RFC5120] and two new Instance Identifiers (MI IDs), based on [I-D.ietf-isis-mi], respectively, in the Intermediate System to Intermediate System. 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
Christian Jacquenet
Dean Cheng
Yiu Lee
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)