%% You should probably cite rfc7054 instead of this I-D. @techreport{ietf-mpls-tp-mip-mep-map-09, number = {draft-ietf-mpls-tp-mip-mep-map-09}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-mip-mep-map/09/}, author = {Adrian Farrel and Hideki Endo and Rolf Winter and Yoshinori Koike and Manuel Paul}, title = {{Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points (MIPs)}}, pagetotal = 11, year = 2013, month = aug, day = 30, 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.}, }