IETF Logo Mail Archive

RE: [HOKEY] EMSK Issue

"Narayanan, Vidya" <vidyan@qualcomm.com> Mon, 24 March 2008 18:29 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F70328C469; Mon, 24 Mar 2008 11:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.47
X-Spam-Level:
X-Spam-Status: No, score=-100.47 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 PY1sbIJbLpCV; Mon, 24 Mar 2008 11:29:17 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 984CB28C443; Mon, 24 Mar 2008 11:29:16 -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 0335B28C412; Mon, 24 Mar 2008 11:29:16 -0700 (PDT)
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 NURXvAR-bG5g; Mon, 24 Mar 2008 11:29:15 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id E142A28C409; Mon, 24 Mar 2008 11:29:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=vidyan@qualcomm.com; q=dns/txt; s=qcdkim; t=1206383216; x=1237919216; h=x-mimeole:content-class:mime-version:content-type: content-transfer-encoding:subject:date:message-id: in-reply-to:x-ms-has-attach:x-ms-tnef-correlator: thread-topic:thread-index:references:from:to:cc: x-originalarrivaltime:x-ironport-av; z=X-MimeOLE:=20Produced=20By=20Microsoft=20Exchange=20V6.5 |Content-class:=20urn:content-classes:message |MIME-Version:=201.0|Content-Type:=20text/plain=3B=0D=0A =09charset=3D"us-ascii"|Content-Transfer-Encoding:=20quot ed-printable|Subject:=20RE:=20[HOKEY]=20EMSK=20Issue |Date:=20Mon,=2024=20Mar=202008=2011:26:46=20-0700 |Message-ID:=20<C24CB51D5AA800449982D9BCB90325130162110E@ NAEX13.na.qualcomm.com>|In-Reply-To:=20<47E70F45.2020106@ cs.umd.edu>|X-MS-Has-Attach:=20|X-MS-TNEF-Correlator:=20 |Thread-Topic:=20[HOKEY]=20EMSK=20Issue|Thread-Index:=20A ciNVURfKL5k48XoQuuTKuVJnSKTeAAhVkrg|References:=20<47DF04 FC.4060706@cs.umd.edu>=20<A3DA4C2546E1614D8ACC896746CDCF2 9E7BF6E@aruba-mx1.arubanetworks.com>=20<C24CB51D5AA800449 982D9BCB90325130142DBF9@NAEX13.na.qualcomm.com>=20<47E70F 45.2020106@cs.umd.edu>|From:=20"Narayanan,=20Vidya"=20<vi dyan@qualcomm.com>|To:=20"Charles=20Clancy"=20<clancy@cs. umd.edu>|Cc:=20"Glen=20Zorn"=20<gzorn@arubanetworks.com>, =20<ietf@ietf.org>,=20<hokey@ietf.org>,=0D=0A=20=20=20=20 =20=20=20=20"Bernard=20Aboba"=20<bernarda@windows.microso ft.com>|X-OriginalArrivalTime:=2024=20Mar=202008=2018:26: 44.0835=20(UTC)=20FILETIME=3D[9D1DB330:01C88DDC] |X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5100,188,5258"=3B=20a =3D"1449653"; bh=E5FowZDiQ5uz1K4aBzTCGrRSxk/PbnnKz8QNpD3DzQ4=; b=DjULxRB92Nhoun8J87/pyl6JI2N9DlyUnRK+CDYQ+36wSLsb8+l0VVzg Sv30kCHnQ8h8UacQCuGwEprnkqx0FW6n1DiCVEuN2GkwLU7DMP0qnOp8T 92uMWQpUTuRt60PY0m0WG7wKc8m0cK79sCxE0NIE0IMPWuD2mhqfYdEbU M=;
X-IronPort-AV: E=McAfee;i="5100,188,5258"; a="1449653"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Mar 2008 11:26:56 -0700
Received: from msgtransport01.qualcomm.com (msgtransport01.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m2OIQtsA005177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 24 Mar 2008 11:26:55 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com [172.30.32.65]) by msgtransport01.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m2OIQjXu018665; Mon, 24 Mar 2008 11:26:55 -0700
Received: from NAEX13.na.qualcomm.com ([129.46.51.249]) by SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Mar 2008 11:26:44 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [HOKEY] EMSK Issue
Date: Mon, 24 Mar 2008 11:26:46 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130162110E@NAEX13.na.qualcomm.com>
In-Reply-To: <47E70F45.2020106@cs.umd.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [HOKEY] EMSK Issue
Thread-Index: AciNVURfKL5k48XoQuuTKuVJnSKTeAAhVkrg
References: <47DF04FC.4060706@cs.umd.edu> <A3DA4C2546E1614D8ACC896746CDCF29E7BF6E@aruba-mx1.arubanetworks.com> <C24CB51D5AA800449982D9BCB90325130142DBF9@NAEX13.na.qualcomm.com> <47E70F45.2020106@cs.umd.edu>
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: Charles Clancy <clancy@cs.umd.edu>
X-OriginalArrivalTime: 24 Mar 2008 18:26:44.0835 (UTC) FILETIME=[9D1DB330:01C88DDC]
Cc: Glen Zorn <gzorn@arubanetworks.com>, ietf@ietf.org, hokey@ietf.org, Bernard Aboba <bernarda@windows.microsoft.com>
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

Charles,

> -----Original Message-----
> From: Charles Clancy [mailto:clancy@cs.umd.edu] 
> Sent: Sunday, March 23, 2008 7:18 PM
> To: Narayanan, Vidya
> Cc: Glen Zorn; ietf@ietf.org; hokey@ietf.org; Bernard Aboba
> Subject: Re: [HOKEY] EMSK Issue
> 
> Vidya,
> 
>  > ... do the responsible thing, which would be to clearly 
> define the  > applicability, along with providing an 
> interoperable means of defining  > the key hierarchy for 
> those usages that want to/can use it.
> 
> This is all I'm suggesting we do.  I think we should add text 
> to the document that gives guidance on the types of usages 
> for which a USRK would be appropriate.  Usages should be for 
> functions related to the access network to which you are 
> connecting, and for functions where it is reasonable for your 
> access network to have an interest in authorization.
> 

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." 

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

v2.23.0 | Report a Bug | By Email