[Idr] Re: WG Adoption for draft-ssangli-idr-bgp-generic-metric-00 (7/9 to 7/23/2024)

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 19 July 2024 09:32 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 0D860C151089 for <idr@ietfa.amsl.com>; Fri, 19 Jul 2024 02:32:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 XtxZnm3Cy3Ih for <idr@ietfa.amsl.com>; Fri, 19 Jul 2024 02:31:58 -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 91A45C14F70F for <idr@ietf.org>; Fri, 19 Jul 2024 02:31:58 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4WQPXV1R4bz6K5lK; Fri, 19 Jul 2024 17:30:02 +0800 (CST)
Received: from lhrpeml500004.china.huawei.com (unknown [7.191.163.9]) by mail.maildlp.com (Postfix) with ESMTPS id DE4ED140C98; Fri, 19 Jul 2024 17:31:55 +0800 (CST)
Received: from dggpemf500007.china.huawei.com (7.185.36.81) by lhrpeml500004.china.huawei.com (7.191.163.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 19 Jul 2024 10:31:55 +0100
Received: from kwepemf100006.china.huawei.com (7.202.181.220) by dggpemf500007.china.huawei.com (7.185.36.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 19 Jul 2024 17:31:52 +0800
Received: from kwepemf100006.china.huawei.com ([7.202.181.220]) by kwepemf100006.china.huawei.com ([7.202.181.220]) with mapi id 15.02.1544.011; Fri, 19 Jul 2024 17:31:52 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Ketan Talaulikar <ketant.ietf@gmail.com>, Susan Hares <shares@ndzh.com>
Thread-Topic: [Idr] Re: WG Adoption for draft-ssangli-idr-bgp-generic-metric-00 (7/9 to 7/23/2024)
Thread-Index: AQHa1scIATdBpKi9SUKq82n/4AgEP7H9zAqF
Date: Fri, 19 Jul 2024 09:31:52 +0000
Message-ID: <c68c70e8b6c3457aabb98dbe658d9a20@huawei.com>
References: <CO1PR08MB66110D7F5477ECFD5823CD98B3DB2@CO1PR08MB6611.namprd08.prod.outlook.com>,<CAH6gdPyHPpfnm7NBHoKejr=K0bdV5V6Ew_B8Qe4a-4X-XTcfEw@mail.gmail.com>
In-Reply-To: <CAH6gdPyHPpfnm7NBHoKejr=K0bdV5V6Ew_B8Qe4a-4X-XTcfEw@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.66.235]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: KRNMLVOU2TV2X2OJPXYTRE6JDWBHWHPL
X-Message-ID-Hash: KRNMLVOU2TV2X2OJPXYTRE6JDWBHWHPL
X-MailFrom: jie.dong@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "idr@ietf.org" <idr@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: WG Adoption for draft-ssangli-idr-bgp-generic-metric-00 (7/9 to 7/23/2024)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/wd1sEd5lhQWi8m9ksNT-SkX0QSo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Hi Sue, 

I am not aware of any IPR related to this document.

And I support the adoption as a coauthor. 

Best regards,
Jie

________________________________________
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Sent: Monday, July 15, 2024 22:50
To: Susan Hares
Cc: idr@ietf.org
Subject: [Idr] Re: WG Adoption for draft-ssangli-idr-bgp-generic-metric-00 (7/9 to 7/23/2024)

Hi Sue/All,

I am not aware of any IPR associated with this document.

Thanks,
Ketan


On Tue, Jul 9, 2024 at 8:58 AM Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:
This begins a 2 week WG Adoption  (7/9/2024 to 7/23/2024)
for draft-ssangli-idr-bgp-generic-metric-00
https://datatracker.ietf.org/doc/draft-ssangli-idr-bgp-generic-metric/

All authors should reply to this email with an IPR Statement.

This draft is a revision of the concepts in
draft-ssangli-idr-bgp-generic-metric-aigp-08,
But uses the NextHop Dependent Capability.

A short description of from the document may help you review the text.

   RFC7311 describes mechanism for carrying accumulated IGP cost across
   BGP domains however it limits to IGP-metric only.  There is a need to
   accumulate and propagate different types of metrics as it will aid in
   intent-based end-to-end path across BGP domains.  This document
   defines BGP extensions for Generic Metric sub-types that enable
   different types of metrics to be accumulated and carried in BGP.
   This is applicable when multiple domains exchange BGP routing
   information.


   This document proposes "Accumulated Metric" TLV in the Next-Hop

   Dependent Capability (NHC) attribute described in

   [I-D.ietf-idr-entropy-label] to carry the accumulated metric value

   for end-to-end path, hereby referred as AMetric.  The AMetric

   supports all the metric types defined in the IGP-Parameters metric-

   type registry.  Additionally this document provides procedures for

   computation and usage of accumulated generic metric value during the

   BGP best path computation.



In your comments, please consider:



1.  Does this mechanism solve the problem we have discussed in interims on AIGP metrics?

2.  Are there any downsides to using NHC?

3.  Do you support IDR working on this mechanism?



Cheerily, Sue Hares

_______________________________________________
Idr mailing list -- idr@ietf.org<mailto:idr@ietf.org>
To unsubscribe send an email to idr-leave@ietf.org<mailto:idr-leave@ietf.org>