Re: [Arcing] Fwd: New Version Notification for draft-stw-whatsinaname-00.txt

"John Levine" <johnl@taugh.com> Tue, 12 July 2016 20:31 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: arcing@ietfa.amsl.com
Delivered-To: arcing@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8F9612D645 for <arcing@ietfa.amsl.com>; Tue, 12 Jul 2016 13:31:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 1s016QYrTSrQ for <arcing@ietfa.amsl.com>; Tue, 12 Jul 2016 13:31:21 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A62E812D630 for <arcing@ietf.org>; Tue, 12 Jul 2016 13:31:20 -0700 (PDT)
Received: (qmail 65001 invoked from network); 12 Jul 2016 20:31:19 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 12 Jul 2016 20:31:19 -0000
Date: Tue, 12 Jul 2016 20:30:57 -0000
Message-ID: <20160712203057.33162.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: arcing@ietf.org
In-Reply-To: <B65329C7-DC2C-4A45-857E-366BAA70E11A@gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/arcing/9CbmQKRLcd5-MU6GmyauTcaCQy8>
Cc: suzworldwide@gmail.com
Subject: Re: [Arcing] Fwd: New Version Notification for draft-stw-whatsinaname-00.txt
X-BeenThere: arcing@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: This list will discuss different architectural approaches to signalling alternative resolution contexts for Internet names <arcing.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/arcing>, <mailto:arcing-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/arcing/>
List-Post: <mailto:arcing@ietf.org>
List-Help: <mailto:arcing-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/arcing>, <mailto:arcing-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2016 20:31:22 -0000

>There seemed to be strong feeling in the ARCING BOF in BA that we needed a document that could serve as advice to
>protocol designers and software implementers, although it's not entirely clear where such a document should live. It's
>*not* intended for adoption by DNSOP; although it may ultimately include advice to DNS operators, that's not the
>primary purpose.

I read it, and it's all reasonable and informative, but I fear it'll
just be preaching to the converted.  The unconverted will continue to
say "yeah, ok, I know all that but I still need to reserve .BANANA"

We have a severe perverse incentive.  On the one hand, we tell people
that squatting on domain names is bad for all sorts of reasons, and
we're not going to let people reserve desirable names for non-DNS use
for other reasons.  Then anyone who's paying attention can see that
what you actually do is pick the name you want and squat on it with
extreme vigor, until we say, oh, all right, just this once.  Or maybe
we don't, but unless there's some external situation like the one for
.onion certificates, they hand out software that uses the name they
want anyway and if the names leak, too bad.

Until and unless we can de-perversify the situtation, I don't see much
point in offering more advice.

R's,
John