Proposed update to smime charted

[Russ Housley <housley@vigilsec.com>]

I would like to clean up the charter of the S/MIME WG before passing the 
working group off to a new chair.  Attached is my proposed update.  Please 
let me know if you have any concerns with this proposal.

Russ


==========

S/MIME Mail Security (smime)

Chair:
     Russ Housley <housley@vigilsec.com>

Security Area Director:
     Steve Belovin <smb@research.att.com>
     Russ Housley <housley@vigilsec.com>

Mailing Lists:
     General Discussion: ietf-smime@imc.org
     To Subscribe:       ietf-smime-request@imc.org
     Archive:            http://www.imc.org/ietf-smime/

Description of Working Group:

The S/MIME Working Group has completed a series of Proposed
Standards that comprise the S/MIME version 3 specification.
Current efforts update and build upon these base specifications.

The Cryptographic Message Syntax (CMS) (RFC 3369) is cryptographic
algorithm independent, yet there is always more than one way to
use any algorithm.  To ensure interoperability, each algorithm
should have a specification that describes its use with CMS.
Specifications for the use of additional cryptographic algorithms
will be developed.

As part of the specification update, a new suite of "mandatory
to implement" algorithms will be selected.  These algorithms will
be reflected in updates to CERT and MSG (RFC 2632 and RFC 2633).
Building on the CMS CompressedData content type specified in
RFC 3274, the update to MSG will specify conventions for message
compression, in addition to message signature and encryption.

To aid implementers, documents containing example output for CMS
will be collected and published.  Some of the examples will include
structures and signed attributes defined in the Enhanced Security
Services (ESS) (RFC 2634) document.

CMS, and thus S/MIME version 3 and later, permit the use of
previously distributed symmetric key-encryption keys.  Specifications
for the distribution of symmetric key-encryption keys to multiple
message recipients will be developed.  Mail List Agents (MLAs) are
one user of symmetric key-encryption keys.  The specification will be
algorithm independent.

S/MIME version 3 and later, CMS is used to provide security to the
message content if an Internet mail message.  However, CMS can also
be employed in an X.400 electronic messaging envionments.
Specifications will be developed allowing this to be done in an
interoperable manner.

Perform necessary interoperability testing to progress the S/MIME
specifications to Draft Standard.  The CMS specification depends on
the RFC 3280, the PKIX certificate and CRL profile.  This profile
must progress to Draft Standard before CMS and the other S/MIME
specification can progress to Draft Standard.  Assuming timely
progress by the PKIX Working Group, the S/MIME specification can
start progressing to Draft Standard toward the end of 2003.


Goals and Milestones:

History:
     Submit CMS compressed data content type a Proposed Standard.
     Submit security label usage specification as Informational RFC.
     Submit elliptic curve algorithm specification as Informational RFC.
     Submit update to CMS as a Proposed Standard.
     Submit CMS Algorithms as a Proposed Standard.
     Submit AES key wrap algorithm description as Informational RFC.
     Last call on X.400 CMS wrapper specification.
     Last call on X.400 transport specification.
     Last call on HMAC key wrap description specification.
     Last call on RSA OAEP algorithm specification.
     Last call on AES algorithm specification.
     Last call on update to MSG.
     First draft of update to CERT.
     First draft of CMS and ESS examples document.
     First draft of S/MIME version 3.1 interoperability matrix.
     First draft of RSA PSS algorithm specification.

March 2003:
     Submit mail list key distribution as a Proposed Standard.
     Submit HMAC key wrap description as Proposed Standard.
     Submit RSA OAEP algorithm specification as a Proposed Standard.
     Sumbit AES algorithm specification as Proposed Standard.
     Submit X.400 CMS wrapper specification as a Proposed Standard.
     Submit X.400 transport as a Proposed Standard.
     Last call on CMS and ESS examples document.

April 2003:
     Sumbit update to CERT as Proposed Standard.
     Sumbit update to MSG as Proposed Standard.
     First draft of RSA KEM algorithm specification.

May 2003:
     Submit CMS and ESS examples document as Informational RFC.

June 2003:
     Last call on RSA PSS algorithm specification.

July 2003:
     Last call on RSA KEM algorithm specification.

September 2003:
     Submit RSA PSS algorithm specification as Proposed Standard.

October 2003:
     Submit RSA KEM algorithm specification as Proposed Standard.
     Final S/MIME version 3.1 interoperability matrix.

November 2003:
     Request advancement of CMS to Draft Standard.
     Request advancement of CMS Algorithms to Draft Standard.

December 2003:
     Request advancement of MSG to Draft Standard.
     Request advancement of CERT to Draft Standard.
     Request advancement of ESS to Draft Standard.