
From wwwrun@core3.amsl.com  Tue Oct 12 14:29:48 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: smime@ietf.org
Delivered-To: smime@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 600AC3A6A9F; Tue, 12 Oct 2010 14:29:48 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20101012212948.600AC3A6A9F@core3.amsl.com>
Date: Tue, 12 Oct 2010 14:29:48 -0700 (PDT)
Cc: paul.hoffman@vpnc.org, smime@ietf.org
Subject: [smime] WG Action: Conclusion of S/MIME Mail Security (smime)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 21:29:48 -0000

The S/MIME Mail Security (smime) working group in the Security Area has
concluded. The IESG contact persons are Tim Polk and Sean Turner.

The smime working group has completed its charter items, and is
officially closing. The mailing list will be retained for future
discussions involving s/mime and the cryptographic message syntax.

The smime working group was primarily focused on the Secure Mime Version
3 and supporting syntax/encoding documents. The working group published
fifty two RFCs, including the Cryptographic Message Syntax (RFC 5652), and
the Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2
message handling and Certificate handling specifications Specification
(RFCs 5751 and 5750). I would like to note that 5652 is a full standard,
which is a rare accomplishment.

A further indication of the wg's success are the many IETF publications
that reference smime RFCs. They are too numerous to list, but IETF working
groups that have built upon smime publications include sip, pkix, and
sidr.

I would like to thank all of the IETF participants who have contributed
to the various documents produced by the smime working group and to the
successful completion of these important deliverables. We especially thank
Russ Housley, Sean Turner, Blake Ramsdell, and Paul Hoffman who have
chaired the working group at various times since its formation, and the
many document editors.

I would also like to recognize RSA Laboratories, which contributed the
original base specifications and transferred change control to the IETF.
The RFCs 2311, 2312, and 2315 document RSA's contributions.

The smime mailing list will remain open and the list archive will be
retained.

-Tim Polk

