Olaf,
here you have diff (against up-to-date SVN) and full text for Key
Algorithm Rollover. The attached text was created as joint effort by me
and Olafur.
Ondrej.
On 20.3.2010 17:10, Olaf Kolkman wrote:
Colleagues
This is a status update on RFC4641bis. Please refer to links provided
FWIW,
This has been addressed in draft-03 although I just noticed that the last
paragraph of 3.1.4.1. still needs a minor rewrite to reflect availability of
SHA 256. (Now there is an inconstancy between giving references to the specs
and saying one has to wait for availability).
On Mar
You probably noticed I swapped in the document and tackling issues one-by-one.
On Mar 20, 2010, at 8:51 PM, Chris Thompson wrote:
On Mar 20 2010, Paul Wouters wrote:
On Sat, 20 Mar 2010, Olaf Kolkman wrote:
- http://www.nlnetlabs.nl/svn/rfc4641bis/trunk/open-issues/NSEC-NSEC3
That
Colleagues
This is a status update on RFC4641bis. Please refer to links provided for more
details on the issues. I have no particular issues I need to discuss in the
face to face meeting and will present what is written below in a somewhat
condensed form. If folk have something they would
On Sat, 20 Mar 2010, Olaf Kolkman wrote:
- http://www.nlnetlabs.nl/svn/rfc4641bis/trunk/open-issues/NSEC-NSEC3
That still states:
as well as no algorithm choice for SHA-256
That's been resolved now, see http://www.bind9.net/dns-sec-algorithm-numbers
RSASHA256 has DNSKEY algorihtm 8
On Mar 20 2010, Paul Wouters wrote:
On Sat, 20 Mar 2010, Olaf Kolkman wrote:
- http://www.nlnetlabs.nl/svn/rfc4641bis/trunk/open-issues/NSEC-NSEC3
That still states:
as well as no algorithm choice for SHA-256
That's been resolved now, see
