Alexander Zubkov via routing-wg wrote on 22/10/2025 20:55:
James, thanks for raising up this topic with BGP Origin attribute. Have
you thought already about making an RFC draft to not consider Origin
attribute in the BGP decision process? It seems to be a reasonable next
step.
PS. And maybe Router ID as well. :)
as you mention updates to the BGP spec, rfc4271bis is in progress at the
moment:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp4-rfc4271bis/
The authors have indicated that this a refinement and consolidation
internet draft, not a change in how bgp works (i.e. changes to the FSM
were explicitly declared out of scope). I'm not sure whether the authors
would be interested in updating the tiebreaker specification:
https://datatracker.ietf.org/doc/html/rfc4271#section-9.1.2.2
Nick
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
