[IPSECKEY] IPSECKEY inheritance of DNSSEC algorithm registry

Sam Weiler <weiler@tislabs.com> Tue, 17 June 2003 23:03 UTC

Received: from noxmail.sandelman.ottawa.on.ca (cyphermail.sandelman.ottawa.on.ca [192.139.46.78]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15643 for <ipseckey-archive@lists.ietf.org>; Tue, 17 Jun 2003 19:03:38 -0400 (EDT)
Received: from lox.sandelman.ottawa.on.ca (IDENT:root@lox.sandelman.ottawa.on.ca [192.139.46.2]) by noxmail.sandelman.ottawa.on.ca (8.11.6p2/8.11.6) with ESMTP id h5HN2kq18509 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Tue, 17 Jun 2003 19:02:48 -0400 (EDT)
Received: (from majordom@localhost) by lox.sandelman.ottawa.on.ca (8.11.6/8.11.6) id h5HN3lg17047 for ipseckey-outgoing; Tue, 17 Jun 2003 19:03:47 -0400 (EDT)
Received: from sentry.rv.nailabs.com (firewall-user@sentry.rv.nailabs.com [204.254.155.100]) by lox.sandelman.ottawa.on.ca (8.11.6/8.11.6) with ESMTP id h5HN3km17036 for <ipseckey@lox.sandelman.ottawa.on.ca>; Tue, 17 Jun 2003 19:03:46 -0400 (EDT)
Received: by sentry.rv.nailabs.com; id TAA17394; Tue, 17 Jun 2003 19:03:33 -0400 (EDT)
Received: from raven.rv.nailabs.com(10.33.1.50) by sentry.gw.tislabs.com via smap (V5.5) id xma017388; Tue, 17 Jun 03 19:03:12 -0400
Received: from localhost (weiler@localhost) by raven.rv.nailabs.com (8.11.6p2/8.11.6) with ESMTP id h5HN0Dc23896; Tue, 17 Jun 2003 19:00:13 -0400 (EDT)
X-Authentication-Warning: raven.rv.nailabs.com: weiler owned process doing -bs
Date: Tue, 17 Jun 2003 19:00:13 -0400
From: Sam Weiler <weiler@tislabs.com>
X-X-Sender: <weiler@raven>
To: namedroppers@ops.ietf.org
cc: ipseckey <ipseckey@lox.sandelman.ottawa.on.ca>
Subject: [IPSECKEY] IPSECKEY inheritance of DNSSEC algorithm registry
In-Reply-To: <a05111b07bb14fca551a4@[192.149.252.108]>
Message-ID: <Pine.GSO.4.33.0306171421200.11723-100000@raven>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ipseckey@sandelman.ottawa.on.ca
Precedence: bulk
X-List: ipseckey@sandelman.ottawa.on.ca

The IPSECKEY RR definition draft is nearing WG last call -- this would
be a good time to review the document.

The chairs would particularly like feedback on whether or not the
IPSECKEY record should inherit format definitions from the DNS
Security Algorithm registry -- if someone defines a (DNS)KEY RR format
for Sam's Public Key Algorithm, does it automagically show up as an
IPSECKEY format?

The text in draft-ietf-ipseckey-rr-04.txt is internally inconsistent,
but the intent with this version was that, yes, the formats are
inherited.

Please send all comments to the IPSECKEY list.
  General Discussion: ipseckey@sandelman.ca
  To Subscribe: ipseckey-request@sandelman.ca
  Archive: http://www.sandelman.ca/lists/html/ipseckey/

http://www.ietf.org/html.charters/ipseckey-charter.html
http://www.ietf.org/internet-drafts/draft-ietf-ipseckey-rr-04.txt

-- Sam

-
This is the IPSECKEY@sandelman.ca list.
Email to ipseckey-request@sandelman.ca to be removed.