The Reasons for Selecting a Single Solution for MPLS-TP OAM
draft-sprecher-mpls-tp-oam-considerations-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rtg area)
Last updated 2012-04-30
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd None
IESG IESG state Waiting for AD Go-Ahead::AD Followup
Telechat date
Has enough positions to pass.
Responsible AD Adrian Farrel
IESG note Ross Callon (rcallon@juniper.net) is the document shepherd.
Send notices to nurit.sprecher@nsn.com, hongk@cisco.com, draft-sprecher-mpls-tp-oam-considerations@tools.ietf.org, rcallon@juniper.net
Network Working Group                                        N. Sprecher
Internet-Draft                                    Nokia Siemens Networks
Intended status: Informational                                  KY. Hong
Expires: November 1, 2012                                  Cisco Systems
                                                          April 30, 2012

      The Reasons for Selecting a Single Solution for MPLS-TP OAM
            draft-sprecher-mpls-tp-oam-considerations-02.txt

Abstract

   The MPLS Transport Profile (MPLS-TP) is a profile of the MPLS
   technology for use in transport network deployments.  The work on
   MPLS-TP has extended the MPLS technology with additional
   architectural elements and functions that can be used in any MPLS
   deployment.  MPLS-TP is a set of functions and features selected from
   the extended MPLS toolset and applied in a consistent way to meet the
   needs and requirements of operators of packet transport networks.

   During the process of development of the profile, additions to the
   MPLS toolset have been made to ensure that the tools available met
   the requirements.  These additions were motivated by MPLS-TP, but
   form part of the wider MPLS toolset such that any of them could be
   used in any MPLS deployment.

   One major set of additions provides enhanced support for Operations,
   Administration, and Maintenance (OAM).  This enables fault management
   and performance monitoring to the level needed in a transport
   network.  Many solutions and protocol extensions have been proposed
   to address the requirements for MPLS-TP OAM, and this document sets
   out the reasons for selecting a single, coherent set of solutions for
   standardization.

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
   material or to cite them other than as "work in progress."

Sprecher & Hong         Expires November 1, 2012                [Page 1]
Internet-Draft         MPLS-TP OAM Considerations             April 2012

   This Internet-Draft will expire on November 1, 2012.

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.

Sprecher & Hong         Expires November 1, 2012                [Page 2]
Internet-Draft         MPLS-TP OAM Considerations             April 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Background . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.2.  The Development of a Parallel MPLS-TP OAM Solution . . . .  6
   2.  Terminology and References . . . . . . . . . . . . . . . . . .  8
     2.1.  Acronyms . . . . . . . . . . . . . . . . . . . . . . . . .  8
   3.  Motivations for a Single OAM Solution in MPLS-TP . . . . . . .  8
     3.1.  MPLS-TP is an MPLS Technology  . . . . . . . . . . . . . .  8
     3.2.  MPLS-TP is a Convergence Technology  . . . . . . . . . . .  9
     3.3.  There is an End-to-End Requirement for OAM . . . . . . . .  9
     3.4.  The Complexity Sausage . . . . . . . . . . . . . . . . . . 10
     3.5.  Interworking is Expensive and Has Deployment Issues  . . . 10
     3.6.  Selection of a Single OAM Solution When There is a
           Choice . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     3.7.  Migration Issues . . . . . . . . . . . . . . . . . . . . . 14
   4.  Potential Models For Coexistence . . . . . . . . . . . . . . . 14
     4.1.  Protocol Incompatibility . . . . . . . . . . . . . . . . . 15
     4.2.  Inevitable Coexistence . . . . . . . . . . . . . . . . . . 15
     4.3.  Models for Coexistence . . . . . . . . . . . . . . . . . . 16
Show full document text