I have had some people tell me that they do or have used the origin type, as a gentler way to prioritise/deprioritise stuff than MED or AS prepending. If that is a good idea or not is a different questing, everyone has different contexts.
Also, we have to consider they we are all probably approaching this with our hats on, as operators in the DFZ. They may be some use case(s) for origin types inside other networking environments, away from the DFZ, we're note thinking off.
This is why I think it could be a good idea to not try and explicitly remove the attribute, but rather produce a BCP that recommends to either implicitly deprecate the attribute *specifically in the DFZ* (by manually setting all learned prefixes via a routing
policy, or an implementation knob to ignore origin type, or a knob which overwrites all learned origin types to a specified value, or whatever).
We could write a draft BCP and throw that into an IETF WG to see what happens (to see what feedback / backlash / praise comes out of it). Who'd be interested in collaborating on such a draft?
With kind regards,
James Bensley (he/him)
[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:
hello@inter.link | Web:
inter.link