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/dns-wg@ripe.net/
[dns-wg] Re: New key-signing keys (KSKs) for RIPE NCC forward and reverse zones
- Previous message (by thread): [dns-wg] Re: New key-signing keys (KSKs) for RIPE NCC forward and reverse zones
- Next message (by thread): [dns-wg] Re: New key-signing keys (KSKs) for RIPE NCC forward and reverse zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Matthijs Mekking
matthijs at NLnetLabs.nl
Tue Mar 17 13:38:55 CET 2009
Furthermore, there are resolver independent implementations of RFC 5011, like autotrust and trustman. - Matthijs Lutz Donnerhacke wrote: > * Anand Buddhdev wrote: >> The toolset that we're using does not have support for setting the >> revocation bit, so we won't be setting it. > > Clear statement. Thank you. > >> Are many people actually running resolvers that understand RFC 5011? > > Unbound has support for RFC5011 as well as the current developement version > of bind (might be 9.7). So it's hard to say how many people are deploying > this RFC. It seems to become the default algorithm for standalone resolvers. > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 544 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/dns-wg/attachments/20090317/b65f583b/attachment.sig>
- Previous message (by thread): [dns-wg] Re: New key-signing keys (KSKs) for RIPE NCC forward and reverse zones
- Next message (by thread): [dns-wg] Re: New key-signing keys (KSKs) for RIPE NCC forward and reverse zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]