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

Re: Q2: crypto algorithm requirements for DNSSEC

To: Mark.Andrews@isc.org
Subject: Re: Q2: crypto algorithm requirements for DNSSEC
From: Derek Atkins <derek@ihtfp.com>
Date: 14 Feb 2003 11:06:15 -0500
Cc: Mark_Andrews@isc.org, Jim Reid <Jim.Reid@nominum.com>, Jakob Schlyter <jakob@crt.se>, Miek Gieben <miekg@atoom.net>, Scott Rose <scottr@nist.gov>, namedroppers@ops.ietf.org
In-reply-to: <200302132321.h1DNL7d6021114@drugs.dv.isc.org>
References: <200302132321.h1DNL7d6021114@drugs.dv.isc.org>
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

Mark.Andrews@isc.org writes:

> > There is a LOT of extra policy decision that needs to happen if you go
> > down this road.  A lot of extra implementation, too!
> 
> 	You are missing the whole point.

No, I'm not.  I'm just looking at it from a different angle.

-derek

-- 
       Derek Atkins
       Computer and Internet Security Consultant
       derek@ihtfp.com             www.ihtfp.com

--
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/>

References:
- Re: Q2: crypto algorithm requirements for DNSSEC
  - From: Mark.Andrews@isc.org

Prev by Date: Re: DNSEXT WGLC Summary: RFC1886bis-01
Next by Date: Re: axfr-clarify's fraudulent claims of consensus
Previous by thread: Re: Q2: crypto algorithm requirements for DNSSEC
Next by thread: RE: Q2: crypto algorithm requirements for DNSSEC
Index(es):
- Date
- Thread