IETF Logo Mail Archive

Re: Fwd: [dnsext] draft-crocker-dnssec-algo-signal-03 -- more time please!

Andrew Sullivan <ajs@shinkuro.com> Wed, 02 September 2009 16:16 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0962728C62C; Wed, 2 Sep 2009 09:16:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.291
X-Spam-Level:
X-Spam-Status: No, score=-0.291 tagged_above=-999 required=5 tests=[AWL=-0.691, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_INFO=1.448, RDNS_NONE=0.1]
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 8BQUlE2-00hZ; Wed, 2 Sep 2009 09:16:14 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 2B0E03A692A; Wed, 2 Sep 2009 09:16:14 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1MisRK-000Om9-6R for namedroppers-data0@psg.com; Wed, 02 Sep 2009 16:12:06 +0000
Received: from [208.86.224.201] (helo=mail.yitter.info) by psg.com with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <ajs@shinkuro.com>) id 1MisRG-000OlT-5C for namedroppers@ops.ietf.org; Wed, 02 Sep 2009 16:12:03 +0000
Received: from crankycanuck.ca (76-10-166-247.dsl.teksavvy.com [76.10.166.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 3A8552FE8CB8 for <namedroppers@ops.ietf.org>; Wed, 2 Sep 2009 16:11:58 +0000 (UTC)
Date: Wed, 02 Sep 2009 12:11:56 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: namedroppers@ops.ietf.org
Subject: Re: Fwd: [dnsext] draft-crocker-dnssec-algo-signal-03 -- more time please!
Message-ID: <20090902161155.GS16078@shinkuro.com>
References: <583565A9-886F-41FB-92EA-B9F3E6741A7C@cisco.com> <434ECD68-79BB-45F1-8A68-A4CD8E4A3E11@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <434ECD68-79BB-45F1-8A68-A4CD8E4A3E11@cisco.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

Dear colleagues,

On Thu, Aug 27, 2009 at 06:18:29AM +0200, Patrik Fältström wrote:
>
> - what the impact *really* is on DNSSEC deployment if we have multiple  
> algorithms
> - how an algorithm change is to handled
> - how to handle the selection process of preferred (plural) algorithms  
> (one main, and one secondary that is rolled in or out?)
>
> Given this, we can talk about how to do the wording in documents that  
> talk about how to register/signal algorithms.

If I read this correctly, then either the candidate draft that Paul
Hoffman has offered to the WG, possibly with some additions or
changes, or something with the same topic is a necessary condition for
adopting draft-crocker-dnssec-algo-signal; and if such a document is
adopted and published, then draft-crocker-dnssec-algo-signal would
also be a good idea.  Am I reading correctly?

Best regards,

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

v2.23.0 | Report a Bug | By Email