[routing-wg] Delay in publishing RPKI objects

Hi Nick,

> Op 17 feb. 2021, om 15:25 heeft Nathalie Trenaman <nathalie at ripe.net> het volgende geschreven:
> 
> Hi Nick,
> 
>> Op 17 feb. 2021, om 13:54 heeft Nick Hilliard <nick at foobar.org> het volgende geschreven:
>> 
>> Hi Nathalie
>> 
>> do any of the other RIRs run any components of the software stack that the RIPE NCC developed for managing its RPKI CA functionality?  I.e. how much exposure to production environments does this software get outside the RIPE NCC?
>> 
>> Nick
> 
> In the past APNIC used some fork of our publication server code, but I’m not aware how far this diverted from our code. I’m not aware of any of the other RIRs using our software stack. 
> 
> Kind regards,
> Nathalie
> 
> 

I stand corrected. Tim pointed out to me that APNIC has their own code base, always had and is actually older than the RIPE NCC code.
AFRINIC runs a fork from APNIC.
ARIN used our code base around 2010 for their pilot, but implemented their own code base from scratch. 
LACNIC uses the RPKI object library but has their own CA and publication stack. 

Sorry for the confusion and thanks for the correction Tim.

Kind regards,
Nathalie