Re: [DNSOP] Alternative Special-Use TLD problem statement draft
Ted Lemon <mellon@fugue.com> Wed, 06 April 2016 18:53 UTC
Return-Path: <mellon@fugue.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D732512D0E1 for <dnsop@ietfa.amsl.com>; Wed, 6 Apr 2016 11:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 kspavko1yPcK for <dnsop@ietfa.amsl.com>; Wed, 6 Apr 2016 11:53:56 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3060212D624 for <dnsop@ietf.org>; Wed, 6 Apr 2016 11:53:54 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id c126so40735809lfb.2 for <dnsop@ietf.org>; Wed, 06 Apr 2016 11:53:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eOz7X0MdC/PwGgI+QN+CEUHpkgjGNsmkU4b+69cSxV4=; b=EyevpB6nn9bN+l9Bvq1EVAwoeP9tbrNwJbfPNvMkbGXpE3aouJ/vNQA0MggAs3u8jj SSMvyyuF5//X5Du2SJw2RvGKDdxukBwQW008qAWnDY0UaZkSlJrwmFmhlwSQz/3nrWQO a9iJDdDkSh4R/fzGXSEfEfp8F1FAEy+VAlnPCJPivUihus7Vq2V8YfzMhY3ve52b0e9/ 43RpABjDH13gknJfAWRaPsK0WcVmKtDLCzhZ4xXdrfjyssiDs3JLmwlI/FiH1Q3gdENk vryQXy0rhMhAAWUruf/KwPbPjEwgKQhfSB/Bb8gi9CUvh+KMo/zF7smX4SnCCUlFi/pi dH8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eOz7X0MdC/PwGgI+QN+CEUHpkgjGNsmkU4b+69cSxV4=; b=U1N4tE/wS0qx65Dx+yPs7WJIYCMz6gj7fqFFrg1QsX5FNyVPHf6PnXDtTN80/ejJgU CR/ynky7h1ACMUCfxSJcwKV9jxHAyJQa1hTVUbZsWw2k6RmdkjqkaDLnSQmZ3d3av5he bvUcaoh1FNOBbbjNw9OOcSqaBaVzKsGnfVSYd5c9EqDDJbebrVZzOrz0b/A6ifdb4nht dFh0n/thFwV/JglXy0GE5GKw+pnZYagtxaphar8d56wN8/rzrSzdsQJlQ9JM49ka8LC+ PSd0m6EQqQkE5iY13hKZnz1E/rho4CM/JQ8S8iXqmpXcCTLUY3JgqN5pbsSZD62PoZHE qCBw==
X-Gm-Message-State: AD7BkJI3dsNS/C22sZOMkmMLopOJbzjMjorSgxzJ60qAuGqdzK2feIFe+5tLqgYCrUKfrtTijKnEltwhuJEuIQ==
X-Received: by 10.25.144.143 with SMTP id s137mr10163862lfd.53.1459968832374; Wed, 06 Apr 2016 11:53:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Wed, 6 Apr 2016 11:53:12 -0700 (PDT)
X-Originating-IP: [2001:67c:1231:998:ec62:80b3:91d7:df8a]
In-Reply-To: <02BC1B94-AC3A-49A8-8595-45B3AF56B35E@vpnc.org>
References: <8D23D4052ABE7A4490E77B1A012B630797A44227@mbx-03.WIN.NOMINUM.COM> <02BC1B94-AC3A-49A8-8595-45B3AF56B35E@vpnc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 06 Apr 2016 15:53:12 -0300
Message-ID: <CAPt1N1=NGGkAZMa4k+KpFyTAmdQ2c1uuzYiCgS-Myp4GzockMQ@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="001a11402274a32fed052fd57b09"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/GxzZltuK0BvhHtqA2NhZw0UHzIs>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [DNSOP] Alternative Special-Use TLD problem statement draft
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 06 Apr 2016 18:54:00 -0000
Paul, draft-adpkja-dnsop-special-names-problem document is not a working group document. The working group can adopt it or not as the working group chooses. The same is true of the document I have offered. So to answer a slightly different question than the one you asked, what I am proposing is that the working group adopt the tldr document, likely with changes, rather than adopting the adpkja document, which I think would take much more work to get into shape. The entire reason that I started the tldr document is that I felt that the adpkja document not only didn't accurately describe the problem, but contained much more text describing some authors' beliefs about what the solutions should be than text describing what the problem is. I also felt that the scope of the adpkja document was too narrow--it mostly talks about problems with 6761, without really talking about the greater context of those problems. On Wed, Apr 6, 2016 at 12:13 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote: > On 5 Apr 2016, at 16:35, Ted Lemon wrote: > > I wrote about six pages of comments on the recently-submitted special-use >> TLD problem statement document. However, ultimately I concluded that it >> would be easier to just write what I thought the problem statement should >> look like rather than try to suggest (and then no doubt discuss one by one) >> a large set of changes that I think it needs. >> >> So this weekend I spent quite a bit of time talking to various people who >> I knew would have insight into the question, and the result is the draft I >> just submitted. Ralph Droms was instrumental in inspiring me to write the >> document, and helped me out by doing an initial review. >> >> I've included the submission announcement below. I realize that this is >> a woefully late submission for discussion at IETF 95, since I mostly wrote >> it yesterday, _at_ IETF 95. However, I think it may serve as a better >> starting point for the discussion than the current problem statement draft, >> so if you have time to read it, I would genuinely appreciate it if you >> could give it a look. >> > > Clarifying question: are you formally requesting the WG to stop work on > draft-adpkja-dnsop-special-names-problem and switch to this one? If not, > what do think we should do about the two? > > --Paul Hoffman > > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
- [DNSOP] Alternative Special-Use TLD problem state… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Philip Homburg
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Philip Homburg
- Re: [DNSOP] Alternative Special-Use TLD problem s… Paul Hoffman
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Tim Wicinski
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Alain Durand
- Re: [DNSOP] Alternative Special-Use TLD problem s… George Michaelson
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… George Michaelson
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… George Michaelson
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Patrik Fältström
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… Philip Homburg
- [DNSOP] Example domains and following the standar… Stephane Bortzmeyer
- [DNSOP] Formal syntax in the Special-Use domain r… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Formal syntax in the Special-Use doma… Alain Durand
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… Alain Durand
- Re: [DNSOP] Alternative Special-Use TLD problem s… Paul Hoffman
- Re: [DNSOP] Alternative Special-Use TLD problem s… joel jaeggli
- Re: [DNSOP] Alternative Special-Use TLD problem s… Suzanne Woolf
- Re: [DNSOP] Alternative Special-Use TLD problem s… Suzanne Woolf
- Re: [DNSOP] Alternative Special-Use TLD problem s… Suzanne Woolf
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… joel jaeggli
- Re: [DNSOP] Alternative Special-Use TLD problem s… George Michaelson
- Re: [DNSOP] Alternative Special-Use TLD problem s… joel jaeggli
- Re: [DNSOP] Alternative Special-Use TLD problem s… Suzanne Woolf
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Warren Kumari
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Stephane Bortzmeyer
- Re: [DNSOP] Alternative Special-Use TLD problem s… John Levine
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… David Conrad
- Re: [DNSOP] Alternative Special-Use TLD problem s… Ted Lemon
- Re: [DNSOP] Alternative Special-Use TLD problem s… Warren Kumari
- Re: [DNSOP] Alternative Special-Use TLD problem s… Adrien de Croy
- Re: [DNSOP] Alternative Special-Use TLD problem s… John R Levine
- Re: [DNSOP] Alternative Special-Use TLD problem s… Philip Homburg
- Re: [DNSOP] Alternative Special-Use TLD problem s… Donald Eastlake