[mpls] FW: [Reminder] RE: Routing directorate review of draft-ietf-mpls-ldp-mrt

"BRUNGARD, DEBORAH A" <db3546@att.com> Thu, 20 April 2017 23:07 UTC

Return-Path: <db3546@att.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 669E2127010; Thu, 20 Apr 2017 16:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.411
X-Spam-Level:
X-Spam-Status: No, score=-3.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 oXO7xILgAEe4; Thu, 20 Apr 2017 16:07:54 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A70C128D8B; Thu, 20 Apr 2017 16:07:49 -0700 (PDT)
Received: from pps.filterd (m0049463.ppops.net [127.0.0.1]) by m0049463.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v3KHkpDR019934; Thu, 20 Apr 2017 13:49:52 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049463.ppops.net-00191d01. with ESMTP id 29xyfjfgfk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 20 Apr 2017 13:49:52 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3KHnoAi028421; Thu, 20 Apr 2017 13:49:51 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v3KHnY7R027561 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 20 Apr 2017 13:49:44 -0400
Received: from MISOUT7MSGHUBAH.ITServices.sbc.com (MISOUT7MSGHUBAH.itservices.sbc.com [130.9.129.152]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Thu, 20 Apr 2017 17:49:16 GMT
Received: from MISOUT7MSGUSRDE.ITServices.sbc.com ([169.254.5.222]) by MISOUT7MSGHUBAH.ITServices.sbc.com ([130.9.129.152]) with mapi id 14.03.0319.002; Thu, 20 Apr 2017 13:49:16 -0400
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: "draft-ietf-mpls-ldp-mrt@ietf.org" <draft-ietf-mpls-ldp-mrt@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Thread-Topic: [Reminder] RE: Routing directorate review of draft-ietf-mpls-ldp-mrt
Thread-Index: AdKlPxUIlRR7IOwpRM2wX5Jdk0DLcgAE+4QAAFN95vEBna3WgAAlpUMwABK4/nwDCPhOgAAHv0Fw
Date: Thu, 20 Apr 2017 17:49:15 +0000
Message-ID: <F64C10EAA68C8044B33656FA214632C85DED3268@MISOUT7MSGUSRDE.ITServices.sbc.com>
References: <9C5FD3EFA72E1740A3D41BADDE0B461FC61BA0CA@szxema506-mbs.china.huawei.com> <1490466710.627965665@f24.my.com> <9C5FD3EFA72E1740A3D41BADDE0B461FC61C7462@szxema506-mbs.china.huawei.com> <CA+wi2hO+n6d0+mNyOeutqswZggdiNipsL+J8=S3BBRXu=sZKvA@mail.gmail.com> <9C5FD3EFA72E1740A3D41BADDE0B461FC61D84C1@szxema506-mbs.china.huawei.com> <9CB1940B-3918-4D16-83E7-541EE08833C7@att.com> <CA+wi2hM3qgzDEDHG6VN0a9MxES3XiUUzh-ZrhnsesPTErma00w@mail.gmail.com>
In-Reply-To: <CA+wi2hM3qgzDEDHG6VN0a9MxES3XiUUzh-ZrhnsesPTErma00w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.227.246]
Content-Type: multipart/alternative; boundary="_000_F64C10EAA68C8044B33656FA214632C85DED3268MISOUT7MSGUSRDE_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-20_17:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704200142
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/pQ7MkXWl3-yrfmdIIjvwjfAy60k>
Subject: [mpls] FW: [Reminder] RE: Routing directorate review of draft-ietf-mpls-ldp-mrt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Apr 2017 23:07:57 -0000

Authors,

Here’s our Routing Directorate reviewer’s comments. Please address the comments by responding to Tony and the list.

Thanks,
Deborah


From: Tony Przygienda [mailto:tonysietf@gmail.com]
Sent: Thursday, April 20, 2017 1:28 PM
To: BRUNGARD, DEBORAH A <db3546@att.com>
Cc: Yemin (Amy) <amy.yemin@huawei.com>om>; rtg-dir@ietf.org
Subject: Re: [Reminder] RE: Routing directorate review of draft-ietf-mpls-ldp-mrt

Here's the review (sorry for delay, lots of material). Pls fwd to according mailing lists

----


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<https://urldefense.proofpoint.com/v2/url?u=http-3A__trac.tools.ietf.org_area_rtg_trac_wiki_RtgDir&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhGpW9lwi9dM7jYlxXD8w&m=2alVGKgP_GREqRqvbnBZVqcgclwC7efVibS2GkUmJjc&s=JOA5mn5ikG_Osb6EtJOk-J0q5a9a__O55zqUSzk_Ck8&e=>

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-ldp-mrt
Reviewer: Tony Przygienda
Review Date: 4/20/17
Intended Status: Standards Track

Summary:

I have several major comments that either indicate technical inconsistencies in the MRT-FRR document set (7811/7812/igp/ldp drafts) or suggest additions to improve readability of those documents and prevent wrong assumptions on the reader's side.


Major Comments:


·         A small section outlining the requirements of “domain-alignment” in MRT could be helpful, i.e. what are the assumptions as to congruency of LDP/IGP areas/MRT islands and features supported in each. A picture of where the proxy nodes fit in, where the rainbow labels are used, a GADAG root would improve readability. MRT has good amount of moving parts that relate in non-obvious ways. This comment is geared probably more toward RFC7812 than this document.

