The IESG's Protocol Action announcement for MOSS and security multiparts is now
2-1/2 months old, and yet neither of these documents has been published as an
RFC. It hasn't taken nearly this long for other recent standards, I think.
Does anyone know what the problem is? I'd hate to think that it has anything to
do with this S/MIME business ...
- RL "Bob" Morgan
ITSS/DCCS
Stanford University
---
Subject: Protocol Action: MIME Object Security Services to Proposed
Standard
From: The IESG <iesg-secretary(_at_)cnri(_dot_)reston(_dot_)va(_dot_)us>
To: IETF-Announce:;, tis(_dot_)com(_at_)TIS(_dot_)COM
CC: RFC Editor <rfc-editor(_at_)isi(_dot_)edu>
Date: Sat, 08 Jul 95 15:03:57 -0400
The IESG has approved the following two Internet-Drafts as Proposed
Standards:
1. MIME Object Security Services <draft-ietf-pem-mime-08.txt>
2. Security Multiparts for MIME: Multipart/Signed and
Multipart/Encrypted
<draft-ietf-pem-sigenc-03.txt>
These documents are the product of the Privacy-Enhanced Electronic Mail
Working Group. The IESG contact person is Jeffrey Schiller.