RIPE NCC hosted RPKI Validator instance?
Dear RIPE community, NCC, Oftentimes I use the RIPE NCC RPKI Validator instance hosted at http://localcert.ripe.net:8088/ for doing simple analysis and debugging. Often it is too much work to spin up a dedicated RPKI Validator instance. For this type of work all I usually need is the JSON dump which I fetch at http://localcert.ripe.net:8088/export.json Questions: a) can RIPE NCC commit to keeping an RPKI Validator instance up and running and relatively stable at a stable URL? b) Can the service be made available _only_ over HTTPS? Kind regards, Job
Dear Job, We recommend that people run a local validator instance for production purposes. The instance on http://localcert.ripe.net:8088/ is our bleeding edge code, but we are more than happy to look into hosting a stable release on a stable httpS url. Kind regards Tim Bruijnzeels RIPE NCC
On 28 Oct 2017, at 12:49, Job Snijders <job@ntt.net> wrote:
Dear RIPE community, NCC,
Oftentimes I use the RIPE NCC RPKI Validator instance hosted at http://localcert.ripe.net:8088/ for doing simple analysis and debugging. Often it is too much work to spin up a dedicated RPKI Validator instance. For this type of work all I usually need is the JSON dump which I fetch at http://localcert.ripe.net:8088/export.json
Questions:
a) can RIPE NCC commit to keeping an RPKI Validator instance up and running and relatively stable at a stable URL?
b) Can the service be made available _only_ over HTTPS?
Kind regards,
Job
Dear Tim, On Sat, Oct 28, 2017 at 09:15:21PM +0200, Tim Bruijnzeels wrote:
We recommend that people run a local validator instance for production purposes.
Of course.
The instance on http://localcert.ripe.net:8088/ is our bleeding edge code, but we are more than happy to look into hosting a stable release on a stable httpS url.
That would be much appreciated! Kind regards, Job
participants (2)
-
Job Snijders -
Tim Bruijnzeels