Re: [KEYPROV] Status and Next Steps

Hannes Tschofenig <hannes.tschofenig@gmx.net> Fri, 24 September 2010 13:52 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: keyprov@core3.amsl.com
Delivered-To: keyprov@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E72143A69E2 for <keyprov@core3.amsl.com>; Fri, 24 Sep 2010 06:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.18
X-Spam-Level:
X-Spam-Status: No, score=-102.18 tagged_above=-999 required=5 tests=[AWL=0.419, BAYES_00=-2.599, 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 2dOIh3zqNZQ4 for <keyprov@core3.amsl.com>; Fri, 24 Sep 2010 06:52:46 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 218E03A6901 for <keyprov@ietf.org>; Fri, 24 Sep 2010 06:52:45 -0700 (PDT)
Received: (qmail invoked by alias); 24 Sep 2010 13:53:15 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.1.10]) [88.115.222.204] by mail.gmx.net (mp046) with SMTP; 24 Sep 2010 15:53:15 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+sUk9o5sGs/o2NF00VQjUQMi8tdAlZgB75Qv9kDF oSCPaAX1KIdhas
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <AANLkTi=b5xMJd=butALLQS3dB7Q79qvByq5qJAOHChRY@mail.gmail.com>
Date: Fri, 24 Sep 2010 16:53:14 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <162985EF-4843-4BB7-82F6-7586782EDCCC@gmx.net>
References: <AANLkTi=b5xMJd=butALLQS3dB7Q79qvByq5qJAOHChRY@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1081)
X-Y-GMX-Trusted: 0
Cc: Hannes Tschofenig <hannes.tschofenig@gmx.net>, KEYPROV <keyprov@ietf.org>
Subject: Re: [KEYPROV] Status and Next Steps
X-BeenThere: keyprov@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Provisioning of Symmetric Keys \(keyprov\)" <keyprov.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyprov>, <mailto:keyprov-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyprov>
List-Post: <mailto:keyprov@ietf.org>
List-Help: <mailto:keyprov-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyprov>, <mailto:keyprov-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 13:52:48 -0000

Hi Phillip, 

this is indeed great news!

There is one document on PSKC algorithm profiles that would need to get finished. Here is the current version: 
https://datatracker.ietf.org/doc/draft-hoyer-keyprov-pskc-algorithm-profiles/

In  a chat with Anders we were also wondering whether a JSON encoding of PSKC would be useful. This would allow us easier integration with JavaScript into the browser. 

The first document does not necessarily need to go through a working group; it could also be an AD sponsored document or directly sent to the RFC Editor. The second document obviously does not yet exist. 

Regarding interoperability: I am actually always in favor of doing interoperability testing (in a lightweight fashion -- potentially over the Internet with some test cases we go through). It would be interesting to know where we are with regard to running code.

Ciao
Hannes

On Sep 24, 2010, at 4:41 PM, Phillip Hallam-Baker wrote:

> As of this morning all KEYPROV drafts are in state RFC-Ed Queue
> 
> draft-ietf-keyprov-symmetrickeyformat	-11			2010-08-09  	RFC Ed Queue
> draft-ietf-keyprov-pskc	-09	ipr		2010-08-02  	RFC Ed Queue
> draft-ietf-keyprov-dskpp	-14	ipr		2010-09-07  	RFC Ed Queue
> 
> First, congratulations and thanks for all the hard work.
> 
> Could authors ensure that they respond to questions from the RFC editor so that we can get into AUTH48 as soon as possible and publish the RFCs before Beijing.
> 
> 
> This completes our charter items and leads to the question of next steps. In particular do we want to progress from PROPOSED standard to whatever comes next?
> 
> From my point of view, this actually depends on whether there is a change from a three step process to two. At the moment a lot of IETF specs languish at PROPOSED and there is safety in numbers. If there is a move to a two step process I think it more likely that completing the IETF process and being promoted to STANDARD will become an expectation.
> 
> 
> Assuming the criteria for progress will remain the same as those for DRAFT status, the main things we will need to do are (1) recharter and (2) demonstrate that we have 2 interoperable implementations for each specification feature.
> 
> Rechartering will of course be subject to the approval of the ADs.
> 
> What do people in the group think about this?
> 
> -- 
> Website: http://hallambaker.com/
> 
> _______________________________________________
> KEYPROV mailing list
> KEYPROV@ietf.org
> https://www.ietf.org/mailman/listinfo/keyprov