datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

MPLS-TP protection for interconnected rings
draft-liu-mpls-tp-interconnected-ring-protection-05

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-10-17
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

MPLS Working Group                                                G. Liu
Internet-Draft                                           ZTE Corporation
Intended status: Informational                              Y. Weigarten
Expires: April 21, 2014
                                                              M. Daikoku
                                                             T. Maruyama
                                                        KDDI Corporation
                                                        October 18, 2013

              MPLS-TP protection for interconnected rings
          draft-liu-mpls-tp-interconnected-ring-protection-05

Abstract

   The requirements for MPLS Transport Profile include a requirement
   (R93) that requires MPLS-TP must support recovery mechanisms for a
   network constructed from interconnected rings that protect user data
   that traverses more than one ring.  In particular, This includes
   protecting against cases of failure at the ring-interconnect nodes
   and links.  This document presents different scenario of
   interconnected rings and special mechanism to address recovery of the
   failure of ring-interconnect nodes and links.  .

   This document is a product of a joint Internet Engineering Task
   Force(IETF) / International Telecommunications Union
   Telecommunications 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 as defined by the ITU-T.

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 April 21, 2014.

Liu, et al.              Expires April 21, 2014                 [Page 1]
Internet-Draft    MPLS-TP protection of interconnection     October 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.

   This document may not be modified, and derivative works of it may not
   be created, and it may not be published except as an Internet-Draft.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   6
   3.  Recovery mechanism  . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Recovery mechanism for Dual-node interconnection  . . . .   7
     3.2.  Recovery mechanism for chained interconnection  . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     7.2.  URL References  . . . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   This document describes different interconnected ring scenario and a
   few special mechanisms to protect against the failure of the ring-
   interconnect nodes and links.  There are three common interconnection
   scenarios that we will address in this document:

   Dual-node interconnection - when the two rings are interconnected by
   two nodes from each ring (see Figure 1);

   Single-node interconnection - when the connection between the two
   rings is through a single node (see Figure 2).As the interconnnection
   node(LSR-A) is a single-point of failure, this scenario should be
   avoided in real network;

[include full document text]