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

David Conrad <drc@virtualized.org> Tue, 21 July 2015 12:05 UTC

Return-Path: <drc@virtualized.org>
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 EA9FD1A1A4D for <ietf@ietfa.amsl.com>; Tue, 21 Jul 2015 05:05:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 x7r_WJgEGs_7 for <ietf@ietfa.amsl.com>; Tue, 21 Jul 2015 05:05:37 -0700 (PDT)
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (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 BD9D31A1A3B for <ietf@ietf.org>; Tue, 21 Jul 2015 05:05:28 -0700 (PDT)
Received: by wibud3 with SMTP id ud3so112233326wib.1 for <ietf@ietf.org>; Tue, 21 Jul 2015 05:05:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=Lc1IautY795wVtNzbs+r8qXhFMsSqzgK6TQ+acy6Vi4=; b=PAVNhDvRLG1qV7g68U5bi2TTyYisHo3yrGYpUJY0k0NdNnLaSeKvXDprHxtkV5k5+C UpjN3VU++jxyG4gBHz+X5IICrZCuQ2NF/jwEWvcZaa5sjPiiRbIcUuQkHtGHV2Idlpkb UTgD6fgAT1QsbCFENYyWO4qkOn0OZgP/pqvaAMrxf9vhL3tKUywC1mGTWHYRD0Xd3IG8 arGMmA5nsqKKZDUMCpPRyjsnKP7iToh3M0lt0vqnNChrNaA4/EXiqo3k7YVMQ7vNhJ7f 9B8EERiiQ5fTBQLC0hvkUaLhtIxSOYe9ZUR8bv9MnN1TZ3ynryi2vy7mX+cN4omTGxvx niRA==
X-Gm-Message-State: ALoCoQndPSkY62zNxMzONVj0GvA1aLb9XF4S68GuyFyVS9hgu5uutYRdo2lScEOzfnXF0Gh30iJI
X-Received: by 10.194.23.194 with SMTP id o2mr68147157wjf.63.1437480327532; Tue, 21 Jul 2015 05:05:27 -0700 (PDT)
Received: from dhcp-b2a5.meeting.ietf.org (dhcp-b2a5.meeting.ietf.org. [31.133.178.165]) by smtp.gmail.com with ESMTPSA id w8sm36732424wja.15.2015.07.21.05.05.25 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Jul 2015 05:05:26 -0700 (PDT)
Subject: Re: Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Content-Type: multipart/signed; boundary="Apple-Mail=_F7BFD55A-104E-4428-BDD2-1AD91F95914C"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5
From: David Conrad <drc@virtualized.org>
In-Reply-To: <099CDAF7-F486-4A8E-9015-DB515312E50E@apnic.net>
Date: Tue, 21 Jul 2015 14:05:23 +0200
Message-Id: <4180BDB4-B7FF-4A01-BF65-57739BC6F70D@virtualized.org>
References: <CD5AD7A8CCF5852BB1CE0AC1@JcK-HP5.jck.com> <099CDAF7-F486-4A8E-9015-DB515312E50E@apnic.net>
To: Geoff Huston <gih@apnic.net>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/tZAUanKHk-8xjyUcz1_3VzV1ujY>
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>
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 12:05:40 -0000

Geoff,

On Jul 21, 2015, at 8:37 AM, Geoff Huston <gih@apnic.net> wrote:
> 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.

I would agree, however I don't believe that's what we're discussing.

I thought we were talking about how to deal with the reality that there are non-global and/or non-DNS uses of domain names. RFC 6761 has created a mechanism to describe those uses, but did not provide any criteria by which a decision would be made as to whether the domain names would be reserved for that use (well other than Standards action or IESG decision).

That is, RFC 6761 has already placed the IETF back into that particular frame. However, if we assume the requests made for Special Use Names are technical and not political or economic, it would seem the IETF would be the right place to come up with the criteria by which those names are placed on the Special Use Names registry, no?

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

John's suggested approach confuses me.

It seems to be suggesting that ICANN should take on the role of doing the technical analysis of whether a particular protocol meets a set of technical criteria specified in a document in which the ICANN community had no input.

That can't be right, so I suspect I misunderstand.

Regards,
-drc