Re: [saag] PKIX report

["Hallam-Baker, Phillip" <[e-mail]>]

I dispute the assertion that a new protocol or port # might be required for OCSP. The protocol is adequately extendable.
 
What I put in the slides was what I felt that the group had already agreed to. Since this was the first occasion where the issues had been raised, I was not proposing a solution. If it is agreed that there is a problem, there is a simple solution.

________________________________

From: [e-mail] on behalf of Stephen Kent
Sent: Tue 3/24/2009 4:27 PM
To: [e-mail]
Subject: [saag] PKIX report


PKIX Meeting report

We have one document in the RFC editor's queue and twelve I-Ds in process.

PRQP, targeted to Experimental status, will be revised one more time, and them move to WGLC.

Traceable Autonomous Certificates, also targeted to Experimental status, has been revised in response to numerous comments from David Cooper. It will be posted and hopefully move to WGLC next month.

The Trust Anchor management requirements document passed WGLC. The format for TA material and the TAMP spec are both ready for WGLC.

An initial OCSP algorithm agility I-D defines the default behavior for a client, and proposes additional client behavior rules to deal with one algorithm mismatch problem. However, SHA-1 is hardwired into the spec and this needs to be addressed, if only for perception reasons. Providing true algorithm agility here may require a more innovative approach, e.g., use of different port or protocol values.

RFC 3161 (Time Stamp Protocol,) will be updated to address a hash agility concern and to address terminology issues (to be compatible with ETSI documents).

David Cooper is assembling data to support advancement of RFC 5280  to Proposed status.

The new ASN.1 draft has been revised and is ready for WGLC,  in parallel with a straw poll to determine whether the document should be Informational or Standards track.

The I-D that provides OIDs for use with DSA and ECDSA will progress to WGLC, despite its dependence on a FIPS (186-3) that has yet to be issued.

The meeting concluded with a presentation by Stefan Santesson on a proposal to include a PDF as a next generation logotype capability. The goal is to do a better job of conveying the identity of a certificate holder to a (human) relying party, compared to  display of certificate contents, etc.