[pkif-wg-technical] OASIS TC Call for Participation: PKI TC

[Karl Best <karl.best@oasis-open.org>]

A new OASIS technical committee is being formed. The OASIS Public Key
Infrastructure Technical Committee (PKI TC) has been proposed by the
following members of OASIS: Terry Leahy, Wells Fargo; Jeff Stapleton,
KPMG LLP; Peter Doyle, Baltimore Technologies; Derek Brink, RSA
Security; John Sabo, Computer Associates; and Patrick Kanaishi, Neucom
Corporation.

The proposal for a new TC meets the requirements of the OASIS TC Process
(see http://oasis-open.org/committees/process.shtml), and is appended to
this message. The proposal, which includes a statement of purpose, list
of deliverables, and proposed schedule, will constitute the TC's
charter. The TC Process allows these items to be clarified (revised) by
the TC members; such clarifications (revisions), as well as submissions
of technology for consideration by the TC and the beginning of technical
discussions, may occur no sooner than the TC's first meeting.

To become a member of this new TC you must 1) be an employee of an OASIS
member organization or an Individual member of OASIS; 2) notify the TC
chair, Terry Leahy (leahyt@wellsfargo.com) of your intent to participate
at least 15 days prior to the first meeting; and 3) attend the first
meeting on 10 January. You should also subscribe to the TC's mail list.
Note that membership in OASIS TCs is by individual, and not by
organization. You must be eligible for participation at the time you
time you notify the chair.

The private mail list pki-tc@lists.oasis-open.org is for committee
discussions. TC members as well as any other interested OASIS members
should subscribe to the list by going to the mail list web page at
http://lists.oasis-open.org/ob/adm.pl, or by sending a message to
pki-tc-request@lists.oasis-open.org with the word "subscribe" as the
body of the message. (Note that subscribing to the mail list does not
make you a member of the TC; to become a member you must contact the TC
chair and attend the first meeting as described in the preceeding
paragraph.)

A public comment list will be available for the public to make comments 
on the work of this TC; a message may be sent to the TC via the address 
  pki-tc-comment@lists.oasis-open.org.

The archives of both of these mail lists are visible to the public at
http://lists.oasis-open.org/archives/

-Karl

=================================================================
Karl F. Best
Vice President, OASIS
+1 978.667.5115 x206
karl.best@oasis-open.org  http://www.oasis-open.org



1. Name

Public Key Infrastructure Technical Committee (PKI TC)

2. Statement of Purpose

Many organizations worldwide are developing strategies to a) utilize
digital certificates to provide higher levels of security, b) make
applications certificate aware. and c) promote the deployment of digital
certificates for many business purposes including digital signatures.
The purpose of the PKI TC is to address issues related to the successful
deployment of digital certificates to meet business and security
requirements, as well as technical and integration/interoperability
issues.  Furthermore, the PKI TC will  increase the awareness of digital
certificates as an important component when managing access to network
resources, delivering secured electronic messages and conducting secure
electronic transactions.   The PKI TC will also provide a forum for a
broad community utilizing PKI and digital certificates in
application-focused standards and projects, as well as a mechanism for
the creation of documents related to the implementation of PKI
internationally.

The goals of the TC are:

To provide an international forum for software vendors, industry,
government, and implementers to internationally discuss issues, share
solutions, and develop white papers with respect to addressing:

- business and security needs
- technical interoperability
- enabling business applications
- increasing awareness of available solutions, applications, and
successful deployment
- coordination with other TCs in areas of overlap or mutual interest


3. List of Deliverables

A very wide range of topics will be addressed by the TC, and it is
expected that several sub-committees will be formed. TC deliverables
will include:

- business implementation guideline white papers
- technical implementation guideline white papers
- best practice and sample implementations
- applications white papers
- forums for networking, information sharing and implementation of
PKI-related projects
- solutions showcase.

The TC recognizes the importance of advancing the understanding and
applicability of XML-based PKI standards as well as other broader Web
services and security standardization effort within OASIS of which PKI
is a component of.  Such standards including: XKMS, WS-Security, the
Security Assertion Markup Language (SAML), the XML Access Control Markup
Language (XACML), the Rights Language, the Service Provisioning Markup
Language (SPML) and XML Common Biometric Format (XCBF), and  Digital
Signature Services (DSS) protocol.  Specific work-plan and deliverables
will be developed based on  TC and OASIS member input.


4. Business Language

English (USA)


5. Date and Time of First Meeting

The first TC meeting will be held on Jan 10th 2003 at 8.00 PST in the
format of a conference call.   The member section face to face meeting
is planned for March 11th - 14th , 2003 with location yet to be determined.


6. Meeting Schedule for the Year

Monthly meetings, mainly teleconference or VTC but a minimum of two
face-to-face meetings


7. Chair

Terry Leahy, Wells Fargo leahyt@wellsfargo.com


8. Proposal Sponsors

Terry Leahy, Wells Fargo, leahyt@wellsfargo.com

Jeff Stapleton, KPMG LLP, jstapleton@kpmg.com

Peter Doyle, Baltimore Technologies, pdoyle@baltimore.com

Derek Brink, RSA Security Inc., dbrink@rsasecurity.com

John Sabo, Computer Associates, john.t.sabo@ca.com

Patrick Kanaishi, Neucom Corporation, gen@neucom.co.jp