MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of SDH, OTN and Ethernet Transport Network Operators
draft-ietf-mpls-tp-psc-itu-01

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2014-01-19
Replaces draft-ryoogray-mpls-tp-psc-itu
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Document shepherd Loa Andersson
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MPLS Working Group                                          J. Ryoo, Ed.
Internet-Draft                                                      ETRI
Updates: 6378 (if approved)                                 E. Gray, Ed.
Intended status: Standards Track                                Ericsson
Expires: July 23, 2014                                   H. van Helvoort
                                                     Huawei Technologies
                                                         A. D'Alessandro
                                                          Telecom Italia
                                                               T. Cheung
                                                                    ETRI
                                                              E. Osborne
                                                     Cisco Systems, Inc.
                                                        January 19, 2014

    MPLS Transport Profile (MPLS-TP) Linear Protection to Match the
  Operational Expectations of SDH, OTN and Ethernet Transport Network
                               Operators
                   draft-ietf-mpls-tp-psc-itu-01.txt

Abstract

   This document describes alternate mechanisms to perform some of the
   sub-functions of MPLS Transport Profile (MPLS-TP) linear protection
   defined in RFC 6378, and also defines additional mechanisms.  The
   purpose of these alternate and additional mechanisms is to provide
   operator control and experience that more closely models the behavior
   of linear protection seen in other transport networks.

   This document also introduces capabilities and modes for linear
   protection.  A capability is an individual behavior, and a mode is a
   particular combination of capabilities.  Two modes are defined in
   this document: Protection State Coordination (PSC) mode and Automatic
   Protection Switching (APS) mode.

   This document describes the behavior of the PSC protocol including
   priority logic and state machine when all the capabilities associated
   with the APS mode are enabled.

   This document updates RFC 6378 in that the capability advertisement
   method defined here is an addition to that document.

Status of This Memo

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

Ryoo, et al.              Expires July 23, 2014                 [Page 1]
Internet-Draft            MPLS-TP LP for ITU-T              January 2014

   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."

   This Internet-Draft will expire on July 23, 2014.

Copyright Notice

   Copyright (c) 2014 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   5
   3.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Capability 1: Priority modification . . . . . . . . . . . . .   6
     4.1.  Motivations for swapping priorities of FS and SF-P  . . .   6
     4.2.  Motivation for raising the priority of SFc  . . . . . . .   7
     4.3.  Motivation for introducing Freeze command . . . . . . . .   7
     4.4.  Modifications to RFC 6378 . . . . . . . . . . . . . . . .   7
   5.  Capability 2: Modification of non-revertive operation . . . .   8
   6.  Capability 3: Support of MS-W command . . . . . . . . . . . .   8
     6.1.  Motivation for adding MS-W  . . . . . . . . . . . . . . .   8
     6.2.  Terms modified to support MS-W  . . . . . . . . . . . . .   9
     6.3.  Behavior of MS-P and MS-W . . . . . . . . . . . . . . . .   9
     6.4.  Equal priority resolution for MS  . . . . . . . . . . . .   9
Show full document text