Re: I-D Action: draft-west-let-localhost-be-localhost-00.txt

"John R Levine" <johnl@taugh.com> Tue, 27 September 2016 21:19 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0DD712B4C3 for <ietf@ietfa.amsl.com>; Tue, 27 Sep 2016 14:19:52 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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=b1TRCMeG; dkim=pass (1536-bit key) header.d=taugh.com header.b=iIW9v5b+
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 lDCfy-uCiqNJ for <ietf@ietfa.amsl.com>; Tue, 27 Sep 2016 14:19:51 -0700 (PDT)
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 D3DBC12B249 for <ietf@ietf.org>; Tue, 27 Sep 2016 14:19:50 -0700 (PDT)
Received: (qmail 63214 invoked from network); 27 Sep 2016 21:19:47 -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=f6ed.57eae273.k1609; bh=yRVumyoa38EteItQMpsk+Fv1mXKCbgN6kHMrm+Ih7kU=; b=b1TRCMeGoQJD7HyYTcRcFZPJRgooFPymQb0P4g2MnbZlSkPhwYkhYzj5chod7r6IM+I9KpSYNvzzETfVNSUYvPK6jRc+LAlRcmNvYHwWTdOX20M4YzhsCVp/iQ0nLlmtlbqlbnZINIfo+ayYZ/bbbX3bKUJpgyyY67ZMbMn0dySRJgzZST5wbAJfvMCjwYAlsTb9U2mGi+qf7kMoCJYbdau4M4ixsqQgLs7XiSmC/Ds7LsyBNfebzT3wEbQ2BZCD
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=f6ed.57eae273.k1609; bh=yRVumyoa38EteItQMpsk+Fv1mXKCbgN6kHMrm+Ih7kU=; b=iIW9v5b+ZjOC1sSBc9JE5beKZVbsv4adQwbnoVrJbT4YyQ16N8V19JfBnMkBQhcKjmwe/+4TWJeQo2/frjHJRGYiDx/h+nc+l6Obd8TuL0aTp2lUeQsD+qSntO5PysN4cevqdTzWOJfES+HLiGb8hhn9oSVWOXjERyG3F+nwM8SV97H6pEzmST9kZGhGy95LGTjVBbwdI1P3IF8K8ma7Q2qh66iF5S0Oklgt7yqw9KVo7KHB43ttlV0vPYTX2YU8
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.0/X.509/SHA1) via TCP6; 27 Sep 2016 21:19:47 -0000
Date: 27 Sep 2016 17:19:49 -0400
Message-ID: <alpine.OSX.2.11.1609271717330.72382@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Emily Shepherd" <emily@emilyshepherd.me>
Subject: Re: I-D Action: draft-west-let-localhost-be-localhost-00.txt
In-Reply-To: <20160927211208.zrkp4txdpelw3at4@emily-tablet>
References: <CAKXHy=fCoQPb4EJ2aS9Lfj6yKM-HotjhO_VsPk2PDeFATxpGdg@mail.gmail.com> <20160927184845.5034.qmail@ary.lan> <20160927211208.zrkp4txdpelw3at4@emily-tablet>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IQeDDU5te_Zd59k784ZhmHaTPxs>
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2016 21:19:53 -0000

> I'm probably not explaining myself well so I'll give an example. In the setup 
> above, let's say you've set 127.0.1.1 to be your local DNS server, meaning 
> that you might expect the following commands to work:
>      $ dig mysite.localhost
>   mysite.localhost IN A 127.0.0.1
>
>   $ dig myothersite.localhost
>   myothersite.localhost IN A 127.200.200.200
>
> But, under this proposal wouldn't dig be obliged to refuse to forward the 
> request onto 127.0.1.1? How does dig (or your browser or any other resolving 
> API) know the difference between a bog standard caching DNS server and a 
> local DNS server that has explicitly been set up to route local lookups?

I don't see why.  You're allowed to use common sense when interpreting 
RFCs, and the message here is clearly that if you want to interoperate you 
do not send queries for *.localhost out of your computer. The twisty way 
my or your internal DNS setup works is out of scope.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly