Subject: RFC 4973 on OSPF-xTE: Experimental Extension to OSPF for Traffic Engineering

From: [email-masked]
Date: Tue, 31 Jul 2007 18:08:40 -0700 (PDT)

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

        RFC 4973

        Title:      OSPF-xTE: Experimental Extension to OSPF 

                    for Traffic Engineering 

        Author:     P. Srisuresh, P. Joseph

        Status:     Experimental

        Date:       July 2007

        Mailbox:    [email-masked], 

                    [email-masked]

        Pages:      50

        Characters: 115361

        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-srisuresh-ospf-te-07.txt

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

This document defines OSPF-xTE, an experimental traffic engineering

(TE) extension to the link-state routing protocol OSPF.  OSPF-xTE

defines new TE Link State Advertisements (LSAs) to disseminate TE

metrics within an autonomous System (AS), which may consist of multiple

areas.  When an AS consists of TE and non-TE nodes, OSPF-xTE ensures

that non-TE nodes in the AS are unaffected by the TE LSAs.  OSPF-xTE

generates a stand-alone TE Link State Database (TE-LSDB), distinct from

the native OSPF LSDB, for computation of TE circuit paths.  OSPF-xTE is

versatile and extendible to non-packet networks such as Synchronous

Optical Network (SONET) / Time Division Multiplexing (TDM) and

optical networks.  This memo defines an Experimental Protocol for the Internet community.

EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community.

It does not specify an Internet standard of any kind.  Discussion and

suggestions for improvement are requested.  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

...

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce