Hi Alexander,

In my head, I had explicitly excluded the idea of taking this to the IETF. The 
reason beind that I can see all manor of problems arising from either trying to 
deprecate the attributes and/or trying to modify the FSM, during the transition 
period as networks upgrade their BGP implementations at different rates.

Networks will come to different conclusions about which path is the best path. 
Within a large network it will differ within a single network, as it takes time 
to rollout the BGP upgrade. There could be forwaridng loops too.

Getting IETF approval, then getting vendor adoption, then getting most of the 
major networks to roll it out to reach critical mass; I can see that being a 10 
year project.

If someone really wants to take this to the IETF, probably the path of lesser 
resistance would be to get a new BCOP published which recommends everyone 
bleach the origin type to IGP to implicitly deprecate the attribute, and advise 
networks do things that avoid the FSM getting as far down the process as router 
ID.

With kind regards,
James Bensley (he/him)
________________________________
From: Alexander Zubkov <[email protected]>
Sent: 22 October 2025 21:55
To: James Bensley <[email protected]>; [email protected] <[email protected]>
Subject: bgp origin attribute

⚠️ Caution: This email originated from outside of your organization. Do not 
click on links or open attachments unless you recognize the sender and know the 
content is safe.
Hi James and all,

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. :)

Regards,
Alexander Zubkov
Qrator Labs
[CompanySignature]
Inter..link GmbH | Boxhagener Straße 80, 10245 Berlin, Germany | Managing 
Directors: Marc Korthaus, Theo Voss | Commercial Register: Amtsgericht 
Charlottenburg, HRB 138876 | VAT ID: DE281288887 | Email: 
[email protected]<mailto:[email protected]> | Web: inter.link<https://inter.link>
-----
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/

Reply via email to