Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-grothoff-iesg-special-use-p2p-names-00.txt]

Ted Lemon <ted.lemon@nominum.com> Tue, 10 December 2013 17:26 UTC

Return-Path: <Ted.Lemon@nominum.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 4D2951ADF62 for <dnsop@ietfa.amsl.com>; Tue, 10 Dec 2013 09:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 v3lyJCiNFtbY for <dnsop@ietfa.amsl.com>; Tue, 10 Dec 2013 09:26:34 -0800 (PST)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id A288F1ADF74 for <dnsop@ietf.org>; Tue, 10 Dec 2013 09:26:34 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKUqdOxSSpj4oSy5ngKID7waRrBTAMcFAg@postini.com; Tue, 10 Dec 2013 09:26:29 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4FB0B1B82E1 for <dnsop@ietf.org>; Tue, 10 Dec 2013 09:26:28 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 350A7190043 for <dnsop@ietf.org>; Tue, 10 Dec 2013 09:26:28 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 10 Dec 2013 09:26:27 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <FA1AB90A-7FA3-48FB-BD30-5C2D141D4104@virtualized.org>
Date: Tue, 10 Dec 2013 12:26:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <FEC642D5-0DAA-4C2F-9D68-3B41905CAE02@nominum.com>
References: <529B75A2.10703@appelbaum.net> <529B7E4A.2070600@grothoff.org> <73387529-308B-424D-807C-D41E59B1D5E8@virtualized.org> <52A244EC.5040104@grothoff.org> <37B27FD9-C0BB-4178-84F3-FD6BA6402AFB@virtualized.org> <52A25F03.3070502@grothoff.org> <D259AC50-E055-457F-841E-E72D2D19C53C@virtualized.org> <52A5237E.8050601@grothoff.org> <FA1AB90A-7FA3-48FB-BD30-5C2D141D4104@virtualized.org>
To: dnsop WG <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Subject: Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-grothoff-iesg-special-use-p2p-names-00.txt]
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, 10 Dec 2013 17:26:36 -0000

Can I just point out here that the only real technical points that have been raised in this discussion thus far, at least that I can recall, are that:

(1) defining sTLDs produces a small (relatively) amount of useless traffic at the root
(2) defining sTLDs may have trademark implications that the IETF is not competent to address
(3) supporting sTLDs in stub resolvers requires changes to stub resolvers
(4) it would be nice to have stable specifications for the proposed sTLDs

There have been a lot of expressions of strong opinion on this topic, many coming from people whose opinions I generally respect, but none of these have been rooted in any technical argument that was in any way overtly expressed.

Please do not respond to this message by re-asserting your strong opinion.   Please do not respond to this message by asserting that there's a better way than what's been proposed in the draft we are discussing, in your opinion.

I assume that there is some reason for the strong negative reaction some DNS glitterati have expressed towards this proposal, but whatever that reason is has not yet been expressed.   If you have an inkling of what that reason might be, and it is not simply a strong feeling based on history, a feeling of dislike for one of the proposed name resolution protocols, or a concern about how someone might react to the IESG taking action on this, I would greatly appreciate it if you could express that reason.

I should point out that I don't have the power to call consensus on this, so you don't need to get all upset if you think this conversation is not going in the direction you want.   I'm just trying to figure out why this has generated so much heat, and so little light.

And, it is gently snowing outside.  Yay!