-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alfred,
I have no further comments on part (A). I have also adopted the
leftovers in part (B), with explanation in between lines.
Best regards,
Matthijs
On 04/11/2012 10:08 PM, Alfred � wrote:
Matthijs, again thanks for your quick and detailed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/05/2012 12:48 AM, Alfred � wrote:
Here we go with part (B); if deemed necessary, please consider
to provide feedback for the items below on the list.
Again, all items that are adopted without feedback necessary have been
omitted from this
Matthijs,
thanks for dealing with my comments so expeditiously.
(This extends to the other review comments as well.)
Please see a few follow-up remarks inline below.
On 11 Apr 2012 15:47:33 +0200, Matthijs Mekking wrote:
Hi,
On 04/05/2012 12:41 AM, Alfred Hönes wrote:
After a long delay, I
Matthijs,
again thanks for your quick and detailed response and action.
A few selected follow-up remark can be found inline below.
On 11 Apr 2012 15:48:26 +0200, Matthijs Mekking wrote:
On 04/05/2012 12:48 AM, Alfred Hönes wrote:
Here we go with part (B); if deemed necessary, please consider
On 11 April 2012 14:48, Matthijs Mekking matth...@nlnetlabs.nl wrote:
On 04/05/2012 12:48 AM, Alfred � wrote:
| o Signature validity period The time interval during which a
| signature is valid. It starts at the (absolute) time specified in
| the signature inception field of
After a long delay, I have revisited the
DNSSEC Operational Practices, Version 2 I-D and performed
a full review from scratch for the most recent draft version,
draft-ietf-dnsop-rfc4641bis-10.
For convenience, and to accommodate message size limitations,
I have split my review comments into 3
