Re: [Dime] New version of draft-wu-dime-local-keytran

[Qin Wu <[e-mail]>]

Hi, Sebastien:
----- Original Message ----- 
From: "Sebastien Decugis" <[e-mail]>
To: "Glen Zorn" <[e-mail]>; <[e-mail]>
Sent: Wednesday, December 09, 2009 10:06 AM
Subject: Re: [Dime] New version of draft-wu-dime-local-keytran


Hi Glen, Qin, all,

By quickly looking into the new version, a few additional comments came
to my mind:

In section 3.1, I would like to propose a change to the ABNF. I think
the Key-Type AVP should be in a fixed position (actually I was under the
impression that this was already decided, but anyway), like this:

   Key ::= < AVP Header: AC1 >
             < Key-Type >
             ...


In section 3.1.1 (definition of Key-Type AVP), I think some of the
defined values should be removed, as follow:
- rMSK (4) : As I understand, there is no difference between rMSK and
MSK, so we may not need a different type for this one ? (not sure)
- USRK (2) & DSUSRK (5): RFC5295 defines a generic algorithm to derive
usage-specific keys. The definition alone is not sufficient to create
keying material: we need the usage itself to define the missing parts.

[Qin]: The usages for USRK and DSUSRK have been defined in the section 4.2 of draft-ietf-hokey-key-mgm-13.
That is to say, USRK and DSUSRK may be derived in the EAP/AAA server and transported in the message to the same USR-KH.
And then DSUSRK can be further transported from USR-KH to DSUSR-KH.