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)

Yisong Liu <liuyisong@chinamobile.com> Tue, 11 October 2022 12:20 UTC

Return-Path: <liuyisong@chinamobile.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 40033C14F740 for <idr@ietfa.amsl.com>; Tue, 11 Oct 2022 05:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 QOo9vUBKC1_G for <idr@ietfa.amsl.com>; Tue, 11 Oct 2022 05:20:21 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id D69DEC1594AF for <idr@ietf.org>; Tue, 11 Oct 2022 05:20:19 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.15]) by rmmx-syy-dmz-app11-12011 (RichMail) with SMTP id 2eeb63455f81c29-c7e40; Tue, 11 Oct 2022 20:20:17 +0800 (CST)
X-RM-TRANSID: 2eeb63455f81c29-c7e40
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCCPC (unknown[10.1.6.52]) by rmsmtp-syy-appsvr08-12008 (RichMail) with SMTP id 2ee863455f7f2b4-7b347; Tue, 11 Oct 2022 20:20:17 +0800 (CST)
X-RM-TRANSID: 2ee863455f7f2b4-7b347
From: Yisong Liu <liuyisong@chinamobile.com>
To: shares@ndzh.com, idr@ietf.org
Cc: jie.dong@huawei.com, gunter.van_de_velde@nokia.com, 'Zhuangshunwan' <zhuangshunwan@huawei.com>
References: <1479ad75fcff498eb7b8e3564070fc09@huawei.com> <01b601d8dd4a$55c45c00$014d1400$@chinamobile.com> <98a9588b67ab4b86bdc377d60f099da8@huawei.com>
In-Reply-To: <98a9588b67ab4b86bdc377d60f099da8@huawei.com>
Date: Tue, 11 Oct 2022 20:20:15 +0800
Message-ID: <02a801d8dd6b$d26938e0$773baaa0$@chinamobile.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02A9_01D8DDAE.E08DB160"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdjdahfUyqTfoFOVQvO4PPmtCLlejg==
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/QKfTRWH9SpOwbOxfxdSE3l4X-_Y>
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: Tue, 11 Oct 2022 12:20:25 -0000

Hi Sue and WG,

 

I've read this document and support the adoption of this draft. It provides
a generic mechanism of designating the target nodes of the routing
information in the centralized control use-cases.

 

The reply to the following 3 questions are as follows:

1) Yes, A similar mechanism has been used in BGP SR Policy. However, the
mechanism applies only to the BGP SR Policy address family and does not
apply to the BGP Flowspec address family. We need a mechanism that can be
applied to the other BGP address families.

2) I think no conflicts have been identified.

3) No. I think the current text is enough for a base of a WG's draft.

 

Best Regards

Yisong

 

From: Susan Hares [mailto:shares@ndzh.com] 
Sent: Wednesday, September 28, 2022 1:30 AM
To: idr@ietf.org <mailto:idr@ietf.org> 
Cc: Dongjie (Jimmy) <jie.dong@huawei.com <mailto:jie.dong@huawei.com> >; Van
De Velde, Gunter (Nokia - BE/Antwerp) <gunter.van_de_velde@nokia.com
<mailto:gunter.van_de_velde@nokia.com> >; Zhuangshunwan
<zhuangshunwan@huawei.com <mailto: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