IETF Logo Mail Archive

Re: [dnsext] Historical root keys: The Large Router Vendor Speaks

Alex Bligh <alex@alex.org.uk> Fri, 28 January 2011 17:31 UTC

Return-Path: <alex@alex.org.uk>
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 22D2E3A6920 for <dnsext@core3.amsl.com>; Fri, 28 Jan 2011 09:31:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level:
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 cgDFbQFBnBHU for <dnsext@core3.amsl.com>; Fri, 28 Jan 2011 09:31:41 -0800 (PST)
Received: from mail.avalus.com (mail.avalus.com [89.16.176.221]) by core3.amsl.com (Postfix) with ESMTP id 41C5E3A68CB for <dnsext@ietf.org>; Fri, 28 Jan 2011 09:31:40 -0800 (PST)
Received: from [192.168.100.15] (87-194-71-186.bethere.co.uk [87.194.71.186]) by mail.avalus.com (Postfix) with ESMTPSA id 78EC4C56648; Fri, 28 Jan 2011 17:34:46 +0000 (GMT)
Date: Fri, 28 Jan 2011 17:34:45 +0000
From: Alex Bligh <alex@alex.org.uk>
To: John Bashinski <jbash@cisco.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <6E1BDC90802ED85AFE548AD0@Ximines.local>
In-Reply-To: <4D42FCB6.70005@cisco.com>
References: <4D41D3E2.6060107@cisco.com> <3125F45F-7594-498F-AFA3-D2D738A228F5@hopcount.ca> <4D42F597.8090006@vpnc.org> <4D42FCB6.70005@cisco.com>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: dnsext@ietf.org
Subject: Re: [dnsext] Historical root keys: The Large Router Vendor Speaks
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Alex Bligh <alex@alex.org.uk>
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 17:31:42 -0000

--On 28 January 2011 12:28:22 -0500 John Bashinski <jbash@cisco.com> wrote:

> That person or persons is NOT going to be the same person or persons
> who generates the software loads. I'm adding a new trusted entity
> to the system.

Isn't the person who generates software loads already going to have
to put the (then current) root key / zone into the image? If so, isn't
this person already a trusted entity?

-- 
Alex Bligh

v2.23.0 | Report a Bug | By Email