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] retaining ripe.int

Previous message (by thread): [dns-wg] RIPE NCC domain registrations
Next message (by thread): [dns-wg] retaining ripe.int

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

Jim Reid jim at rfc1035.com
Tue Jun 30 20:16:30 CEST 2015

On 30 Jun 2015, at 18:53, Peter Koch <pk at DENIC.DE> wrote:

> This is probably an exception for the lack of a drop catching risk,
> but keeping the domain to maintain a stake in the INT domain
> might be OK.

That is a remarkably bad idea. The .int domain's supposed to be for international treaty organisations. The NCC is not one. There is no reason why it should "maintain a stake in the INT domain". It simply shouldn't have a stake in this at all. If anything the NCC should be running away from .int as fast as is humanly possible.

Previous message (by thread): [dns-wg] RIPE NCC domain registrations
Next message (by thread): [dns-wg] retaining ripe.int

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

[ dns-wg Archives ]