[Arcing] lacking a reference for domain names... was Re: Fwd: New Version Notification for draft-stw-whatsinaname-00.txt

Edward Lewis <edward.lewis@icann.org> Wed, 13 July 2016 13:25 UTC

Return-Path: <edward.lewis@icann.org>
X-Original-To: arcing@ietfa.amsl.com
Delivered-To: arcing@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5F39312D142 for <arcing@ietfa.amsl.com>; Wed, 13 Jul 2016 06:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.488
X-Spam-Status: No, score=-5.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id obmoPCHG9Fe0 for <arcing@ietfa.amsl.com>; Wed, 13 Jul 2016 06:25:50 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1491312B056 for <arcing@ietf.org>; Wed, 13 Jul 2016 06:25:50 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org ( by PMBX112-W1-CA-1.pexch112.icann.org ( with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 13 Jul 2016 06:25:48 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1178.000; Wed, 13 Jul 2016 06:25:48 -0700
From: Edward Lewis <edward.lewis@icann.org>
To: "arcing@ietf.org" <arcing@ietf.org>
Thread-Topic: lacking a reference for domain names... was Re: [Arcing] Fwd: New Version Notification for draft-stw-whatsinaname-00.txt
Thread-Index: AQHR3QoRIEfBe1qjcEKvYzs82p0sIg==
Date: Wed, 13 Jul 2016 13:25:47 +0000
Message-ID: <FF85EC77-E1B2-48DD-9771-81CC22A1AA00@icann.org>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/f.18.0.160709
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <FF35C5CCB33663438BDE491DB4FE8108@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/arcing/rhbVB6XqSGrPQ0uDl9m36jyJonM>
Cc: "suzworldwide@gmail.com" <suzworldwide@gmail.com>
Subject: [Arcing] lacking a reference for domain names... was Re: Fwd: New Version Notification for draft-stw-whatsinaname-00.txt
X-BeenThere: arcing@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: This list will discuss different architectural approaches to signalling alternative resolution contexts for Internet names <arcing.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/arcing>, <mailto:arcing-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/arcing/>
List-Post: <mailto:arcing@ietf.org>
List-Help: <mailto:arcing-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/arcing>, <mailto:arcing-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2016 13:25:54 -0000

Referring to the document that can be found here:

Differentiating the subject line for a new thread.

I first sent comments to Suzanne on this in another context, more related to how the document was described to me versus what I read.  This comment is not related to that (which was more a comment on the description and not the document.  It's complicated.)

My initial itch begins with something missing from this passage:

>   It's common for protocol designers in this predicament to attempt to
>   use domain names as the starting point for their systems of names,

What's missing is a reference for "domain names."  Again, this isn't a hit on the document at hand - the lack of a definitional document is a separate thing, but a necessary prerequisite for this document.  Without a documented definition of domain names, we continue to engage in hand waving.

I haven't had time to read the rest of the document and come up with worthwhile comments, which I will get (the time) after I begin traveling to the IETF venue.  (I did skim.)  I see that the document does talk about the DNS, policy, etc., which is helpful but still does not get to the heart of what is meant by domain names (beyond the DNS).  The draft at hand touches on the problem of the day (Special Use Domain Names registry).

What I have in mind is the experimenter, coding up an innovative use of the network and finds a necessary evil in having to name things.  The experimenter might try for re-use of other code by selecting names with dots in them.  At that point, the experimenter might need a guide to see if the names fit a/the naming model of domain names and from that see if there is more to leverage.

I'm not sure the draft at hand (the framework at hand) covers that use case - "not sure" meaning I haven't had the time to dutifully read carefully and write up a reasonable response (as I've already said).