RFC 4652 on Evaluation of Existing Routing Protocols against Automatic Switched Optical Network (ASON) Routing Requirements

[rfc-editor@rfc-editor.org]

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

        
        RFC 4652

        Title:      Evaluation of Existing Routing Protocols 
                    against Automatic Switched Optical Network (ASON) 
                    Routing Requirements 
        Author:     D. Papadimitriou, Ed.,
                    L.Ong, J. Sadler,
                    S. Shew, D. Ward
        Status:     Informational
        Date:       October 2006
        Mailbox:    dimitri.papadimitriou@alcatel.be, 
                    lyong@ciena.com, 
                    jonathan.sadler@tellabs.com, sdshew@nortel.com, 
                    dward@cisco.com
        Pages:      22
        Characters: 47179
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-gmpls-ason-routing-eval-03.txt

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

The Generalized MPLS (GMPLS) suite of protocols has been defined to
control different switching technologies as well as different
applications.  These include support for requesting TDM connections
including Synchronous Optical Network/Synchronous Digital Hierarchy
(SONET/SDH) and Optical Transport Networks (OTNs).

This document provides an evaluation of the IETF Routing Protocols
against the routing requirements for an Automatically Switched
Optical Network (ASON) as defined by ITU-T.  This memo provides 
information for the Internet community.

This document is a product of the Common Control and Measurement Plane
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

help: ways_to_get_rfcs. For example:

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...