Hi, During chartering we got a comment that the proposed name of this WG might be considered insensitive. We don't need to have a discussion about that, as it makes little difference otherwise, but we will be changing the name of the proposed working group to: lamps - Limited Additional Mechanisms for PKIX and SMIME Thanks to Michael Jenkins for the suggestion on the current WG mailing list. [1] The secretariat will handle migrating the mailing list in the coming weeks, and the IETF96 agenda will be updated accordingly, assuming that the IESG approve the new working group on the telechat tomorrow. If approved, the announcement of the working group will use the new name, "lamps." There are no other substantive changes to the draft charter. [2] Thanks, S. [1] https://mailarchive.ietf.org/arch/msg/spasm/t4f5LKRJILn0KsLQdzA1fo8B1lM [2] https://datatracker.ietf.org/doc/charter-ietf-spasm/ On 17/06/16 17:33, The IESG wrote: > A new IETF WG has been proposed in the Security Area. The IESG has not > made any determination yet. The following draft charter was submitted, > and is provided for informational purposes only. Please send your > comments to the IESG mailing list (iesg@xxxxxxxx) by 2016-06-27. > > Some PKIX and SMIME (spasm) > ----------------------------------------------------------------------- > Current status: Proposed WG > > Chairs: > TBD > > Assigned Area Director: > Stephen Farrell <stephen.farrell@xxxxxxxxx> > > Security Area Directors: > Stephen Farrell <stephen.farrell@xxxxxxxxx> > Kathleen Moriarty <Kathleen.Moriarty.ietf@xxxxxxxxx> > > Mailing list: > Address: spasm@xxxxxxxx > To subscribe: https://www.ietf.org/mailman/listinfo/spasm > Archive: https://www.ietf.org/mail-archive/web/spasm/ > > Charter: https://datatracker.ietf.org/doc/charter-ietf-spasm/ > > > 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 SPASM (Some PKIX and S/MIME) 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-melnikov-spasm-eai-addresses is a proposal in this space. > > 2. Specify the way to use authenticated encryption in S/MIME. > draft-schaad-rfc5751-bis 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. > > Milestones: > > TBD > > _______________________________________________ > Spasm mailing list > Spasm@xxxxxxxx > https://www.ietf.org/mailman/listinfo/spasm >
<<attachment: smime.p7s>>