IETF Logo Mail Archive

Re: [trill] AD review of draft-ietf-trill-p2mp-bfd-06

"Zhangmingui (Martin)" <zhangmingui@huawei.com> Wed, 27 December 2017 01:32 UTC

Return-Path: <zhangmingui@huawei.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9233D126CD6; Tue, 26 Dec 2017 17:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 h-MdE6gsLu4T; Tue, 26 Dec 2017 17:32:14 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 1FE94126B7F; Tue, 26 Dec 2017 17:32:14 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id F26CD18198810; Wed, 27 Dec 2017 01:32:09 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 27 Dec 2017 01:32:10 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0361.001; Wed, 27 Dec 2017 09:32:05 +0800
From: "Zhangmingui (Martin)" <zhangmingui@huawei.com>
To: Alia Atlas <akatlas@gmail.com>, "draft-ietf-trill-p2mp-bfd@ietf.org" <draft-ietf-trill-p2mp-bfd@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: AD review of draft-ietf-trill-p2mp-bfd-06
Thread-Index: AQHTeEm1YQtMBc8UR06VDxg1Ae1N16NWctcQ
Date: Wed, 27 Dec 2017 01:32:05 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7AAF89713@NKGEML515-MBX.china.huawei.com>
References: <CAG4d1rdDpL4FOVbsjZBp=W7-+ku4gVSgKNuZOHZtnFVrKz9FGA@mail.gmail.com>
In-Reply-To: <CAG4d1rdDpL4FOVbsjZBp=W7-+ku4gVSgKNuZOHZtnFVrKz9FGA@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.146.93]
Content-Type: multipart/alternative; boundary="_000_4552F0907735844E9204A62BBDD325E7AAF89713NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/3dccdT6WdddePJpKvVQ_KkedgF4>
Subject: Re: [trill] AD review of draft-ietf-trill-p2mp-bfd-06
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Dec 2017 01:32:16 -0000

Hi Alia,

Your review is much appreciated.

We’ve made the draft-ietf-trill-resilient-trees-08 to be a informative reference. The suggested improvement is sensible. The draft has been updated accordingly.

The 07 version has been uploaded.

Thanks!
Mingui

From: Alia Atlas [mailto:akatlas@gmail.com]
Sent: Tuesday, December 19, 2017 5:47 AM
To: draft-ietf-trill-p2mp-bfd@ietf.org; trill@ietf.org
Subject: AD review of draft-ietf-trill-p2mp-bfd-06

As is customary, I have done my AD review of draft-ietf-trill-p2mp-bfd-06. I would first like to thank the authors - Mingui, Santosh, and Vengada - as well as the WG for their work on this document.

My primary concern is that this document currently has a normative dependency on draft-ietf-trill-resilient-trees-08.  I do not understand why.  I can certainly see it being useful as an informative reference for how p2mp BFD might be useful in a TRILL network - but I don't see a need to understand or implement that draft to support this technology.  Text in this draft (e.g. "If the head is keeping track of some or all of the tails [I-D.ietf-trill-resilient-trees], it has a session of type MultipointClient per tail that it cares about [I-D.ietf-bfd-multipoint-active-tail].") could use improvement - such as "An example use is when a multicast tree root needs to keep track of all the receivers as in [I-D.ietf-trill-resilient-trees]; this can be done by maintaining a session of type MultipointClient per receiver that is of interest, as described in [I-D.ietf-bfd-multipoint-active-tail]."

I am going to request IETF Last Call for this draft - with it being extra long due to the holidays - and expect an update from the authors.

Regards,
Alia

v2.23.0 | Report a Bug | By Email