Re: [Dime] New version of draft-wu-dime-local-keytran
Sebastien Decugis <sdecugis@nict.go.jp> Wed, 09 December 2009 02:07 UTC
Return-Path: <sdecugis@nict.go.jp>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 128243A6AA8 for <dime@core3.amsl.com>; Tue, 8 Dec 2009 18:07:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.008
X-Spam-Level: *
X-Spam-Status: No, score=1.008 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, FRT_SOMA2=2.199, HELO_EQ_JP=1.244]
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 ZD90Ja-H3n9w for <dime@core3.amsl.com>; Tue, 8 Dec 2009 18:07:17 -0800 (PST)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:2f8:29::3]) by core3.amsl.com (Postfix) with ESMTP id 0EDFB3A6AA6 for <dime@ietf.org>; Tue, 8 Dec 2009 18:07:16 -0800 (PST)
Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp with ESMTP id nB9274oX019588; Wed, 9 Dec 2009 11:07:04 +0900 (JST)
Received: from gw2.nict.go.jp (localhost [127.0.0.1]) by gw2.nict.go.jp with ESMTP id nB9274wl006160; Wed, 9 Dec 2009 11:07:04 +0900 (JST)
Received: from mail2.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw2.nict.go.jp with ESMTP id nB9273GP006157; Wed, 9 Dec 2009 11:07:04 +0900 (JST)
Received: from mail2.nict.go.jp (localhost [127.0.0.1]) by mail2.nict.go.jp (NICT Mail) with ESMTP id E4C8116AC3; Wed, 9 Dec 2009 11:07:03 +0900 (JST)
Received: from [133.243.146.206] (5gou2f-dhcp46.nict.go.jp [133.243.146.206]) by mail2.nict.go.jp (NICT Mail) with ESMTP id CA5B116A97; Wed, 9 Dec 2009 11:07:03 +0900 (JST)
Message-ID: <4B1F0642.2090604@nict.go.jp>
Date: Wed, 09 Dec 2009 11:06:58 +0900
From: Sebastien Decugis <sdecugis@nict.go.jp>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Glen Zorn <gwz@net-zen.net>, "dime@ietf.org" <dime@ietf.org>
References: <01ce01ca7842$352c49b0$9f84dd10$@net>
In-Reply-To: <01ce01ca7842$352c49b0$9f84dd10$@net>
X-Enigmail-Version: 0.96.0
OpenPGP: id=33D9F61D
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Subject: Re: [Dime] New version of draft-wu-dime-local-keytran
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Dec 2009 02:07:19 -0000
Hi Glen, Qin, all,
By quickly looking into the new version, a few additional comments came
to my mind:
In section 3.1, I would like to propose a change to the ABNF. I think
the Key-Type AVP should be in a fixed position (actually I was under the
impression that this was already decided, but anyway), like this:
Key ::= < AVP Header: AC1 >
< Key-Type >
...
In section 3.1.1 (definition of Key-Type AVP), I think some of the
defined values should be removed, as follow:
- rMSK (4) : As I understand, there is no difference between rMSK and
MSK, so we may not need a different type for this one ? (not sure)
- USRK (2) & DSUSRK (5): RFC5295 defines a generic algorithm to derive
usage-specific keys. The definition alone is not sufficient to create
keying material: we need the usage itself to define the missing parts.
Therefore, having a "USRK" or "DSUSRK" container is pointless, it does
not allow the recipient to understand what is in the key. On the other
hand, rRK and rDSRK make sense, since ERP defines completely the
algorithm (they are instances of USRK and DSUSRK). Anyway, I guess it
would make more sense that the rRK and rDSRK values are assigned in the
registry by Diameter ERP document, if needed. But this is not very
important. As a summary, I believe an initial version the document
should only define MSK and DSRK Key-Type values.
I section 4, maybe a bit of explanation about the Key-Type and Key-Name
AVPs inside DER / DEA would be useful. From the remaining of the
document, I had only guessed that the Key AVP could be present in DEA,
and nothing about the other ones.
I believe the "Security Considerations" section should also reference
RFC5295's security section, especially Section 7.4 (Key Distribution),
and mention that Diameter honors these security requirements. It should
also mention that different key usages may have stronger security
requirements, that must be carefully considered before using the
mechanism defined in this document.
That's all I have for the moment :) Sorry for the long mail!
Best regards,
Sebastien.
Glen Zorn a écrit :
> FYI, http://www.ietf.org/id/draft-wu-dime-local-keytran-03.txt has been
> posted; we think that all outstanding comments have been addressed.
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>
>
--
Sebastien Decugis
Research fellow
Network Architecture Group
NICT (nict.go.jp)
- [Dime] New version of draft-wu-dime-local-keytran Glen Zorn
- Re: [Dime] New version of draft-wu-dime-local-key… Sebastien Decugis
- Re: [Dime] New version of draft-wu-dime-local-key… Sebastien Decugis
- Re: [Dime] New version of draft-wu-dime-local-key… Glen Zorn
- Re: [Dime] New version of draft-wu-dime-local-key… Qin Wu
- Re: [Dime] New version of draft-wu-dime-local-key… Sebastien Decugis
- Re: [Dime] New version of draft-wu-dime-local-key… Qin Wu
- Re: [Dime] New version of draft-wu-dime-local-key… Sebastien Decugis
- Re: [Dime] New version of draft-wu-dime-local-key… Qin Wu