Re: [mpls] MPLS-RT Review of draft-fbb-mpls-tp-p2mp-framework-05

<kenji.fujihira.dj@hitachi.com> Mon, 07 January 2013 10:15 UTC

Return-Path: <kenji.fujihira.dj@hitachi.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2DDA21F843F for <mpls@ietfa.amsl.com>; Mon, 7 Jan 2013 02:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.09
X-Spam-Level:
X-Spam-Status: No, score=-1.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QPQhfW3-fq3f for <mpls@ietfa.amsl.com>; Mon, 7 Jan 2013 02:15:47 -0800 (PST)
Received: from mail7.hitachi.co.jp (mail7.hitachi.co.jp [133.145.228.42]) by ietfa.amsl.com (Postfix) with ESMTP id 292C721F8417 for <mpls@ietf.org>; Mon, 7 Jan 2013 02:15:47 -0800 (PST)
Received: from mlsv4.hitachi.co.jp (unknown [133.144.234.166]) by mail7.hitachi.co.jp (Postfix) with ESMTP id 11F5F37AC7; Mon, 7 Jan 2013 19:15:46 +0900 (JST)
Received: from mfilter05.hitachi.co.jp by mlsv4.hitachi.co.jp (8.13.1/8.13.1) id r07AFki6012275; Mon, 7 Jan 2013 19:15:46 +0900
Received: from vshuts04.hitachi.co.jp (vshuts04.hitachi.co.jp [10.201.6.86]) by mfilter05.hitachi.co.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id r07AFi2T025933; Mon, 7 Jan 2013 19:15:45 +0900
Received: from gmml25.itg.hitachi.co.jp (unknown [158.213.165.145]) by vshuts04.hitachi.co.jp (Postfix) with ESMTP id 957FB14003D; Mon, 7 Jan 2013 19:15:44 +0900 (JST)
Received: from [127.0.0.1] by gmml25.itg.hitachi.co.jp (AIX5.2/8.11.6p2/8.11.0) id r07AFiX19988654; Mon, 7 Jan 2013 19:15:44 +0900
Message-Type: Multiple Part
MIME-Version: 1.0
Message-ID: <XNM1$6$0$0$$9$1$2$A$2008106U50eaa02d@hitachi.com>
Content-Type: text/plain; charset="ISO-2022-JP"
To: stbryant@cisco.com
From: kenji.fujihira.dj@hitachi.com
Date: Mon, 07 Jan 2013 19:15:22 +0900
Priority: normal
Importance: normal
X400-Content-Identifier: X50EAA02D00000M
X400-MTS-Identifier: [/C=JP/ADMD=HITNET/PRMD=HITACHI/;gmml28130107191509QRV]
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, mpls-chairs@tools.ietf.org, draft-fbb-mpls-tp-p2mp-framework@tools.ietf.org
Subject: Re: [mpls] MPLS-RT Review of draft-fbb-mpls-tp-p2mp-framework-05
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 10:15:48 -0000

Hi, Stewart.

The updated document has addressed my comments.
Thank you.

Best Regards.
Kenji.

>On 03/09/2012 11:18, kenji.fujihira.dj@hitachi.com wrote:
>> Hi, authors and chairs.
>>
>> As the MPLS-RT process, I've reviewed draft-fbb-mpls-tp-p2mp-framework-05.
>>
>> a. Is the document coherent?
>> It is almost coherent. I have two comments.
>>
>> - Section 7. (Network Management)
>> I think the following description should be moved from section 7 to section 4 (OAM).
>> "Packet Loss and Delay Measurement for
>>  MPLS Networks [RFC6374] already considers the P2MP case and it is not
>>  thought that any change is needed to the MPLS-TP profile of [RFC6374]
>>  [RFC6375]."
>Done.
>>
>> - Section 1.2. (Terminology)
>> I suppose PM is "Performance Monitoring", not "Performance Measurement",
>> referring to RFC5921, 5951 and 6371.
>Done
>> b. Is it useful (ie, is it likely to be actually useful in operational networks)?
>> I believe this draft is useful. If possible, comments from operators will help.
>>
>> c. Is the document technically sound?
>> My concern is 1:n protection. 
>> As addressed in section 6, it needs further discussion.
>> Relating to this point, it will be valuable if the draft lists up protection types
>> P2MP MAY support (for example, partial tree protection as addressed in section 6).
>The draft says:
>More sophisticated survivability approaches such as partial tree
>protection and 1:n protection are for further study.
>
>The further study can happen during the WG phase of the draft. At this
>stage the draft is only up for WG adoption not WG LC, and thus the test is
>whether the draft is a good starting point for the WG to work on it, and
>I suggest that it passed that hurdle.
>
>>
>> The other descriptions are clear and well aligned with referred RFCs. 
>>
>> d. Is the document ready to be considered for WG adoption?
>> IMO, it's better to close my comments above on section 7 before WG adoption.
>That one is done.
>
>- Stewart
>>
>> Best Regards,
>> Kenji.
>>
>>
>>> Kenji, Jia, Dave;
>>>
>>> You have been selected as an MPLS Review team reviewers for
>>> draft-fbb-mpls-tp-p2mp-framework-05.txt
>>>
>>> Note to authors: You have been CC壇 on this email so that you can know
>>> that this review is going on. However, please do not review your own
>>> document.
>>>
>>> Reviews should comment on whether the document is coherent, is it useful
>>> (ie, is it likely to be actually useful in operational networks), and is
>>> the document technically sound?  We are interested in knowing whether
>>> the document is ready to be considered for WG adoption (ie, it doesn稚
>>> have to be perfect at this point, but should be a good start).
>>>
>>> Reviews should be sent to the document authors, WG co-chairs and
>>> secretary, and CC壇 to the MPLS WG email list. If necessary, comments
>>> may be sent privately to only the WG chairs.
>>>
>>> Are you able to review this draft by Sep 3, 2012?
>>>
>>> Thanks, Loa
>>> (as MPLS WG chair)
>>> -- 
>>>
>>>
>>> Loa Andersson                         email: loa.andersson@ericsson.com
>>> Sr Strategy and Standards Manager            loa@pi.nu
>>> Ericsson Inc                          phone: +46 10 717 52 13
>>>                                              +46 767 72 92 13
>>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>> .
>>
>
>
>-- 
>For corporate legal information go to:
>
>http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>