IPv4-mapped IPv6 Instance IDs in IS-IS
draft-boucadair-isis-v4v6-mi-01

Document Type Expired Internet-Draft (individual)
Authors Mohamed Boucadair  , Christian Jacquenet  , Dean Cheng  , Yiu Lee 
Last updated 2009-10-20 (latest revision 2009-10-19)
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-isis-v4v6-mi-01.txt

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 (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.)