IETF Logo Mail Archive

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

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Wed, 16 March 2022 11:01 UTC

Return-Path: <giuseppe.fioccola@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 450423A17A0 for <idr@ietfa.amsl.com>; Wed, 16 Mar 2022 04:01:11 -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_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 RmcvxiXqEEgJ for <idr@ietfa.amsl.com>; Wed, 16 Mar 2022 04:01: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 8CA2A3A179E for <idr@ietf.org>; Wed, 16 Mar 2022 04:01:06 -0700 (PDT)
Received: from fraeml711-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KJS2R16Kfz67KPY; Wed, 16 Mar 2022 18:59:11 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 16 Mar 2022 12:01:03 +0100
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2375.024; Wed, 16 Mar 2022 12:01:03 +0100
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Susan Hares <shares@ndzh.com>, "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: Adg0iU/LdOzWENOQQCinCgHK9waz6gElbpVg
Date: Wed, 16 Mar 2022 11:01:02 +0000
Message-ID: <8b278c3e8062472fa0235b606e3a075d@huawei.com>
References: <00ca01d8348c$8b05d270$a1117750$@ndzh.com>
In-Reply-To: <00ca01d8348c$8b05d270$a1117750$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.194.106]
Content-Type: multipart/alternative; boundary="_000_8b278c3e8062472fa0235b606e3a075dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/gVwx3lSHWlAzuJcy3Z3ygYYepqE>
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: Wed, 16 Mar 2022 11:01:12 -0000

Dear Sue, All,
I support the adoption of draft-wang-idr-bgp-ifit-capabilities. It provides a solution for IFIT capability advertisement in order to communicate the supported and unsupported IFIT methods though BGP. It will therefore help with the IFIT deployment.
Regarding the relation with draft-ietf-idr-sr-policy-ifit, I think that the two drafts can be considered independent. Indeed draft-wang-idr-bgp-ifit-capabilities aims to define a general approach for IFIT capability advertisement for IPv4/IPv6 networks. While draft-ietf-idr-sr-policy-ifit applies specifically to SR Policy and, as an extension of draft-ietf-idr-segment-routing-te-policy, it allows to distribute SR policies carrying IFIT information and provides the configurable knobs of the supported IFIT methods at candidate path level.

Regards,

Giuseppe

From: Idr <idr-bounces@ietf.org> On Behalf Of Susan Hares
Sent: Thursday, March 10, 2022 3:39 PM
To: idr@ietf.org
Subject: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)

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

v2.23.0 | Report a Bug | By Email