Totally agree. The ripe.int domain comes from the time of ip6.int (another bad idea) and the perceived need of alternatives to arpa (for the wrong reasons). The sooner this gets dropped the better. Joao
On 30 Jun 2015, at 20:16, Jim Reid <jim@rfc1035.com> wrote:
On 30 Jun 2015, at 18:53, Peter Koch <pk@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.