IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Tue, 26 May 2015 21:18 UTC

Return-Path: <johnl@taugh.com>
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 581B21B31D2 for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 14:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.663
X-Spam-Level: *
X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 Di6fOf93VocT for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 14:18:36 -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-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A9F01B31CF for <dnsop@ietf.org>; Tue, 26 May 2015 14:18:36 -0700 (PDT)
Received: (qmail 4062 invoked from network); 26 May 2015 21:18:42 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 26 May 2015 21:18:42 -0000
Date: Tue, 26 May 2015 21:18:13 -0000
Message-ID: <20150526211813.15713.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <DFC8A733-1876-4362-B1AC-E7A7151FBF8F@nic.br>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/IkAsvyj3NTYCF8N_fYkU9d0ul58>
Cc: rubensk@nic.br
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 21:18:37 -0000

>I'm curious about one of those TLDs: MAIL. Besides dotless "mail", which seems to hit
>the root at very high rate (lack of negative caching) and shouldn't be ever allowed to
>exist, and a few meaningful labels like local.mail*, I can't recall the reasoning for
>being concerned with <something-here>.mail.  
>
>No matter whether one thinks the responsibility to deal with .MAIL lies with, what are
>the issues that people see with it ? 

Queries for dotless mail already provide plenty of issues.  See RFC
7085.

R's,
John

v2.23.0 | Report a Bug | By Email