%% You should probably cite rfc7054 instead of this I-D. @techreport{ietf-mpls-tp-mip-mep-map-01, number = {draft-ietf-mpls-tp-mip-mep-map-01}, 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/01/}, author = {Adrian Farrel and Hideki Endo and Rolf Winter and Yoshinori Koike and Manuel Paul}, title = {{Handling MPLS-TP OAM Packets Targeted at Internal MIPs}}, pagetotal = 15, year = 2012, month = mar, day = 12, abstract = {The Framework for Operations, Administration and Maintenance (OAM) within the MPLS Transport Profile (MPLS-TP) describes how Maintenance Entity Group Intermediate Points (MIPs) may be situated within network nodes at the incoming and outgoing interfaces. This document describes a way of forming OAM messages so that they can be targeted at MIPs on incoming or MIPs on outgoing interfaces, forwarded correctly through the "switch fabric", and handled efficiently in node implementations where there is no distinction between the incoming and outgoing MIP. This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport network.}, }