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] oversight of .int

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

Jim Reid jim at rfc1035.com
Thu Nov 13 21:55:42 CET 2014

On 13 Nov 2014, at 20:50, Peter Koch <pk at DENIC.DE> wrote:

> So, again: who is to be convinced to make INT signed?

Runs away screaming...

The politics around .int and its oversight are... well... interesting. It might be inadvisable to dive into that while the IANA arrangements are in flux.

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