[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Q2: crypto algorithm requirements for DNSSEC

To: Miek Gieben <miekg@atoom.net>
Subject: Re: Q2: crypto algorithm requirements for DNSSEC
From: Jakob Schlyter <jakob@crt.se>
Date: Thu, 13 Feb 2003 11:25:34 +0100 (MET)
Cc: Scott Rose <scottr@nist.gov>, namedroppers@ops.ietf.org
In-reply-to: <20030213091929.GB30441@atoom.net>
References: <4E25ECBBC03F874CBAD03399254ADFDE104A87@US-Columbia-CIST.mail.saic.com><003201c2d2c5$2f9ddba0$b9370681@barnacle> <20030213091929.GB30441@atoom.net>

On Thu, 13 Feb 2003, Miek Gieben wrote:

> I'm not sure what the answer should be, but I don't think a TLD will
> ever want to support two different algorithms in a zone,

why? due to zone size constraints? I do not agree.


	jakob

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>

Follow-Ups:
- Re: Q2: crypto algorithm requirements for DNSSEC
  - From: Jim Reid <Jim.Reid@nominum.com>

References:
- RE: Q2: crypto algorithm requirements for DNSSEC
  - From: "Loomis, Rip" <GILBERT.R.LOOMIS@saic.com>
- Re: Q2: crypto algorithm requirements for DNSSEC
  - From: "Scott Rose" <scottr@nist.gov>
- Re: Q2: crypto algorithm requirements for DNSSEC
  - From: Miek Gieben <miekg@atoom.net>

Prev by Date: Re: Q2: crypto algorithm requirements for DNSSEC
Next by Date: Re: Q2: crypto algorithm requirements for DNSSEC
Previous by thread: Re: Q2: crypto algorithm requirements for DNSSEC
Next by thread: Re: Q2: crypto algorithm requirements for DNSSEC
Index(es):
- Date
- Thread