@techreport{boucadair-isis-v4v6-mi-01,
    number =    {draft-boucadair-isis-v4v6-mi-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-boucadair-isis-v4v6-mi/01/},
    author =    {Mohamed Boucadair and Christian Jacquenet and Dean Cheng and Yiu Lee},
    title =     {{IPv4-mapped IPv6 Instance IDs in IS-IS}},
    pagetotal = 7,
    year =      2009,
    month =     oct,
    day =       20,
    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.},
}