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

"John Levine" <johnl@taugh.com> Wed, 29 January 2014 05:55 UTC

Return-Path: <prvs=00995a0cdf=johnl@iecc.com>
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 B89A01A0280 for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 21:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level:
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 9ScRpbel10yf for <dnsop@ietfa.amsl.com>; Tue, 28 Jan 2014 21:55:06 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 21C2F1A0193 for <dnsop@ietf.org>; Tue, 28 Jan 2014 21:55:05 -0800 (PST)
Received: (qmail 73226 invoked from network); 29 Jan 2014 05:55:02 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 29 Jan 2014 05:55:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52e897b6.xn--9vv.k1401; i=johnl@user.iecc.com; bh=Sa/ErOPWv4YLrzOlgx12YvrmLQJN7IiRLICYgzuUMa4=; b=dERrP36fA90W8/xiNgNrR00YTnxR7pKQ4KgEvffSvYheI7f6FbK3kIabmhJ5ERz41o0H4DL0+q2hZ7UocHsS1tTqYg+GRHqyS0OgT7d3qd0snJuGJ0Y2Y7DTscsQ96hJTX3iW7iaj9P4aOijRZmiR7pVe2H/xvMPUhOj7r7oZzERrfzXMKIECBj0JjXr2RvKaxlr2DtUbvGs+Db2rh7kOinUKqVJSlx0D+0+Ne00664E4UrN4tndAohJsC7Fd0x7
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52e897b6.xn--9vv.k1401; olt=johnl@user.iecc.com; bh=Sa/ErOPWv4YLrzOlgx12YvrmLQJN7IiRLICYgzuUMa4=; b=aDPaRe3q5w5ZJK2JEZZtsLrR4Oq6/qlfsNQJvZAgw8k96I+GY0zuOXdWpBEGsHOtMt5Yxt86K/trG5gpd+dk3kwXI0fgKf1TJnrf5FcaWPKhEPDNvYtoFt8sBkBf7Jt251vPTg9iNm8je7tTS/SW5Xgus598r1DA+2DF/ee+3RMAaVVG2reT+fSPgfrlRYyTCR0td6uLFaYSpFoQM8aUQsMi32Njc+9SiSr8Cv94iMYmdUDIIVVPQd3IcO+iA313
Date: 29 Jan 2014 05:54:38 -0000
Message-ID: <20140129055438.2402.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <E7C51A3E-1F2A-4327-A9C7-E0832A265184@apple.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: cheshire@apple.com
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 05:55:07 -0000

>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.

On my home network I have a couple of dozen hosts, what with all the
networked printers, phones, tablets, laptops, and so forth, and
because I am a lazy guy, I give them names like kindle.lan rather than
longer global names.  My local DNS cache resolves those names to
addresses in 192.168/16.  I think that's pretty typical of small
business networks.  It's useful, but I don't see anything worth
standardizing other than don't resolve .LAN on the global Internet.

R's,
John