Re: [DNSOP] on private use TLDS

Doug Barton <dougb@dougbarton.us> Thu, 28 November 2019 21:38 UTC

Return-Path: <dougb@dougbarton.us>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA485120804 for <dnsop@ietfa.amsl.com>; Thu, 28 Nov 2019 13:38:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dougbarton.us
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJyuQXGXYsTQ for <dnsop@ietfa.amsl.com>; Thu, 28 Nov 2019 13:38:32 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11CD9120047 for <dnsop@ietf.org>; Thu, 28 Nov 2019 13:38:32 -0800 (PST)
Received: from [IPv6:2600:6c50:17f:7759:b4bf:bc0a:78c5:1a15] (unknown [IPv6:2600:6c50:17f:7759:b4bf:bc0a:78c5:1a15]) by dougbarton.us (Postfix) with ESMTPSA id C25411F39; Thu, 28 Nov 2019 13:38:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dkim; t=1574977111; bh=MlKM0h0z8/K3VBrHr9417GiUqReK+JWG0DJb/R877O8=; h=Subject:To:References:From:Date:In-Reply-To:From; b=rA5vXRyJnw/yb6P/XCWnXSf7b6GLtjkBPZD+/kUBuZVMYjKsv1cj0MfIWCDt8wNNZ H7RdFKnIznanm+1Qe/tQImVkas8xcyLkEPN/k+7OsxA4UR0C7Tfb3ubbsx6nSHLFJT I6c8ZiLXCUPavG3Tx3xxJG4JAkTDcq0YudfVlVKg=
To: John Levine <johnl@taugh.com>, dnsop@ietf.org
References: <20191128165507.2A60BFDF451@ary.qy>
From: Doug Barton <dougb@dougbarton.us>
Message-ID: <fb307c7a-348a-03d3-3d8e-8e683cec603d@dougbarton.us>
Date: Thu, 28 Nov 2019 13:38:31 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1
MIME-Version: 1.0
In-Reply-To: <20191128165507.2A60BFDF451@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ijR-R7QFS9V5gzrWbCTXoAr5b0s>
Subject: Re: [DNSOP] on private use TLDS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 21:38:33 -0000

On 11/28/19 8:55 AM, John Levine wrote:
> In article <71ad677a-8c88-8916-fe02-7d0d8ae930b9@dougbarton.us> you write:
>> I agree with Matt, Bill Woodcock, Steve Crocker, and others that have
>> expressed that we should stay out of ISO's sandbox. Whatever the rules
>> are today, they can change, and poaching their stuff for our purposes is
>> bad form (and yes, I feel that poaching is what is being proposed, in
>> spite of the arguments to the contrary).
> 
> I don't see how relying on ISO's advice is poaching.  They say:

You, like Ted, are ignoring the fact that ISO can choose to change those 
rules.

>> ICANN has already said that it's not going to ever delegate CORP, HOME,
>> or MAIL.
> 
> They said indefinitely defer which is not the same thing at all. 

Ok, so if you think there is a risk here, then it should be mitigated by 
working together with ICANN on a draft that codifies that they will 
never be delegated. Since there is apparently a need for additional such 
names (like INTERNAL) then they should be included.

Other than some sort of gratuitous "we hate ICANN so we don't want to 
work with them" thing, it's not at all clear to me why we wouldn't want 
to lock the necessary resources down in cooperation with the only other 
entity that has anything to say about what happens in the root zone.

> The IETF has already decided to stay out of the home/corp/mail
> argument

The IETF can change its mind too.  :)

Seriously, there is obviously a need to have private-use TLDs that we 
can guarantee will never be part of the public root zone. So let's make 
that happen, in a way that we can be sure will never be pulled out from 
under us.

Doug