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

[Aditya Kaul <[e-mail]>]

I support the WG adoption of this draft.

Regards,
Aditya

From: Tony Przygienda <[e-mail]>
Date: Sunday, 14 July 2024 at 15:47
To: Julian Lucek <jlucek=[e-mail]>
Cc: Susan Hares <[e-mail]>, [e-mail] <[e-mail]>
Subject: [Idr] Re: WG Adoption for draft-ssangli-idr-bgp-generic-metric-00 (7/9 to 7/23/2024)
support. I think my reasoning and suggestions happened on an earlier thread already

-- tony


On Sat, Jul 13, 2024 at 8:02 PM Julian Lucek <jlucek=[e-mail]<mailto:[e-mail]>> wrote:
I support working group adoption of the draft

Thanks

Julian



Juniper Business Use Only

________________________________
From: Colby Barth <[e-mail]<mailto:[e-mail]>>
Sent: Saturday, July 13, 2024 6:34 PM
To: Susan Hares <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Subject: [Idr] Re: WG Adoption for draft-ssangli-idr-bgp-generic-metric-00 (7/9 to 7/23/2024)

[External Email. Be cautious of content]

I support WG adoption.

Cheers,

—Colby


On Jul 9, 2024, at 11:56 AM, Susan Hares <[e-mail]<mailto:[e-mail]>> 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/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ssangli-idr-bgp-generic-metric/__;!!NEt6yMaO-gk!HeG4qeKRVi15MI-mJS_QGM9Pe4rlct_G-0q0v8o1j5Sj66EGur8VeathazFSG6A_x2QQ62BpgGYuXAPxdmYK$>

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 -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>

_______________________________________________
Idr mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>