[bess] Re: [Idr] Do we need yet another link bandwidth community?

[Ketan Talaulikar <[e-mail]>]

Hi Reshma,

Glad to see that we are in agreement to avoid another LBW extcomm.

One of the points that I was trying to make is that we don't have a "single
source of truth" if we look at this more holistically from BGP protocol
perspective. We have two that have been implemented and deployed (even if
for different address families).

Let's work this out keeping the full and broader picture in mind.

Thanks,
Ketan

On Wed, 24 Jul, 2024, 6:00 pm Reshma Das, <[e-mail]> wrote:

> Hi Ketan,
>
>
>
> I agree we don’t need yet another new draft to carry LBW community.
>
>
>
> As we know the base draft(draft-ietf-idr-link-bandwidth) is being revived
> to support both transitive and non-transitive use cases. This was presented
> in Mondays IDR session: (https://www.youtube.com/watch?v=ePPCAPOSQfM)
>
>
>
> It is worth updating the base draft as a single source of truth to
> accommodate all use cases. That provides the most interop.
>
>
>
> Since this is an effort initiated by IDR chairs, you are more than welcome
> to contribute to this effort as part the IDR WG.
>
>
>
> Thanks & Regards,
> Reshma Das
>
>
>
>
>
>
>
> Juniper Business Use Only
>
> *From: *Ketan Talaulikar <[e-mail]>
> *Date: *Wednesday, July 24, 2024 at 2:57 PM
> *To: *idr@ietf. org <[e-mail]>,
> [e-mail] <
> [e-mail]>
> *Cc: *BESS <[e-mail]>
> *Subject: *[Idr] Do we need yet another link bandwidth community?
>
> *[External Email. Be cautious of content]*
>
>
>
> Hello All,
>
>
>
> Checking on the need for draft-li-idr-link-bandwidth-ex when we already
> have the EVPN Link Bandwidth Extended Community
> (draft-ietf-bess-evpn-unequal-lb). Is it because of the name containing
> "EVPN" or am I missing something?
>
>
>
> If it is just the name, I hope we still have the time to change it in
> draft-ietf-bess-evpn-unequal-lb?
>
>
>
> We already have 2 types (ignoring the transitive/non-transitive variants)
> and I hope we can avoid the need for a third one ...
>
>
>
> Thanks,
>
> Ketan
>
>
>