IETF Logo Mail Archive

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

Sam Hartman <hartmans-ietf@mit.edu> Tue, 11 August 2015 15:46 UTC

Return-Path: <hartmans@mit.edu>
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 B0A831A8765; Tue, 11 Aug 2015 08:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] 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 eqJrgtJFQE28; Tue, 11 Aug 2015 08:46:42 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE2FB1A90B9; Tue, 11 Aug 2015 08:45:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id BDA8620797; Tue, 11 Aug 2015 11:44:37 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W_jfsdoLdZBf; Tue, 11 Aug 2015 11:44:37 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 11 Aug 2015 11:44:37 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 4831780910; Tue, 11 Aug 2015 11:45:51 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Darcy Kevin (FCA)" <kevin.darcy@fcagroup.com>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard
References: <20150714192438.1138.96059.idtracker@ietfa.amsl.com> <D1EA295A.DFA3%edward.lewis@icann.org> <55C4C0DA.8070502@w3.org> <D1EA43FA.DFB8%edward.lewis@icann.org> <554DA9E5-2071-48A2-8AC8-DD07DE3B2BB0@fb.com> <CA+9kkMAcW_g28qAZ8SKbqefZfdDxzdM7=0D_of7f_qLm08d3wA@mail.gmail.com> <CD2ABBDD-F9CA-4A27-A0B6-3CDD37DB1AB4@fb.com> <CA+9kkMAmuXuLpsHVm8PeFQ5V+48mdd06=u=L+gKPqGVQSh-FFg@mail.gmail.com> <8D7DDDFF-BC2E-4A98-ADDB-A72D2C6A796E@fb.com> <EE0CF597-EC22-4853-8020-1F2AFECF73EE@cursive.net> <C0DB3F19-80F2-415C-9968-CD4072C9298A@fb.com> <2dc608607be34a09bc1192e5366323ed@mxph4chrw.fgremc.it>
Date: Tue, 11 Aug 2015 11:45:49 -0400
In-Reply-To: <2dc608607be34a09bc1192e5366323ed@mxph4chrw.fgremc.it> (Darcy Kevin's message of "Mon, 10 Aug 2015 22:54:35 +0000")
Message-ID: <tslvbcl3k2a.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HnNldP_qX6szz7DdfyKEdzRHy7Y>
Cc: Edward Lewis <edward.lewis@icann.org>, Joe Hildebrand <hildjj@cursive.net>, Ted Hardie <ted.ietf@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, Richard Barnes <rlb@ipv.sx>, "dnsop@ietf.org" <dnsop@ietf.org>, Mark Nottingham <mnot@mnot.net>
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, 11 Aug 2015 15:46:43 -0000

>>>>> "Darcy" == Darcy Kevin (FCA) <kevin.darcy@fcagroup.com> writes:

    Darcy>    In retrospect, the definition of the
    Darcy> €œhttp€ and
    Darcy> €œhttps€ schemes (i.e.  RFC 7230) should
    Darcy> have probably enumerated clearly which name registries were
    Darcy> acceptable for those schemes, so that the following language
    Darcy> from RFC 7320 (a BCP) could be invoked against any attempt by
    Darcy> an app €“ Onion or anyone else -- to inject their
    Darcy> own unique brand of €œspecialness€ into
    Darcy> the interpretation of the Authority component of their URIs:

I think all of this discussion ignores the realities of how host
software works.  Onion is not injected at the browser.  It's handled at
a layer that deals with connecting to names, not connecting to URIs.
Actually being responsive to these practical concerns in how people
build real-world systems is supposed to be an important part of the
IETF.  I find this ongoing discussion frustrating because people are
ignoring the impact of their thoughts on the systems we actually have
before us.  There have been many nice theoretical models presented.
However we have not chosen to specify APIs in the spaces under
discussion, and the APIs that are specified do not map well onto these
models.  The approach that the TOR Project has chosen does map well onto
the real-world systems.

v2.23.0 | Report a Bug | By Email