RFC 4426: Generalized Multi-Protocol Label Switching (GMPLS) Recovery Functional Specification
In plain English — editorial summary, not part of the RFC
This document presents a functional description of the protocol extensions needed to support Generalized Multi-Protocol Label Switching (GMPLS)-based recovery (i.e., protection and restoration). Protocol specific formats and mechanisms will be described in companion documents. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4426
- Published
- March 2006
- Authors
- J. Lang; B. Rajagopalan; D. Papadimitriou
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4427Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)Current
March 2006
- RFC 4428Analysis of Generalized Multi-Protocol Label Switching (GMPLS)-based Recovery Mechanisms (including Protection and Restoration)Current
March 2006
- RFC 4420Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)Obsoleted
February 2006
- RFC 4444Management Information Base for Intermediate System to Intermediate System (IS-IS)Current
April 2006
- RFC 4446IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)Current
April 2006
- RFC 4447Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)Obsoleted
April 2006
- RFC 4448Encapsulation Methods for Transport of Ethernet over MPLS NetworksUpdated
April 2006
- RFC 4454Asynchronous Transfer Mode (ATM) over Layer 2 Tunneling Protocol Version 3 (L2TPv3)Updated
May 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?