RFC 4378: A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM)
In plain English — editorial summary, not part of the RFC
This document is a framework for how data plane protocols can be applied to operations and maintenance procedures for Multi-Protocol Label Switching (MPLS). The document is structured to outline how Operations and Management (OAM) functionality can be used to assist in fault, configuration, accounting, performance, and security management, commonly known by the acronym FCAPS. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4378
- Published
- February 2006
- Authors
- D. Allan; T. Nadeau
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4379Detecting Multi-Protocol Label Switched (MPLS) Data Plane FailuresObsoleted
February 2006
- RFC 6383Advice on When It Is Safe to Start Sending Data on Label Switched Paths Established Using RSVP-TECurrent
September 2011
- RFC 4377Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) NetworksCurrent
February 2006
- RFC 4382MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information BaseCurrent
February 2006
- RFC 4385Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSNUpdated
February 2006
- RFC 4368Multiprotocol Label Switching (MPLS) Label-Controlled Asynchronous Transfer Mode (ATM) and Frame-Relay Management Interface DefinitionCurrent
January 2006
- RFC 4365Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs)Current
February 2006
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 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?