<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-isis-wg-multi-topology" target="https://datatracker.ietf.org/doc/html/draft-ietf-isis-wg-multi-topology-12">
   <front>
      <title>M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)</title>
      <author initials="N." surname="Shen" fullname="Naiming Shen">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="N." surname="Sheth" fullname="Nischal Sheth">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="T." surname="Przygienda" fullname="Tony Przygienda">
         <organization>Z2 Sagl</organization>
      </author>
      <date month="November" day="13" year="2007" />
      <abstract>
	 <t>This document describes an optional mechanism within Intermediate System to Intermediate Systems (IS-ISs) used today by many ISPs for IGP routing within their clouds.  This document describes how to run, within a single IS-IS domain, a set of independent IP topologies that we call Multi-Topologies (MTs).  This MT extension can be used for a variety of purposes, such as an in-band management network &quot;on top&quot; of the original IGP topology, maintaining separate IGP routing domains for isolated multicast or IPv6 islands within the backbone, or forcing a subset of an address space to follow a different topology. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-isis-wg-multi-topology-12" />
   
</reference>
