RFC 7054

Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points (MIPs), November 2013

File formats:
icon for text file icon for PDF icon for HTML
Status:
INFORMATIONAL
Authors:
A. Farrel
H. Endo
R. Winter
Y. Koike
M. Paul
Stream:
IETF
Source:
mpls (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  10.17487/RFC7054

Discuss this RFC: Send questions or comments to the mailing list mpls@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7054


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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search