Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points (MIPs)
RFC 7054

 
Document Type RFC - Informational (November 2013; No errata)
Last updated 2013-11-11
Replaces draft-farrel-mpls-tp-mip-mep-map
Stream IETF
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Loa Andersson
Shepherd write-up Show (last changed 2013-04-22)
IESG IESG state RFC 7054 (Informational)
Telechat date
Responsible AD Stewart Bryant
IESG note Assigned to Stewart as Adrian is a co-author
Send notices to mpls-chairs@ietf.org, draft-ietf-mpls-tp-mip-mep-map@ietf.org
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                         A. Farrel
Request for Comments: 7054                              Juniper Networks
Category: Informational                                          H. Endo
ISSN: 2070-1721                                            Hitachi, Ltd.
                                                               R. Winter
                                                                     NEC
                                                                Y. Koike
                                                                     NTT
                                                                 M. Paul
                                                        Deutsche Telekom
                                                           November 2013

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

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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7054.

Farrel, et al.                Informational                     [Page 1]
RFC 7054               Internal MIP Considerations         November 2013

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................2
   2. Terminology .....................................................3
   3. Summary of the Problem Statement ................................3
   4. Requirements and Design Considerations for Internal-MIP
      Addressing ......................................................6
   5. Security Considerations ........................................10
   6. Acknowledgments ................................................10
   7. References .....................................................10
      7.1. Normative References ......................................10
      7.2. Informative References ....................................11

1.  Introduction

   The framework for Operations, Administration and Maintenance (OAM)
   within the MPLS Transport Profile (MPLS-TP)(the MPLS-TP OAM
   Framework, [RFC6371]) distinguishes two configurations for the
   Maintenance Entity Group Intermediate Points (MIPs) on a node.  It
   defines per-node MIPs and per-interface MIPs, where a per-node MIP is
   a single MIP per node in an unspecified location within the node and
   per-interface MIPs are two (or more) MIPs per node on each side of
   the forwarding engine.

   In-band OAM messages are sent using the Generic Associated Channel
   (G-ACh) [RFC5586].  OAM messages for the transit points of
   pseudowires (PWs) or Label Switched Paths (LSPs) are delivered using
   the expiration of the MPLS shim header Time-to-Live (TTL) field.  OAM
   messages for the end points of PWs and LSPs are simply delivered as
Show full document text