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

Rubens Kuhl <rubensk@nic.br> Fri, 29 May 2015 12:34 UTC

Return-Path: <rubensk@nic.br>
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 26F271A884E for <dnsop@ietfa.amsl.com>; Fri, 29 May 2015 05:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.437
X-Spam-Level: *
X-Spam-Status: No, score=1.437 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 3jdMwybKdeIy for <dnsop@ietfa.amsl.com>; Fri, 29 May 2015 05:34:45 -0700 (PDT)
Received: from mail.nic.br (mail.nic.br [200.160.4.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FFAD1A8825 for <dnsop@ietf.org>; Fri, 29 May 2015 05:34:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.nic.br (Postfix) with ESMTP id 9482110C44D; Fri, 29 May 2015 09:34:43 -0300 (BRT)
X-Virus-Scanned: Debian amavisd-new at mail.nic.br
Authentication-Results: mail.nic.br (amavisd-new); dkim=pass (1024-bit key) header.d=nic.br
Received: from mail.nic.br ([127.0.0.1]) by localhost (mail.nic.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 38tGxuHR8o4w; Fri, 29 May 2015 09:34:42 -0300 (BRT)
Received: from [IPv6:2001:12f0:4cf:ffff:65e2:7244:6986:b27] (unknown [IPv6:2001:12f0:4cf:ffff:65e2:7244:6986:b27]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.nic.br (Postfix) with ESMTPSA id A802810C44B; Fri, 29 May 2015 09:34:42 -0300 (BRT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.br; s=dkim; t=1432902882; bh=YRqFVyQ6fGjkwdNh2JjtjOVK5aLSDNFsQy+xi0RL6fE=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=Z/uwt9ZKT4XB8JJ7gjcrm/HJ8QMA1IYCB1Pslhm+eD0xGX6USZ+uvS/lg2nTT1akt gA86rmjpYe26lqSCSMyrcRbYOho+yDmTBzYiL8D9Px/k7caNRELL4K6Ei7yDm072fi /HVa0kwRxxj+oloHUx2jE+0crEpwvFkkdVvGIaQ0=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Rubens Kuhl <rubensk@nic.br>
In-Reply-To: <7FBF3D8B-E340-4540-A8B4-4786FB3E39C4@gmail.com>
Date: Fri, 29 May 2015 09:34:40 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB6C8C85-D26A-4003-8B51-496F6251BB08@nic.br>
References: <0CB7A66E-B6C9-4FE7-8452-172A5CF48895@gmail.com> <F28C4DE3-12CF-462D-BB55-5A02CA364173@interisle.net> <47EE9472-3E0C-4FA8-A058-8A288675C936@uniregistry.com> <E3483DBB-7F69-4CEB-ACD4-545B3CF7D4E0@INTERISLE.NET> <7FBF3D8B-E340-4540-A8B4-4786FB3E39C4@gmail.com>
To: Suzanne Woolf <suzworldwide@gmail.com>
X-Mailer: Apple Mail (2.2098)
DMARC-Filter: OpenDMARC Filter v1.3.1 mail.nic.br A802810C44B
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/lbpDDemUIyh2OYsWXPZBZxqz--Q>
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: Fri, 29 May 2015 12:34:46 -0000

> 
> It would be helpful to me in discerning consensus to separate two different concepts here.
> 
> 1. Delegating home/corp/mail in the root zone would be bad.
> 2. Adding home/corp/mail to the special-use name registry would be good.
> 
> Again, trying my best to speak as a disinterested observer of the discussion, I've seen little support for such delegations(1). I've seen a couple of arguments that seem to have strong support against such delegations.
> 
> However, that's not the question in front of the WG. The IETF doesn't decide what goes into the root zone. ICANN does, and appears to have already decided (stipulating that not everyone believes them, which strikes me as a separate problem) not to add those names to the root zone.
> 
> The question in front of the WG is whether to propose adding those names to the IETF registry for special-use names(2). I've heard support for that, but I've also heard a number of objections to such additions, and I'm having trouble telling how much the support for (2) is really support for (1) or vice versa.

It's also of notice that the support level for doing $something (for some value of $something) with 2 of those strings (home and corp) are higher than the support level for one of those strings (mail). 


Rubens