Re: [DNSOP] ALT-TLD and (insecure) delgations.

Andrew Sullivan <ajs@anvilwalrusden.com> Sat, 04 February 2017 02:10 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A892E1295F1 for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 18:10:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 y-qgEMlZmU2e for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 18:10:11 -0800 (PST)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id AA4CB1295F4 for <dnsop@ietf.org>; Fri, 3 Feb 2017 18:10:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 4ACAD11649 for <dnsop@ietf.org>; Sat, 4 Feb 2017 02:10:16 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBJKbqCRR6lA for <dnsop@ietf.org>; Sat, 4 Feb 2017 02:10:15 +0000 (UTC)
Received: from mx2.yitter.info (192-0-220-231.cpe.teksavvy.com [192.0.220.231]) by mx2.yitter.info (Postfix) with ESMTPSA id A0B601162D for <dnsop@ietf.org>; Sat, 4 Feb 2017 02:10:15 +0000 (UTC)
Date: Fri, 3 Feb 2017 21:10:09 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20170204021009.GE67739@mx2.yitter.info>
References: <CAH1iCiqXohb_7LsQ2EMo8ZB-t20mKq_nUDS8vebhtSXoM13DTg@mail.gmail.com> <20170203210922.7286C618213C@rock.dv.isc.org> <9B6211A9-20B5-4B15-A8FD-A1390DAD76AE@fugue.com> <20170203224708.A0EE061891C7@rock.dv.isc.org> <5EAC5DDC-7B93-40B5-B28D-150DAABE4BAC@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5EAC5DDC-7B93-40B5-B28D-150DAABE4BAC@fugue.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/67GPOSTk5run51oZVkGE3ySRWo0>
Subject: Re: [DNSOP] ALT-TLD and (insecure) delgations.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 04 Feb 2017 02:10:13 -0000

On Fri, Feb 03, 2017 at 07:59:24PM -0500, Ted Lemon wrote:
> Mark, I don't think you've actually given an answer to my question.
> I understood that .ALT was for alternative naming systems, not for
> DNS locally-served zones.   We simply need to decide whether or not
> that's true.   I think either answer is fine; we just need to pick
> one.

I agree with this.  I will say that, when I first started working on
this with Warren, it was really for the use-case where people would
tread on the namespace as a protocol switch -- we wanted a sandbox in
which things like onion could live.  My memory is that only after that
did we start thinking of a sort of 1918-style part of the DNS as
well.  That may have been a mistake, since as this discussion is
showing the properties of an in-protocol, in-DNS namespace without
delegations are somewhat different to alternative-protocol uses that
do not rely on the DNS at all.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com