Re: [mpls] I-D Action: draft-cui-mpls-tp-mfp-use-case-and-requirements-05.txt

Hi Huub,

Thanks for your very helpful suggestions.

I agree with you. We'll upload the next version shortly after the I-D submission tool is reopened.

-----Original Message-----
From: Huub van Helvoort [mailto:huubatwork@gmail.com]
Sent: Sunday, July 12, 2015 9:13 PM
To: draft-cui-mpls-tp-mfp-use-case-and-requirements@tools.ietf.org
Cc: mpls@ietf.org
Subject: ##freemail## Re: [mpls] I-D Action: draft-cui-mpls-tp-mfp-use-case-and-requirements-05.txt

Hello authors of this draft,

Triggered by a reference to your draft in another discussion I have read your draft.

It describes useful use cases.

I would recommend to add to the introduction an explicit statement that these use cases are specifically to end-to-end
linear protection.
Currently only the abstract briefly mentions this and can easily be overlooked.

I also would recommend to add a requirement that any of the n working entities and m protection entities should follow
a disjoint path through the network from node A to node Z.

Best regards, Huub.

A New Internet-Draft is available from the on-line Internet-Drafts directories.
  This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

         Title           : Use Cases and Requirements for MPLS-TP multi-failure protection
         Authors         : Zhenlong Cui
                           Rolf Winter
                           Himanshu Shah
                           Sam Aldrin
                           Masahiro Daikoku
	Filename        : draft-cui-mpls-tp-mfp-use-case-and-requirements-05.txt
	Pages           : 8
	Date            : 2015-07-06

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.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-cui-mpls-tp-mfp-use-case-and-re" rel="nofollow">https://datatracker.ietf.org/doc/draft-cui-mpls-tp-mfp-use-case-and-re
quirements/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-cui-mpls-tp-mfp-use-case-and-require" rel="nofollow">https://tools.ietf.org/html/draft-cui-mpls-tp-mfp-use-case-and-require
ments-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-cui-mpls-tp-mfp-use-case-and-r" rel="nofollow">https://www.ietf.org/rfcdiff?url2=draft-cui-mpls-tp-mfp-use-case-and-r
equirements-05

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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/" rel="nofollow">ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls" rel="nofollow">https://www.ietf.org/mailman/listinfo/mpls

-- 
*****************************************************************
              请记住，你是独一无二的，就像其他每一个人一样 