Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points
RFC 7054, “Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points”, is an Informational document published in November 2013 by A. Farrel, H. Endo, R. Winter, Y. Koike, M. Paul. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7054 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7053 SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol
- RFC 7055 A GSS-API Mechanism for the Extensible Authentication Protocol
- RFC 7052 Locator/ID Separation Protocol MIB
- RFC 7056 Name Attributes for the GSS-API Extensible Authentication Protocol Mechanism
- RFC 7051 Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix
- RFC 7057 Update to the Extensible Authentication Protocol Applicability Statement for Application Bridging for Federated Access Beyond Web
- RFC 7050 Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis
- RFC 7058 Media Control Channel Framework Call Flow Examples