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

"Dongjie (Jimmy)" <jie.dong@huawei.com> Sat, 08 October 2022 10:10 UTC

Return-Path: <jie.dong@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 2F978C14CF0B for <idr@ietfa.amsl.com>; Sat, 8 Oct 2022 03:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 U2CWE___MXFz for <idr@ietfa.amsl.com>; Sat, 8 Oct 2022 03:10:18 -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 9D424C14F73A for <idr@ietf.org>; Sat, 8 Oct 2022 03:10:18 -0700 (PDT)
Received: from fraeml742-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Ml19C3clTz67PFb; Sat, 8 Oct 2022 18:08:47 +0800 (CST)
Received: from kwepemi500018.china.huawei.com (7.221.188.213) by fraeml742-chm.china.huawei.com (10.206.15.223) 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:10:15 +0200
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by kwepemi500018.china.huawei.com (7.221.188.213) 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 18:10:13 +0800
Received: from kwepemi500017.china.huawei.com ([7.221.188.110]) by kwepemi500017.china.huawei.com ([7.221.188.110]) with mapi id 15.01.2375.031; Sat, 8 Oct 2022 18:10:13 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>, 'Susan Hares' <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "'Van De Velde, Gunter (Nokia - BE/Antwerp)'" <gunter.van_de_velde@nokia.com>
Thread-Topic: [Idr] draft-dong-idr-node-target-ext-comm-05.txt - WG Adoption and IPR call (9/27 to 10/11/2022)
Thread-Index: AdjSloXuKBSDw00XRRGZ9oJo+L4v0QIHz4UAABHIxUA=
Date: Sat, 08 Oct 2022 10:10:13 +0000
Message-ID: <6a1632e9211049d3b7929f08c57675e8@huawei.com>
References: <BYAPR08MB4872EEE329BDDDCC0F387B17B3559@BYAPR08MB4872.namprd08.prod.outlook.com> <0d7901d8daf8$d2ab5ce0$780216a0$@tsinghua.org.cn>
In-Reply-To: <0d7901d8daf8$d2ab5ce0$780216a0$@tsinghua.org.cn>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.66]
Content-Type: multipart/alternative; boundary="_000_6a1632e9211049d3b7929f08c57675e8huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/6jl_boBPpLz_YPSxEh76K_ifa9s>
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 10:10:20 -0000

Hi Aijun,

Thanks a lot for your support and comments.

In the previous version of this draft, the default behavior of RR is similar to what you suggested. Based on some comments received, the text in current version simplify the default behavior of RR, and allows to enable this function in a flexible manner. That said, the refinement of the default behavior can be discussed further as the next step.

Hope this helps.

Best regards,
Jie

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Aijun Wang
Sent: Saturday, October 8, 2022 5:32 PM
To: 'Susan Hares' <shares@ndzh.com>; idr@ietf.org
Cc: 'Van De Velde, Gunter (Nokia - BE/Antwerp)' <gunter.van_de_velde@nokia.com>
Subject: Re: [Idr] draft-dong-idr-node-target-ext-comm-05.txt - WG Adoption and IPR call (9/27 to 10/11/2022)

Hi, All:

Support for its adoption.

One comments for the current contents of the draft:
Should the default behavior of RR be also constrained by the Node Targets that associated with the BGP Update?  That is to say, if there is no special configurable policy, the RR should check the Node Targets; if there is no other Node Targets, then it can reflect the Update to all its peers.
Such approach will be consistent with the behavior of ASBR.


Best Regards

Aijun Wang
China Telecom

From: idr-bounces@ietf.org<mailto:idr-bounces@ietf.org> <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Susan Hares
Sent: Wednesday, September 28, 2022 1:30 AM
To: idr@ietf.org<mailto:idr@ietf.org>
Cc: Van De Velde, Gunter (Nokia - BE/Antwerp) <gunter.van_de_velde@nokia.com<mailto:gunter.van_de_velde@nokia.com>>
Subject: [Idr] 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