[rfc-dist] RFC 5120 on M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Feb 8 17:23:41 PST 2008

A new Request for Comments is now available in online RFC libraries.

        RFC 5120

        Title:      M-ISIS: Multi Topology (MT) Routing 
                    in Intermediate System to Intermediate Systems 
        Author:     T. Przygienda, N. Shen,
                    N. Sheth
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    prz at net4u.ch, 
                    naiming at cisco.com, 
                    nsheth at juniper.net
        Pages:      14
        Characters: 30318
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-wg-multi-topology-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5120.txt

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 "on top" 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]

This document is a product of the IS-IS for IP Internets
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.Please refer to the current edition of the Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list