Re: [mpls] Routing directorate review of draft-ietf-mpls-residence-time

"Hejia (Jia)" <hejia@huawei.com> Tue, 13 December 2016 06:01 UTC

Return-Path: <hejia@huawei.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 B21271296D1; Mon, 12 Dec 2016 22:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.116
X-Spam-Level:
X-Spam-Status: No, score=-7.116 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.896, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqYfkyFlARG9; Mon, 12 Dec 2016 22:01:16 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B3DB126D74; Mon, 12 Dec 2016 22:01:15 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CWZ75146; Tue, 13 Dec 2016 06:01:12 +0000 (GMT)
Received: from SZXEMA411-HUB.china.huawei.com (10.82.72.70) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 13 Dec 2016 06:01:10 +0000
Received: from SZXEMA507-MBS.china.huawei.com ([169.254.6.194]) by szxema411-hub.china.huawei.com ([10.82.72.70]) with mapi id 14.03.0235.001; Tue, 13 Dec 2016 14:01:02 +0800
From: "Hejia (Jia)" <hejia@huawei.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Thread-Topic: [mpls] Routing directorate review of draft-ietf-mpls-residence-time
Thread-Index: AdJU57F2KlgGXJQbTKGj782AYLERzQ==
Date: Tue, 13 Dec 2016 06:01:02 +0000
Message-ID: <735916399E11684EAF4EB4FB376B719551C85BF2@szxema507-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.57.113.123]
Content-Type: multipart/alternative; boundary="_000_735916399E11684EAF4EB4FB376B719551C85BF2szxema507mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.584F8EA9.026F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.6.194, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: afce8b78c8075c0a6d1e1f23e62b7feb
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/Kxo9tjTNeOzNvdNK1U6Km5f-NmE>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "draft-ietf-mpls-residence-time.all@ietf.org" <draft-ietf-mpls-residence-time.all@ietf.org>, "jonathan.hardwick@metaswitch.com" <jonathan.hardwick@metaswitch.com>, Jon Hudson <jon.hudson@gmail.com>
Subject: Re: [mpls] Routing directorate review of draft-ietf-mpls-residence-time
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 13 Dec 2016 06:01:21 -0000

Hi Greg,

Thanks for your quick updates. They have addressed all of my questions. I’m OK the draft moves forward.

B.R.
Jia
发件人: Greg Mirsky [mailto:gregimirsky@gmail.com]
发送时间: 2016年12月13日 0:29
收件人: Hejia (Jia)
抄送: rtg-ads@ietf.org; draft-ietf-mpls-residence-time.all@ietf.org; rtg-dir@ietf.org; mpls@ietf.org; jonathan.hardwick@metaswitch.com; Jon Hudson
主题: Re: [mpls] Routing directorate review of draft-ietf-mpls-residence-time

Hi Jia,
greatly appreciate your thorough review and thoughtful recommendations. Please find my answers in-line tagged GIM>>.

Kind regards,
Greg


On Tue, Dec 6, 2016 at 6:43 AM, Hejia (Jia) <hejia@huawei.com<mailto:hejia@huawei.com>> wrote:
Hello,

I have been selected as the Routing Directorate reviewer for this draft. The Routing
Directorate seeks to review all routing or routing-related drafts as they pass through IETF
last call and IESG review, and sometimes on special request. The purpose of the review is to
provide assistance to the Routing ADs. For more information about the Routing Directorate,
please see ​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it would be helpful if
you could consider them along with any other IETF Last Call comments that you receive, and
strive to resolve them through discussion or by updating the draft.

Document: draft-ietf-mpls-residence-time-11.txt
Reviewer: Jia He
Review Date: Dec.6, 2016
IETF LC End Date:
Intended Status: Standards Track

Summary:
This document is basically ready for publication, but has minor issues that should be
considered prior to publication.

Comments:
The draft is clearly structured and easy to read.
GIM>> Thank you.

Major Issues:
No major issues found.
GIM>> Thank you.

Minor Issues:
1) Section 3.1, the description of "Type field" of PTP Sub-TLV format (following Figure 3) is
the same as the description of "PTPType". Shouldn't the PTP Sub-TLV follow RTM sub-TLV
registry?

"The Type field identifies PTP sub-TLV defined in the Table 19 Values of messageType field in
[IEEE.1588.2008]."

"The PTPType indicates the type of PTP packet carried in the TLV. PTPType is the messageType
field of the PTPv2 packet whose values are defined in the Table 19 [IEEE.1588.2008]."

GIM>> Great catch, thank you. Indeed, some cut-paste error. Proposed new text for Type field:
""
No changes for PTPType field.
Another question about RTM sub-TLV registry, why only PTP 2-step is defined under RTM sub-TLV
registry(8.3)?
GIM>> You absolutely right. There's no need for two types of sub-TLV for PTP.


Nits:
1) Section 1, first paragragh, s/Generalized Associated Channel/Generic Associated Channel
GIM>> Yes, agreed.
2) Section 3, first paragragh, s/select/selected
GIM>> Yes, agreed.
3) Section 4.7, last paragraph of Page 12, s/If match have been found, then the calculated..../If match has been found, the calculated....
GIM>> Yes, agreed.
4) Section 5, the first paragragh, ".....as described in Section 4.6 or as described in the second paragraph of Section 4 and in Section 4.6, ...." Duplication? Not sure about what " the second paragraph of Section 4" really indicates
GIM>> Great catch, thank you. The part after "or" is old. Removed "or as described in the second paragraph of Section 4 and in Section 4.6".
5) Section 7, Page 18(in the middle), BC needs to be spelt out, s/BC/Boundary Clock
GIM>>  First use of Boundary Clock term I've found is in section 4.6. I've added it to Terminology section and in 4.6 did s/Boundary Clock/Boundary Clock (BC)/



B.R.
Jia

发件人: Zhangxian (Xian)
发送时间: 2016年11月22日 16:41
收件人: Hejia (Jia)
抄送: db3546@att.com<mailto:db3546@att.com>; jonathan.hardwick@metaswitch.com<mailto:jonathan.hardwick@metaswitch.com>; 'Jon Hudson'
主题: Routing directorate review of draft-ietf-mpls-residence-time

Hey, Jia,

Please would you do a routing directorate review of this draft?
https://tools.ietf.org/html/draft-ietf-mpls-residence-time-11


The draft has been submitted to the IESG for publication.  The responsible AD – Deborah – has requested a review from the directorate before she initiates the IETF last call.  It would be great if you could review the document and send comments by 6th December.

You can find some guidance and a review template at the following link:
​https://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDirGuidance

Please send your comments to the RTG Area Directors (​rtg-ads@ietf.org<mailto:rtg-ads@ietf.org>) and the draft authors, and copy the MPLS mailing list and the rtg-dir list.

Please let me know if you can do it, or not.

Many thanks,
Xian





_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls