#23 [*] KE interoperability (section 6.8)

> #23 [*] KE interoperability (section 6.8)
> 
> 	What happens if a peer that implements the KE payloads communicates
> 	with a peer that does not.  Specify the behavior in sufficient detail
> 	to guarantee interoperability.  (Sam Hartman)

my understanding is correct, there is no description in the IKEv1
specifications though it defines the error code which can be used
in this case.  IKEv2 defines clearly.  so if KINK specification
complies to IKEv1 manner, we have to define the behavior and describe
it for interoperability.  if KINK complies to IKEv2 manner, we can
probably leave it.

another problem comes up.  there is no way to negotiate a DH group
to use in a quick mode.  so in IKEv1, they have to define the DH group
before they negotiate.  current KINK specification does not touch it.
this is no matter in IKEv2.

and an initiator can not install the inbound SA when the initiator
choices to send KE because KEYMAT is not calculated before the initiator
receives KE from the responder.  the document has to touch this situation.