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] {Use of} the INT TLD {by the NCC and others} [Re: RIPE NCC DNSSEC trust anchors]

• Previous message (by thread): [dns-wg] {Use of} the INT TLD {by the NCC and others} [Re: RIPE NCC DNSSEC trust anchors]
• Next message (by thread): [dns-wg] {Use of} the INT TLD {by the NCC and others} [Re: RIPE NCC DNSSEC trust anchors]

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Kim Davies kim.davies at icann.org
Thu Nov 13 22:56:47 CET 2014

Hi Peter,

> So, there is a registrant in INT interested in having key material published.
> What does it take to get INT sigend?

It is our desire to sign .INT and we are working on making it happen. It is the only zone we manage that isn’t signed and we are keen to reach 100%. There is probably not a lot more I can say beyond that at this time.

kim

• Previous message (by thread): [dns-wg] {Use of} the INT TLD {by the NCC and others} [Re: RIPE NCC DNSSEC trust anchors]
• Next message (by thread): [dns-wg] {Use of} the INT TLD {by the NCC and others} [Re: RIPE NCC DNSSEC trust anchors]

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]