RPKI protocol is loop starting if the min version is not available

[Alarig Le Lay]

On Mon 16 Dec 2024 17:23:46 GMT, Ondrej Zajicek wrote:
> Hello
> 
> So if i undestand it correctly, if you put both 'min version 2' and
> 'max version 2', it failed? (that is expected if the peer does not support
> version 2)

My original goal was to feed the ASPA table, but the protocol was
negotiated on v1. So I tried to put the 'min version' option to try to
force it, without success, then add the 'max version' as well, just to
have the same thing than on the documentation.

> If you remove that option or put lower number it worked?

Both 'min version' alone or with 'max version' have the same loop
behaviour

> I see here two issues:
> 
> 1) There should be some timeout between retries.

Indeed 
 
> 2) The RPKI protocol outline in documentation should not contain 'min
> version 2' but 'min version <num>' as it is just an outline of options,
> not an example.

For this part, I added the 'min version 2' just to try to force it. My
first try was without it.
And the initial issue is probably that I mis-configured the routinator.
 
> Is that what you mean?
> 
> 
> Also it is funny that Routinator answered with:
> 'only versions 0 up to and including MAX_VERSION supported'
> without stating what is the MAX_VERSION.

You tell me, that’s not a very useful error message :p

-- 
Alarig