Domain-based signing and encryption using S/MIME
draft-melnikov-smime-msa-to-mda-04

After consultation with one of the authors (Alexey), I'm marking this document as dead.  A revision might be submitted in the future.  In that case, the review process would have to restart from the beginning.

IESG/Authors/WG Chairs:

IANA has reviewed draft-melnikov-smime-msa-to-mda-02.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

IANA's reviewer has the following comments/questions:

IANA understands that, upon approval of this document, there is a single action which IANA must complete.

First, this document requests adding two URI schemes to the URI scheme registry located at:

http://www.iana.org/assignments/uri-schemes/

The two URI schemes to be added are:

smtp
submit

Currently the URI scheme registry is maintained through expert review as defined in RFC 5226. IANA is required to ask the designated expert to review this document.

IANA understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

1. Summary

The document shepherd is Alan Ross. The responsible Area Director is Sean Turner.

This document specifies how S/MIME signing and encryption can be applied between a Message Submission Agent (MSA) and a Message Delivery Agent (MDA) or between 2 Message Transfer Agents (MTA).

This document is an updated version of Experimental RFC 3183. This specification re-uses the concepts described in RFC 3183 for: Domain Signatures; and Domain Encryption and Decryption. The changes from RFC 3183 that have been incorporated in this specification have been declared in Appendix A.

There are several existing implementations of this document, so it is suitable for being published on Standard Track.

2. Review and Consensus

This is an individual submission based on an existing RFC.

This document was reviewed by several S/MIME experts.

There is at least one implementation of the document and several older implementations that are doing similar things (for example  and ).

3. Intellectual Property

Each author has confirmed conformance with BCP 78/79. There are no IPR disclosures on the document.

4. Other Points

A question was raised about the need to register "smtp" and "submit" URI schemes.

The "smtp" URI is in wide use and can be provisionally registered.

For example see  and

The IANA Considerations section might change if the "submit" and/or "smtp" URI scheme needs to be registered.

A question was raised about deprecating other signature types from RFC 3183 ("Review Signature" (Section 2.2 of RFC 3183) and "Additional Attributes Signature" (Section 2.3 of RFC 3183)). This was not the original intention of draft-melnikov-smime-msa-to-mda-02. An option may be to move them from RFC 3183 to draft-melnikov-smime-msa-to-mda-02.

In addition to this if these signature types or others are required for draft-melnikov-smime-msa-to-mda-02 it may make sense to obsolete RFC 3183.

The document needs an old boilerplate, as RFC 3183 used an old one. This can be fixed once IETF LC is over.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (MSA and MTA S/MIME signing & encryption) to Proposed Standard


The IESG has received a request from an individual submitter to consider
the following document:
- 'MSA and MTA S/MIME signing & encryption'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-03-05. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document specifies how S/MIME signing and encryption can be
  applied between a Message Submission Agent (MSA) and a Message
  Delivery Agent (MDA) or between 2 Message Transfer Agents (MTA).




The file can be obtained via
http://datatracker.ietf.org/doc/draft-melnikov-smime-msa-to-mda/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-melnikov-smime-msa-to-mda/ballot/


No IPR declarations have been submitted directly on this I-D.