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 ]
Doug Barton
dougb at dougbarton.us
Thu Nov 13 23:32:18 CET 2014
On 11/13/14 2:22 PM, Barbara Roseman wrote: > ICANN inherited a number of INT registrations when it assumed management of the zone. Since 2005, at least, and probably since 1998, only treaty-based organizations who meet the other criteria have been given registrations, to the best of my knowledge. I believe that ICANN uses an outside expert who has experience with UN treaty organizations to evaluate the requests for .INT registrations. FWIW, that policy definitely predates 2003, although I can't speak authoritatively as to how long it was in place before I joined the staff. Doug
- 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 ]