Re: [DNSOP] Status of "let localhost be localhost"?

Paul Vixie <paul@redbarn.org> Wed, 02 August 2017 14:45 UTC

Return-Path: <paul@redbarn.org>
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 0AB2613211D for <dnsop@ietfa.amsl.com>; Wed, 2 Aug 2017 07:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 Jmvl6uX3a8lF for <dnsop@ietfa.amsl.com>; Wed, 2 Aug 2017 07:45:15 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51F1A131CA2 for <dnsop@ietf.org>; Wed, 2 Aug 2017 07:45:15 -0700 (PDT)
Received: from [192.168.1.33] (unknown [47.143.68.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id B61A461FF3; Wed, 2 Aug 2017 14:45:13 +0000 (UTC)
Message-ID: <5981E579.1040808@redbarn.org>
Date: Wed, 02 Aug 2017 07:45:13 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.16 (Windows/20170718)
MIME-Version: 1.0
To: william manning <chinese.apricot@gmail.com>
CC: Jacob Hoffman-Andrews <jsha@eff.org>, dnsop <dnsop@ietf.org>
References: <05e469cf-1325-89fc-4a81-661f8647e869@eff.org> <CAKXHy=ctB=LZkX9j=8-Jy0NkTAs2tAesa4gmFhfp94O5=9U4TA@mail.gmail.com> <1dbb47a4-c6e2-97d2-a1d7-ce6c65a4042a@eff.org> <CACfw2hiX7U74n9+defcYiD7jLKZeLhtLM6WP5YM_WuAoA8ecYQ@mail.gmail.com>
In-Reply-To: <CACfw2hiX7U74n9+defcYiD7jLKZeLhtLM6WP5YM_WuAoA8ecYQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pXLVdDJShbCJDPbl4EMTeoN-7oc>
Subject: Re: [DNSOP] Status of "let localhost be localhost"?
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, 02 Aug 2017 14:45:16 -0000


william manning wrote:
> ...
> if you are concerned that completion logic is broken in resolvers
> and the string "localhost" is not appended to the domain, then you
> really are asking for the root servers to backstop the query with an
> entry for localhost. and for the first 20 years of the DNS, there was
> an entry for localhost. in many of the root servers. it was phased
> out for several reasons, two key ones were DNSSEC and the fact that
> most resolvers had corrected their broken completion logic. There is
> no good reason to bring it back for special processing. It's just a
> string.

+1.

-- 
P Vixie