[Jeffrey Hutzelman] Followup on KINK last call

[Sam Hartman <hartmans-ietf@xxxxxxx>]

[Jeff points out that we also need to specify the key to use.  It is presumably the session key because that's the only key involved.
]


Some discussion related to the last call of draft-ietf-kink-kink-10.txt was 
copied to the Kerberos WG list, but I'm afraid part of it may have missed 
both the IETF and IESG lists.  In particular...

- This comment appears to have gone unaddressed in -11:

> I did notice that section 4.2.7 KINK_ENCRYPT does not specify what key is
> used, only that it "is encrypted using the encryption algorithm specified
> by the etype of the session key"