RFC 5920: Security Framework for MPLS and GMPLS Networks
In plain English — editorial summary, not part of the RFC
This document provides a security framework for Multiprotocol Label Switching (MPLS) and Generalized Multiprotocol Label Switching (GMPLS) Networks. This document addresses the security aspects that are relevant in the context of MPLS and GMPLS. It describes the security threats, the related defensive techniques, and the mechanisms for detection and reporting. This document emphasizes RSVP-TE and LDP security considerations, as well as inter-AS and inter-provider security considerations for building and maintaining MPLS and GMPLS networks across different domains or different Service Providers. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5920
- Published
- July 2010
- Authors
- L. Fang
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 66
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5919Signaling LDP Label Advertisement CompletionCurrent
August 2010
- RFC 5921A Framework for MPLS in Transport NetworksUpdated
July 2010
- RFC 5918Label Distribution Protocol (LDP) 'Typed Wildcard' Forward Equivalence Class (FEC)Updated
August 2010
- RFC 5950Network Management Framework for MPLS-based Transport NetworksCurrent
September 2010
- RFC 5951Network Management Requirements for MPLS-based Transport NetworksCurrent
September 2010
- RFC 5886A Set of Monitoring Tools for Path Computation Element (PCE)-Based ArchitectureCurrent
June 2010
- RFC 5885Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)Updated
June 2010
- RFC 5884Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)Updated
June 2010
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?