IETF Logo Mail Archive

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

Ray Bellis <ray@bellis.me.uk> Mon, 06 February 2017 15:56 UTC

Return-Path: <ray@bellis.me.uk>
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 E1555129EB2 for <dnsop@ietfa.amsl.com>; Mon, 6 Feb 2017 07:56:04 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 9nqMMBxQkIx0 for <dnsop@ietfa.amsl.com>; Mon, 6 Feb 2017 07:56:03 -0800 (PST)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FB91129412 for <dnsop@ietf.org>; Mon, 6 Feb 2017 07:56:03 -0800 (PST)
Received: from [46.227.151.81] (port=58247 helo=rays-mbp.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1cale3-0003cU-T1 (Exim 4.72) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Mon, 06 Feb 2017 15:55:59 +0000
To: dnsop@ietf.org
References: <6391B5BB-19BD-4717-B9BB-ECD145F7B4F6@fugue.com> <20170206040516.1701.qmail@ary.lan> <CAPt1N1mbzhS19G_uDA8HokVxXuHy5uA7F1c84-1yUUpqZ2ifJQ@mail.gmail.com> <alpine.OSX.2.20.1702052315130.13902@ary.qy> <CAPt1N1m2mowdCF6igU0TN-FCcjas9AaY-uGma4HgPGKx0Jg4Tw@mail.gmail.com> <4E481C14-1C2B-4A18-A4F2-582208C1DDE3@ogud.com>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <d355013d-e1f9-2e92-6ac6-a09fdc38dcec@bellis.me.uk>
Date: Mon, 06 Feb 2017 15:56:01 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <4E481C14-1C2B-4A18-A4F2-582208C1DDE3@ogud.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YlOrk5bZLgZHSydL7YqY2Y61wak>
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 15:56:05 -0000


On 06/02/2017 15:29, Ólafur Gudmundsson wrote:
> Ted,
> 
> What RFC are you referring to?
> 
> Why do you think .ARPA is for services?
> It's for infrastructure and homenet wants to join the infrastructure.
> 
> It is waste of time arguing if name A or B is better take the one you
> can get faster.

It really isn't.

If I type "arpa" into Google (without the leading dot) I don't get the
new "Address and Routing Parameter Area" definition.

I get a big side bar with the DARPA logo and mention of the US DoD
everywhere.

That might well be fine for us "in the know" techies, but as far as I'm
concerned it's not fine for the residential users that are the target
market for Homenet.

That's even more true now than it was before November.

Ray (no hat)

v2.23.0 | Report a Bug | By Email