IETF Logo Mail Archive

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, 03 December 2013 17:27 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 500F21ABD2A for <dnsop@ietfa.amsl.com>; Tue, 3 Dec 2013 09:27:15 -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 5aaW-NZq4Xv8 for <dnsop@ietfa.amsl.com>; Tue, 3 Dec 2013 09:27:13 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id C55F01A1F72 for <dnsop@ietf.org>; Tue, 3 Dec 2013 09:27:13 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUp4Ub46klt5h6VULD/iN0qDb/uQ4V9KC@postini.com; Tue, 03 Dec 2013 09:27:11 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 0CE061B82DD for <dnsop@ietf.org>; Tue, 3 Dec 2013 09:27:11 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (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 D5F4E190043; Tue, 3 Dec 2013 09:27:10 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 3 Dec 2013 09:27:10 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20131203170825.GA17211@nic.fr>
Date: Tue, 03 Dec 2013 12:27:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <21D03162-81D1-494A-89A9-41BE89D28A0E@nominum.com>
References: <20131201164841.GB12135@sources.org> <BF87877A-8989-4AA4-9ED1-52C82E1BC538@nominum.com> <alpine.LFD.2.10.1312011206480.12923@bofh.nohats.ca> <20131202151651.GD16808@mx1.yitter.info> <A12FD3E0-58F6-4490-877F-A9C59405F717@vpnc.org> <6DBBC8339C394DBDAE4FE1F764E02A8D@hopcount.ca> <20131203170825.GA17211@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: dnsop WG <dnsop@ietf.org>, Joe Abley <jabley@hopcount.ca>, Andrew Sullivan <ajs@anvilwalrusden.com>, Paul Hoffman <paul.hoffman@vpnc.org>
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, 03 Dec 2013 17:27:15 -0000

On Dec 3, 2013, at 12:08 PM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> If we want actual testing of the ability to run non-IN classes, I
> accept donations in bitcoins to do so in my lab :-) But, anyway, you
> have very little chance of convincing any developer to spend time in
> this direction, which is clearly dead.

Furthermore, it doesn't even address the problem, because the problem we are talking about is a naming problem, not a problem that exists within the DNS protocol.  So by definition you can't solve it with classes, because classes are a DNS thing.

v2.23.0 | Report a Bug | By Email