IETF Logo Mail Archive

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

Joe Abley <jabley@hopcount.ca> Thu, 25 February 2010 18:04 UTC

Return-Path: <jabley@hopcount.ca>
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 EB4DC3A86EF for <ietf@core3.amsl.com>; Thu, 25 Feb 2010 10:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 fqRDJbhflkVh for <ietf@core3.amsl.com>; Thu, 25 Feb 2010 10:04:08 -0800 (PST)
Received: from monster.hopcount.ca (monster.hopcount.ca [216.235.14.38]) by core3.amsl.com (Postfix) with ESMTP id 22DD63A6FF9 for <ietf@ietf.org>; Thu, 25 Feb 2010 10:04:08 -0800 (PST)
Received: from [199.212.90.30] (helo=dh30.r1.owls.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1Nki8A-00075e-3G; Thu, 25 Feb 2010 18:08:15 +0000
Subject: Re: DNSCurve vs. DNSSEC - FIGHT! (was OpenDNS today announced it has adopted DNSCurve to secure DNS)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <alpine.LSU.2.00.1002242049510.16971@hermes-2.csi.cam.ac.uk>
Date: Thu, 25 Feb 2010 13:05:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5619D88-DA9C-4DB5-A5BB-B1719DB55173@hopcount.ca>
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>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1077)
X-SA-Exim-Connect-IP: 199.212.90.30
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Cc: Phillip Hallam-Baker <hallam@gmail.com>, 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: Thu, 25 Feb 2010 18:04:09 -0000

On 2010-02-24, at 15:50, 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?

The whole channel from end-user (registrant) to registry cannot usefully be specified in any general way because there is no consistent way of interacting with a registrar (in the name of open competition) and no consistent registry-registrar-registrant structure across all TLDs (for reasons that surely would require more than one parenthetical phrase to describe adequately).

The component that concerns communication between a registry and a registrar does have one solution that has been standardised in the IETF, however, which is being implemented at some TLDs, I hear.

  http://www.ietf.org/rfc/rfc4310.txt


Joe

v2.23.0 | Report a Bug | By Email