Re: [DNSOP] 4641bis (draft 3 and 4) review - largely 5011 related

2010-10-20 Thread Olaf Kolkman
Clearly I am trying to get a (hopefully WG last call ready) version 05 of the document out by the deadline. Some comments in-line based on specific feedback you provided. On Aug 5, 2010, at 9:43 AM, Matthijs Mekking wrote: The KSK RFC5011-based rollover method says that the removed key

[DNSOP] 4641bis (draft 3 and 4) review - largely 5011 related

2010-08-05 Thread Matthijs Mekking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There seems something went wrong with the layout on the previous try... Matthijs - Original Message Subject: 4641bis (draft 3 and 4) review - largely 5011 related Date: Thu, 05 Aug 2010 09:42:14 +0200 From: Matthijs Mekking

Re: [DNSOP] 4641bis (draft 3 and 4) review - largely 5011 related

2010-08-05 Thread Matthijs Mekking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Algorithm rollover is also discussed on namedroppers. Wouter listed some other options you have when algorithm rollover and 5011 are both in place: * Go MISSING. use the steps for removal without the REVOKE publish step. The key goes into