RFC 3475: Documentation of IANA assignments for Constraint-Based LSP setup using LDP (CR-LDP) Extensions for Automatic Switched Optical Network (ASON)
In plain English — editorial summary, not part of the RFC
Automatic Switched Optical Network (ASON) is an architecture, specified by ITU-T Study Group 15, for the introduction of a control plane for optical networks. The ASON architecture specifies a set of reference points that defines the relationship between the ASON architectural entities. Signaling over interfaces defined in those reference points can make use of protocols that are defined by the IETF in the context of Generalized Multi-Protocol Label Switching (GMPLS) work. This document describes Constraint-Based LSP setup using LDP (CR-LDP) extensions for signaling over the interfaces defined in the ASON reference points. The purpose of the document is to request that the IANA assigns code points necessary for the CR-LDP extensions. The protocol specifications for the use of the CR-LDP extensions are found in ITU-T documents. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3475
- Published
- April 2003
- Authors
- O. Aboul-Magd
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 13
- Also known as
- —
- Updated by:
- RFC 3468
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3591Definitions of Managed Objects for the Optical Interface TypeCurrent
September 2003
- RFC 3214LSP Modification Using CR-LDPCurrent
January 2002
- RFC 3047RTP Payload Format for ITU-T Recommendation G.722.1Obsoleted
January 2001
- RFC 4628RTP Payload Format for H.263 Moving RFC 2190 to Historic StatusCurrent
February 2007
- RFC 4652Evaluation of Existing Routing Protocols against Automatic Switched Optical Network (ASON) Routing RequirementsCurrent
October 2006
- RFC 4749RTP Payload Format for the G.729.1 Audio CodecUpdated
October 2006
- RFC 5317Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport ProfileCurrent
February 2009
- RFC 5404RTP Payload Format for G.719Current
January 2009
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?