IETF Logo Mail Archive

Re: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)

Zhuangshunwan <zhuangshunwan@huawei.com> Sat, 19 March 2022 01:24 UTC

Return-Path: <zhuangshunwan@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 3F8463A1517 for <idr@ietfa.amsl.com>; Fri, 18 Mar 2022 18:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 ZLlPJxAOFkjp for <idr@ietfa.amsl.com>; Fri, 18 Mar 2022 18:24:06 -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 0C8EF3A1514 for <idr@ietf.org>; Fri, 18 Mar 2022 18:24:06 -0700 (PDT)
Received: from fraeml742-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KL3551hpkz67bhc; Sat, 19 Mar 2022 09:22:01 +0800 (CST)
Received: from kwepeml100006.china.huawei.com (7.221.188.192) 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.24; Sat, 19 Mar 2022 02:24:00 +0100
Received: from kwepeml500004.china.huawei.com (7.221.188.141) by kwepeml100006.china.huawei.com (7.221.188.192) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Sat, 19 Mar 2022 09:23:59 +0800
Received: from kwepeml500004.china.huawei.com ([7.221.188.141]) by kwepeml500004.china.huawei.com ([7.221.188.141]) with mapi id 15.01.2308.021; Sat, 19 Mar 2022 09:23:59 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: Gyan Mishra <hayabusagsm@gmail.com>, Susan Hares <shares@ndzh.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)
Thread-Index: AQHYOoVvdOzWENOQQCinCgHK9waz6qzF6VIA
Date: Sat, 19 Mar 2022 01:23:59 +0000
Message-ID: <98ada82d97d340f298b65757121445ae@huawei.com>
References: <00ca01d8348c$8b05d270$a1117750$@ndzh.com> <CABNhwV2BXK9vf0tvoYprd8aYdFOe_6JHWAD2tmztC=0N9mYRpA@mail.gmail.com>
In-Reply-To: <CABNhwV2BXK9vf0tvoYprd8aYdFOe_6JHWAD2tmztC=0N9mYRpA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.152.178]
Content-Type: multipart/alternative; boundary="_000_98ada82d97d340f298b65757121445aehuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/vV-xZGXRwornAMR3eb3IvwY1ghw>
Subject: Re: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)
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, 19 Mar 2022 01:24:12 -0000

Hi Gyan,

Thanks for your support!
Regarding the new extended communities, we will add some clearer description based on comments and input from the working group.

Best Regards,
Shunwan

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Gyan Mishra
Sent: Friday, March 18, 2022 1:03 PM
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf.org
Subject: Re: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)

Hi Sue & WG

I Support WG adoption.

I believe this draft will help operators in distribution of IFIT telemetry  capabilities from tail to head end nodes.  The draft needs to describe more clearly what the new extended communities are to be used for.  Is is not clear the use.

The draft iFIT SR policy draft below is completely independent of this draft and is used to distribute SR policy containing IFIT information.

https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr-policy-ifit-03

I think this draft will help in the deployment of IFIT technology.

Kind Regards

Gyan

On Thu, Mar 10, 2022 at 9:39 AM Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:
Greeting:

This begins a 2 week WG Adoption call (3/10/2022 to 3/24/2022)
for draft-wang-idr-bgp-ifit-capabilities-04
https://datatracker.ietf.org/doc/draft-wang-idr-bgp-ifit-capabilities/

In your comments please consider if:

1) Do the additions to BGP (2 Communities and
TLV for next-hop-capability attribute)
help the distribute information regarding the  IFIT options
from tail (egress) nodes to head nodes (ingress)?

Are there any cases where these BGP
Communities should be removed or ignored?


2) Are the mechanisms (2 Communities and
attribute TLV) correctly specified?

3) How do these additions interaction with the
  With SR technology for IFIT described in
   draft-ietf-idr-sr-policy-ifit, and its
   use of RFC9012 (tunnel attributes)?

(Authors an example on how these
technologies work together or
 operate separately would be helpful).

4)  Will this addition help network operators
deploying IFIT technology?


Cheerily, Sue
_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr
--

[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mishra@verizon.com<mailto:gyan.s.mishra@verizon.com>

M 301 502-1347

v2.23.0 | Report a Bug | By Email