RFC 4328: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control
In plain English — editorial summary, not part of the RFC
This document is a companion to the Generalized Multi-Protocol Label Switching (GMPLS) signaling documents. It describes the technology-specific information needed to extend GMPLS signaling to control Optical Transport Networks (OTN); it also includes the so-called pre-OTN developments. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4328
- Published
- January 2006
- Authors
- D. Papadimitriou
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
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 4652Evaluation of Existing Routing Protocols against Automatic Switched Optical Network (ASON) Routing RequirementsCurrent
October 2006
- RFC 7709Requirements for Very Fast Setup of GMPLS Label Switched Paths (LSPs)Current
November 2015
- RFC 4394A Transport Network View of the Link Management Protocol (LMP)Current
February 2006
- RFC 4139Requirements for Generalized MPLS (GMPLS) Signaling Usage and Extensions for Automatically Switched Optical Network (ASON)Current
July 2005
- RFC 7096Evaluation of Existing GMPLS Encoding against G.709v3 Optical Transport Networks (OTNs)Current
January 2014
- RFC 7138Traffic Engineering Extensions to OSPF for GMPLS Control of Evolving G.709 Optical Transport NetworksCurrent
March 2014
- RFC 3591Definitions of Managed Objects for the Optical Interface TypeCurrent
September 2003
- RFC 4327Link Management Protocol (LMP) Management Information Base (MIB)Obsoleted
January 2006
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?