Re: [HOKEY] draft-gaonkar-radext-erp-attrs-03

"Glen Zorn" <gzorn@arubanetworks.com> Thu, 13 March 2008 01:55 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 B387828C4B9; Wed, 12 Mar 2008 18:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.797
X-Spam-Level:
X-Spam-Status: No, score=-100.797 tagged_above=-999 required=5 tests=[AWL=-0.360, 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 VfA8XexgfL6Q; Wed, 12 Mar 2008 18:55:31 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C5FA3A6C1D; Wed, 12 Mar 2008 18:55:31 -0700 (PDT)
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 49DCC3A6BEB for <hokey@core3.amsl.com>; Wed, 12 Mar 2008 18:55:30 -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 wbmulxrG8wPG for <hokey@core3.amsl.com>; Wed, 12 Mar 2008 18:55:29 -0700 (PDT)
Received: from mail.arubanetworks.com (mail.arubanetworks.com [216.31.249.253]) by core3.amsl.com (Postfix) with SMTP id A02A03A6A71 for <hokey@ietf.org>; Wed, 12 Mar 2008 18:55:29 -0700 (PDT)
Received: from aruba-mx1.arubanetworks.com ([10.1.1.17]) by mail.arubanetworks.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 12 Mar 2008 18:53:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 12 Mar 2008 18:53:04 -0700
Message-ID: <A3DA4C2546E1614D8ACC896746CDCF29E7B531@aruba-mx1.arubanetworks.com>
In-Reply-To: <003f01c88496$97b60b30$091716ac@xpsuperdvd2>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-gaonkar-radext-erp-attrs-03
Thread-Index: AciDiPPZHcUdU+98TbC66jCoRaIFogA/V3JQAAGwtqAAAi5joAAFwT5w
References: <003601c88386$d06b7a20$091716ac@xpsuperdvd2> <47D69F03.3030800@qualcomm.com> <002401c88487$99e12660$091716ac@xpsuperdvd2> <001101c8848e$2e04ad20$2d01f00a@arubanetworks.com> <003f01c88496$97b60b30$091716ac@xpsuperdvd2>
From: Glen Zorn <gzorn@arubanetworks.com>
To: "David B. Nelson" <dnelson@elbrysnetworks.com>, Glen Zorn <glenzorn@comcast.net>, Lakshminath Dondeti <ldondeti@qualcomm.com>
X-OriginalArrivalTime: 13 Mar 2008 01:53:11.0785 (UTC) FILETIME=[FE6CE590:01C884AC]
Cc: Bernard_Aboba@hotmail.com, hokey@ietf.org
Subject: Re: [HOKEY] draft-gaonkar-radext-erp-attrs-03
X-BeenThere: hokey@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HOKEY WG Mailing List <hokey.ietf.org>
List-Unsubscribe: <https://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: <https://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

David B. Nelson <mailto:dnelson@elbrysnetworks.com> scribbled on
Wednesday, March 12, 2008 7:13 PM:

> Glen writes...
> 
>>> If I understand the direction in HOKEY, there will be an
>>> un-encrypted RADIUS Key Container Attribute defined for use in
>>> HOKEY, within a HOKEY draft.
>> 
>> I'm not at all sure that that is a good idea -- it seems to assume
>> the usage of an external-to-RADIUS protection method (DTLS, IPsec,
>> etc.) & preclude the usage of RADIUS-based protection (e.g., key
>> wrap). 
> 
> Why do you say that?  If we have Encrypted Attributes in
> RADIUS, surely that specifies an internal-to-RADIUS
> cryptographic protection mechanism.  Cannot the HOKEY Key
> Container attribute use the Encrypted Attribute format?

Maybe; nobody knows for sure, yet...
_______________________________________________
HOKEY mailing list
HOKEY@ietf.org
https://www.ietf.org/mailman/listinfo/hokey