Re: who will edit the draft ?

Sam Hartman <[email protected]> Thu, 20 Jan 2005 15:27:17 -0500
Newsgroups gmane.ietf.kink
Message-ID <[email protected]>
>>>>> "Jan" == Jan Vilhuber <[email protected]> writes:

    Jan> On Wed, 19 Jan 2005, Derek Atkins wrote:

    >>  Hi,
    >> 
    >> Michael Thomas <[email protected]> writes:
    >> 
    >> > I'm still willing to edit the draft if we're not > talking
    >> about wholesale changes, and we're talking > about a relatively
    >> modest amount of time (eg, a > few months).
    >> 
    >> I hope it'll only take a few months, but I know Sam is going to
    >> be a stickler for quality before the IESG.  This isn't a bad
    >> thing, but I think it's going to put a lot more scrutiny on the
    >> document, so it may be significantly more work than you expect
    >> at the moment.  It's hard to say right now.
    >> 
    >> At the face of it we need to update the document to meet the
    >> new format requirements, update to krb-clarifications and
    >> krb-crypto, and probably update to reference IKEv2 and 2401bis.
    >> I dont know what other changes are going to be required.
    >> 

    Jan> I think I missed something: Why do we need to update to
    Jan> reference ikev2? The ikev1 phase 2 exchange works just fine.


I think there was confusion.  I said that you needed to reference
2401bis rather than 2401.  (I've explained the assumptions behind that
in an earlier message)

I suggested you should consider providing the additional features that
2401bis supports/requests from a key management protocol over 2401.
You should either implement these features or explain why you chose
not to do so.

How you implement these features (referencing ikev2, etc) is up to
you.