Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt

George Michaelson <ggm@algebras.org> Tue, 04 February 2014 01:19 UTC

Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5741A02DE for <dnsop@ietfa.amsl.com>; Mon, 3 Feb 2014 17:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 z8UKanIiD3zO for <dnsop@ietfa.amsl.com>; Mon, 3 Feb 2014 17:18:59 -0800 (PST)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF2C1A02D0 for <dnsop@ietf.org>; Mon, 3 Feb 2014 17:18:59 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id ld10so7824568pab.38 for <dnsop@ietf.org>; Mon, 03 Feb 2014 17:18:59 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=37U7B3DDlN7MUm1p+DatlaQlvNbJ2SRkX1F7D0VEENI=; b=Oabv2cE3yCEw7YTCf5HF+qXKaoIYUI6zkiooQn4j2BSDbiWVO58e6LyytWz44gaP+d UxdwZpdMUPWKFH1okwsDO6ar7HPZ3xWZ1rGPITmmT3E3ybACQ8NxEqTqJlqxY5KxNQC9 ursHpA7V6kjprrPTCh1WVLNrOJIxljP2rXs3+58c9WZkQ/WSMbgF5ePeNSFpO4CVipP7 yGzpGYbNxwgPXE4z77BTeKw6CV7htc3cUbmVIhHXYW8xEyViKlBQAzbWsMLr0M9a2vvU aGd0/Y74bNzZSaX0esX8upNw4jqFl+Nb8FjDbC6lJDZ5P/+6sXUPKwH1jk8fvP6J7T8X BP7Q==
X-Gm-Message-State: ALoCoQkMYxiZRyJwVMJgnF3NHeKWpZ00aR9muIlksCMP9nM1VlI6X2Wqutn68/NHb8K/9Jxi4ri7
MIME-Version: 1.0
X-Received: by 10.68.231.35 with SMTP id td3mr40352443pbc.137.1391476739450; Mon, 03 Feb 2014 17:18:59 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Mon, 3 Feb 2014 17:18:59 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:302e:dba0:2280:4927]
In-Reply-To: <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com>
References: <20140129055438.2402.qmail@joyce.lan> <97E20887-2B9C-4EAD-826B-043306605F88@fl1ger.de> <72A3E4AE-F116-4496-BADB-5973DEC46598@vpnc.org> <C2A6625B-BEF7-41D6-B8BB-B870694CAFD9@fl1ger.de> <555B2F7B-7D29-43BC-AADC-1EA65A17DEF0@hopcount.ca> <EE6063EE-A69E-4460-91B4-862096A00F0F@fl1ger.de> <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com>
Date: Tue, 4 Feb 2014 11:18:59 +1000
Message-ID: <CAKr6gn2BFxuy28Wo0ZB88W0-rq8PuDO+ZTjob+Dgp7MvSw2yWQ@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=047d7b33d592c4c3a204f18a6cd4
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 04 Feb 2014 01:19:08 -0000

ok. I see where you are. I can be there, somewhat. Thats not a bad position
Ted.

So my sense of this is "you were advised not to do this, and you didn't
respect the process" for some value of "you"

What I don't like about that is a schoolmarm/punitive voice. But it has the
qualities. Tragedies of the commons don't just take one form, and having
s/w develop a dependency on name/locator properties with high visibility,
without considering the commons, is (in my opinion) a tragedy.

I'm not inherently arguing for ICANN process, or even the DNS. I think a
mature sense of the locator/id separation qualities of any endeavour, and
the arguments around naming, lead you to caution in seizing names in any
space.

IETF is constantly advised by w3c people (mark nottingham?) to be mindful
of the URI/URL concept, and not to over-egg stipulations on what is
meaningful in that space. And I think by and large, thats right.

So is what the TOR people did usurping .onion respectful of process? What
do you do, when process isn't respected?

-G



On Tue, Feb 4, 2014 at 11:08 AM, Ted Lemon <ted.lemon@nominum.com>; wrote:

> On Feb 3, 2014, at 6:27 PM, George Michaelson <ggm@algebras.org>; wrote:
> > .onion is an eminently tractable problem. Arguing otherwise is to argue
> the current .onion codebase dependency cannot move, therefore any future
> CVE against TOR cannot be fixed, therefore further code development on TOR
> is fruitless, therefore lets all stop coding. Breathing even.\
>
> What I'm saying is that it's an obnoxious thing to do, and there's no good
> reason to do it.   We really ought to have a good reason to demand that an
> organization over which we exert no control at all make a significant and
> incompatible change to their deployed code purely on the basis that some of
> us don't like what they did.   We need a better reason than that, and thus
> far none has been stated.
>
>