[Idr] 答复: draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019) -

"Chengli (Cheng Li)" <chengli13@huawei.com> Sat, 26 October 2019 21:00 UTC

Return-Path: <chengli13@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B53E120096 for <idr@ietfa.amsl.com>; Sat, 26 Oct 2019 14:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 r2jTVWN8ORWV for <idr@ietfa.amsl.com>; Sat, 26 Oct 2019 14:00:14 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 23059120033 for <idr@ietf.org>; Sat, 26 Oct 2019 14:00:14 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id A03766E53B9F8E8643E8 for <idr@ietf.org>; Sat, 26 Oct 2019 22:00:10 +0100 (IST)
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 26 Oct 2019 22:00:09 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.172]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0439.000; Sun, 27 Oct 2019 05:00:01 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: Susan Hares <shares@ndzh.com>, 'idr wg' <idr@ietf.org>
CC: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
Thread-Topic: [Idr] draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019) -
Thread-Index: AdWLQaI/WXcsqjEDROatNbmYd62yMQA/BlTA
Date: Sat, 26 Oct 2019 21:00:00 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB02763C75@dggeml529-mbx.china.huawei.com>
References: <00f401d58b43$aa968ac0$ffc3a040$@ndzh.com>
In-Reply-To: <00f401d58b43$aa968ac0$ffc3a040$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.193.103]
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB02763C75dggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Xy_DEq_ua_SZVUCZPTge_cT7tNI>
Subject: [Idr] =?gb2312?b?tPC4tDogIGRyYWZ0LWxpLWlkci1mbG93c3BlYy1ycGQt?= =?gb2312?b?MDUudHh0IC0gV0cgQWRvcHRpb24gY2FsbCAoMTAvMTQgdG8gMTAvMjgvMjAx?= =?gb2312?b?OSkgLQ==?=
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Oct 2019 21:00:17 -0000

Hi WG,

After reading the document, I think it is useful to distribute routing policy in BGP, and I think it is ready for WG adoption.

Well,  I have some comments and questions:


0.  Section 3, Problem statement, may add more text to specify


1.In #section-3.1<https://tools.ietf.org/html/draft-li-idr-flowspec-rpd-05#section-3.1> and 3.2, P node should be illustrated in the figure, I do not find it in the figure. Also, it is a little bit hard for me to get what is inbound and outbound from the figure. May add more text to clarify?

2. Section 4.1,

Distinguisher:  4 octet value, it should be 4 octets or 4-octet?



3. Section 4.1, may add reference to 0?



When receiving a BGP UPDATE message, a BGP speaker processes it only

   if the peer IP address in the NLRI is the IP address of the BGP

   speaker or 0.



Best Regards,

Cheng


发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Susan Hares
发送时间: 2019年10月25日 22:51
收件人: 'idr wg' <idr@ietf.org>
主题: Re: [Idr] draft-li-idr-flowspec-rpd-05.txt - WG Adoption call (10/14 to 10/28/2019) -

Greetings:

The WG Adoption call for daft-li-idr-flowspec-rpd-05.txt need additional support for adoption.   I encourage the authors to make sure those wishing to make comments on this draft to do so over the weekend.

This draft deploys the passing of BGP policy in a new AFI/SAFI and Wide communities.   At this point, my understanding from the email is that mechanisms eases the configuration burden in some networks.

Are there any operators who are concerned that this mechanism (AFI/SAFI + Wide Communities), contains information that will leak into their network by accident?   Or will the AFI/SAFI + WIDE communities provide a clear delineation between a group of networks who support this feature and those who do not.

Thank you, Sue Hares