Subject: [OSPF] RFC 4915 on Multi-Topology (MT) Routing in OSPF

From: [email-masked]
Date: Sat, 30 Jun 2007 14:38:00 -0700 (PDT)

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

        RFC 4915

        Title:      Multi-Topology (MT) Routing in OSPF 

        Author:     P. Psenak, S. Mirtorabi,

                    A. Roy, L. Nguyen,

                    P. Pillay-Esnault

        Status:     Standards Track

        Date:       June 2007

        Mailbox:    [email-masked], 

                    [email-masked], 

                    [email-masked],  [email-masked], 

                    [email-masked]

        Pages:      20

        Characters: 43115

        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-mt-08.txt

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

This document describes an extension to Open Shortest Path First

(OSPF) in order to define independent IP topologies called Multi-

Topologies (MTs).  The Multi-Topologies extension can be used for

computing different paths for unicast traffic, multicast traffic,

different classes of service based on flexible criteria, or an in-

band network management topology.

An optional extension to exclude selected links from the default

topology is also described.  [STANDARDS TRACK]

This document is a product of the Open Shortest Path First IGP

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 [email-masked].  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to [email-masked] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email-masked]

        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 [email-masked].  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.

Submissions for Requests for Comments should be sent to

[email-masked].  Please consult RFC 2223, Instructions to RFC

Authors, for further information.

The RFC Editor Team

USC/Information Sciences Institute

...

_______________________________________________
OSPF mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ospf