Re: [DNSOP] Some thoughts on special-use names, from an application standpoint
hellekin <hellekin@gnu.org> Thu, 26 November 2015 12:00 UTC
Return-Path: <hellekin@gnu.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 4324B1A1A5D for <dnsop@ietfa.amsl.com>; Thu, 26 Nov 2015 04:00:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level:
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] 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 vOQXiUYfqb93 for <dnsop@ietfa.amsl.com>; Thu, 26 Nov 2015 04:00:39 -0800 (PST)
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:4830:134:3::10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF4B91A1A58 for <dnsop@ietf.org>; Thu, 26 Nov 2015 04:00:38 -0800 (PST)
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <hellekin@gnu.org>) id 1a1vE0-00006C-TO for dnsop@ietf.org; Thu, 26 Nov 2015 07:00:37 -0500
Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37888) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <hellekin@gnu.org>) id 1a1vE0-000064-GL for dnsop@ietf.org; Thu, 26 Nov 2015 07:00:32 -0500
Received: from x55b50b1e.dyn.telefonica.de ([85.181.11.30]:43728 helo=[172.23.216.173]) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <hellekin@gnu.org>) id 1a1vDz-0002hS-UN for dnsop@ietf.org; Thu, 26 Nov 2015 07:00:32 -0500
Message-ID: <5656F43D.9060401@gnu.org>
Date: Thu, 26 Nov 2015 11:59:57 +0000
From: hellekin <hellekin@gnu.org>
Organization: https://gnu.org/consensus
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0
MIME-Version: 1.0
To: dnsop@ietf.org
References: <7E4C1956-8477-4F07-BC29-3D163B7160AA@mnot.net>
In-Reply-To: <7E4C1956-8477-4F07-BC29-3D163B7160AA@mnot.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value).
X-Received-From: 2001:4830:134:3::e
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/s_3kU7eseQgRnHwJ8E2tI5OkMyM>
Subject: Re: [DNSOP] Some thoughts on special-use names, from an application standpoint
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 26 Nov 2015 12:00:41 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 11/26/2015 06:38 AM, Mark Nottingham wrote: > > Given this context, I was disturbed to hear the design team presentati on > in Yokohama > So you mean there's an already working team on the revision of RFC6761, and that team had the time to prepare a presentation, while the DNSOP chairs didn't have the time to respond to volunteers nor to announce this team. This is simply unacceptable. I concur that the revision of RFC6761 should go to another group where "Internet community" makes some sense and corporate dissent is not silenced by ignoring legitimate requests. Please don't expect any apologies from me for telling the truth. This is a carnival of an inclusive process. Thank you Mark for the heads up. == hk -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJWVvQ8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0 ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg9ewoQALD1dF/Wqyh2Lo5qZ35PUANA bvq2k5BZd1UsN488+V4v7PnAHxO7XgR8IQSYYnp1oYNaZl5WbFEPjT6HOSR3O4lr 7iSVeSxPux8hssSxorkWtBVk8oAnImGEPyIlYunBLcTyasXLY5+2fzmR1+P4/9Kk ahjHvuQa6dOAXhqTMBizwb3kZ2PC2hFlM5LKMIBcf9GfTVmH//fbEalHYPYEwMCY AvX9mkMvvWcWhn15OXRi50r3kQl65d0KQA2euQ8mUIe5qafDHASBtZLc81t0rAXv fjaWT4REu+KUHexWKgI7NFF3uZ0M0Cm7imYN6+YG+AWFtPrr4SPh1BA0L4td93q8 bGxGEJrDTWRVaW2c98UO5bFxm3kqcM4oTdBD1Rg4yC1OatvuKzZp6nPrFG09G5rn PjorrqoNx0MHxwejrTHkkhnmvmgTfPUTvkT/7zUYLTwRITDrjzOyj932COrZV+A3 dak5M5hRLhR8jswx/lh+SmY1RFAtCuNDcoFuXTOJygwSpj7WvigIORiT6ATLFlfW mxYxkVP/Tc76anRTk5O/AIu87c5K9fr6TPiFRIL/0eKnFBEMn2qbaW7TLvAl6o89 kgYYp4u59ve0vCL6gE2sn1w1EYnctFVxpzcg9HkFl/MFuQyWdc4yb5OdFWW8sema 8hpTT/KiW1/KDHGj0kcB =IZoh -----END PGP SIGNATURE-----
- [DNSOP] Some thoughts on special-use names, from … Mark Nottingham
- Re: [DNSOP] Some thoughts on special-use names, f… hellekin
- Re: [DNSOP] Some thoughts on special-use names, f… George Michaelson
- Re: [DNSOP] Some thoughts on special-use names, f… Tim Wicinski
- Re: [DNSOP] Some thoughts on special-use names, f… Mark Nottingham
- Re: [DNSOP] Some thoughts on special-use names, f… Philip Homburg
- Re: [DNSOP] Some thoughts on special-use names, f… Jacob Appelbaum
- Re: [DNSOP] Some thoughts on special-use names, f… Philip Homburg
- Re: [DNSOP] Some thoughts on special-use names, f… Jacob Appelbaum
- Re: [DNSOP] Some thoughts on special-use names, f… David Conrad
- Re: [DNSOP] Some thoughts on special-use names, f… str4d
- Re: [DNSOP] Some thoughts on special-use names, f… Edward Lewis
- Re: [DNSOP] Some thoughts on special-use names, f… John Levine
- Re: [DNSOP] Some thoughts on special-use names, f… Philip Homburg