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

Paul Wouters <paul@nohats.ca> Tue, 26 May 2015 23:00 UTC

Return-Path: <paul@nohats.ca>
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 85F981B32D4 for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 16:00:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 EbXYl-vDaDAa for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 16:00:13 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FA0B1B32D0 for <dnsop@ietf.org>; Tue, 26 May 2015 16:00:13 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3lx9jl150szB3B for <dnsop@ietf.org>; Wed, 27 May 2015 01:00:11 +0200 (CEST)
Authentication-Results: mx.nohats.ca; dkim=pass (1024-bit key) header.d=nohats.ca header.i=@nohats.ca header.b=cJu6RNzQ
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id sOgplxxoDHMC for <dnsop@ietf.org>; Wed, 27 May 2015 01:00:08 +0200 (CEST)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <dnsop@ietf.org>; Wed, 27 May 2015 01:00:08 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 7B1638003D for <dnsop@ietf.org>; Tue, 26 May 2015 19:00:07 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1432681207; bh=fChKQL/fGQF0GumvCBNi0wiQUK2JrTG17ro21ITpaPQ=; h=Date:From:To:Subject:In-Reply-To:References; b=cJu6RNzQ44YRuhBW1BInALbBSmMz1aqkCEDFADJDVQMxYWYoCFV3K1qMPQQL0BlMr o7vOCoBWQgqWJO1XnedX6oByRa9rL4raWjNe+br/QpcM6CrpbGPu3FTwBz58t8XU0g e5Sawz3NGsir5/moUAG8DnsqAcqws3HZIkpowvIQ=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.15.1/8.15.1/Submit) with ESMTP id t4QN079p005256 for <dnsop@ietf.org>; Tue, 26 May 2015 19:00:07 -0400
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Tue, 26 May 2015 19:00:07 -0400
From: Paul Wouters <paul@nohats.ca>
To: dnsop WG <dnsop@ietf.org>
In-Reply-To: <5564F291.70109@redbarn.org>
Message-ID: <alpine.LFD.2.11.1505261844410.2531@bofh.nohats.ca>
References: <20150526211813.15713.qmail@ary.lan> <CB0978C7-AB12-4580-A7D7-6E87991D7BAA@nic.br> <5564F291.70109@redbarn.org>
User-Agent: Alpine 2.11 (LFD 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/aqj7w7nG_SfpJzRCt0nqfKu7_Pw>
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:00:15 -0000

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. Or will it get
NXDOMAIN and fail the mail. And when the application sending mail is not
an enduser MUA, what will happen with these failed emails and when will
people notice the problem?

I've been inside a bank network where they could not get rid of "unused"
zones for > 10 years because of unqualified lookups and applications of
which they only had the binary and no replacement product ready, running
on very old Microsoft Windows versions. (although perhaps now they could
DNAME it)

While this applies to all unqualified names, the most used ones that I
expect this would hit, based on my personal biased experience, is
"linux", "server", "mail", "oracle" and "exchange".

The last two can be handled by those starting the problem TLDs (vendor and
their customers). The first three will cause outages and problems.

Paul