-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
-Original Message-
From: dnsop-boun...@ietf.org [mailto:dnsop-boun...@ietf.org] On Behalf Of
Paul Wouters
Subject: [DNSOP] Comments/Additions on I-D Action:draft-ietf-dnsop-
rfc4641bis-01.txt
4.4.5
(remove use of registrar A and
On Sun, 26 Apr 2009, Ted Lemon wrote:
On Apr 26, 2009, at 12:46 PM, Paul Wouters wrote:
You're not using RFC 4255 yet? Shame on you!
From the RFC:
Another dependency is on the implementation of DNSSEC itself. As stated in
Section 2.4, we mandate the use of secure methods for lookup and
Wes Hardaker wrote:
On Sat, 21 Mar 2009 22:44:42 -0700, Doug Barton do...@dougbarton.us
said:
DB I've read the draft at the URL above and am generally supportive of
DB its moving forward.
Doug,
Thanks for responding with a review about the Management Requirements
document. I've
In your previous mail you wrote:
= there are places where cryptography is required to be implemented
in hardware, and many business reasons or even regulations which
mandate HSMs.
But the risk for the key is not only people modifying it, it is simply
people *reading* it (a concern which
On Tue, 28 Apr 2009 10:25:15 -0700, Doug Barton do...@dougbarton.us
said:
OLD: Reloading zone data
NEW: Reloading some or all of the zone data sets
DB That wording may imply granularity at less than the zone level, which
DB I'm not suggesting but would not be opposed to.
Ok, how
