WG Review: Recharter of Public-Key Infrastructure (X.509) (pkix)

IESG Secretary <iesg-secretary@ietf.org> Thu, 31 January 2008 15:15 UTC

Return-path: <ietf-announce-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKb87-00067m-1B; Thu, 31 Jan 2008 10:15:07 -0500
Received: from [] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKb82-00064u-Ue; Thu, 31 Jan 2008 10:15:03 -0500
Received: from ns4.neustar.com ([]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JKb82-000662-Fu; Thu, 31 Jan 2008 10:15:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com []) by ns4.neustar.com (Postfix) with ESMTP id 5F40B2AC76; Thu, 31 Jan 2008 15:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1JKb82-00033Y-4p; Thu, 31 Jan 2008 10:15:02 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: ietf-announce@ietf.org
From: IESG Secretary <iesg-secretary@ietf.org>
Message-Id: <E1JKb82-00033Y-4p@stiedprstage1.ietf.org>
Date: Thu, 31 Jan 2008 10:15:02 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: ietf-pkix@imc.org, Stephen Kent <kent@bbn.com>
Subject: WG Review: Recharter of Public-Key Infrastructure (X.509) (pkix)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

A modified charter has been submitted for the Public-Key Infrastructure
(X.509) (pkix) working group in the Security Area of the IETF. The IESG
has not made any determination as yet.  The modified charter is provided
below for informational purposes only.  Please send your comments to the
IESG mailing list (iesg@ietf.org) by February 4.


Public-Key Infrastructure (X.509) (pkix)


Stephen Kent <kent@bbn.com>
Stefan Santesson <stefans@microsoft.com>

Security Area Director(s):

Tim Polk <tim.polk@nist.gov>
Sam Hartman <hartmans-ietf@mit.edu>

Security Area Advisor:

Tim Polk <tim.polk@nist.gov>

Mailing Lists:

General Discussion: ietf-pkix@imc.org
To Subscribe: ietf-pkix-request@imc.org
In Body: subscribe (In Body)
Archive: http://www.imc.org/ietf-pkix

Description of Working Group:

The PKIX Working Group was established in the fall of 1995 with the 
goal of developing Internet standards to support X.509-based Public 
Key Infrastructures (PKIs). Initially PKIX pursued this goal by 
profiling X.509 standards developed by the CCITT (later the ITU-T). 
Later, PKIX initiated the development of standards that are not 
profiles of ITU-T work, but rather are independent initiatives 
designed to address X.509-based PKI needs in the Internet. Over time 
this latter category of work has become the major focus of PKIX work, 
i.e., most PKIX-generated RFCs are no longer profiles of ITU-T X.509 

PKIX has produced a number of standards track and informational RFCs. 
RFC 3280 (Certificate and CRL Profile), and RCF 3281 (Attribute 
Certificate Profile) are recent examples of standards track RFCs that 
profile ITU-T documents. RFC 2560 (Online Certificate Status 
Profile), RFC 3779 (IP Address and AS Number Extensions), and RFC 
3161 (Time Stamp Authority) are examples of standards track RFCs that 
are IETF-initiated. RFC 4055 (RSA) and RFC 3874 (SHA2) are examples 
of informational RFCs that describe how to use public key and hash 
algorithms in PKIs.

PKIX Work Plan

PKIX will continue to track the evolution of ITU-T X.509 documents, 
and will maintain compatibility between these documents and IETF PKI 
standards, since the profiling of X.509 standards for use in the 
Internet remains an important topic for the working group.

PKIX does not endorse the use of specific cryptographic algorithms 
with its protocols. However, PKIX does publish standards track RFCs 
that describe how to identify algorithms and represent associated 
parameters in these protocols, and how to use these algorithms with 
these protocols. We anticipate efforts in this arena will continue to 
be required over time.

PKIX will pursue new work items in the PKI arena if working group 
members express sufficient interest, and if approved by the cognizant 
Security Area director. For example, certificate validation under X. 
509 and PKIX standards calls for a relying party to use a trust 
anchor as the start of a certificate path. Neither X.509 nor extant 
PKIX standards define protocols for the management of trust anchors. 
Existing mechanisms for managing trust anchors, e.g., in browsers, 
are limited in functionality and non-standard. There is considerable 
interest in the PKI community to define a standard model for trust 
anchor management, and standard protocols to allow remote management. 
Thus a future work item for PKIX is the definition of such protocols 
and associated data models.


Feb 2008 Update to CMC approved as PROPOSED Standard
Mar 2008 RFC 3280bis approved as PROPOSED Standard
Mar 2008 ECC Algorithms approved as PROPOSED Standard
Mar 2008 TAM Problem Statement published as Informational
Jul 2008 TAM Protocols and Models published as PROPOSED Standard

IETF-Announce mailing list