Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 29 January 2014 15:21 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 0A1271A03D5 for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 07:21:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=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 krfpdoeYFymv for <dnsop@ietfa.amsl.com>; Wed, 29 Jan 2014 07:21:30 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id F198B1A028A for <dnsop@ietf.org>; Wed, 29 Jan 2014 07:21:29 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s0TF1COe043719 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsop@ietf.org>; Wed, 29 Jan 2014 08:01:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20140129055438.2402.qmail@joyce.lan>
Date: Wed, 29 Jan 2014 07:21:26 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5B0F7E9-E638-4666-AD84-CE3526FE0A74@vpnc.org>
References: <20140129055438.2402.qmail@joyce.lan>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1827)
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-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: Wed, 29 Jan 2014 15:21:31 -0000

On Jan 28, 2014, at 9:54 PM, John Levine <johnl@taugh.com>; wrote:

>> I believe that with the considerable sleuthing abilities of the IETF
>> community, we ought to be able to take this initial set of observed data
>> and treat it as a call to action for the IETF community, for someone to
>> step forward and tell us *why* those names are in use, are leaking out
>> to the root name servers, and what the intended use is for these names.
> 
> Um, we already know.  They're used to name things on private networks,
> often behind a NAT, and they leak out for random not particularly
> interesting reasons, such as people taking their laptops on trips
> which then look for the printer that lives on their office LAN when
> they're connected to the wifi at a coffee shop.

All that, plus "on their corporate network, there are search lists that allow shortened names; when they take their laptop off that network, they try to type in the shortened name".

--Paul Hoffman