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]/
[dns-wg] DNSSEC Policy Development Process
- Previous message (by thread): [dns-wg] DNSSEC Policy Development Process
- Next message (by thread): [dns-wg] DNSSEC Policy Development Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Olaf M. Kolkman
olaf at ripe.net
Tue Aug 30 09:58:58 CEST 2005
Just extracting one sentence out of Randy's e-mail: > no. you just want me to hold the trust keys for the zones you > think are important. and, in today's email (for some value of > 'today'), brett warns us that he has a handful of third level > zones he thinks are important enough. > > hence "does not scale." RIPE NCC thinks it is important enough to sign the zones. If any of these handful of third level zones is not important enough for your operations to go through the trouble of validating then you do not need to configure them; During early deployment of DNSSEC, there is a burden for the validating clients. I agree that if we do not get to a point where validators only have to configure between one and a handful of trust-anchors and those trust-anchors get automatically rolled DNSSEC will not reach the masses. On the other hand we have to start deploying somewhere. Olaf Kolkman PS: The IETF DNSEXT group has a work item on automatic key-rollover; work is progressing slowly.
- Previous message (by thread): [dns-wg] DNSSEC Policy Development Process
- Next message (by thread): [dns-wg] DNSSEC Policy Development Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]