tim, lots of good points
> It requires that the parent CA (RIPE NCC in this case) monitors the > repositories for member CA certificates that it issues to delegated > CAs. These CAs may use the Publication-as-a-Service (PaaS) provided > by RIPE NCC, or they could run their own publication server. i am of two minds on this. while i like publication at reliable PPs, i am not fond of over-centralisation and spsof. originally, we hoped for a dozen or two PaaS providers. randy ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
