<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='I-D.boucadair-ospf-v4v6-ospfv3-mt'>
<front>
<title>Multi-Topology/Multi-Instance OSPFv3 for IPv4-Embedded IPv6</title>

<author initials='M' surname='Boucadair' fullname='Mohammed Boucadair'>
    <organization />
</author>

<author initials='C' surname='Jacquenet' fullname='Christian Jacquenet'>
    <organization />
</author>

<author initials='D' surname='Cheng' fullname='Dean Cheng'>
    <organization />
</author>

<author initials='Y' surname='Lee' fullname='Yiu Lee'>
    <organization />
</author>

<date month='February' day='11' year='2010' />

<abstract><t>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.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-boucadair-ospf-v4v6-ospfv3-mt-02' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-boucadair-ospf-v4v6-ospfv3-mt-02.txt' />
</reference>

