Re: [DNSOP] CPE devices doing DNSSEC

Patrik Fältström <paf@frobbit.se> Sun, 09 March 2014 13:20 UTC

Return-Path: <paf@frobbit.se>
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 A8A541A0344 for <dnsop@ietfa.amsl.com>; Sun, 9 Mar 2014 06:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level:
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=no
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 eXZcn2u-ZcWa for <dnsop@ietfa.amsl.com>; Sun, 9 Mar 2014 06:20:24 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 690461A0339 for <dnsop@ietf.org>; Sun, 9 Mar 2014 06:20:24 -0700 (PDT)
Received: from ix-2.local (unknown [194.72.72.170]) by mail.frobbit.se (Postfix) with ESMTPSA id F374920153; Sun, 9 Mar 2014 14:20:18 +0100 (CET)
Message-ID: <531C6A92.8020503@frobbit.se>
Date: Sun, 09 Mar 2014 13:20:18 +0000
From: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Patrik Wallstrom <pawal@blipp.com>
References: <20140307100524.2F42810CD58F@rock.dv.isc.org> <A0D47DA8-6E19-4A61-8A7C-FE960A0FA7E9@cybersecurity.org> <20140308090009.5E51210D1595@rock.dv.isc.org> <531C2637.6020405@frobbit.se> <6175B0CC-D8E3-44BB-83DD-7DA8548E6120@blipp.com> <531C5C4D.4010700@frobbit.se> <545AE25E-A609-4D03-A3DD-AFD41E573820@blipp.com>
In-Reply-To: <545AE25E-A609-4D03-A3DD-AFD41E573820@blipp.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="e0d1t8SepAJD4LfWA1K8Wis6jTXP2ASc9"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/5I-ojIjJyGG812jz-kakyR_ulS8
Cc: dnsop@ietf.org, Paul Hoffman <paul.hoffman@cybersecurity.org>
Subject: Re: [DNSOP] CPE devices doing DNSSEC
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: Sun, 09 Mar 2014 13:20:25 -0000


On 2014-03-09 12:55, Patrik Wallstrom wrote:
>> Given this pricing structure, and that registries do change their
>> implementations far too often, where do you think registrars do spend
>> the money they have? They MUST support what the changes the registries
>> do, they do not HAVE TO implement a common API.
>
> Well, registries have made registrars do DNSSEC before. So if we would actually try to describe a standardised interface for the registrars, there could be ways to make the registrars implement this new interface. Pressure from customers, registrars and ICANN combined, perhaps?

I did btw notice you did not comment on the price squeeze issue. That is
_very_ serious as at the end of the day someone have to pay for the
developer writing the code.

Registries dumping wholesale prices must stop doing that.

   Patrik