[RPKI-Deployers] New RPKI tool from NLnet Labs: RTRTR

[Chris Morrow]

On Thu, Nov 12, 2020 at 11:58 AM Job Snijders <job at ntt.net> wrote:
>
> In RTRTR the only 'export' interface into the decision making end (the
> BGP router) in RTRTR is the RTR protocol. NLNetlabs is setting the stage
> to take 'low quality data' and upsample it through the RTR interface
> into something it is not.

oh, I read their readme:
  "...and finally feeds it to routers either via protocols such as RTR or
   through generated configuration files."

to mean it could spit out 'router configuration' which here means (to me):
  prefix-list data

though possibly prefix-list data and/or route-map and/or juniper
policies/route-filters...
though I dont' see anything like vendor-specific templates or such that'd make
prefix-list/routemap/etc exist :( oops.

> It seems future version of RTRTR will be able to take not-validated-data
> (like IRR), and convert that into the RTR (stands for RPKI-To-Router)
> protocol, which on the receiving EBGP router side is interpreted as
> validated ROA payload data to be used in the RFC 6811 process. RTRTR is
> not an "prefix list cleanup tool" (like ripe-731 or irrd 4.1.0 are).
> Seems to me they are setting the stage to somewhat dillute the current
> interfaces in the ecosystem.

yea this could go badly :(