Re: [Dime] AD review of draft-ietf-dime-local-keytran-09

Glen Zorn <gwz@net-zen.net> Thu, 26 May 2011 05:11 UTC

Return-Path: <gwz@net-zen.net>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D980EE06DE for <dime@ietfa.amsl.com>; Wed, 25 May 2011 22:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.662
X-Spam-Level:
X-Spam-Status: No, score=-102.662 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id to0lRzNZ9BHl for <dime@ietfa.amsl.com>; Wed, 25 May 2011 22:11:41 -0700 (PDT)
Received: from p3plsmtpa01-02.prod.phx3.secureserver.net (p3plsmtpa01-02.prod.phx3.secureserver.net [72.167.82.82]) by ietfa.amsl.com (Postfix) with SMTP id 3B756E06C1 for <dime@ietf.org>; Wed, 25 May 2011 22:11:41 -0700 (PDT)
Received: (qmail 13908 invoked from network); 26 May 2011 05:11:39 -0000
Received: from unknown (124.120.33.179) by p3plsmtpa01-02.prod.phx3.secureserver.net (72.167.82.82) with ESMTP; 26 May 2011 05:11:39 -0000
Message-ID: <4DDDE107.9090501@net-zen.net>
Date: Thu, 26 May 2011 12:11:35 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04031E5369@307622ANEX5.global.avaya.com> <4DDBC0A4.4000802@net-zen.net> <EDC652A26FB23C4EB6384A4584434A04032508C3@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04032508C3@307622ANEX5.global.avaya.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------040805060300020203090900"
Cc: dime@ietf.org
Subject: Re: [Dime] AD review of draft-ietf-dime-local-keytran-09
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 26 May 2011 05:11:43 -0000

On 5/25/2011 6:34 PM, Romascanu, Dan (Dan) wrote:

...

>>> T2: Are there any special recommendations for the experts who will
> be
>>> in charge in the future with the "Expert Review" policy as per
>>> [RFC5226] for AVP types?
>>
>> Do you mean values for the Key-Type AVP?  No such recommendations
> would
>> come from me; we had originally specified the policy as "First Come,
>> First Served"
>> (http://www.potaroo.net/ietf/all-ids/draft-wu-dime-local-keytran-
>> 03.txt)
>> on the simple theory that anybody who wanted to register, use & deploy
>> e.g. rot13 would get what they deserved ;-).  IIRC, one of the dime
>> Chairs suggested the expert review policy, so maybe they have some
>> suggestions.
>>
>> ...
> 
> [[DR]] Can you please clarify this with the chairs? If the policy is
> "Expert Review" criteria for reviewing requests for new Key-Type AVP
> values should be specified. 

I would prefer to change the policy to "Specification Required" because
this seems to be all that is really necessary for interoperability.

> 
> ...
> 
>>>
>>> E1: Why is RSA-KEM not expanded and explained in Section 2.2. -
>>> Technical Terms and Acronyms?
>>
>> Would you like the whole thing expanded or just KEM?
> [[DR]] RFC 5990 explains KEM (in the Abstract actually). This would be
> probably sufficient, although I would bet that even in the security
> community not everybody knows the names beyond R, S and A. 

OK, added definitions of both "RSA" and "RSA-KEM".

...