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] 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 ]

Lutz Donnerhacke lutz at iks-jena.de
Tue Mar 17 13:22:56 CET 2009

* 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.

• 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 ]