RFC 3946: Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4606.
In plain English — editorial summary, not part of the RFC
This document is a companion to the Generalized Multi-Protocol Label Switching (GMPLS) signaling. It defines the Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) technology specific information needed when using GMPLS signaling. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3946
- Published
- November 2004
- Authors
- E. Mannie; D. Papadimitriou
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
- Obsoleted by:
- RFC 4606
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 3945Generalized Multi-Protocol Label Switching (GMPLS) ArchitectureUpdated
November 2004
- RFC 3931Layer Two Tunneling Protocol - Version 3 (L2TPv3)Updated
March 2005
- RFC 3973Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)Updated
January 2005
- RFC 3916Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)Current
October 2004
- RFC 3913Border Gateway Multicast Protocol (BGMP): Protocol SpecificationCurrent
September 2004
- RFC 3985Pseudo Wire Emulation Edge-to-Edge (PWE3) ArchitectureUpdated
March 2005
- RFC 3906Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering TunnelsCurrent
October 2004
- RFC 3988Maximum Transmission Unit Signalling Extensions for the Label Distribution ProtocolCurrent
February 2005
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?