Re: [DNSOP] moving forward on special use names

David Cake <dave@davecake.net> Tue, 20 September 2016 09:32 UTC

Return-Path: <dave@davecake.net>
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 8E3B612B234 for <dnsop@ietfa.amsl.com>; Tue, 20 Sep 2016 02:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793] autolearn=no autolearn_force=no
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 AdBx9lcF0NTJ for <dnsop@ietfa.amsl.com>; Tue, 20 Sep 2016 02:32:13 -0700 (PDT)
Received: from agwe.difference.com.au (unknown [103.4.235.78]) by ietfa.amsl.com (Postfix) with ESMTP id EE26D12B214 for <dnsop@ietf.org>; Tue, 20 Sep 2016 02:32:12 -0700 (PDT)
Received: from [192.168.1.106] (106-69-253-251.dyn.iinet.net.au [106.69.253.251]) by agwe.difference.com.au (Postfix) with ESMTPSA id E6BB8154092; Tue, 20 Sep 2016 19:32:10 +1000 (AEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: David Cake <dave@davecake.net>
In-Reply-To: <alpine.OSX.2.11.1609182047100.7288@ary.lan>
Date: Tue, 20 Sep 2016 17:32:09 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0AD4FFFB-EBF5-4CDE-B29C-3220D1DBA111@davecake.net>
References: <CAPt1N1=xNaHpO-ZxusWK9_UBzOpKa0zk0y0h7iGvRS2P=Og-3g@mail.gmail.com> <20160918234346.78983.qmail@ary.lan> <CAPt1N1nOMUA0ZNQioZ7wngDE6gSjJn_qroBv2a2kdsvFMKngHg@mail.gmail.com> <alpine.OSX.2.11.1609182047100.7288@ary.lan>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/u4dCPGO4v6Mp4SflN36b_jAbYVM>
Cc: dnsop WG <dnsop@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [DNSOP] moving forward on special use names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 20 Sep 2016 09:32:14 -0000

I tend to think that they may be within scope for the problem statement, but it is likely that existing solutions (e.g. ICANN refusing to delegate them while they remain toxic) are adequate to deal with the problem. 

David

> On 19 Sep 2016, at 8:47 AM, John R Levine <johnl@taugh.com> wrote:
> 
>> Dealing with toxic waste names is out of scope for the problem statement.
> 
> Well, that's one theory.  Let's see of other people agree.
> 
> R's,
> John
> 
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop