Re: [trill] Eric Rescorla's No Objection on draft-ietf-trill-p2mp-bfd-08: (with COMMENT)

"Zhangmingui (Martin)" <zhangmingui@huawei.com> Mon, 22 January 2018 09:40 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 13C8E124B17; Mon, 22 Jan 2018 01:40:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.231
X-Spam-Level:
X-Spam-Status: No, score=-4.231 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, 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 AlH9j4xNtA2B; Mon, 22 Jan 2018 01:40:55 -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 4A38D1243F6; Mon, 22 Jan 2018 01:40:55 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id C64C640001311; Mon, 22 Jan 2018 09:40:50 +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; Mon, 22 Jan 2018 09:40:52 +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; Mon, 22 Jan 2018 17:40:49 +0800
From: "Zhangmingui (Martin)" <zhangmingui@huawei.com>
To: Eric Rescorla <ekr@rtfm.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-trill-p2mp-bfd@ietf.org" <draft-ietf-trill-p2mp-bfd@ietf.org>, Susan Hares <shares@ndzh.com>, "trill-chairs@ietf.org" <trill-chairs@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: Eric Rescorla's No Objection on draft-ietf-trill-p2mp-bfd-08: (with COMMENT)
Thread-Index: AQHTkISu2oJGZ9NlbEWr9okTy4cPxaN/qHCQ
Date: Mon, 22 Jan 2018 09:40:48 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7AAFAF80F@NKGEML515-MBX.china.huawei.com>
References: <151629775024.3841.11679795774117326021.idtracker@ietfa.amsl.com>
In-Reply-To: <151629775024.3841.11679795774117326021.idtracker@ietfa.amsl.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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/zZyWYn0ws6kzs1pGDhDgJBn9F7k>
Subject: Re: [trill] Eric Rescorla's No Objection on draft-ietf-trill-p2mp-bfd-08: (with COMMENT)
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: Mon, 22 Jan 2018 09:40:57 -0000

Hi Eric,

Thanks for your review. When the referred document mentions Section 6.7, it actually points to the Section 6.7 of RFC5880.

Thanks,
Mingui

> -----Original Message-----
> From: Eric Rescorla [mailto:ekr@rtfm.com]
> Sent: Friday, January 19, 2018 1:49 AM
> To: The IESG
> Cc: draft-ietf-trill-p2mp-bfd@ietf.org; Susan Hares; trill-chairs@ietf.org;
> shares@ndzh.com; trill@ietf.org
> Subject: Eric Rescorla's No Objection on draft-ietf-trill-p2mp-bfd-08: (with
> COMMENT)
> 
> Eric Rescorla has entered the following ballot position for
> draft-ietf-trill-p2mp-bfd-08: No Objection
> 
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-trill-p2mp-bfd/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I'm hoping this can be resolved quickly, as it's probably just a missing cite. If it
> turns out that there's actually missing content, this may turn into a DISCUSS.
> 
>    Multipoint BFD provides its own authentication but does not provide
>    encryption (see Security Considerations in [I-D.ietf-bfd-
>    multipoint]). As specified in this document, the point-to-multipoint
> 
> I skimmed the reference here, but wasn't able to figure out what the
> authentication was. In particular, the document says:
> 
>       If the A bit is set, the packet MUST be authenticated under the
>       rules of section 6.7, based on the authentication type in use
>       (bfd.AuthType.)  This may cause the packet to be discarded.
> 
> But there is no 6.7. So, this makes me worry that I don't understand any of this.
>