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 ]
Opteamax GmbH
ripe at opteamax.de
Sun Jun 16 19:51:14 CEST 2013
On 16.06.2013 18:49, Florian Weimer wrote: > * 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.) Maybe the context was not pointed good enough in my post. I was talking about making RPKI available for RIPE-PI-Space identicalliy for as for RIPE-PA, not about signing ARIN, LACNIC or whatever space... The hierarchical model should be kept in my opinion ... BR Jens > > > !DSPAM:637,51bdf2e746056786959777! > -- Jens Ott Opteamax GmbH Simrockstr. 4b 53619 Rheinbreitbach Tel.: +49 2224 969500 Fax: +49 2224 97691059 Email: jo at opteamax.de HRB: 23144, Amtsgericht Montabaur Umsatzsteuer-ID.: DE264133989
- 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 ]