Re: [DNSOP] Alternative Special-Use TLD problem statement draft
George Michaelson <ggm@algebras.org> Thu, 07 April 2016 19:19 UTC
Return-Path: <ggm@algebras.org>
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 AD05612D158 for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 12:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.com
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 ElzbTPJifZpa for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 12:19:02 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E1C312D0EF for <dnsop@ietf.org>; Thu, 7 Apr 2016 12:19:02 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id s79so111298455oie.1 for <dnsop@ietf.org>; Thu, 07 Apr 2016 12:19:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-transfer-encoding; bh=+6kiCnKT43KZNCR1eojcpOUwGZrxgVoPCMl6QWyzW0g=; b=I3wZH+Mi+Pqk2AioK3g7EcdXh4M4o6uWAB0ibU2ut+s+QDz9wiiuIBkOxdEwVOL4AU tTvdzpPoOr5EbhKo1XVABMWBJaJDS3FQisNZhjFWkvdFZZUxXgoP9AOOh56pOZHwy9/A 53k3pavm1exF8A9XgRyDYDCcRH1WMXI302ZVjQthXS6AvnzIwMGUQ2Hz9/M0K2u52FAa Alax2C1wjSs25GuJxJah+iv2T40jR9Dq4ISKYh//3uNe0cex4LXVUtRqq0qiF1CZs/SZ xDgIAgP0G6eXzs/23nojK4llmd9AUI1IqYWg2s94+rZprESuhFd7dsl6kdbnLPAgozFC 3H/Q==
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:content-transfer-encoding; bh=+6kiCnKT43KZNCR1eojcpOUwGZrxgVoPCMl6QWyzW0g=; b=CaBBtX93wg9xBLgOJzupDcQ8SJAFnb/V9ZzrBf/UOaVNZ7GgxNf5VPOIGDIqEObTCs c04uatmqgHftHsiEe8RTcaA3U4oozTqzq2SLfME1QMEaOaEq3M6bWzjp9OP5EjXM4DTv ZidaTLyy7KnnVh6DMb/Mk7ulfJS3eWLqaiz6RO04nyg8ixX2fn7glDCxFZNH/tGRtpzh Nsa+CMKmugWUU6bEx7oCAOvmwGY4UYS6j+Ou4XD/nOMg8z9s4svGPZKVYrj1rAAFtM8W /cRmZEeShUsanczfxbSQDBBZZEJ2Okm0XnvmckAORBXBBHhaHHDct5G0Z3TZm0jklHPp 6ssg==
X-Gm-Message-State: AD7BkJJymPqk/yNXoayPzIcfOGXVYzp1nv5toUGpHniHqHh262+tKpdR9UnMxQQ4cIMHiU1cx2sKPWGEFaBW5g==
MIME-Version: 1.0
X-Received: by 10.157.38.135 with SMTP id l7mr2171524otb.150.1460056741921; Thu, 07 Apr 2016 12:19:01 -0700 (PDT)
Received: by 10.182.187.97 with HTTP; Thu, 7 Apr 2016 12:19:01 -0700 (PDT)
X-Originating-IP: [2001:67c:370:176:d8b3:ba33:b070:ec9a]
In-Reply-To: <524c1242-4cfc-fa16-3ace-efe5a6eeda19@bogus.com>
References: <8D23D4052ABE7A4490E77B1A012B630797A44227@mbx-03.WIN.NOMINUM.COM> <251C9653-EDB4-41E8-BF08-B921A192B7BC@virtualized.org> <20160407151722.GB17505@laperouse.bortzmeyer.org> <9ECAB54F-3A4D-40E0-B0D3-0FDF5A3F15CF@gmail.com> <460E105C-F49C-4716-9AAA-1782AA0E2A3A@virtualized.org> <524c1242-4cfc-fa16-3ace-efe5a6eeda19@bogus.com>
Date: Thu, 07 Apr 2016 16:19:01 -0300
Message-ID: <CAKr6gn3qi4RTq+m8Q7ADt=iMhK5WCtzBh71RK8oveCGWE_8zwg@mail.gmail.com>
From: George Michaelson <ggm@algebras.org>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/H06plG0KwbvfpLYt8S-7_9DXG1o>
Subject: Re: [DNSOP] Alternative Special-Use TLD problem statement draft
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: Thu, 07 Apr 2016 19:19:05 -0000
I wouldn't normally invoke 'the nuclear option' but the parallels with good science/bad politics are stark here. Norbert Weiner left the field and moved into biology and cybernetics because he realized his personal ethics were totally adrift in the sea of consequence of work on nuclear physics. I think Condon or somebody said after the trinity test, he lived on sleeping pills forever. I don't want to be in that space. (its in richard rhodes' book. i forget where) Ignoring the social consequences of entirely logical technologically driven decisions is not just silly, its actually dangerous. This is what RFC6761 does. It ignores consequence in the world of names as social constructs. We're not the gods of the internet. The social consequences of build outs has to be understood to exist. ICANN is the forum where social constructs meet, and discuss names. technically motivated internet names have a social context. It has to be discussed properly by the people who understand it. I know John Perry Barlow's statement of independence is very popular, but I live in the real world. Aspirations are not concurrent with reality, and I prefer desire and reality to align. I believe Barlow has more recently said he understands aspiration to be different to reality, so maybe we're all of one mind here. The best possible alignment right now of desire and reality, is for ICANN to be the forum which adjudicates what labels exist or are special in the top levels of worldwide socially visible naming. The IETF should be seen to ask them, based on sound technical reasons, to consider names. Not telling, asking. This is what I believe. This is what motivates me to discuss this problem: Lets not pretend we can drive this on technology alone. We can't. -G On Thu, Apr 7, 2016 at 4:08 PM, joel jaeggli <joelja@bogus.com> wrote: > On 4/7/16 3:25 PM, David Conrad wrote: >> Suzanne, >> >> On Apr 7, 2016, at 2:39 PM, Suzanne Woolf <suzworldwide@gmail.com> wrote: >>>> On Apr 7, 2016, at 11:17 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote: >>>> >>>> Since we have this liaison, does anyone know if it was used to inform >>>> ICANN of this discussion (it seems the right thing to do) and to ask >>>> them if they wanted to comment? >>> >>> https://datatracker.ietf.org/liaison/1351/ >>> >>> (DNSOP co-chairs, AD, and IAB collaborated on this, as the IAB has oversight of liaisons for the IETF.) >> >> Out of curiosity, since that liaison statement was made about 18 months after RFC 6761 was published and about a 10 months after draft-grothoff-iesg-special-use-p2p-names was submitted, was there any previous liaison communication to ICANN prior to that statement related to RFC 6761? > > Afaik there's only one liason statement to icann since the inception of > liason statement tracking; the basis of inter-organiation collaboration > is imho largely the RFC series. > >> Thanks, >> -drc >> (speaking only for myself) >> >> >> >> _______________________________________________ >> DNSOP mailing lis >> DNSOP@ietf.org >> https://www.ietf.org/mailman/listinfo/dnsop >> > > > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
- [DNSOP] Alternative Special-Use TLD problem state… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Philip Homburg
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Philip Homburg
- Re: [DNSOP] Alternative Special-Use TLD problem s… Paul Hoffman
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Tim Wicinski
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Alain Durand
- Re: [DNSOP] Alternative Special-Use TLD problem s… George Michaelson
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… George Michaelson
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… George Michaelson
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Patrik Fältström
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… Philip Homburg
- [DNSOP] Example domains and following the standar… Stephane Bortzmeyer
- [DNSOP] Formal syntax in the Special-Use domain r… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Formal syntax in the Special-Use doma… Alain Durand
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Alain Durand
- Re: [DNSOP] Alternative Special-Use TLD problem s… Paul Hoffman
- Re: [DNSOP] Alternative Special-Use TLD problem s… joel jaeggli
- Re: [DNSOP] Alternative Special-Use TLD problem s… Suzanne Woolf
- Re: [DNSOP] Alternative Special-Use TLD problem s… Suzanne Woolf
- Re: [DNSOP] Alternative Special-Use TLD problem s… Suzanne Woolf
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… joel jaeggli
- Re: [DNSOP] Alternative Special-Use TLD problem s… George Michaelson
- Re: [DNSOP] Alternative Special-Use TLD problem s… joel jaeggli
- Re: [DNSOP] Alternative Special-Use TLD problem s… Suzanne Woolf
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Warren Kumari
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… John Levine
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Warren Kumari
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… John R Levine
- Re: [DNSOP] Alternative Special-Use TLD problem s… Philip Homburg
- Re: [DNSOP] Alternative Special-Use TLD problem s… Donald Eastlake