Re: [dnsext] A question about the need for "historical keys"

Ted Lemon <Ted.Lemon@nominum.com> Fri, 28 January 2011 18:29 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 450BB3A6911 for <dnsext@core3.amsl.com>; Fri, 28 Jan 2011 10:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.595
X-Spam-Level:
X-Spam-Status: No, score=-106.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 nd5E4jx9fReC for <dnsext@core3.amsl.com>; Fri, 28 Jan 2011 10:29:02 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by core3.amsl.com (Postfix) with ESMTP id 878913A6924 for <dnsext@ietf.org>; Fri, 28 Jan 2011 10:29:01 -0800 (PST)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKTUMLqIKPqDtdbtKPhGd3B5pyo+iKMFlh@postini.com; Fri, 28 Jan 2011 10:32:08 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 3E8931B82F4 for <dnsext@ietf.org>; Fri, 28 Jan 2011 10:32:08 -0800 (PST)
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 291F119005D; Fri, 28 Jan 2011 10:32:08 -0800 (PST)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 28 Jan 2011 10:32:05 -0800
MIME-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <4D430A56.9040600@cisco.com>
Date: Fri, 28 Jan 2011 13:31:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <CB2E6797-C219-4675-A14E-8F7F3FF7A2D5@nominum.com>
References: <4D41D3E2.6060107@cisco.com> <3125F45F-7594-498F-AFA3-D2D738A228F5@hopcount.ca> <4D42ED13.5030000@cisco.com> <562C7583-B719-482F-B201-EFB54138BAF1@icsi.berkeley.edu> <E4865E48-383B-4591-AF27-34571C4AA367@nominum.com> <4D430265.8020100@cisco.com> <a06240802c968b4fefc24@[10.31.200.110]> <4D430A56.9040600@cisco.com>
To: John Bashinski <jbash@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: Edward Lewis <Ed.Lewis@neustar.biz>, dnsext@ietf.org
Subject: Re: [dnsext] A question about the need for "historical keys"
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jan 2011 18:29:03 -0000

On Jan 28, 2011, at 1:26 PM, John Bashinski wrote:
> Take the Linksys home routers. My guess is that maybe a couple of
> percent of them *ever* get firmware updates.

Before you use this as a basis for argument, it might be worth your while to (not in this discussion) explore the question of *why* they don't get updates.   From my own personal experience, this is not because of a lack of demand.