IETF Logo Mail Archive

Re: DNSCurve vs. DNSSEC - FIGHT! (was OpenDNS today announced it has adopted DNSCurve to secure DNS)

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 24 February 2010 21:19 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 543293A856A for <ietf@core3.amsl.com>; Wed, 24 Feb 2010 13:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.983
X-Spam-Level:
X-Spam-Status: No, score=-5.983 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DpYAqo2iQKpE for <ietf@core3.amsl.com>; Wed, 24 Feb 2010 13:19:42 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 4E4113A8515 for <ietf@ietf.org>; Wed, 24 Feb 2010 13:19:41 -0800 (PST)
Received: from [10.20.30.158] (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o1OLEDsX085574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Feb 2010 14:14:14 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240819c7ab46c7fbf9@[10.20.30.158]>
In-Reply-To: <alpine.LSU.2.00.1002242049510.16971@hermes-2.csi.cam.ac.uk>
References: <874c02a21002231826y613b9f97ya83740ba240f7bf9@mail.gmail.com> <ABE739C5ADAC9A41ACCC72DF366B719D02C29D87@GLKMS2100.GREENLNK.NET> <a123a5d61002240700i4a68367tf901b91265f79da1@mail.gmail.com> <1267039830.9710.11106.camel@shane-asus-laptop> <alpine.LSU.2.00.1002242049510.16971@hermes-2.csi.cam.ac.uk>
Date: Wed, 24 Feb 2010 13:14:11 -0800
To: Tony Finch <dot@dotat.at>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: DNSCurve vs. DNSSEC - FIGHT! (was OpenDNS today announced it has adopted DNSCurve to secure DNS)
Content-Type: text/plain; charset="us-ascii"
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 21:19:43 -0000

At 8:50 PM +0000 2/24/10, Tony Finch wrote:
>On Wed, 24 Feb 2010, Shane Kerr wrote:
>>
>> DNSSEC declares out of scope:
>>       * the channel where DS records get added to the parent
>
>Is that actually out of scope or just not specified yet?

What part of DNSCurve did you think was "specified" yet? It's described on a web site that is not versioned. To date, the authors and his fans have not produced an Internet Draft, even after a bit of prodding.

--Paul Hoffman, Director
--VPN Consortium

v2.23.0 | Report a Bug | By Email