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

Warren Kumari <warren@kumari.net> Sun, 22 March 2015 16:49 UTC

Return-Path: <warren@kumari.net>
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 F13E31A0275 for <dnsop@ietfa.amsl.com>; Sun, 22 Mar 2015 09:49:35 -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, RCVD_IN_DNSWL_LOW=-0.7] 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 uPSf6w3xgnDw for <dnsop@ietfa.amsl.com>; Sun, 22 Mar 2015 09:49:34 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) (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 4534D1A0113 for <dnsop@ietf.org>; Sun, 22 Mar 2015 09:49:34 -0700 (PDT)
Received: by wibgn9 with SMTP id gn9so38610707wib.1 for <dnsop@ietf.org>; Sun, 22 Mar 2015 09:49:33 -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=lrYtWMNQyaUnrb/YIItqqwlyczMhuyYmeFjpLM/wgj8=; b=lcb1NKLUCDE5ZvKGNADMgwRH9MZso7RdU7xaPAc3y85eyp5OgHzlveklFHrN4y5cGI dONCboN3nfpsQiipGVc2oXw+4DYI7wb8oYwKZgJ5ERiJhGHlLJUIjr2a4x0ztrgvhonV 8k2A9QqyMXK1IpktgOijQuA5U3XYGkSleGis72ByuM57YdkwMtrJYO8kHjdTaPDpmiHV x2PwtC8PkQh/GJ2TajhJ2qJ3foiZdZTh2HmtT14XHDHNAd0KfdcZ8ACZDozu0iwLZALZ WFUilCv8TOK2w96d/2bHd6c5sJgXO7pF/RrxVhDHRl2rU+Z13emUjA+2H+8CDkYsPBFK 4vVA==
X-Gm-Message-State: ALoCoQlE3UBwJ4mwBTHx9cAUdFaSdaejJI/HyLXh1cfLNB8D/zdUJBMVOroF8BKIyks/T4VWNlgX
MIME-Version: 1.0
X-Received: by 10.194.63.16 with SMTP id c16mr180935587wjs.117.1427042973021; Sun, 22 Mar 2015 09:49:33 -0700 (PDT)
Received: by 10.194.110.97 with HTTP; Sun, 22 Mar 2015 09:49:32 -0700 (PDT)
In-Reply-To: <20150321231246.GJ6841@mx1.yitter.info>
References: <CAFggDF0XX3v7yGsaCwFnE7cjK0yz4-frxFgoBJfnztO8k-LFBg@mail.gmail.com> <20150321231246.GJ6841@mx1.yitter.info>
Date: Sun, 22 Mar 2015 11:49:32 -0500
Message-ID: <CAHw9_iKgPoi+knisjCNFGtjKwZPyvnD+iES+KQNTm+PfQY+dfw@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/bxv7yf1-G-knjBh1DC-SzAC1BCc>
Cc: dnsop <dnsop@ietf.org>
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: Sun, 22 Mar 2015 16:49:36 -0000

On Sat, Mar 21, 2015 at 6:12 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> 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.

+1. This is useful.

W

>  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
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf