Relaxed handling of OTC attribute

[André Grüneberg]

Hi Bird team,

We are currently evaluating the implementation of RFC9234 for our IXP route
servers. Looking at it naively, one just needs to set local role rs_server
in the protocol. And indeed, routes from peers will be rejected and this is
logged.

Instead of just logging, we would really like to apply our "blame and
shame" policy, i.e. make the invalid routes (in our case, anything with an
OTC set) visible in our looking glass (similar to RPKI invalids). To do so,
we'd need the "ineligible" routes to be imported into the main table,
tagged in a sensible way.

I understand that RFC9234 section 5 mandates that the behaviour wrt OTC
attribute handling shall not be configurable by the operator. But
ineligible does not require the route to be invisible (see section 3).

Would it be possible to implement a more relaxed behaviour by allowing the
import of ineligible routes (but never export)?

Our current alternative is to avoid using BGP roles capability, but only
implement OTC handling in filters.

Thanks and best wishes,
André
-- 
André Grüneberg, Managing Director
andre.grueneberg at bcix.de
+49 30 2332195 42

BCIX Management GmbH
Albrechtstr. 110
12103 Berlin
Germany

Geschäftsführer/Managing Directors: Jens Lietzmann, André Grüneberg
Handelsregister: Amtsgericht Charlottenburg, HRB 143581 B
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20250612/1e6cb0ab/attachment.htm>