IETF Logo Mail Archive

Re: [HOKEY] EMSKname in keyName-NAI

"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> Wed, 20 February 2008 20:23 UTC

Return-Path: <hokey-bounces@ietf.org>
X-Original-To: ietfarch-hokey-archive@core3.amsl.com
Delivered-To: ietfarch-hokey-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 586B33A68A3; Wed, 20 Feb 2008 12:23:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.607
X-Spam-Level:
X-Spam-Status: No, score=-2.607 tagged_above=-999 required=5 tests=[AWL=-2.170, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ddQjtQAuiQ4q; Wed, 20 Feb 2008 12:23:54 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 239A128C998; Wed, 20 Feb 2008 12:23:52 -0800 (PST)
X-Original-To: hokey@core3.amsl.com
Delivered-To: hokey@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15D1D28C7F8 for <hokey@core3.amsl.com>; Wed, 20 Feb 2008 12:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ZJ4mjTLOMUg for <hokey@core3.amsl.com>; Wed, 20 Feb 2008 12:23:47 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 20B4F28C8CA for <hokey@ietf.org>; Wed, 20 Feb 2008 12:22:51 -0800 (PST)
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 20 Feb 2008 12:22:48 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m1KKMl3I001537; Wed, 20 Feb 2008 12:22:47 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1KKMlJg028259; Wed, 20 Feb 2008 20:22:47 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Feb 2008 12:22:46 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 20 Feb 2008 12:23:30 -0800
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE5054A8BD9@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <20080220201232.GH10906@steelhead.localdomain>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [HOKEY] EMSKname in keyName-NAI
Thread-Index: Achz/PyZRYoqocZnRXyF4aOEHffYOgAAE7hQ
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, hokey@ietf.org
X-OriginalArrivalTime: 20 Feb 2008 20:22:46.0091 (UTC) FILETIME=[5AB751B0:01C873FE]
Authentication-Results: sj-dkim-4; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Subject: Re: [HOKEY] EMSKname in keyName-NAI
X-BeenThere: hokey@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HOKEY WG Mailing List <hokey.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/hokey>, <mailto:hokey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/hokey>
List-Post: <mailto:hokey@ietf.org>
List-Help: <mailto:hokey-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/hokey>, <mailto:hokey-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: hokey-bounces@ietf.org
Errors-To: hokey-bounces@ietf.org

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.  

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

v2.23.0 | Report a Bug | By Email