IETF Logo Mail Archive

RE: [HOKEY] EMSK Issue

Bernard Aboba <bernarda@windows.microsoft.com> Tue, 08 April 2008 18:57 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BAEC328C32F; Tue, 8 Apr 2008 11:57:28 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EDFE3A6DA1; Tue, 8 Apr 2008 10:37:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.999
X-Spam-Level:
X-Spam-Status: No, score=-109.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 rfhrwlo11KTC; Tue, 8 Apr 2008 10:37:38 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 01A993A697A; Tue, 8 Apr 2008 10:37:37 -0700 (PDT)
Received: from TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.18.53) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.1.240.5; Tue, 8 Apr 2008 10:37:54 -0700
Received: from tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com (157.54.18.33) by TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.18.53) with Microsoft SMTP Server id 8.1.240.5; Tue, 8 Apr 2008 10:37:53 -0700
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com ([fe80::75be:c82f:ae04:55bf]) by tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.33]) with mapi; Tue, 8 Apr 2008 10:37:50 -0700
From: Bernard Aboba <bernarda@windows.microsoft.com>
To: 'Charles Clancy' <clancy@cs.umd.edu>, "'Narayanan, Vidya'" <vidyan@qualcomm.com>
Date: Tue, 08 Apr 2008 10:37:47 -0700
Subject: RE: [HOKEY] EMSK Issue
Thread-Topic: [HOKEY] EMSK Issue
Thread-Index: AciXaC+u+eyTw4iXQhCLnby4wsISzACNsUNg
Message-ID: <2828BDE8DC61004E8104C78E82A0B39702C6AFB8A5@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <47DF04FC.4060706@cs.umd.edu> <A3DA4C2546E1614D8ACC896746CDCF29E7BF6E@aruba-mx1.arubanetworks.com> <C24CB51D5AA800449982D9BCB90325130142DBF9@NAEX13.na.qualcomm.com> <47E70F45.2020106@cs.umd.edu> <C24CB51D5AA800449982D9BCB90325130162110E@NAEX13 <47F7F60D.406@cs.umd.edu>
In-Reply-To: <47F7F60D.406@cs.umd.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 08 Apr 2008 11:57:24 -0700
Cc: "'ietf@ietf.org'" <ietf@ietf.org>, "'hokey@ietf.org'" <hokey@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Is this saying that inter-domain handoff is not supported?  My
understanding is that ERX supports inter-domain use, no?

I understand the restriction for other uses though (such as OTA
Provisioning).

-----Original Message-----
From: Charles Clancy [mailto:clancy@cs.umd.edu]
Sent: Saturday, April 05, 2008 2:59 PM
To: Narayanan, Vidya
Cc: Glen Zorn; ietf@ietf.org; hokey@ietf.org; Bernard Aboba
Subject: Re: [HOKEY] EMSK Issue

Narayanan, Vidya wrote:
> How about the following text for applicability:
>
> "It must be noted that any application of EAP keying material to other
> usages such as handoffs, IP mobility or other applications is only
> feasible when those services are provided either by or through the
> provider handling network access.  It is also only feasible when those
> usages only occur over EAP-capable interfaces. Hence, deriving USRKs or
> DSUSRKs for usages other than those facilitated by the network access
> provider is NOT RECOMMENDED."
>

Sounds good to me.

--
t. charles clancy, ph.d.                 eng.umd.edu/~tcc
electrical & computer engineering, university of maryland

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email