Re: [KEYPROV] Status and Next Steps

Phillip Hallam-Baker <hallam@gmail.com> Sun, 26 September 2010 14:23 UTC

Return-Path: <hallam@gmail.com>
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 5FBC03A6AA2 for <keyprov@core3.amsl.com>; Sun, 26 Sep 2010 07:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.38
X-Spam-Level:
X-Spam-Status: No, score=-2.38 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 fRVgPTeXVPbD for <keyprov@core3.amsl.com>; Sun, 26 Sep 2010 07:23:29 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 6E20A3A6A22 for <keyprov@ietf.org>; Sun, 26 Sep 2010 07:23:29 -0700 (PDT)
Received: by wwd20 with SMTP id 20so115649wwd.13 for <keyprov@ietf.org>; Sun, 26 Sep 2010 07:24:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=nz5U9aZtwKs8lShQuAEEJkNaBBvqBjg6nhDLMHc4Ezw=; b=SDe/SyQk4NUKfY1HBtH6xZI5H96QO628+i4haDgsh3NVZbCXsCyUFPd4HcGZ1NQoEZ 68aFa9N6ZS35f3UgKcb4wySNkVTyiSJSmXkwreBfolj1siFc4z4FgEh7r0BGtHApo4Nr P6m5ozKvsLv1nO8cmyy+6xf/UjeNaRjsOhnSE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=b2B6cYwNeVnM5QhLfDF3vHUZbhmJ7LX7Be5qecl/Dgrs9VLLjP1PXB9OrBua+G/3Qu VDQzqwdOk0rz3eGY5xHzpCaelXU5AzAnoIOnUJwNhOwv41d/5IlQljpljsmThEdara9w ItbgGA9Xr9Dv0Ctg0FVJBbpW1LFY4H1Lzfi9s=
MIME-Version: 1.0
Received: by 10.216.158.18 with SMTP id p18mr11720641wek.2.1285511045046; Sun, 26 Sep 2010 07:24:05 -0700 (PDT)
Received: by 10.216.163.195 with HTTP; Sun, 26 Sep 2010 07:24:04 -0700 (PDT)
In-Reply-To: <162985EF-4843-4BB7-82F6-7586782EDCCC@gmx.net>
References: <AANLkTi=b5xMJd=butALLQS3dB7Q79qvByq5qJAOHChRY@mail.gmail.com> <162985EF-4843-4BB7-82F6-7586782EDCCC@gmx.net>
Date: Sun, 26 Sep 2010 10:24:04 -0400
Message-ID: <AANLkTimZ8mpO2YP9k9OBK2U1mYddUgozTe2tmwP0XopH@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: multipart/alternative; boundary="0016e64974e631e3bc04912a5d33"
Cc: 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: Sun, 26 Sep 2010 14:23:31 -0000

The PSKC algorithm profiles is currently submitted as an individual
submission which is why it is not showing up in the tracker as a keyprov
item.



On Fri, Sep 24, 2010 at 9:53 AM, Hannes Tschofenig <
hannes.tschofenig@gmx.net> wrote:

> 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
>
>


-- 
Website: http://hallambaker.com/