Re: [DNSOP] draft-lewis-domain-names-00.txt

"Joe Abley" <jabley@hopcount.ca> Fri, 18 September 2015 16:19 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89E031A1A14 for <dnsop@ietfa.amsl.com>; Fri, 18 Sep 2015 09:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FSL_MY_NAME_IS=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 HIKexuE3Lqre for <dnsop@ietfa.amsl.com>; Fri, 18 Sep 2015 09:19:39 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (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 C017E1A1A30 for <dnsop@ietf.org>; Fri, 18 Sep 2015 09:19:39 -0700 (PDT)
Received: by ioiz6 with SMTP id z6so61455996ioi.2 for <dnsop@ietf.org>; Fri, 18 Sep 2015 09:19:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-type; bh=A+INXwqWxsSP/1H4yfG1mHsr/ACcjO+QZMCEL/LYkLU=; b=mx7Kd1qTd09HgerncOVGLrmDc+VhyHhqCdq+/q8ynMlqvvgRAzVVdB/8DuXlbXYBI/ ZWhpQ4tdR+FtLk4SlkRLlivzinPXVz3iWmbD72tGP/7QjjMQkCDp3vsjxLurtt5aEhhu dCDZxL/Dps2HfDQyn2Elwx16AuFfKCr65NoJw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-type; bh=A+INXwqWxsSP/1H4yfG1mHsr/ACcjO+QZMCEL/LYkLU=; b=Tiup6OY0E8zh3YLP9pm8P8aRHD6VBcLDMsiW4gr+IBwVc/a2awYCqZskRFDd0sOUlt bf2RbjQBAnbbhR+1ZVq4qOobjEe1e88rvRhSCZWTr+yF1qSEzI5k/DwO0dY5guG0ADH8 PVPey1+XUsELYbHFF5djtpBWIXmE91LnCxQ6mmQaizzo5pGmLtH79YClYhx7kIGqnOSt noc5z4GJbM6+HvaGJ8dTMwVTGIpddFfgSPmme6uFOnvKkvjt/JCxLuO4Kj2+lbKQ+/f/ lbLSOwQxM3cZy03X4A7SYEfJXWRqi8SUlVaHht8/5/CKoolEHUXUu9V+9h2lIoF7fe9v kHuw==
X-Gm-Message-State: ALoCoQkMeRl90EKzXzDXE12B5/6V9bYfgmgMPLiC0sa+JiuwHQPDmRUPDvF5jEmcPGc+6xnUeKmB
X-Received: by 10.107.162.204 with SMTP id l195mr14710059ioe.196.1442593179044; Fri, 18 Sep 2015 09:19:39 -0700 (PDT)
Received: from [172.19.129.46] (135-23-68-43.cpe.pppoe.ca. [135.23.68.43]) by smtp.gmail.com with ESMTPSA id a8sm6829459igo.2.2015.09.18.09.19.37 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 18 Sep 2015 09:19:38 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
To: Alec Muffett <alecm@fb.com>
Date: Fri, 18 Sep 2015 12:19:26 -0400
Message-ID: <45A1C205-3DF1-40A3-9282-CA8344805CBE@hopcount.ca>
In-Reply-To: <14957733-EB45-45ED-9B5C-55B0943CDACD@fb.com>
References: <D2209363.F235%edward.lewis@icann.org> <CAKr6gn1aM0=Mi3343aaXKc=WtqGnJqoQm64+r4LDKzT0MyAF7A@mail.gmail.com> <14957733-EB45-45ED-9B5C-55B0943CDACD@fb.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_E7E724C8-958E-41B1-95D1-95B09DFBB622_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-Mailer: MailMate (1.9.1r5103)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/cgmXG83zePDoMG_N-MbF8EmEQ94>
Cc: Edward Lewis <edward.lewis@icann.org>, dnsop <dnsop@ietf.org>, George Michaelson <ggm@algebras.org>
Subject: Re: [DNSOP] draft-lewis-domain-names-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 18 Sep 2015 16:19:41 -0000


On 18 Sep 2015, at 9:54, Alec Muffett wrote:

>> On Sep 18, 2015, at 14:16, George Michaelson <ggm@algebras.org> wrote:
>>
>> My private comment bears repeating in public.
>>
>> DOMAIN names is about the property of domains. Domains are encompassing, set-theory/venn-diagram style. A domain and a prefix are analogous concepts. One is expressed syntactically somehow, the other is a mathematical property of bounding in a number field but they have the same basic behaviour.
>>
>> the UK domain order in coloured book mails obeyed this property: it just used reverse semantics to the ARPA model.
>>
>> XXXXXXXX.onion is *not* a domain name inside the .onion part: as I understand it, the value is a hash, or other function which has no nesting properties expressed syntactically.
>
> Hi, my name's Alec, I work for Facebook and lead the engineering team for Facebook over Tor.

This reminds me of the time I set down with a collection of people who would later turn into NZNOG, at a Uniforum meeting in Taupo. Since we were sitting in a circle, it seemed only natural to start things off with "My name is Joe, and I work for an ISP". Everybody else without missing a beat replied with the twelve-step "Hi Joe". We had a moment.

Hi Alec!

> You are certainly correct that the label immediately left of ".onion" is a hash, and functions not unlike a layer-3 address; however, there may be other labels leftwards of the hash, under (to some extent) other administrative control.

I think that we are all guilty from time to time of trying to form elegant, general descriptions of things that are not actually elegant, or useful to generalise.

The DNS is frequently described has having three core concepts: (a) the servers and the wire-format protocols that they talk, (b) the data model (resource records, etc) and (c) the namespace. (a) provides the infrastructure for (b) to be retrieved using a key from (c).

There are other name resolution protocols that are not the DNS, but which use similar namespaces to (c) and perhaps similar (b) but different (a). Pertinent examples are multicast DNS and Onion/tor, and (arguably) the localhost "protocol" that simply maps the name localhost to the addresses 127.0.0.1 and ::1.

The ugliness all rotates around the pragmatic decision to use the right-most label in a name as a resolution protocol selector. We can complain about that all we like, but reality is that we're going to have a hard time pushing those cats back into the bag. At the very least there will be injuries and bleeding, and you know the cats aren't going to like it.

It would be lovely if nobody had ever used the right-most label like this, and instead there was a standard and accepted way to specify a resolution protocol in a URI, and everywhere else that a name is used. But there isn't. Also, running code, etc.

Whether or not we should call an onion or mdns name a "domain name" or something else is just a detail. I don't think agreeing on the answer is going to solve any of the problems that we actually have.


Joe