From paul.hoffman@vpnc.org  Mon Oct 25 12:36:45 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: smime@core3.amsl.com
Delivered-To: smime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EE323A67B3 for <smime@core3.amsl.com>; Mon, 25 Oct 2010 12:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.417
X-Spam-Level: 
X-Spam-Status: No, score=-101.417 tagged_above=-999 required=5 tests=[AWL=0.629, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ncrN-kAEhuXl for <smime@core3.amsl.com>; Mon, 25 Oct 2010 12:36:43 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 8E0733A67AD for <smime@ietf.org>; Mon, 25 Oct 2010 12:36:43 -0700 (PDT)
Received: from [10.20.30.150] (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9PJcRrd017576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <smime@ietf.org>; Mon, 25 Oct 2010 12:38:28 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240856c8eb8d0c1aad@[10.20.30.150]>
Date: Mon, 25 Oct 2010 12:38:26 -0700
To: smime@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [smime] Fwd: UPDATED Document Action: 'Certified Electronic Mail' to Informational RFC
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 19:36:45 -0000

Of interest to this no-longer-WG:

>The IESG has approved the following document:
>- 'Certified Electronic Mail'
>  <draft-gennai-smime-cnipa-pec-08.txt> as an Informational RFC
>
>This document has been reviewed in the IETF but is not the product of an
>IETF Working Group.
>
>The IESG contact person is Tim Polk.
>
>A URL of this Internet Draft is:
>https://datatracker.ietf.org/doc/draft-gennai-smime-cnipa-pec/
>
>Technical Summary
>
>Posta Elettronica Certificata (PEC) defines an official electronic
>delivery service analogous to the postal service's registered mail with
>return receipt.  Originators use an unaltered User Agent (UA) to submit
>emails to a PEC provider who performs checks  (e.g., formatting, virus)
>on the message and then returns an acceptance receipt to the originator.
>After returning the acceptance receipt the PEC provider, the PEC
>provider generates the signed "transport message" that includes the
>original message and certification data (e.g., date and time of
>dispatch, sender email address, recipient(s) email address(es), subject,
>and message ID) and sends it to the recipient's PEC provider.  Upon
>receipt of the transport message, the recipient's PEC provider returns a
>signed  take charge receipt, which also includes certification data, to
>the originator's PEC provider indicating that the recipient's PEC
>provider has agreed to deliver the message.  The recipient's PEC
>provider then delivers the message to the recipients mailbox.  After
>successful delivery, the recipient's PEC provider returns a signed
>delivery notification to the originator.  Both terse and verbose
>responses are supported as well as error conditions.  The above system
>also relies on an PEC Direcotry (LDAP-based) to store certificates and
>CRLs, which are checked during signature verifications by the originator
>and recipient PEC providers.
>
>Working Group Summary
>
>The PEC concept was pitched to the SMIME WG at IETF 71.  Numerous
>questions were asked and answered to the satisfaction of the WG.  The WG
>did not adopt the PEC ID as a WG item not due to lack of interest, but
>due to lack of man power (SMIME is not very active at this point). The
>WG did agree to discuss it on the mailing list.  Reviews, comments, and
>revisions were posted on the mailing list.
>
>Document Quality
>
>This document has already been implemented by the following vendors:
>Tmail, OpenPec, In Rete PEC, Microsoft, Critical Path, Babel,
>InnovaPuglia, and Infocert.  In addition, the vendors undergo
>interoperability testing amongst each other to ensure they have properly
>implemented PEC.
>
>Note that the SMTP header fields use Italian as opposed to English.  The
>Shepherd assumed that this was acceptable from a standardization
>perspective.  An Italian-to-English translation is provided in an
>Appendix.
>
>Personnel
>
>Sean Turner is the document Shepherd.  Tim Polk is the sponsoring AD.
>
>RFC Editor Note
>
>There was an IETF Last Call for this document, but the result shows that
>there is not IETF Consensus for the content of this document.
>
>Please change the title of the document to:
>La Posta Elettronica Certificata - Italian Certified Electronic Mail
>
>Please change the Introduction as follows:
>
>OLD:
>
>Since 1997, the Italian Laws have recognized electronic delivery
>systems as legally usable. In 2005 after two years of technical
>tests, the characteristics of an official electronic delivery
>service, named certified electronic mail (in Italian Posta
>Elettronica Certificata, from now on "PEC") were defined, giving
>the system legal standing.
>This document represents the English version of the Italian
>specfications, (http://www.cnipa.gov.it/site/_files/Pec-def.pdf)
>which will be the ultimate PEC reference.
>
>Since this specification describes existing deployment and
>implementation, some issues identified by the community were
>determined to be out of scope. However, these issues would
>need to be addressed before a successor to this document could
>be be published as a standards track document.
>
>In particular, a standards track document would need to include:
>
>* A clear statement of the requirements/goals that need to be
>satisfied by the protocol;
>
>* A comprehensive diagram and description of the overall message
>flow and delivery sequence required to achieve the requirements;
>
>* Alignment with traditional IETF email and security terminology;
>and
>
>* Review of prior art, and a comparison with the proposed standards
>track solution.
>
>NEW:
>
>Since 1997, the Italian Laws have recognized electronic delivery
>systems as legally usable. In 2005 after two years of technical
>tests, the characteristics of an official electronic delivery
>service, named certified electronic mail (in Italian Posta
>Elettronica Certificata, from now on "PEC") were defined, giving
>the system legal standing.
>
>This document represents the English version of the Italian
>specifications (http://www.cnipa.gov.it/site/_files/Pec-def.pdf);
>the Italian version is the normative PEC reference.
>
>IETF review did not result in community consensus. Since this
>specification describes existing deployment and implementation,
>the issues identified by the IETF community have not been
>addressed in this document. However, these issues would need to
>be addressed before a successor to this document could be be
>published. At a minimum, the successor document would need to
>include:
>
>* A clear statement of the requirements/goals that need to be
>satisfied by the protocol;
>
>* A comprehensive diagram and description of the overall message
>flow and delivery sequence required to achieve the requirements;
>
>* Alignment with traditional terminology for IETF email and
>security; and
>
>* Review of prior art.

From paul.hoffman@vpnc.org  Fri Oct 29 19:14:20 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: smime@core3.amsl.com
Delivered-To: smime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2F643A6767 for <smime@core3.amsl.com>; Fri, 29 Oct 2010 19:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.448
X-Spam-Level: 
X-Spam-Status: No, score=-101.448 tagged_above=-999 required=5 tests=[AWL=0.598, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I+vcH9XDS-hZ for <smime@core3.amsl.com>; Fri, 29 Oct 2010 19:14:19 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id A58733A63D2 for <smime@ietf.org>; Fri, 29 Oct 2010 19:14:19 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9U2GEVI040004 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <smime@ietf.org>; Fri, 29 Oct 2010 19:16:15 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624082ec8f1302e74eb@[10.20.30.150]>
Date: Fri, 29 Oct 2010 19:15:52 -0700
To: smime@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [smime] Fwd: RFC 6025 on ASN.1 Translation
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Oct 2010 02:14:20 -0000

Of as much interest here as on PKIX.

--Paul Hoffman

>A new Request for Comments is now available in online RFC libraries.
>
>       
>        RFC 6025
>
>        Title:      ASN.1 Translation
>        Author:     C. Wallace, C. Gardiner
>        Status:     Informational
>        Stream:     IETF
>        Date:       October 2010
>        Mailbox:    cwallace@cygnacom.com,
>                    gardiner@bbn.com
>        Pages:      19
>        Characters: 39221
>        Updates/Obsoletes/SeeAlso:   None
>
>        I-D Tag:    draft-ietf-pkix-asn1-translation-03.txt
>
>        URL:        http://www.rfc-editor.org/rfc/rfc6025.txt
>
>Abstract Syntax Notation One (ASN.1) is widely used throughout the
>IETF Security Area and has been for many years.  Some specifications
>were written using a now deprecated version of ASN.1 and some were
>written using the current version of ASN.1.  Not all ASN.1 compilers
>support both older and current syntax.  This document is intended to
>provide guidance to specification authors and to implementers
>converting ASN.1 modules from one version of ASN.1 to another version
>without causing changes to the "bits on the wire".  This document
>does not provide a comprehensive tutorial of any version of ASN.1.
>Instead, it addresses ASN.1 features that are used in IETF Security
>Area specifications with a focus on items that vary with the ASN.1
>version.  This document is not an Internet Standards Track
>specification; it is published for informational purposes.
>
>This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.
>
>
>INFORMATIONAL: This memo provides information for the Internet community.
>It does not specify an Internet standard of any kind. Distribution of
>this memo is unlimited.
>
