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/[email protected]/
[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 ]
Job Snijders
job at fastly.com
Thu Oct 7 16:58:16 CEST 2021
On Thu, Oct 07, 2021 at 04:30:58PM +0200, Tim Bruijnzeels wrote: > If this is added to the RIPE NCC RPKI backlog then I would also > request that LIRs, and PI holders, can have multiple CAs publish at > the RIPE NCC. The reason for this is that one of benefits of running a > delegated CA lies in having the option to sub-delegate to child CAs. > For example one can create child CAs with specific sub-sets of > resources for departments, business units etc. To make this scale it > would very beneficial if those children could publish under the > publication server as well. You make a good point. Kind regards, Job
- 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 ]