[rfc-dist] RFC 4973 on OSPF-xTE: Experimental Extension to OSPF for Traffic Engineering
rfc-editor at rfc-editor.org
Tue Jul 31 18:08:40 PDT 2007
A new Request for Comments is now available in online RFC libraries.
Title: OSPF-xTE: Experimental Extension to OSPF
for Traffic Engineering
Author: P. Srisuresh, P. Joseph
Date: July 2007
Mailbox: srisuresh at yahoo.com,
paul_95014 at yahoo.com
I-D Tag: draft-srisuresh-ospf-te-07.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
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
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
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
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
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