Subject: [mpls] MPLS-TP multi-failure protection

From: Zhenlong Cui <[email-masked]>
Date: Tue, 8 Jul 2014 04:45:31 +0000

Dear All,

We've submitted a new version of I-D, draft-cui-mpls-tp-mfp-use-case-and-requirements-02 as shown in the following e-mail.

 -History
  Older version(-01) includes m:1, but not m:n.

 -Purpose of the new version.
  Extend the scope to cover m:n, because it meets the customer needs well.

Any comments or suggestions would be greatly appreciated. 

Thank you,
zhenlong

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Saturday, July 05, 2014 3:49 AM
To: Masahiro Daikoku; Rolf Winter; Sam Aldrin; Himanshu C. Shah; Cui Zhenlong(崔 珍龍); Rolf Winter; Masahiro Daikoku; Himanshu Shah; Sam Aldrin; Cui Zhenlong(崔 珍龍)
Subject: New Version Notification for draft-cui-mpls-tp-mfp-use-case-and-requirements-02.txt

A new version of I-D, draft-cui-mpls-tp-mfp-use-case-and-requirements-02.txt
has been successfully submitted by Zhenlong Cui and posted to the IETF repository.

Name:		draft-cui-mpls-tp-mfp-use-case-and-requirements
Revision:	02
Title:		Use Cases and Requirements for MPLS-TP multi-failure protection
Document date:	2014-07-04
Group:		Individual Submission
Pages:		7
URL:            http://www.ietf.org/internet-drafts/draft-cui-mpls-tp-mfp-use-case-and-requirements-02.txt
Status:         https://datatracker.ietf.org/doc/draft-cui-mpls-tp-mfp-use-case-and-requirements/
Htmlized:       http://tools.ietf.org/html/draft-cui-mpls-tp-mfp-use-case-and-requirements-02
Diff:           http://www.ietf.org/rfcdiff?url2=draft-cui-mpls-tp-mfp-use-case-and-requirements-02

Abstract:
   The basic survivability technique has been defined in Multiprotocol
   Label Switching Transport Profile (MPLS-TP) network [RFC6378].  That
   protocol however is limited to 1+1 and 1:1 protection, not designed
   to handle multi-failure protection.

   This document introduces some use cases and requirements for multi-
   failure protection functionality.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat