Re: [pkng] Where to go? What to do?

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 28 September 2010 21:26 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: pkng@core3.amsl.com
Delivered-To: pkng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCF493A6D46 for <pkng@core3.amsl.com>; Tue, 28 Sep 2010 14:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.402
X-Spam-Level:
X-Spam-Status: No, score=-102.402 tagged_above=-999 required=5 tests=[AWL=-0.403, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, 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 tuh2gVCzvMNZ for <pkng@core3.amsl.com>; Tue, 28 Sep 2010 14:26:14 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [IPv6:2001:770:10:200:21b:21ff:fe3a:3d50]) by core3.amsl.com (Postfix) with ESMTP id 917B43A6D2C for <pkng@irtf.org>; Tue, 28 Sep 2010 14:26:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 12C5E3E4094; Tue, 28 Sep 2010 22:26:54 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1285709213; bh=4AVQssJD7GcKNA T2+cvqEHpvInz3UPQumrShFYHOJVI=; b=tezkH/DE7MpNTryc1hP/H1hk+qaj5h g9HMa7E5+2yI9ABe2wvP3uQT2cm+GiTm1lLKz4TGr6/i8EJs5VeFB50OWDRgh+Hg CLSx3KBw6ReVXt4u85OE91sza81DmP7f7k+cIuFN9WAJwbrOSmEokZiIg7uefRHQ +8sZwVJ6OYWwI/+1RXxcMF8p0LUJ3qYrQoKe4Cf7trTxJM8Hy9V6J6WcMWvlo6nB vIHsY+dMLAQnVP+KXzlk8G6ezxuMJi4qPKSMgz/g0s7UK/S8J9hlZpMJqRxc4Yy2 CKLq9jmsSTV3KgXnGxgBTWQOEs5sty8QhDS3clWmgMq19iK60UMiyIrg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id eLPTAUAnfJtq; Tue, 28 Sep 2010 22:26:53 +0100 (IST)
Received: from [10.87.48.5] (dsl-102-234.cust.imagine.ie [87.232.102.234]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id A51B03E4090; Tue, 28 Sep 2010 22:26:53 +0100 (IST)
Message-ID: <4CA25D9C.1010609@cs.tcd.ie>
Date: Tue, 28 Sep 2010 22:26:52 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.12) Gecko/20100915 Lightning/1.0b1 Thunderbird/3.0.8
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <p06240825c8c7fd5ca338@[10.20.30.163]>
In-Reply-To: <p06240825c8c7fd5ca338@[10.20.30.163]>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: pkng@irtf.org
Subject: Re: [pkng] Where to go? What to do?
X-BeenThere: pkng@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Public Key Next Generation \(PKNG\) Research Group" <pkng.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/pkng>, <mailto:pkng-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/pkng>
List-Post: <mailto:pkng@irtf.org>
List-Help: <mailto:pkng-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/pkng>, <mailto:pkng-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 21:26:15 -0000

On 28/09/10 21:22, Paul Hoffman wrote:
> Please speak up soon if you think that there is interesting work in our charter, and hopefully start threads here with such discussions. If we don't have sufficient interest, we can close the list quietly.

I believe there could be, but that some of the oxygen has been
sucked out of the room (to keyassure) so I'm no longer sure if
there's a realistic target for pkng, nor whether there're
sufficient cycles for doing work. (I'd be happy if my concerns
are unfounded.)

Assuming keyassure turns into an IETF WG developing some kind
of way to manage public keys in the DNS, (and offers a reasonable
potential successor/addition to X.509), I think this group could
maybe try look beyond that towards pk systems that might start
to be deployed in 5+ years after both X.509 and keyassure are
already out there. But I think we'd have to know where keyassure
is going before re-scoping the work here.

If keyassure founders, then there's a role for this group
in understanding why and maybe working towards fixing whatever
caused the failure. (Assuming the failure is technology
and not personnel;-)

Bottom line for me for now: let's see what happens with
keyassure first before we kill or pump up this group. My
guess is that we won't know until the new year.

S.

PS: I still have that list of things I'd like that I sent to
this list a long while ago.