Re: [DNSOP] discussion for draft-appelbaum-dnsop-onion-tld-00.txt

Andrew Sullivan <ajs@anvilwalrusden.com> Sat, 21 March 2015 23:12 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 168271A905B for <dnsop@ietfa.amsl.com>; Sat, 21 Mar 2015 16:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.758
X-Spam-Level: *
X-Spam-Status: No, score=1.758 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 YH2aiXLz6fcO for <dnsop@ietfa.amsl.com>; Sat, 21 Mar 2015 16:12:44 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C84341A1AA5 for <dnsop@ietf.org>; Sat, 21 Mar 2015 16:12:44 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-905d.meeting.ietf.org [31.133.144.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id BEBA48A031 for <dnsop@ietf.org>; Sat, 21 Mar 2015 23:12:43 +0000 (UTC)
Date: Sat, 21 Mar 2015 18:12:46 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20150321231246.GJ6841@mx1.yitter.info>
References: <CAFggDF0XX3v7yGsaCwFnE7cjK0yz4-frxFgoBJfnztO8k-LFBg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAFggDF0XX3v7yGsaCwFnE7cjK0yz4-frxFgoBJfnztO8k-LFBg@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/G3kdikxJfQEV7xm82g7PFN9z_dA>
Subject: Re: [DNSOP] discussion for draft-appelbaum-dnsop-onion-tld-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: Sat, 21 Mar 2015 23:12:46 -0000

Dear colleagues,

On Mon, Mar 16, 2015 at 10:16:37PM +0000, Jacob Appelbaum wrote:

> I realized after uploading that I hadn't sent this along for discussion.

> > Name:		draft-appelbaum-dnsop-onion-tld

I've read this draft.  I have a few comments.

To begin with, in general I think this document is on the right path
and something very close to it should be published.  It's
narrowly-focussed, I _think_ it meets the template requirements of RFC
6761 (but see a remark below).  It's clearly a technical distinction,
because this approach is a backward-compatible user interface
namespace without any real DNS vestige at all: it's not intended to be
a general-purpose identifier system on the Internet, but rather as I
understand it a cryptographic identifier in the Tor network.

I have a couple nits:

In section 1, it'd probably be useful to pick up the term "domain name
slot" that was introduced by RFC 5890.  This is not an i18n case, of
course, but that's sort of the point: this is an example of something
that more or less fits in places people already use ordinary DNS
domain names, but this name is special and actually not in the DNS as
it shows up in the domain name slot.

In section 4, 3-5, what if a "synthetic" NXDOMAIN gets generated and
cached?  Will that have any effect on .onion resolution?  If this is
explained in detail in some thing I've failed to follow, a simple
reference would be enough.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com