RFC 4003: GMPLS Signaling Procedure for Egress Control
In plain English — editorial summary, not part of the RFC
This document clarifies the procedures for the control of the label used on an output/downstream interface of the egress node of a Label Switched Path (LSP). This control is also known as "Egress Control". Support for Egress Control is implicit in Generalized Multi-Protocol Label Switching (GMPLS) Signaling. This document clarifies the specification of GMPLS Signaling and does not modify GMPLS signaling mechanisms and procedures. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4003
- Published
- February 2005
- Authors
- L. Berger
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 3473
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4090Fast Reroute Extensions to RSVP-TE for LSP TunnelsUpdated
May 2005
- RFC 5439An Analysis of Scaling Issues in MPLS-TE Core NetworksCurrent
February 2009
- RFC 3988Maximum Transmission Unit Signalling Extensions for the Label Distribution ProtocolCurrent
February 2005
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 4208Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay ModelCurrent
October 2005
- RFC 3784Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)Obsoleted
June 2004
- RFC 4687Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS NetworksCurrent
September 2006
- RFC 4726A Framework for Inter-Domain Multiprotocol Label Switching Traffic EngineeringCurrent
November 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?