RFC 4652: Evaluation of Existing Routing Protocols against Automatic Switched Optical Network (ASON) Routing Requirements
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC4652
- Published
- October 2006
- Authors
- D. Papadimitriou; L. Ong; J. Sadler; S. Shew; D. Ward
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4394A Transport Network View of the Link Management Protocol (LMP)Current
February 2006
- RFC 4197Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching NetworksCurrent
October 2005
- RFC 3592Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface TypeCurrent
September 2003
- RFC 2823PPP over Simple Data Link (SDL) using SONET/SDH with ATM-like framingCurrent
May 2000
- RFC 4204Link Management Protocol (LMP)Updated
October 2005
- RFC 3473Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) ExtensionsUpdated
February 2003
- RFC 3472Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) ExtensionsUpdated
February 2003
- RFC 3471Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional DescriptionUpdated
February 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?