IETF Logo Mail Archive

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

Bob Harold <rharolde@umich.edu> Mon, 20 July 2015 17:50 UTC

Return-Path: <rharolde@umich.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 713561B2F70 for <ietf@ietfa.amsl.com>; Mon, 20 Jul 2015 10:50:55 -0700 (PDT)
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 rsaHfIakV-Kf for <ietf@ietfa.amsl.com>; Mon, 20 Jul 2015 10:50:53 -0700 (PDT)
Received: from mail-yk0-f175.google.com (mail-yk0-f175.google.com [209.85.160.175]) (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 858D11B2D44 for <ietf@ietf.org>; Mon, 20 Jul 2015 10:50:53 -0700 (PDT)
Received: by ykax123 with SMTP id x123so145200448yka.1 for <ietf@ietf.org>; Mon, 20 Jul 2015 10:50:52 -0700 (PDT)
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=PYr5v+Uybuee41PeBnJZtvt0uoqLMFCpAJXXryvf+TU=; b=CawDgzIbASUvbyDLQBo8Ae2jdHPViovMX+6xHX5l5uz8rLyN4FPcwU9lUhHZet7QmV T8t+b9wCwzUxODWlZwE1VDR02TMygfzbnNoPi7bRfTy7gj77fibq/BPHol1jSa858rra 4R3L0qch3LURCLGlFdL8zwqVh2FIAMNuI/ZYbZ9wFhXFQi33FHfJKy4cQ0UAupEcQqxD 5j6EAtg6mq5ObtzcnH73Odbti3YrWJlSUDnv1lYngL96Mqpy0OxtCMAsUDH49SDsa2AS QbvDamBci7Wagc+5JT/ZEI61aC70gRJGv4+F3iZQFlx0kBL+aXk7CNn8xc5jKb4Jumu2 0p6g==
X-Gm-Message-State: ALoCoQmXKt9K8gt2ceMDo82TlgS3meIiBnvgcBQO27345N0/YagwbJdumHIiDOxNyTaMdZrgcjo5
MIME-Version: 1.0
X-Received: by 10.13.213.210 with SMTP id x201mr28122067ywd.51.1437414652745; Mon, 20 Jul 2015 10:50:52 -0700 (PDT)
Received: by 10.129.52.194 with HTTP; Mon, 20 Jul 2015 10:50:52 -0700 (PDT)
In-Reply-To: <55ACF8C8.90303@cisco.com>
References: <20150714192438.1138.96059.idtracker@ietfa.amsl.com> <55A90F34.4010901@cisco.com> <CAL02cgTJM1FxTHfaQb_x5=7MExOd3YumQbrAEE487a2+Ax0i=w@mail.gmail.com> <55A91C90.1050201@cisco.com> <49481ED5-52CA-470D-8B0E-895F11A1BA46@difference.com.au> <55ACA123.7020803@cisco.com> <04F3F38A-097E-4DCF-9295-273F0C4B4651@fb.com> <55ACF8C8.90303@cisco.com>
Date: Mon, 20 Jul 2015 13:50:52 -0400
Message-ID: <CA+nkc8Bwj-RGRSZk1_GYi8kS+n_iWAFOGcaEit+LiMgb53zRFg@mail.gmail.com>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-onion-tld-00.txt> (The .onion Special-Use Domain Name) to Proposed Standard
From: Bob Harold <rharolde@umich.edu>
To: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary="001a114fa88cc5aa83051b522dd8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/agzazkKfD8cbD1nql7m_geETaZM>
X-Mailman-Approved-At: Thu, 23 Jul 2015 04:08:04 -0700
Cc: Richard Barnes <rlb@ipv.sx>, Alec Muffett <alecm@fb.com>, dnsop <dnsop@ietf.org>, David Cake <dave@difference.com.au>, "ietf@ietf.org" <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: Mon, 20 Jul 2015 17:50:55 -0000

On Mon, Jul 20, 2015 at 9:34 AM, Eliot Lear <lear@cisco.com> wrote:

>  So... Alec and I did a bit of wordsmithing and what I propose is a slight
> clarification on the existing text, based on this exchange, and here it is:
>
>
>    Like Top-Level Domain Names, .onion addresses can have an arbitrary
>    number of subdomain components.  Only the first first label to the
>    left of ".onion" is significant to the layer 3 Tor protocol, while
>    application layers above have access to the full name.  For example...
>
>
> And then an HTTP example would be inserted (or otherwise "For example..."
> taken out).
>
> Eliot
>

This thread has taught me more about the .onion names - thanks for that.
But I would have to agree with those that think this bit of explanation is
unnecessary to the RFC and should be excluded, rather than attempting to
clarify it.  The RFC only needs to deal with ".onion".  No need to explain
the other parts of the name.

-- 
Bob Harold

v2.23.0 | Report a Bug | By Email