IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 18 August 2010 23:36 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 449223A68F5 for <pkng@core3.amsl.com>; Wed, 18 Aug 2010 16:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.146
X-Spam-Level:
X-Spam-Status: No, score=-100.146 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, 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 ABXphkEgZgK1 for <pkng@core3.amsl.com>; Wed, 18 Aug 2010 16:36:29 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 773783A6823 for <pkng@irtf.org>; Wed, 18 Aug 2010 16:36:28 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o7INaxYo020258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Aug 2010 16:37:00 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240812c8921e7303c7@[10.20.30.158]>
In-Reply-To: <4C6C6D4F.2020703@cs.tcd.ie>
References: <4C6C6830.9040103@KingsMountain.com> <4C6C6D4F.2020703@cs.tcd.ie>
Date: Wed, 18 Aug 2010 16:36:57 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, =JeffH <Jeff.Hodges@KingsMountain.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: IRTF PKng WG <pkng@irtf.org>
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: Wed, 18 Aug 2010 23:36:30 -0000

At 12:31 AM +0100 8/19/10, Stephen Farrell wrote:
>On 19/08/10 00:09, =JeffH wrote:
>> Of possible interest...
>
>Indeed. Seems like that list had more traffic in one day
>than this one in a year. (Well, I didn't actually count
>'em up but it feels that way.)
>
>Personally, I reckon this means there is no point in this
>group at present, until the IETF BoF process plays out. I
>think that's a pity and maybe a missed opportunity (but
>of course, we'll never know, by definition;-)

Not at all. PKNG's charter is to "look into alternate certificate formats, semantics, and PK services that could eventually replace PKIX if deployed".

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.

--Paul Hoffman, Director
--VPN Consortium

v2.23.0 | Report a Bug | By Email