IETF Logo Mail Archive

Re: [pkng] fyi: keyassure@ mailing list - aka tls@dnssec, certs/keys-in-DNS(sec), DKI

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 19 August 2010 00:00 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 BB1033A68C7 for <pkng@core3.amsl.com>; Wed, 18 Aug 2010 17:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.749
X-Spam-Level:
X-Spam-Status: No, score=-102.749 tagged_above=-999 required=5 tests=[AWL=-0.150, 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 FunzO0-RYUhy for <pkng@core3.amsl.com>; Wed, 18 Aug 2010 17:00:10 -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 29D8D3A68C4 for <pkng@irtf.org>; Wed, 18 Aug 2010 17:00:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id CC6C73E4096; Thu, 19 Aug 2010 01:00:43 +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=1282176043; bh=92yTRcM0MzAK3a VBai/QmSfqgi6ed9iQMA6iJYF6v2w=; b=zUOfbyamyYbhYNMt6tqZApxNok2omu jDVK6hSW+CHZ9WRfVBk4bPY+udZTA9mRjgkIAAwgRFHKesIdwVrmpF62IiX3dHpX Su4aytA/JDRtgQvyZ+2nKLQN/6pGOFZjDJjJL5eyfRGakbmAIaXWF3gfY0GqNrz3 Zbig0FjPMa6La/LwMnRXYTkZwt93Y+jMQdAQ1vfU7/iDfe0o3Hle9oPwQCLnIcL2 gpoRfaP1Vqguy+90FGqJeHbXFH+jqdzl7gM+I3z+FlTegscWe3tgPZNwixoo9Ztc wj1SZ3HYgX6Wq9YUKpxRpEU+o3Sue6kjfmT4gj4ZaptCrE1+Lt166Q3Q==
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 AWXWsg4iuQBV; Thu, 19 Aug 2010 01:00:43 +0100 (IST)
Received: from [10.87.48.3] (dsl-102-234.cust.imagine.ie [87.232.102.234]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 7579F3E4090; Thu, 19 Aug 2010 01:00:43 +0100 (IST)
Message-ID: <4C6C7429.7020209@cs.tcd.ie>
Date: Thu, 19 Aug 2010 01:00:41 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100713 Lightning/1.0b1 Thunderbird/3.0.6
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <4C6C6830.9040103@KingsMountain.com> <4C6C6D4F.2020703@cs.tcd.ie> <p06240812c8921e7303c7@[10.20.30.158]>
In-Reply-To: <p06240812c8921e7303c7@[10.20.30.158]>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: IRTF PKng WG <pkng@irtf.org>, =JeffH <Jeff.Hodges@KingsMountain.com>
Subject: Re: [pkng] fyi: keyassure@ mailing list - aka tls@dnssec, certs/keys-in-DNS(sec), DKI
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: Thu, 19 Aug 2010 00:00:13 -0000

On 19/08/10 00:36, Paul Hoffman wrote:
> Not at all. PKNG's charter is to "look into alternate certificate formats, semantics, and PK services that could eventually replace PKIX if deployed".

Right. Zero documents and a moribund list seem to imply the
charter was wishful thinking.

> The new mailing list is aimed at protocols that use PKIX certificates, and the draft that I co-authored is specifically about TLS, which requires a PKIX certificate to identify the server.
> 
> This list can still be useful within our charter if folks get get some creative juices flowing around the idea of alternate formats, semantics, and services.

(Don't I recall you saying that new format work was exactly
what you didn't want to happen first?)

Look, if something does start to happen here, then that'd be great.
All I'm saying is that given the (lack of) history here and the
evident interest in websockets/keys-in-DNS et al I suspect the
relevant CPU cycles are going to be invested elsewhere for the
next while. I'd be delighted to be proven wrong.

S.

v2.23.0 | Report a Bug | By Email