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)

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 13 October 2022 11:12 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 9DEF9C14CE3F for <idr@ietfa.amsl.com>; Thu, 13 Oct 2022 04:12:54 -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, 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 I3Z-rYHEi6Xz for <idr@ietfa.amsl.com>; Thu, 13 Oct 2022 04:12:52 -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 569A0C14CF11 for <idr@ietf.org>; Thu, 13 Oct 2022 04:12:52 -0700 (PDT)
Received: from fraeml740-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Mp6Jx6bbdz687S2; Thu, 13 Oct 2022 19:11:13 +0800 (CST)
Received: from kwepemi100017.china.huawei.com (7.221.188.163) by fraeml740-chm.china.huawei.com (10.206.15.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Thu, 13 Oct 2022 13:12:49 +0200
Received: from kwepemi500017.china.huawei.com (7.221.188.110) by kwepemi100017.china.huawei.com (7.221.188.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Thu, 13 Oct 2022 19:12:47 +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; Thu, 13 Oct 2022 19:12:47 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Gert Doering <gert@space.net>
CC: Susan Hares <shares@ndzh.com>, "idr@ietf. org" <idr@ietf.org>, "Van De Velde, Gunter \\(Nokia - BE/Antwerp\\)" <gunter.van_de_velde@nokia.com>, "duzongpeng@foxmail.com" <duzongpeng@foxmail.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+L4v0QKq/sNhAFMI0oAAGS9aIA==
Date: Thu, 13 Oct 2022 11:12:47 +0000
Message-ID: <39a075e7afd04d94b324075a5c696b84@huawei.com>
References: <BYAPR08MB4872EEE329BDDDCC0F387B17B3559@BYAPR08MB4872.namprd08.prod.outlook.com> <tencent_E2B151AFE51150823EF1EC847C656D5E6A08@qq.com> <Y0e360YJv/edt6pz@Space.Net>
In-Reply-To: <Y0e360YJv/edt6pz@Space.Net>
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/5Qyfrg8-8DLV2C5A_jSKuLDM3_U>
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: Thu, 13 Oct 2022 11:12:54 -0000

Hi Gert,

Thanks for your comments. 

The proposed mechanism can be used to control the distribution of BGP routes to a set of BGP nodes in the network. One specific node is a possible use case, while not the only one. 

Best regards,
Jie

> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Gert Doering
> Sent: Thursday, October 13, 2022 3:02 PM
> To: duzongpeng@foxmail.com
> Cc: Susan Hares <shares@ndzh.com>; idr@ietf. org <idr@ietf.org>; 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,
> 
> On Tue, Oct 11, 2022 at 03:22:07PM +0800, duzongpeng@foxmail.com
> wrote:
> >     I support the adoption of the draft. It is useful when we need notify
> some specific node in the network by using BGP.
> 
> BGP is really not a signalling tool "send information to one specific node".
> 
> Gert Doering
>         -- NetMaster
> --
> have you enabled IPv6 on something today...?
> 
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard,
> Michael Emmer
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A.
> Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email