Re: Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard

Geoff Huston <gih@apnic.net> Tue, 21 July 2015 06:37 UTC

Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75CA91AD080 for <ietf@ietfa.amsl.com>; Mon, 20 Jul 2015 23:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.801
X-Spam-Level:
X-Spam-Status: No, score=-101.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=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 zPgJK0VdK7gn for <ietf@ietfa.amsl.com>; Mon, 20 Jul 2015 23:37:41 -0700 (PDT)
Received: from nx-mailgw.apnic.net (nx-mailgw.apnic.net [IPv6:2001:dd8:9:801::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BF8D1AD071 for <ietf@ietf.org>; Mon, 20 Jul 2015 23:37:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:content-type:mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer:return-path: x-originating-ip; bh=ugk9rEedoSKRlmovwpbKVwzwhgRkZjdYEgj8eERxA6g=; b=ecgKtlGMwMm3I52ze/I8vxBy4XLVVcN9Zpww6zGfpfaswAjNlsJZIbJQrSLKRSyoCvZrMB5P6M9pW dr2xVT7wynAe4WuU03CTL7YJmXphS4LQnTbKZ2RFGaHKQ/yhd+BK514EtqmLSumFhPEDTD5PvJcYZ6 NElqKn+ygL1OI3nw=
Received: from iamda3.org.apnic.net (unknown [IPv6:2001:dd8:9:2::101:249]) by nx-mailgw.apnic.net (Halon Mail Gateway) with ESMTPS; Tue, 21 Jul 2015 16:41:13 +1000 (AEST)
Received: from [130.129.6.54] (203.119.101.249) by iamda3.org.apnic.net (203.119.111.31) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 21 Jul 2015 16:37:36 +1000
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Subject: Re: Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <CD5AD7A8CCF5852BB1CE0AC1@JcK-HP5.jck.com>
Date: Tue, 21 Jul 2015 08:37:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-ID: <099CDAF7-F486-4A8E-9015-DB515312E50E@apnic.net>
References: <CD5AD7A8CCF5852BB1CE0AC1@JcK-HP5.jck.com>
To: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-Mailer: Apple Mail (2.2102)
X-Originating-IP: [203.119.101.249]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/l3bzk52aNFKbS7G06Z8GE5dAlws>
Cc: John C Klensin <john-ietf@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2015 06:37:43 -0000

> Rather than engaging in a drama that looks from a distance like
> "ICANN asserts that they are in charges of everything, including
> the IETF" and "IETF asserts they can grab whatever names they
> want, whenever they like". why can't we take the Special Names
> problem to them, say "look, we understand that these names look
> like names in the public DNS root and that confusion that would
> have bad effects is a real risk, how about you devise a
> procedure for dealing with them that recognizes the importance
> of existing deployment and use and considers the low likelihood
> that people who are using these names will stop because you tell
> them too.  Clearly the procedure you use for new gTLD
> applications won't work.  And, because some of these names won't
> wait, if you can't get that procedure together immediately, we'd
> be willing to let you delegate things to us on some reasonable
> basis until you do."
> 
> It seems to me something like that, rather than continual
> testing of boundaries, is how two peer organizations led by
> adults treat each other.  It also allows us to take the position
> that we are ICANN's customers for the IANA function but are
> otherwise an independent entity that can work with them when
> that is in the best interests of both of us and of the Internet,
> but that is not, in any respect, responsible for them or their
> operational or governance models.


Having been around at the time when the IETF was first engaged in
"policy debates that few people in our community really enjoy and fewer seem
equipped to really understand and engage with.” and actively played in that space
at the time, I find the reversion of putting the IETF back into the frame
for a repeat play an amazing poor move on the part of all concerned.

FWIW I strongly object to this draft moving forward to a proposed standard.

Furthermore, I appreciate and support John’s analysis and suggested
approach here.

  Geoff