Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps

Paul Vixie <paul@redbarn.org> Tue, 26 May 2015 23:07 UTC

Return-Path: <paul@redbarn.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 AE6821B3306 for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 16:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 jtGS5SpguqL9 for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 16:07:37 -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 789021B3304 for <dnsop@ietf.org>; Tue, 26 May 2015 16:07:37 -0700 (PDT)
Received: from [172.16.35.163] (unknown [109.235.242.75]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 48900184D7; Tue, 26 May 2015 23:07:35 +0000 (UTC)
Message-ID: <5564FCB3.3020608@redbarn.org>
Date: Tue, 26 May 2015 16:07:31 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.11 (Windows/20140602)
MIME-Version: 1.0
To: Paul Wouters <paul@nohats.ca>
References: <20150526211813.15713.qmail@ary.lan> <CB0978C7-AB12-4580-A7D7-6E87991D7BAA@nic.br> <5564F291.70109@redbarn.org> <alpine.LFD.2.11.1505261844410.2531@bofh.nohats.ca>
In-Reply-To: <alpine.LFD.2.11.1505261844410.2531@bofh.nohats.ca>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/cFecWXxjnVapJY1BgjOQPqFzJww>
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps
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: Tue, 26 May 2015 23:07:38 -0000


Paul Wouters wrote:
> On Tue, 26 May 2015, Paul Vixie wrote:
>
>>> Saying there is a concern with dotless MAIL is an easy sell, my
>>> question was on issues with not-dotless MAIL.
>>
>> i agree with ruben. i know of a lot of local uses of HOME, CORP, and
>> LOCAL, where non-dotless names inside some network perimeter have local
>> meaning. i know of no instance of MAIL being used that way.
>
> How do 15 year old OSes and applications implement and interact for
> "search domains".
>
> The answer is "very differently and often very wrongly".
>
> Are we sure that an application querying "mail" will still end up
> receiving
> an A record for mail.corp.com. when mail. is delegated.

yes. i wrote a lot of the 15-year-old code in question. (actually some
of it is 25 years old.) NOERROR vs. NXDOMAIN doesn't matter. all that
matters is that there is no AAAA or A RR at "MAIL.", and that's already
a rule, so what we're discussing here (your mail.corp.com example) will
not be impacted.

your example is spot-on when it comes to CORP, HOME, or LOCAL, or to
dotless domains, but not to *.MAIL.

-- 
Paul Vixie