Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-grothoff-iesg-special-use-p2p-names-00.txt]

Tony Finch <dot@dotat.at> Wed, 04 December 2013 12:36 UTC

Return-Path: <fanf2@hermes.cam.ac.uk>
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 3F9D91AE21E for <dnsop@ietfa.amsl.com>; Wed, 4 Dec 2013 04:36:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 bK0PLKMjLh47 for <dnsop@ietfa.amsl.com>; Wed, 4 Dec 2013 04:36:13 -0800 (PST)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id 99DA11AE129 for <dnsop@ietf.org>; Wed, 4 Dec 2013 04:36:13 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:52411) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1VoBgW-0007vg-gs (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 04 Dec 2013 12:36:08 +0000
Received: from fanf2 by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1VoBgW-0007Qm-7y (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 04 Dec 2013 12:36:08 +0000
Date: Wed, 04 Dec 2013 12:36:08 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: David Conrad <drc@virtualized.org>
In-Reply-To: <D3E446D0-F9ED-4671-A1C2-29A15D3DE010@virtualized.org>
Message-ID: <alpine.LSU.2.00.1312041229560.8824@hermes-2.csi.cam.ac.uk>
References: <20131201164841.GB12135@sources.org> <BF87877A-8989-4AA4-9ED1-52C82E1BC538@nominum.com> <alpine.LFD.2.10.1312011206480.12923@bofh.nohats.ca> <20131202151651.GD16808@mx1.yitter.info> <A12FD3E0-58F6-4490-877F-A9C59405F717@vpnc.org> <6DBBC8339C394DBDAE4FE1F764E02A8D@hopcount.ca> <20131203170825.GA17211@nic.fr> <21D03162-81D1-494A-89A9-41BE89D28A0E@nominum.com> <BB7627E9-8D50-48E5-B809-64AE4D574271@virtualized.org> <20131203221006.GB5689@sources.org> <D3E446D0-F9ED-4671-A1C2-29A15D3DE010@virtualized.org>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-grothoff-iesg-special-use-p2p-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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Dec 2013 12:36:16 -0000

David Conrad <drc@virtualized.org> wrote:
>
> "My point was exactly that the local stub resolver (that is, the library
> on the system that issues to name resolution requests, not the part of
> the name resolution system that does the work, be it DNS, mDNS, YP, or
> whatever) will be expected to distinguish between real DNS names and
> these pseudo-DNS names. This implies every time the IETF makes use of
> 6761, those tables of special labels is going to need to be updated (and
> I suspect the chances of this being done universally and consistently
> approach zero). This means an application that will work on one system
> (that has update the table) won't work on another (because the table
> hasn't been updated). I consider this sub-optimal."
>
> Haven't we been here before (e.g., .bitnet/.csnet/.uucp)?

To me this sounds a lot like private namespaces in the DNS which
correspond to private networks - the analogy being that these special
non-DNS names often correspond to special overlay networks (as in Tor and
GNUnet).

So you need to have the p2p software in order to use the overlay network
and to resolve the names. If your system doesn't know about the
specialness of the name then it won't resolve properly but you would not
be able to use it if it did resolve properly.

If an application needs the special connectivity, then it needs to require
the special support software.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.