Date: Wed, 09 Dec 2009 14:49:18 +0800
From: Qin Wu <sunseawq@huawei.com>
To: Sebastien Decugis <sdecugis@nict.go.jp>
Message-id: <030901ca789b$bb071cf0$420ca40a@china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7BIT
References: <01ce01ca7842$352c49b0$9f84dd10$@net> <4B1F0642.2090604@nict.go.jp>
 <02a301ca7881$73bf1f60$420ca40a@china.huawei.com>
 <4B1F2A20.9060407@nict.go.jp>
Cc: dime@ietf.org
Subject: Re: [Dime] New version of draft-wu-dime-local-keytran
Precedence: list

Hi,Sebastien:
----- Original Message ----- 
From: "Sebastien Decugis" <sdecugis@nict.go.jp>
To: "Qin Wu" <sunseawq@huawei.com>
Cc: "Glen Zorn" <gwz@net-zen.net>; <dime@ietf.org>
Sent: Wednesday, December 09, 2009 12:40 PM
Subject: Re: [Dime] New version of draft-wu-dime-local-keytran


> Hi Qin,
> 
>> - 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.
> Sorry, I have difficulties to express my idea clearly. What I mean is
> that for example the definition of USRK is just a generic method to
> derive a class of keys, we will never have a "USRK key" without any
> precision on the usage it-self (usage as in the "US" part of USRK). On
> the other hand, rRK is an instance of this class, where the algorithm
> parameters are specified in the ERP document, and we can effectively
> have to transport rRK keys. As I understand draft-ietf-hokey-key-mgm-13,
> that document is also talking about generic mechanisms, that can be
> applied for instance to the ERP specific usage.

[Qin]: According to draft-ietf-hokey-key-mgm-13, USRK and DSUSRK can be used in
Key Distribution Exchange Scenarios, that is to say EAP based key transportation is not limited for ERP
specific usage. Also I am not saying using of USRK and DSUSRK in the ERP scenario. I am wondering 
whether USRK and DSUSRK transportation can be used for other non ERP specific cases like Key Distribution 
Exchange Scenarios.

> Does this make my point more understandable?
> 
> Best regards,
> Sebastien.
> 
> -- 
> Sebastien Decugis
> Research fellow
> Network Architecture Group
> NICT (nict.go.jp)
>