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/address-policy-wg@ripe.net/
[address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
- Previous message (by thread): [address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
- Next message (by thread): [address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fw at deneb.enyo.de
Sun Jun 16 18:49:07 CEST 2013
* Jens Ott: > IMHO the whole system only make sense, when it is open for all > resources! Wouldn't this mean that ARIN (or LACNIC or ...) could issue resource certification for resources allocated to you by RIPE NCC? Resource certification outside the regular hierarchical model can get very messy. (That's probably the most significant advantage of DNSSEC over the out-of-tree browser PKI.)
- Previous message (by thread): [address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
- Next message (by thread): [address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]