IETF Logo Mail Archive

Re: [therightkey] [pkix] Proposal for working on PKIX revocation open issues

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 15 November 2014 18:12 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: therightkey@ietfa.amsl.com
Delivered-To: therightkey@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37DB41ACD8A; Sat, 15 Nov 2014 10:12:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.647
X-Spam-Level:
X-Spam-Status: No, score=-3.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-5uJC1ULDFe; Sat, 15 Nov 2014 10:12:49 -0800 (PST)
Received: from proper.com (Hoffman.Proper.COM [207.182.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC8151ACD37; Sat, 15 Nov 2014 10:12:48 -0800 (PST)
Received: from [10.20.30.90] (142-254-17-6.dsl.dynamic.fusionbroadband.com [142.254.17.6]) (authenticated bits=0) by proper.com (8.14.9/8.14.7) with ESMTP id sAFICl8k078358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 Nov 2014 11:12:48 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 142-254-17-6.dsl.dynamic.fusionbroadband.com [142.254.17.6] claimed to be [10.20.30.90]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <5466AF87.2050307@gmail.com>
Date: Sat, 15 Nov 2014 10:12:47 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4ACAB901-FE45-4E5E-A9E0-8F51E94A2924@vpnc.org>
References: <5466AF87.2050307@gmail.com>
To: "pkix@ietf.org" <pkix@ietf.org>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/therightkey/uaA6UiCpPuSQwgaacWmytjhBTl8
X-Mailman-Approved-At: Sat, 15 Nov 2014 10:22:45 -0800
Cc: therightkey@ietf.org
Subject: Re: [therightkey] [pkix] Proposal for working on PKIX revocation open issues
X-BeenThere: therightkey@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <therightkey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/therightkey>, <mailto:therightkey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/therightkey/>
List-Post: <mailto:therightkey@ietf.org>
List-Help: <mailto:therightkey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/therightkey>, <mailto:therightkey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Nov 2014 18:12:54 -0000

On Nov 14, 2014, at 5:42 PM, Dr. Massimiliano Pala <massimiliano.pala@gmail.com> wrote:
> (a) Defining new transport protocols for revocation information availability (e.g., OCSP over DNS or OCSP over LDAP)

If you mean "pre-recorded (sometimes called 'stapled') OCSP responses", yes, this is useful. Maybe even over HTTP!

> (b) (Possibly) defining a more lightweight revocation mechanisms (e.g. Lightweight Revocation Tokens)

Not interested.

> (c) (Possibly) helping other working groups to revise and update how revocation information are provided (e.g., the client authentication case)

Not interested.

> (d) (Possibly) introducing privacy consideration when it comes to revocation checking

Slightly interested.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email