This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]?
- Previous message (by thread): [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]?
- Next message (by thread): [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rubens Kuhl
rubensk at gmail.com
Mon Sep 20 18:46:42 CEST 2021
> > What do you think? > > i suspect that ops who run delegated tend toward wanting control; and > would be disinclined to publish back at parent. but, back in the day > when we designed this stuff, we had the idea that there might be highly > scaled providers of publication services not associated with any CA. > </hint> Not our experience here in Brazil. People liked that they could run their CA at a modest CPU (Raspberry Pi, low resource VM etc.) and only allow the NIR publishing service / ROA signing service to interact with it. Rubens
- Previous message (by thread): [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]?
- Next message (by thread): [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]