Use Cases and Requirements for MPLS-TP multi-failure protection
draft-ietf-mpls-tp-mfp-use-case-and-requirements-03

Document Type Active Internet-Draft (mpls WG)
Last updated 2017-02-21
Replaces draft-cui-mpls-tp-mfp-use-case-and-requirements
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state Waiting for WG Chair Go-Ahead
Document shepherd Loa Andersson
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Loa Andersson" <loa@pi.nu>
Network Working Group                                             Z. Cui
Internet-Draft                                                 R. Winter
Updates: 5654 (if approved)                                          NEC
Intended status: Informational                                   H. Shah
Expires: August 25, 2017                                           Ciena
                                                               S. Aldrin
                                                     Huawei Technologies
                                                              M. Daikoku
                                                                    KDDI
                                                       February 21, 2017

    Use Cases and Requirements for MPLS-TP multi-failure protection
          draft-ietf-mpls-tp-mfp-use-case-and-requirements-03

Abstract

   For the Multiprotocol Label Switching Transport Profile (MPLS-TP)
   linear protection capable of 1+1 and 1:1 protection has already been
   defined.  That linear protection mechanism has not been designed for
   handling multiple, simultaneously occuring failures, i.e. multiple
   failures that affect the working and the protection entity during the
   same time period.  In these situations currently defined protection
   mechanisms would fail.

   This document introduces use cases and requirements for mechanisms
   that are capable of protecting against such failures.  It does not
   specify a multi-failure protection mechanism itself.

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

   This Internet-Draft will expire on August 25, 2017.

Cui, et al.              Expires August 25, 2017                [Page 1]
Internet-Draft    Multi-failure protection requirements    February 2017

Copyright Notice

   Copyright (c) 2017 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
     1.1.  Document scope  . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements notation . . . . . . . . . . . . . . . . . .   3
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  General m:n protection scenario . . . . . . . . . . . . . . .   4
   3.  Use cases . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  m:1 (m > 1) protection  . . . . . . . . . . . . . . . . .   5
       3.1.1.  Pre-configuration . . . . . . . . . . . . . . . . . .   5
       3.1.2.  On-demand configuration . . . . . . . . . . . . . . .   6
     3.2.  m:n (m, n > 1, n >= m > 1) protection . . . . . . . . . .   6
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Today's packet optical transport networks concentrate large volumes
   of traffic onto a relatively small number of nodes and links.  As a
   result, the failure of a single network element can potentially
   interrupt a large amount of traffic.  For this reason, ensuring
   survivability through careful network design and appropriate
   technical means is important.

   In MPLS-TP networks, a basic end-to-end linear protection
   survivability technique is available as specified in [RFC6378],
   [RFC7271] and [RFC7324].  That protocol however is limited to 1+1 and
Show full document text