IETF-95 Proceedings

Introduction  |  Area, Working Goup & BoF Reports  |  Plenaries  |  Training  |  Internet Research Task Force

Some PKIX and SMIME (spasm) (WG)

Minutes   |   Jabber Logs  |   Mailing List Archives

Additional information is available at tools.ietf.org/wg/spasm

Chair(s):

Security Area Area Director(s):

Assigned Area Director



Recordings:

No Recordings Present

Meeting Slides:

No Slides Present

No Current Internet-Drafts

No Request for Comments

Charter (as of 2016-05-14):


The PKIX and S/MIME Working Groups have been closed for some time. Some
updates have been proposed to the X.509 certificate documents produced by the
PKIX Working Group and the electronic mail security documents produced by the
S/MIME Working Group.

The Some PKIX and S/MIME (SPASM) Working Group is chartered to make updates
where there is a known constituency interested in real deployment and there is
at least one sufficiently well specified approach to the update so that the
working group can sensibly evaluate whether to adopt a proposal. The current
charter encompasses updates to satisfy the following needs:

1. Specify the way to include an i18n email address as a subject
alternative name and an issuer alternative name.
draft-lbaudoin-iema and draft-ietf-pkix-eai-addresses are
proposals in this space.

2. Specify the processing for the Extended Key Usage certificate
extension when it appears in the certificate of an intermediate
certification authority. draft-housley-spasm-eku-constraints
is a proposal in this space.

3. Specify the way to use authenticated encryption in S/MIME.
draft-schaad-rfc5751-bis is a proposal in this space.

4. Using a DNS SRV record to locate an X.509 certificate store.
draft-bhjl-x509-srv is a proposal in this space.

In addition, the SPASM Working Group may investigate other updates to the
documents produced by the PKIX and S/MIME Working Groups, but the SPASM Working
Group shall not adopt any of these potential work items without rechartering.
No such re-chartering is envisaged until one or more of the above work items have
been successfully delivered to the RFC editor queue.