·         It seems that the implicit assumption that the IGP MRT support is congruent with the LDP MRT support, i.e. LDP MRT capability is advertised IIF if the node supports MRT in IGP on the link (and vice versa)? Otherwise section 5.2 is ambiguous as in “is LDP on anything that will be on red or blue assumed/a MUST” or “IGP shall not compute red/blue if LDP peer is not MT-MRT-capable, i.e. take the link out the MRT topology” ?  If such an assumption is made, spelling it out would improve readability of the document.

·         Proxy node attachment router in section in 5.1.2 is loosely introduced and would benefit from reference to Section 11.2 in 7812. A clear definition with distinction between the “proxy node” and “proxy node attachment" in the glossary (of RFC7812?) would help the reader of the document set.

·         I don’t see a specification how non-default profiles would be supported in the future in this document. It seems implied that negotiating certain MT-IDs in LDP will imply certain profile values in the future but the document would gain readability if that is spelled out (I think RFC7812 does indicate that in 8.1 already so reference maybe enough). However when reading 5.1 of draft-ietf-isis-mrt-02 I see  that the profile ID is explicity given with the topology ID which seem contradictory if topology IDs imply the profile used.

·         I find it surprising that the document does not describe in section 5 the interaction of different LDP modes and the MRT computations. Do we do unsolicited  liberal, retain when MRT computed the next-hops and so on?  Maybe one sentence along the lines of “LDP mode must be the same as unicast IGP forwarding mode” would help clarify or the specific necessary modes listed.

Minor comments:


·         For easy reference suggest to add “two-connected graph” to the glossary since it’s not a common term. Or refer to  RFC7812

·         Maybe same for “cut-vertex” or refer to 7812

·         Maybe same for “topological ordering”. Reference to 7811 would be helpful for readability





thanks



--- tony


On Wed, Apr 5, 2017 at 3:41 AM, BRUNGARD, DEBORAH A <db3546@att.com<mailto:db3546@att.com>> wrote:
It's ok Tony-
Thanks for doing-
Deborah

Sent from my iPhone

On Apr 4, 2017, at 9:47 PM, Yemin (Amy) <amy.yemin@huawei.com<mailto:amy.yemin@huawei.com>> wrote:
I think the AD Deborah could allow additional days.
Deborah, could you please confirm on this?

Amy
From: Tony Przygienda [mailto:tonysietf@gmail.com]
Sent: Tuesday, April 04, 2017 11:47 PM
To: Yemin (Amy) <amy.yemin@huawei.com<mailto:amy.yemin@huawei.com>>
Subject: Re: [Reminder] RE: Routing directorate review of draft-ietf-mpls-ldp-mrt

Swamped with work, any chance you can grant me extension to 12th or so ?

On Sun, Mar 26, 2017 at 9:22 PM, Yemin (Amy) <amy.yemin@huawei.com<mailto:amy.yemin@huawei.com>> wrote:
Thanks, Tony.

Amy
________________________________
发件人: Tony Przygienda [tonysietf@gmail.com<mailto:tonysietf@gmail.com>]
发送时间: 2017年3月26日 2:31
收件人: Yemin (Amy)
主题: Re: [Reminder] RE: Routing directorate review of draft-ietf-mpls-ldp-mrt
Will review



Sent from myMail for iOS


Saturday, March 25, 2017, 01:09 -0700 from Yemin (Amy) <amy.yemin@huawei.com<mailto:amy.yemin@huawei.com>>:

Hi Tony,



Could you reply if you could review the draft or not.

Thanks.



Amy

From: Yemin (Amy)
Sent: Monday, March 20, 2017 2:20 PM
To: 'tonysietf@gmail.com<mailto:tonysietf@gmail.com>' <tonysietf@gmail.com<mailto:tonysietf@gmail.com>>; 'prz@zeta2.ch<mailto:prz@zeta2.ch>' <prz@zeta2.ch<mailto:prz@zeta2.ch>>
Cc: 'BRUNGARD, DEBORAH A' <db3546@att.com<mailto:db3546@att.com>>; 'Jonathan Hardwick' <Jonathan.Hardwick@metaswitch.com<mailto:Jonathan.Hardwick@metaswitch.com>>
Subject: Routing directorate review of draft-ietf-mpls-ldp-mrt



Hi Tony,



Please would you do a routing directorate review of this draft?

https://datatracker.ietf.org/doc/draft-ietf-mpls-ldp-mrt/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dmpls-2Dldp-2Dmrt_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhGpW9lwi9dM7jYlxXD8w&m=QPzfSKiJk8VBP1mieYBoPRdjO-IAl2SJ3eWoKw1yAZ0&s=lvMJ6m4iPoRt849E-0JZLXIb60OKHx8X3T3zo1F9nso&e=>



This is to accompany the IETF last call of this document. The ADs have requested your comments by April, 7th, 2017.

You can find some guidance and a review template at the following link:

https://trac.ietf.org/trac/rtg/wiki/RtgDirGuidance<https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.ietf.org_trac_rtg_wiki_RtgDirGuidance&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhGpW9lwi9dM7jYlxXD8w&m=QPzfSKiJk8VBP1mieYBoPRdjO-IAl2SJ3eWoKw1yAZ0&s=lyE88Wt1dwavAB6p_eIOt7gWjugzwpDWs90LoWA2e5k&e=>



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 relevant WG mailing list and the rtg-dir list.

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

Many thanks

Amy



________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!





--
We’ve heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.
—Robert Wilensky



--
We’ve heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.
—Robert Wilensky