[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

deploying RPKI based Origin Validation

Subject: deploying RPKI based Origin Validation
From: job at ntt.net (Job Snijders)
Date: Fri, 27 Jul 2018 14:40:42 +0000
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <CAL9jLaYExYkkZnCFHXKp_khzdc62W04UbukDbgGsjBuoiQ4CTA@mail.gmail.com> <[email protected]> <CAL9jLaa_oXn-5a=m+mM5E8gETP2YsBvbBNvmee0Lt5vbV6+d2Q@mail.gmail.com> <[email protected]> <CAPkb-7Cq7wr88+QUEPBs-hfw7VSBUXohfAduQH2m16-5PSHa7w@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

Dear Alex,

On Thu, 26 Jul 2018 at 19:11, Alex Band <alex at nlnetlabs.nl> wrote:
> NLnet Labs recently committed to building a full RPKI Toolset, including a (Delegated) Certificate Authority, a Publication Server and Relying Party software. As an RP implementation was the easiest way to get going, we now have some running code â?? in Rust â?? here:
>
> https://github.com/NLnetLabs/routinator
>
> Weâ??re committed to offering a toolset that is on par with our other projects such as NSD and Unbound, in terms of quality, feature set and update frequency. Weâ??re looking forward to your feedback; in the mean time weâ??re getting started with the CA and Publication Server.

This is awesome! I think it is important to have multiple high quality
implementations so operators have a choice, this way we can work
towards a healthy routing security software ecosystem and avoid
mono-culture.

Kind regards,

Job

References:
- deploying RPKI based Origin Validation
  - From: mark.tinka at seacom.mu (Mark Tinka)
- deploying RPKI based Origin Validation
  - From: job at ntt.net (Job Snijders)
- deploying RPKI based Origin Validation
  - From: mark.tinka at seacom.mu (Mark Tinka)
- deploying RPKI based Origin Validation
  - From: gtaylor at tnetconsulting.net (Grant Taylor)
- deploying RPKI based Origin Validation
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- deploying RPKI based Origin Validation
  - From: gtaylor at tnetconsulting.net (Grant Taylor)
- deploying RPKI based Origin Validation
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- deploying RPKI based Origin Validation
  - From: mark.tinka at seacom.mu (Mark Tinka)
- deploying RPKI based Origin Validation
  - From: baldur.norddahl at gmail.com (Baldur Norddahl)
- deploying RPKI based Origin Validation
  - From: mark.tinka at seacom.mu (Mark Tinka)
- deploying RPKI based Origin Validation
  - From: job at ntt.net (Job Snijders)
- deploying RPKI based Origin Validation
  - From: michel.py at tsisemi.com (Michel Py)
- deploying RPKI based Origin Validation
  - From: mark.tinka at seacom.mu (Mark Tinka)
- deploying RPKI based Origin Validation
  - From: michel.py at tsisemi.com (Michel Py)
- deploying RPKI based Origin Validation
  - From: mark.tinka at seacom.mu (Mark Tinka)
- deploying RPKI based Origin Validation
  - From: michel.py at tsisemi.com (Michel Py)
- deploying RPKI based Origin Validation
  - From: mark.tinka at seacom.mu (Mark Tinka)

Prev by Date: SP security knowledge build up
Next by Date: Rising sea levels are going to mess with the internet
Previous by thread: deploying RPKI based Origin Validation
Next by thread: deploying RPKI based Origin Validation
Index(es):
- Date
- Thread