RFC 4783: GMPLS - Communication of Alarm Information
In plain English — editorial summary, not part of the RFC
This document describes an extension to Generalized MPLS (Multi-Protocol Label Switching) signaling to support communication of alarm information. GMPLS signaling already supports the control of alarm reporting, but not the communication of alarm information. This document presents both a functional description and GMPLS-RSVP specifics of such an extension. This document also proposes modification of the RSVP ERROR_SPEC object. This document updates RFC 3473, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", through the addition of new, optional protocol elements. It does not change, and is fully backward compatible with, the procedures specified in RFC 3473. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4783
- Published
- December 2006
- Authors
- L. Berger
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
- Updates:
- RFC 3473
Topics
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 4920Crankback Signaling Extensions for MPLS and GMPLS RSVP-TECurrent
July 2007
- RFC 5253Applicability Statement for Layer 1 Virtual Private Network (L1VPN) Basic ModeCurrent
July 2008
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 7709Requirements for Very Fast Setup of GMPLS Label Switched Paths (LSPs)Current
November 2015
- RFC 4781Graceful Restart Mechanism for BGP with MPLSCurrent
January 2007
- RFC 4797Use of Provider Edge to Provider Edge (PE-PE) Generic Routing Encapsulation (GRE) or IP in BGP/MPLS IP Virtual Private NetworksCurrent
January 2007
- RFC 4798Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)Current
February 2007
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?