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

"John R Levine" <johnl@taugh.com> Mon, 06 February 2017 04:18 UTC

Return-Path: <johnl@taugh.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 03F8C129B39 for <dnsop@ietfa.amsl.com>; Sun, 5 Feb 2017 20:18:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=TKaRvqBo; dkim=pass (1536-bit key) header.d=taugh.com header.b=hzIjJv7p
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 Qa3OiR1Qak54 for <dnsop@ietfa.amsl.com>; Sun, 5 Feb 2017 20:18:20 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2C11129B2F for <dnsop@ietf.org>; Sun, 5 Feb 2017 20:18:19 -0800 (PST)
Received: (qmail 59572 invoked from network); 6 Feb 2017 04:18:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=e8b2.5897f90b.k1702; bh=B/NEmBuWv2TO+lEq/0fZWsnmKMNNXWSFPzYM6Suh5Ds=; b=TKaRvqBo0c9kRkFxjuVUrDYSfwvD8rIW5GIhGwoW6TWfatzYTKVO/NfD0jRexgB4YBo6DX52Z3y5idjhPWgbkEMnzgsMBgFMU4veeW3qxaehRmDLe53FKtDkXZXMzcwqx6O06rK8FTNjvM6PpycXEX2DT1cvX9wZoRFX/BffojYUd1k0sDcrTifWwJl755pPFn60a1u9t4OEzuUDlwmkyDtOTPSsB2hU9Oh5UvT5EWQjZcNwuHkPFtYLSzOL29sE
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=e8b2.5897f90b.k1702; bh=B/NEmBuWv2TO+lEq/0fZWsnmKMNNXWSFPzYM6Suh5Ds=; b=hzIjJv7p3tDz+7e7Qp7LQJJQNUEat2usWVNTwR0DusSbvA34lg+t2FeD9LGe8PvpK/XLxkNx6cW0ymy2PburP2md4iRMniRdftT8aN20+Jnz7JWbrEHkzo/jIjiwUSWuH19upcJQk5CHNIeGZNQg9wlR4rbwfkhwg9DHgjPJs9zzm0Q3/fu5jddDQ5w98pAVyrLEFwcKN7h/xwCEXX4CjZUOR+Z4/R78Zai86DsWfidDQIG15Ji01bD4TbVKhGp2
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 06 Feb 2017 04:18:18 -0000
Date: Sun, 05 Feb 2017 23:18:18 -0500
Message-ID: <alpine.OSX.2.20.1702052315130.13902@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPt1N1mbzhS19G_uDA8HokVxXuHy5uA7F1c84-1yUUpqZ2ifJQ@mail.gmail.com>
References: <6391B5BB-19BD-4717-B9BB-ECD145F7B4F6@fugue.com> <20170206040516.1701.qmail@ary.lan> <CAPt1N1mbzhS19G_uDA8HokVxXuHy5uA7F1c84-1yUUpqZ2ifJQ@mail.gmail.com>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/IH0ZyYyDiSc9nqb027LXi2p2wHc>
Cc: dnsop WG <dnsop@ietf.org>
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: Mon, 06 Feb 2017 04:18:21 -0000

> I'm pretty sure I've explained it enough times on this mailing list and in
> the relevant documents by now. If you don't agree, maybe we should just
> accept that. If you don't remember the explanation, it's in the homenet
> naming architecture doc I wrote.

Well, OK, I took another look, and from what I can see, it's a belief that 
people will find toaster.homenet.arpa harder or more confusing to type 
than toaster.homenet.

Just out of curiosity, how long is it worth waiting to get .homenet rather 
than .homenet.arpa?  If it took five more years, which at the current rate 
seems optimistic, would homenet still be relevant?

R's,
John