Handling MPLS-TP OAM Packets Targeted at Internal MIPs
draft-ietf-mpls-tp-mip-mep-map-03

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2012-10-22
Replaces draft-farrel-mpls-tp-mip-mep-map
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          A. Farrel
Internet-Draft                                          Juniper Networks
Intended status: Informational                                   H. Endo
Expires: April 25, 2013                                    Hitachi, Ltd.
                                                               R. Winter
                                                                     NEC
                                                                Y. Koike
                                                                     NTT
                                                                 M. Paul
                                                        Deutsche Telekom
                                                        October 22, 2012

         Handling MPLS-TP OAM Packets Targeted at Internal MIPs
                   draft-ietf-mpls-tp-mip-mep-map-03

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 forwarding engine, 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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference

Farrel, et al.           Expires April 25, 2013                 [Page 1]
Internet-Draft            Internal MIP Handling             October 2012

   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 25, 2013.

Copyright Notice

   Copyright (c) 2012 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.

Farrel, et al.           Expires April 25, 2013                 [Page 2]
Internet-Draft            Internal MIP Handling             October 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  4
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Summary of the Problem Statement . . . . . . . . . . . . . . .  5
   5.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     5.1.  Rejected Partial Solution  . . . . . . . . . . . . . . . . 10
   6.  Per-Interface MIP Message Handling . . . . . . . . . . . . . . 11
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 12
   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 12
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 13
     10.2. Informative References . . . . . . . . . . . . . . . . . . 13
   Appendix A.  Previously considered solutions . . . . . . . . . . . 14
     A.1.  GAL TTL  . . . . . . . . . . . . . . . . . . . . . . . . . 14
     A.2.  A separate channel type for the out-MIP  . . . . . . . . . 14
     A.3.  Decrement TTL once per MIP . . . . . . . . . . . . . . . . 14
Show full document text