RFC 7054: Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points (MIPs)
In plain English — editorial summary, not part of the RFC
The framework for Operations, Administration and Maintenance (OAM) within the MPLS Transport Profile (MPLS-TP) describes how the Maintenance Entity Group Intermediate Points (MIPs) may be situated within network nodes at incoming and outgoing interfaces. This document elaborates on important considerations for internal MIP addressing. More precisely, it describes important restrictions for any mechanism that specifies a way of forming OAM messages so that they can be targeted at MIPs on either incoming or outgoing interfaces and forwarded correctly through the forwarding engine. Furthermore, the document includes considerations for node implementations where there is no distinction between the incoming and outgoing MIP.
Document record
- Document ID
- RFC7054
- Published
- November 2013
- Authors
- A. Farrel; H. Endo; R. Winter; Y. Koike; M. Paul
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7052Locator/ID Separation Protocol (LISP) MIBCurrent
October 2013
- RFC 7060Using LDP Multipoint Extensions on Targeted LDP SessionsCurrent
November 2013
- RFC 7062Framework for GMPLS and PCE Control of G.709 Optical Transport NetworksCurrent
November 2013
- RFC 7063Survey Report on Protocol Independent Multicast - Sparse Mode (PIM-SM) Implementations and DeploymentsCurrent
December 2013
- RFC 7067Directory Assistance Problem and High-Level Design ProposalCurrent
November 2013
- RFC 7041Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Backbone BridgingCurrent
November 2013
- RFC 7038Use of OSPF-MDR in Single-Hop Broadcast NetworksCurrent
October 2013
- RFC 7074Revised Definition of the GMPLS Switching Capability and Type FieldsCurrent
November 2013
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?