Re: [Idr] WGLC is for "BGP Router Capabilities Attribute” [was: Re: WG LC for draft-ietf-idr-entropy-09 (8/29 to 9/12/2023)]

Robert:

This draft-ietf-idr-entropy-09 text allows new features to be added to this attribute.  Are you suggesting that this signal the capability for handling different forms next-hops in the NLRI?   This seems to be within scope of this attribute as a capability.

draft-kaliraj-idr-multinexthop-attribute-09 suggests including multiple nexthops in an attribute (see section 5).  It removes the Next Hop from the AFI/SAFI NLRI into a attribute.   Are you suggesting we merge the draft-kaliraj-idr-multinexthop-attribute encoding also be merged into the variable Next Hop field?

Please let me know if I understand your proposal.

If I do understand your proposal, do you have a specific proposal for an encoding format?

Sue

From: Robert Raszuk <robert@raszuk.net>
Sent: Thursday, September 7, 2023 4:02 PM
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: John Scudder <jgs=40juniper.net@dmarc.ietf.org>; idr@ietf.org; Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] WGLC is for "BGP Router Capabilities Attribute” [was: Re: WG LC for draft-ietf-idr-entropy-09 (8/29 to 9/12/2023)]

Hi Jeff,  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌
External (robert@raszuk.net<mailto:robert@raszuk.net>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tL2JhZDY0MGZmOTFmMzk0ZTEwNTA4ZmY2MmM2NWZkNWI2LzE2OTQxMTY5NTMuOQ==#key=2db8255c23a4677e681cdcd9e5bf5793>  FAQ<https://www.godaddy.com/help/report-email-with-advanced-email-security-40813>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>

Hi Jeff,

Speaking as an individual contributor, I also think next-hop-capabilit(ies) better reflects the proposal.

IMHO it would be the preferred title and name of the draft.

But then we have the (multi) next hop attribute coming up as well.

Shouldn't that work be combined ?

That said, I think painting each service route with the same attribute(s) is a bit wasteful design at best.

It does seem to me like sooner or later we would benefit from separate next hop state/description SAFI especially for the applications which use BGP recursion and resolve BGP service routes via another BGP AF (example BGP-LU), but even if the next hop reachability is carried in IGPs as we do not want to pollute IGP link state flooding too much.

Thx,
R.

> On Sep 7, 2023, at 2:35 PM, John Scudder <jgs=40juniper.net@dmarc.ietf.org<mailto:40juniper.net@dmarc.ietf.org>> wrote:
>
> Hi All,
>
> Robert Raszuk pointed out [1] that the draft filename (draft-ietf-idr-entropy) doesn’t clearly reflect the title and scope of the spec — the title is "BGP Router Capabilities Attribute”, and indeed the ELCv3/Entropy Label Capability is only one example of a capability the RCA can contain.
>
> As a reminder, we ended up with this filename because the draft is a merger of draft-ietf-idr-next-hop-capability and draft-ietf-idr-entropy-label, and that was the one we picked to merge down to. In retrospect maybe we should have merged down to draft-ietf-idr-next-hop-capability instead, or even picked a third, new, filename.
>
> I’ve adjusted the subject line to spotlight this fact, because Robert expressed concern that WG participants might not realize what the WGLC is about, and I promised [2] to follow up.
>
> Thanks,
>
> —John
>
> [1] https://mailarchive.ietf.org/arch/msg/idr/lEabkTb0VjymshotgF8Ej29vVkM/<https://shared.outlook.inky.com/link?domain=mailarchive.ietf.org&t=h.eJxFjbsOgyAYhV_FMDf84oVIJxe7dWvcQUAULw2gSW367pUuXc5wLt95o81N6JogE8LTXwFmPkzcdWbYFR5U0Hh1PUQDZt_DIB1MDRf2IdJ2fM3erKG_Vc2Ysb21d0CXBNmIW1Q4hyQtK8pIBt5wp3y9yMPgbp1BcEmLVGtGdM4KdfbSSmuadbTUshQUCGUFOaXMMYtQFaFuFcqF2nF_bBafFzGRv-Rvfb59n0JL.MEYCIQCwTE2S9e9A6nJcqB4E3EzW7q6c0N8JbnFii6looHlv2wIhAJ_QoKaTP8BqElljOXUtM0cxDNyxUKMeeqFR0lC2Nwoe>
> [2] https://mailarchive.ietf.org/arch/msg/idr/5XchsuIzrj5Hb4a8Ju2zG7jI_kM/<https://shared.outlook.inky.com/link?domain=mailarchive.ietf.org&t=h.eJxFjTsPgjAUhf-K6Wx6KdBKmdx8JO5uptDWFgTMbXHA-N-lLi5nOI_vvMmMD1JviIvxGWqAQfmHwtb5l6HeREsnvEMyYAh38BqBX1sX5tOCHT82parOc74cdt3p1l-AbDekT7jRxHXIMl4JyXIITqEJ-1EvjrbTAI3SosyslcwWsjRrL6usFXkruNW8EcCELNkqvKAyQU2C4tQYjHtUYZl7ul6kRP-Sv_X5Aj4WQd0.MEQCIDL9WfE9mc2wqzryvlfAA2C0zaAUSrhM77j_3VoiaGtTAiBfmuKKFB6BBejYEjoMU7VdRWg1Mi7Rbf2CQkOXa8-Xmw>
>

_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr<https://shared.outlook.inky.com/link?domain=www.ietf.org&t=h.eJxFjUEOgyAURK9iWDd8USHiyqug8CtRoQEMiU3vXuimm1nMvJl5kyscZGrIltIrTgA5Z2pNQurDE05lj1M5OGxM1qEHqwN5NGSvDWdSYVjLRyFZB3FTwcTZ6Xujqz9hUVoMLaJk2MvBFK4dEUW3Co6aLwKYkAMrwnsq66ipo8EvJqQ5qHhfOy0XNdG_5G99vtK2OIM.MEUCIAbZgmXAyuLrWpLP8CwkH_f1RMUf4Ci469XblW0CJ53RAiEA0s03RusboXivVD5pWTSk1XC55yzz5066pQ6jGfqi5Ig>