Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps
Paul Vixie <paul@redbarn.org> Tue, 26 May 2015 22:24 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 AC1341B3221 for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 15:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.789
X-Spam-Level:
X-Spam-Status: No, score=0.789 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 RxFdWs9JcGUT for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 15:24:23 -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 4392F1B322E for <dnsop@ietf.org>; Tue, 26 May 2015 15:24:23 -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 4B764184D7; Tue, 26 May 2015 22:24:21 +0000 (UTC)
Message-ID: <5564F291.70109@redbarn.org>
Date: Tue, 26 May 2015 15:24:17 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.11 (Windows/20140602)
MIME-Version: 1.0
To: Rubens Kuhl <rubensk@nic.br>
References: <20150526211813.15713.qmail@ary.lan> <CB0978C7-AB12-4580-A7D7-6E87991D7BAA@nic.br>
In-Reply-To: <CB0978C7-AB12-4580-A7D7-6E87991D7BAA@nic.br>
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/UCSyRbcZ1E46RSld6wSGjXKcmWY>
Cc: dnsop WG <dnsop@ietf.org>, John Levine <johnl@taugh.com>
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 22:24:24 -0000
Rubens Kuhl wrote: > > RFC 7085 mentions MX queries to other existing TLDs, not MAIL. And I would be equally concerned with MX requests for dotless MAIL than with A/AAAA/SRV requests for dotless MAIL. dotless names were never contemplated as endpoints, even in the HOSTS.TXT era (see for example DECWRL.ARPA). so while i'm happy to have dotlessness shot down as often and as variously as possible, and to see those shoot-downs well documented, diverse, and unassailable, the raw fact of the matter is that a dotless name should _never_ be accidentally presentation-reachable. what i mean by presentation reachable is, you can't ping it, you can't send mail to it, you can't point an MX or NS or PTR at it, you can't look up its AAAA or A by typing it into a web browser, and so on. anybody who wants more background, see <http://www.circleid.com/posts/20110620_domain_names_without_dots/>. anybody still not convinced and who thinks this is a castle worth storming, see <http://queue.acm.org/detail.cfm?id=1242499>. > 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. -- Paul Vixie
- [DNSOP] followup and proposed actions: RFC 6761 i… Suzanne Woolf
- Re: [DNSOP] followup and proposed actions: RFC 67… Tom Ritter
- Re: [DNSOP] followup and proposed actions: RFC 67… Warren Kumari
- Re: [DNSOP] followup and proposed actions: RFC 67… Daniel Kahn Gillmor
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Tom Ritter
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Lyman Chapin
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Rubens Kuhl
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… Rubens Kuhl
- Re: [DNSOP] followup and proposed actions: RFC 67… John R Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… John R Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… John R Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Wouters
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… Mark Andrews
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Wouters
- [DNSOP] dotless names (was Re: followup and propo… David Conrad
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] dotless names (was Re: followup and p… Paul Vixie
- Re: [DNSOP] dotless names (was Re: followup and p… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Lyman Chapin
- Re: [DNSOP] followup and proposed actions: RFC 67… Jim Reid
- Re: [DNSOP] dotless names (was Re: followup and p… Mark Andrews
- Re: [DNSOP] followup and proposed actions: RFC 67… Patrik Fältström
- Re: [DNSOP] followup and proposed actions: RFC 67… Suzanne Woolf
- Re: [DNSOP] followup and proposed actions: RFC 67… Bob Harold
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Mark Andrews
- Re: [DNSOP] followup and proposed actions: RFC 67… Lyman Chapin
- Re: [DNSOP] followup and proposed actions: RFC 67… Rubens Kuhl
- Re: [DNSOP] followup and proposed actions: RFC 67… Andrew Sullivan