IETF Logo Mail Archive

Re: [Idr] draft-dong-idr-node-target-ext-comm-05.txt - WG Adoption and IPR call (9/27 to 10/11/2022)

Lizhenbin <lizhenbin@huawei.com> Sat, 08 October 2022 04:09 UTC

Return-Path: <lizhenbin@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 390E7C1524D4 for <idr@ietfa.amsl.com>; Fri, 7 Oct 2022 21:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iWA5RzdohVN1 for <idr@ietfa.amsl.com>; Fri, 7 Oct 2022 21:09:28 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2108EC1524D2 for <idr@ietf.org>; Fri, 7 Oct 2022 21:09:28 -0700 (PDT)
Received: from fraeml705-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Mks9x0sgfz67ynR; Sat, 8 Oct 2022 12:08:53 +0800 (CST)
Received: from kwepemi500001.china.huawei.com (7.221.188.114) by fraeml705-chm.china.huawei.com (10.206.15.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.31; Sat, 8 Oct 2022 06:09:24 +0200
Received: from dggpemm500008.china.huawei.com (7.185.36.136) by kwepemi500001.china.huawei.com (7.221.188.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Sat, 8 Oct 2022 12:09:23 +0800
Received: from dggpemm500008.china.huawei.com ([7.185.36.136]) by dggpemm500008.china.huawei.com ([7.185.36.136]) with mapi id 15.01.2375.031; Sat, 8 Oct 2022 12:09:22 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>, Zhuangshunwan <zhuangshunwan@huawei.com>
Thread-Topic: draft-dong-idr-node-target-ext-comm-05.txt - WG Adoption and IPR call (9/27 to 10/11/2022)
Thread-Index: AQHY2su/hI2YF9mdD0OSP+t1z5om7w==
Date: Sat, 08 Oct 2022 04:09:22 +0000
Message-ID: <ac515f1e317943ef99d2dc0d967c4f39@huawei.com>
References: <BYAPR08MB4872EEE329BDDDCC0F387B17B3559@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872EEE329BDDDCC0F387B17B3559@BYAPR08MB4872.namprd08.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.153.179.20]
Content-Type: multipart/alternative; boundary="_000_ac515f1e317943ef99d2dc0d967c4f39huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_hmW9_gCKprU5TkVr0joXGB8AEM>
Subject: Re: [Idr] draft-dong-idr-node-target-ext-comm-05.txt - WG Adoption and IPR call (9/27 to 10/11/2022)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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, 08 Oct 2022 04:09:33 -0000

Hi All,
I support the adoption of the draft.  My answer to the questions is as follows:
1) Yes. It is useful to introduce a direct way to specify nodes to receive the BGP messages.
2) No.
3) No.


Best Regards,
Robin



From: Susan Hares [mailto:shares@ndzh.com]
Sent: Wednesday, September 28, 2022 1:30 AM
To: idr@ietf.org
Cc: Dongjie (Jimmy) <jie.dong@huawei.com>; Van De Velde, Gunter (Nokia - BE/Antwerp) <gunter.van_de_velde@nokia.com>; Zhuangshunwan <zhuangshunwan@huawei.com>
Subject: draft-dong-idr-node-target-ext-comm-05.txt - WG Adoption and IPR call (9/27 to 10/11/2022)

This begins a 2 week WG adoption and IPR call for draft-dong-idr-node-target-ext-comm-05.txt.
https://datatracker.ietf.org/doc/draft-dong-idr-node-target-ext-comm/

The authors should respond to this email with an IPR statement.

The WG should consider in their discussion:
1) Will this new  transitive extended community help
in operational networks?

2) What conflicts does this new Extended Community have
with other functions in general BGP route distribution or
VPNs (EVPN, IPVPN)?

3) do you have any concern about the text in the draft?

Cheerily, Sue

v2.23.0 | Report a Bug | By Email