RFC 7325: MPLS Forwarding Compliance and Performance Requirements
In plain English — editorial summary, not part of the RFC
This document provides guidelines for implementers regarding MPLS forwarding and a basis for evaluations of forwarding implementations. Guidelines cover many aspects of MPLS forwarding. Topics are highlighted where implementers might otherwise overlook practical requirements which are unstated or under emphasized or are optional for conformance to RFCs but are often considered mandatory by providers.
Document record
- Document ID
- RFC7325
- Published
- August 2014
- Authors
- C. Villamizar; K. Kompella; S. Amante; A. Malis; C. Pignataro
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 59
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7190Use of Multipath with MPLS and MPLS Transport Profile (MPLS-TP)Current
March 2014
- RFC 7226Requirements for Advanced Multipath in MPLS NetworksCurrent
May 2014
- RFC 7510Encapsulating MPLS in UDPCurrent
April 2015
- RFC 7167A Framework for Point-to-Multipoint MPLS in Transport NetworksCurrent
April 2014
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
- RFC 7759Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using Label Switched Path (LSP) PingCurrent
February 2016
- RFC 8184Dual-Homing Protection for MPLS and the MPLS Transport Profile (MPLS-TP) PseudowiresCurrent
June 2017
- RFC 8185Dual-Homing Coordination for MPLS Transport Profile (MPLS-TP) Pseudowires ProtectionCurrent
June 2017
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?