Re: [DNSOP] WGLC draft-ietf-dnsop-dnssec-key-timing-03.txt until 2012-09-14

Dear colleagues, On Thu, Aug 23, 2012 at 11:49:24PM +0200, Peter Koch wrote: > Dear DNSOP WG, > > this is to initiate a working group last call (WGLC) for > > "DNSSEC Key Timing Considerations" > draft-ietf-dnsop-dnssec-key-timing-03.txt >

Re: [DNSOP] draft-yoneya-dnssec-kskro-failure-recovery-01

On Fri, 7 Sep 2012, Yoshiro YONEYA wrote: The document intent to describe what to do when child zone administrator failed to do KSK rollover. It also intent to advice to parent zone administrator for that case. I think this concept is not included in rfc4641bis. A lot of what can be done the

Re: [DNSOP] draft-yoneya-dnssec-kskro-failure-recovery-01

Hi, On Thu, 6 Sep 2012 10:31:03 -0400 (EDT) Paul Wouters wrote: > I find this document does not add enough new information compared to > draft-ietf-dnsop-rfc4641bis-12#section-4.2 to warrant a new RFC. The document intent to describe what to do when child zone administrator failed to do KSK r

Re: [DNSOP] draft-yoneya-dnssec-kskro-failure-recovery-01

Hi, On Thu, 6 Sep 2012 11:08:39 +0200 Phil Regnauld wrote: > There are indeed many ways to facilitate recovery, not all of them > practical or realistic. Yes, currently there are some cases listed in the document, but I'd like to narrow down the list and remain 1 or 2 as a best pra

Re: [DNSOP] WGLC draft-ietf-dnsop-dnssec-key-timing-03.txt until 2012-09-14

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/06/2012 01:44 PM, Tony Finch wrote: > Matthijs Mekking wrote: >> > > Most of your points look OK to me though I have not yet reviewed > the document in detail. I have a disagreement and a suggestion: > >> * Section 2.1. ZSK Rollovers >> >> -