Re: [HOKEY] EMSKname in keyName-NAI

On Wed, Feb 20, 2008 at 12:23:30PM -0800, Joseph Salowey (jsalowey) wrote:
> Hi Yoshihiro,
> 
> We are currently editing the draft to include EMSKName.  The name will
> be derived similar to the following:
> 
> EMSKname = SHA-256-64 ( EAP Session-ID | "EMSK" )
> 
> This name is a 64-bit binary string.  In order to use this in an NAI it
> would need to be encoded into a character set that is usable in an NAI.
> 
> 
> I think the ERX draft should define the NAI encoding of the EMSKname.
> Perhaps a straight binary to lowercase ASCII hex encoding would be
> simplest.  

Or just use base64?

Yoshihiro Ohba

> 
> Joe
> 
> > -----Original Message-----
> > From: hokey-bounces@ietf.org [mailto:hokey-bounces@ietf.org] 
> > On Behalf Of Yoshihiro Ohba
> > Sent: Wednesday, February 20, 2008 12:13 PM
> > To: hokey@ietf.org
> > Subject: [HOKEY] EMSKname in keyName-NAI
> > 
> > I have two questions on EMSKname in keyName-NAI in 
> > draft-ietf-hokey-erx-11.txt:
> > 
> > "
> >   keyName-NAI - ERP messages are integrity protected with the rIK or
> >   the DS-rIK.  The use of rIK or DS-rIK for integrity protection of
> >   ERP messages is indicated by the EMSKname [3], the protocol, which
> >   is ERP, and the realm, which indicates the domainname of the ER
> >   server.  The EMSKname is copied into the username part of the NAI.
> > "
> > 
> > - What is the exact format of EMSKname ?  I could not fined 
> > an EMSK name definition in [3].  
> > 
> > - Does the format of EMSKname (if specified somewhere) follow 
> > the NAI format defined in RFC 4282?
> > 
> > Best Regards,
> > Yoshihiro Ohba
> > _______________________________________________
> > HOKEY mailing list
> > HOKEY@ietf.org
> > http://www.ietf.org/mailman/listinfo/hokey
> > 
> 
> 
> 
_______________________________________________
HOKEY mailing list
HOKEY@ietf.org
http://www.ietf.org/mailman/listinfo/hokey