-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Johan Ihren wrote: > > I don't remember exactly what I said, but what I meant was not that > "double signature" is sufficient to accomplish an algorithm rollover, > only that it was needed as part of one. So I think you and I agree hee. >
I think so too, mostly :) I would dub what I proposed for algorithm rollovers 'reverse double signature' >> (btw i agree with olaf that some form of collaboration between these >> documents >> might be nice) > > Of course there will be, although I'm still skeptical about circular > dependencies. > Of course, though i rather see a circular dependency than an inter-rfc inconsistency. I was thinking more of collaborative documents :) > > This falls down into the question about whether to cover all the > rollover "methods" or make a recommendation and only cover that > alternative. My take away from the WG was that the key timing doc should > not make recommendations, but describe all the alternatives. > Well, since I am the proud owner of the humble opinion that algorithm rollover requires a substantially different method, I would personally like to see that method covered as well. >> I think a reference to 4641bis and a scheme to match the text there >> would be nice > > My primary issue with that is that as soon as we refer to 4641bis there > is a circular dependency and then the two documents must be published > together. My secondary issue is that I maintain my position that the key > timing document is "theory" while 4641bis is "practice". Therefore, as > the key timing document covers a more narrow topic in greater depth, > there is just no way to avoid references from 4641bis to us. > Ah, now there may lie the (a?) problem. I was thinking of 4641bis as the defining rfc (ie. what to do), and key timing as a mathematical description of (some of) the methods mentioned in the former (ie. how to do it). Jelte -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksDCtEACgkQ4nZCKsdOncVzlACgnpChOSLEoQ5jeIzbOVWRusEY GIEAoKKi9RxVxbFHoo56IEoT68jZxT5Q =ZVam -----END PGP SIGNATURE----- _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
