Re: [DNSOP] .arpa

Tim Chown <tjc@ecs.soton.ac.uk> Wed, 22 March 2017 11:50 UTC

Return-Path: <tjc@ecs.soton.ac.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 A28331294C1 for <dnsop@ietfa.amsl.com>; Wed, 22 Mar 2017 04:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 y5EsspFvwcOr for <dnsop@ietfa.amsl.com>; Wed, 22 Mar 2017 04:50:24 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 086A512714F for <dnsop@ietf.org>; Wed, 22 Mar 2017 04:50:23 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2MBoG7M028995; Wed, 22 Mar 2017 11:50:17 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v2MBoG7M028995
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1490183417; bh=HdyUxEP41LgYX0j8nj1o2d3bd2I=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=lqNWaGVdJm7EsZNTX++2kbUaWv2andE5/HDQxCkKB5YKqWNl+U6XaLSN0GC6dWm7D RSfalNQV39VVKt9Xbg1OHVXK1szeKcjL5WfanQ04+5oXRo7RZx+nnhcFpLDDPkd7PO rKo0bYsntmF76IrWYJd221UsZAkRwZuiSdf1ERHk=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y2LBoG3006105960Ks ret-id none; Wed, 22 Mar 2017 11:50:17 +0000
Received: from [10.99.194.168] ([94.117.221.163]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v2MBoC9v014704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Mar 2017 11:50:13 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <4DC4999E-CB4D-4F72-93BC-FDDC9A26A195@gmail.com>
Date: Wed, 22 Mar 2017 11:50:12 +0000
Cc: Jim Reid <jim@rfc1035.com>, IETF dnsop Working Group <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|7748a271060e43ad02f4e918d6bc04f1y2LBoG03tjc|ecs.soton.ac.uk|5B809E6D-8C23-4B41-B142-5706316775C6@ecs.soton.ac.uk>
References: <E07AFAEB-2B84-4610-87E7-94CF32CF3761@fugue.com> <7652B138-FEAB-4138-91FB-D71AFE6BEF2C@vigilsec.com> <6DCFBC9D-666A-4A3C-A418-82BB6AE3D25D@gmail.com> <alpine.LRH.2.20.999.1703210928390.28925@bofh.nohats.ca> <m1cqKPa-0000FeC@stereo.hq.phicoh.net> <71F88034-72C5-4AEE-9ACE-3493A1173634@gmail.com> <alpine.LRH.2.20.999.1703211011170.30281@bofh.nohats.ca> <0A544BEC-F719-4A7B-99E4-DC878EBE7B0C@gmail.com> <63DEB599-B4CD-4664-9AB6-9F505D81EDA7@rfc1035.com> <4DC4999E-CB4D-4F72-93BC-FDDC9A26A195@gmail.com> <5B809E6D-8C23-4B41-B142-5706316775C6@ecs.soton.ac.uk>
To: Suzanne Woolf <suzworldwide@gmail.com>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y2LBoG300610596000; tid=y2LBoG3006105960Ks; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v2MBoG7M028995
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PIg-p_BmzEHxlCY1P19ZE4T-79o>
Subject: Re: [DNSOP] .arpa
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 22 Mar 2017 11:50:28 -0000

> On 22 Mar 2017, at 11:40, Suzanne Woolf <suzworldwide@gmail.com> wrote:
> 
>> On Mar 22, 2017, at 3:05 AM, Jim Reid <jim@rfc1035.com> wrote:
>> 
>>> On 21 Mar 2017, at 14:53, Suzanne Woolf <suzworldwide@gmail.com> wrote:
>>> 
>>> RFC 3172 was written in 2001…
>> 
>> RFC 3172 was an attempt to rewrite history and contrive an acronym: Address and Routing Parameter Area - really?
> 
> Well, no. I thought it wasn’t rewriting anything, but setting a future direction. (The backronym was cute or annoying, depending on your POV, but ultimately not that important.)
> 
>>> Respectfully, I’ve always wondered who has this problem (US or non-US) besides network infrastructure geeks Of a Certain Age (yes, including myself, and many IETF participants).
>> 
>> It's a convenient tool for those hostile to USG "control" of the Internet: ie the US military is responsible for everything under .arpa, the US military's ARPA has still got some special status in the operation/development/control of the Internet, etc, etc. 
> 
> So the answer to “Why not actually use it where it’s technically suitable” is essentially “installed base”? 
> 
> I don’t mean to sound flippant— I’m just trying to understand the view that there’s a bigger obstacle to using .arpa than there is to asking ICANN for a root zone entry and engaging with all of the resulting complexities.

Surely the people who would make comments about (say) homenet.arpa are already making comments about in-addr.arpa and ip6.arpa?  So is there really that great a harm in using .arpa for additional things (that make many lives easier in many other ways)?

Tim