The recent release of the PEM RFCs prompted me to revise the "official"
PEM-DEV announcement, which I am attaching below, for your information.
-DB
-----
The PEM-DEV mailing list has been created for discussions related to
the development and deployment of Privacy Enhanced Mail (PEM) systems.
PEM is an IAB standards track protocol for the Internet community, and
is now a Proposed Standard Protocol.
PEM specifies protocol extensions and processing procedures for
cryptographic-based message encipherment and authentication for
electronic mail transferred using the Internet mail protocols. PEM
includes the specification of a supporting key management architecture
and infrastructure, based on public key certificates. The key
management architecure is compatible with the authentication framework
described in CCITT X.509, The Directory - Authentication Framework.
PEM is defined in a series of four documents:
RFC 1421: Privacy Enhancement for Internet Electronic Mail:
Part I: Message Encryption and Authentication Procedures
RFC 1422: Privacy Enhancement for Internet Electronic Mail:
Part II: Certificate-Based Key Management
RFC 1423: Privacy Enhancement for Internet Electronic Mail:
Part III: Algorithms, Modes, and Identifiers
RFC 1424: Privacy Enhancement for Internet Electronic Mail:
Part IV: Key Certification and Related Services
Various organizations are jointly developing RFC-compliant software for
deployment in the Internet in order to encourage the use and
development of RFC-based privacy enhanced mail systems.
The PEM-DEV mailing list is intended to cover a wide range of
discussion including:
o General discussion among the members of the Internet Engineering
Task Force (IETF) PEM Working Group.
o Issues related to the protocol extensions and message
processing procedures and the key management architecture and
infrastructure.
o Issues related to the development and deployment of privacy
enhanced mail systems, including technical issues, development
status, availability, etc.
Please send contributions to the list proper to "pem-dev(_at_)tis(_dot_)com".
Administrivia, e.g., additions to or deletions from the list, should be
sent to "pem-dev-request(_at_)tis(_dot_)com".
The archives are available by sending a message to
"pem-dev-request(_at_)tis(_dot_)com". The message must contain two fields, a
Subject field and a Reply-To field, which must be located and formatted
as described below:
(1) The Subject field of the message must be located in the headers of
the message, and must be formatted as follows:
Subject: get pem-dev archive volume VOL number NUM
where "VOL" is the volume number of the digest and "NUM" is the
number of that volume. Do NOT including leading zeroes. The
volume number changes when it is convenient for the maintainer, not
at specific intervals.
(2) The Reply-To field can be located either in the body or in the
headers of the message, and must be formatted as follows:
Reply-To: ADDRESS
where "ADDRESS" is your address AS IT WOULD LOOK TO MY HOST. I
will help you determine that address if you need it. If you place
the "reply-to" in the headers rather than the body, you must be
certain that it will be altered properly along the path to me so
that it reflects the proper return address.
The third of three volumes is currently under construction.
An index is available for each volume. It may be retrieved by
requesting number 0 of the desired volume. The index consists of a
collection of the subject lines of all messages in all the digests of
the requested volume, preceded by the digest number in which that
subject line appears.
-David Balenson <pem-dev-request(_at_)tis(_dot_)com>