Re: [trill] Review of draft-ietf-trill-p2mp-bfd-04

"Zhangmingui (Martin)" <zhangmingui@huawei.com> Thu, 23 March 2017 22:37 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 70D4612948D; Thu, 23 Mar 2017 15:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 xjwB-BMBvTFh; Thu, 23 Mar 2017 15:37:22 -0700 (PDT)
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 3B4DB1292FD; Thu, 23 Mar 2017 15:37:21 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML714-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DJM22142; Thu, 23 Mar 2017 22:37:18 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 23 Mar 2017 22:37:17 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Fri, 24 Mar 2017 06:37:09 +0800
From: "Zhangmingui (Martin)" <zhangmingui@huawei.com>
To: Carlos Pignataro <cpignata@cisco.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "draft-ietf-trill-p2mp-bfd.all@ietf.org" <draft-ietf-trill-p2mp-bfd.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: Review of draft-ietf-trill-p2mp-bfd-04
Thread-Index: AQHSpAqM/H6sHj72GE6hAlFdfMbv2aGjAqca
Date: Thu, 23 Mar 2017 22:37:09 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7A6418619@NKGEML515-MBX.china.huawei.com>
References: <149029682927.22415.11722241596169339182@ietfa.amsl.com>
In-Reply-To: <149029682927.22415.11722241596169339182@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.150.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.58D44E1F.00F6, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0afbde728a7e0f1dbe61aa7f651780fa
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/7bEAFBRZlLYE1vgv5O2r-2x0lg8>
Subject: Re: [trill] Review of draft-ietf-trill-p2mp-bfd-04
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: Thu, 23 Mar 2017 22:37:24 -0000

Hi Carlos,

1. Yes. Section 5 rather than Seciton 4 is relevant. The last paragraph of the Intro will be updated to reflect this.

2. OK. The text will be updated.

Thanks,
Mingui
________________________________________
From: Carlos Pignataro [cpignata@cisco.com]
Sent: Friday, March 24, 2017 3:20
To: rtg-dir@ietf.org
Cc: draft-ietf-trill-p2mp-bfd.all@ietf.org; ietf@ietf.org; trill@ietf.org
Subject: Review of draft-ietf-trill-p2mp-bfd-04

Reviewer: Carlos Pignataro
Review result: Has Nits

Hi,

This is a short yet well written document. Looks really good. Just a
couple of small questions/comments:

1. It's not clear exactly what from RFC 7175 is being updated by
Section 4. This is based on the last paragraph of the Intro, yet
Section 5 also seems relevant to that update.
2. In the IANA COnsiderations, it would be useful to explicitly list
that the "RBridge Channel Protocols" registry is part of the
"Transparent Interconnection of Lots of Links (TRILL) Parameters"

Thanks,

Carlos Pignataro.