RE: [HOKEY] EMSK Issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [HOKEY] EMSK Issue
- To: "Charles Clancy" <clancy at cs.umd.edu>
- Subject: RE: [HOKEY] EMSK Issue
- From: "Narayanan, Vidya" <vidyan at qualcomm.com>
- Date: Mon, 24 Mar 2008 11:26:46 -0700
- Cc: Glen Zorn <gzorn at arubanetworks.com>, ietf at ietf.org, hokey at ietf.org, Bernard Aboba <bernarda at windows.microsoft.com>
- Delivered-to: ietfarch-ietf-web-archive at core3.amsl.com
- Delivered-to: ietf at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=vidyan at 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 at cs.umd.edu>=20<A3DA4C2546E1614D8ACC896746CDCF2 9E7BF6E at aruba-mx1.arubanetworks.com>=20<C24CB51D5AA800449 982D9BCB90325130142DBF9 at NAEX13.na.qualcomm.com>=20<47E70F 45.2020106 at cs.umd.edu>|From:=20"Narayanan,=20Vidya"=20<vi dyan at qualcomm.com>|To:=20"Charles=20Clancy"=20<clancy at cs. umd.edu>|Cc:=20"Glen=20Zorn"=20<gzorn at arubanetworks.com>, =20<ietf at ietf.org>,=20<hokey at ietf.org>,=0D=0A=20=20=20=20 =20=20=20=20"Bernard=20Aboba"=20<bernarda at 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=;
- In-reply-to: <47E70F45.2020106 at cs.umd.edu>
- List-help: <mailto:ietf-request@ietf.org?subject=help>
- List-id: IETF Discussion <ietf.ietf.org>
- List-post: <mailto:ietf@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
- References: <47DF04FC.4060706 at cs.umd.edu> <A3DA4C2546E1614D8ACC896746CDCF29E7BF6E at aruba-mx1.arubanetworks.com> <C24CB51D5AA800449982D9BCB90325130142DBF9 at NAEX13.na.qualcomm.com> <47E70F45.2020106 at cs.umd.edu>
- Sender: ietf-bounces at ietf.org
- Thread-index: AciNVURfKL5k48XoQuuTKuVJnSKTeAAhVkrg
- Thread-topic: [HOKEY] EMSK Issue
Charles,
> -----Original Message-----
> From: Charles Clancy [mailto:clancy at cs.umd.edu]
> Sent: Sunday, March 23, 2008 7:18 PM
> To: Narayanan, Vidya
> Cc: Glen Zorn; ietf at ietf.org; hokey at 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 at ietf.org
https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions
of the senders and do not imply endorsement by the IETF.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.