Ketan -

I have reviewed the content of this draft and it seems accurate and 
comprehensive as regards the defined scope.

I support WG adoption of this draft.

   Les


> -----Original Message-----
> From: Ketan Talaulikar <[email protected]>
> Sent: Friday, October 18, 2024 2:07 AM
> To: idr@ietf. org <[email protected]>
> Cc: lsr <[email protected]>
> Subject: [Lsr] BGP-LS Flex Algo Extensions draft submitted to catch up with 
> LSR
> work
> 
> Hello IDR WG,
> 
> We've posted a "routine" BGP-LS draft that includes extensions for
> conveying some of the more recent Flex Algo IGP extensions defined by
> the LSR WG into BGP-LS.
> 
> https://datatracker.ietf.org/doc/draft-hegdearavind-idr-bgp-ls-flex-algo-ext/
> 
> These are extensions beyond the base Flex Algo spec which was covered
> by the BGP-LS RFC9351
> 
> This document catches up with the following LSR WG documents:
> - IP Flex Algo: https://datatracker.ietf.org/doc/rfc9502/
> - https://datatracker.ietf.org/doc/draft-ietf-lsr-flex-algo-bw-con/
> - 
> https://datatracker.ietf.org/doc/draft-ietf-lsr-igp-flex-algo-reverse-affinity/
> 
> Request the WG to review and provide feedback/comments. Also including
> LSR WG.
> 
> Given that these are straightforward BGP-LS extensions that are
> aligned with and in continuation of RFC9552 and RFC9351, we would like
> to ask for IDR WG adoption. We can also present this during the IDR
> session at IETF 121 if required and if time allows.
> 
> Thanks,
> Ketan (on behalf of all co-authors)
> 
> ---------- Forwarded message ---------
> From: <[email protected]>
> Date: Fri, Oct 18, 2024 at 2:11 PM
> Subject: New Version Notification for
> draft-hegdearavind-idr-bgp-ls-flex-algo-ext-00.txt
> To: Aravind Babu MahendraBabu <[email protected]>, Bruno Decraene
> <[email protected]>, Ketan Talaulikar <[email protected]>,
> Peter Psenak <[email protected]>, Shraddha Hegde
> <[email protected]>
> 
> 
> A new version of Internet-Draft
> draft-hegdearavind-idr-bgp-ls-flex-algo-ext-00.txt has been successfully
> submitted by Ketan Talaulikar and posted to the
> IETF repository.
> 
> Name:     draft-hegdearavind-idr-bgp-ls-flex-algo-ext
> Revision: 00
> Title:    Advertising Flexible Algorithm Extensions in BGP Link-State
> Date:     2024-10-18
> Group:    Individual Submission
> Pages:    16
> URL:      https://www.ietf.org/archive/id/draft-hegdearavind-idr-bgp-ls-flex-
> algo-ext-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-hegdearavind-idr-bgp-ls-flex-
> algo-ext/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-hegdearavind-idr-bgp-
> ls-flex-algo-ext
> 
> 
> Abstract:
> 
>    Flexible Algorithm is a solution that allows some routing protocols
>    (e.g., OSPF and IS-IS) to compute paths over a network based on user-
>    defined (and hence, flexible) constraints and metrics.  The
>    computation is performed by routers participating in the specific
>    network in a distributed manner using a Flexible Algorithm
>    Definition.  This Definition is provisioned on one or more routers
>    and propagated through the network by OSPF and IS-IS flooding.
> 
>    BGP Link-State (BGP-LS) enables the collection of various topology
>    information from the network.  BGP-LS supports the advertisement of
>    Flexible Algorithm Definition and other Flexible Algorithm related
>    advertisements as a part of the topology information from the
>    network.  This document specifies the advertisement of further
>    Flexible Algorithm related extensions in BGP-LS.
> 
> 
> 
> The IETF Secretariat
> 
> _______________________________________________
> Lsr mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
Lsr mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to