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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in sec area)
Last updated 2014-03-05 (latest revision 2014-02-14)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Alan Ross
Shepherd write-up Show (last changed 2014-02-12)
IESG IESG state Waiting for Writeup
Consensus Boilerplate Unknown
Telechat date
Responsible AD Sean Turner
Send notices to alexey.melnikov@isode.com, wjottaway@qinetiq.com, draft-melnikov-smime-msa-to-mda@tools.ietf.org, smime@ietf.org, stephen.farrell@cs.tcd.ie
IANA IANA review state IANA - Not OK
IANA action state None
Network Working Group                                         W. Ottaway
Internet-Draft                                                   QinetiQ
Intended status: Standards Track                        A. Melnikov, Ed.
Expires: August 18, 2014                                       Isode Ltd
                                                       February 14, 2014

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

Abstract

   The S/MIME protocols Message Specification (RFC 5751), Cryptographic
   Message Syntax (RFC 5652), S/MIME Certificate Handling (RFC 5750) and
   Enhanced Security Services for S/MIME (RFC 2634) specify a consistent
   way to securely send and receive MIME messages providing end to end
   integrity, authentication, non-repudiation and confidentiality.  This
   document identifies a number of interoperability, technical,
   procedural and policy related issues that may result in end-to-end
   security services not being achievable.  To resolve such issues, this
   document profiles domain-based signing and encryption using S/MIME,
   such as specifying 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).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 18, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Ottaway & Melnikov       Expires August 18, 2014                [Page 1]
Internet-Draft              MSA-to-MDA S/MIME              February 2014

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   4
     2.1.  Domain Signature  . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Review Signature  . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Additional Attributes Signature . . . . . . . . . . . . .   6
     2.4.  Domain Encryption and Decryption  . . . . . . . . . . . .   6
     2.5.  Signature Encapsulation . . . . . . . . . . . . . . . . .   6
     2.6.  Naming Conventions  . . . . . . . . . . . . . . . . . . .   7
   3.  Domain-Based S/MIME Signing . . . . . . . . . . . . . . . . .   8
     3.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  Signature Type Attribute  . . . . . . . . . . . . . . . .   9
     3.3.  Domain Signature Generation and Verification  . . . . . .  10
     3.4.  Additional Attributes Signature Generation and
           Verification  . . . . . . . . . . . . . . . . . . . . . .  12
     3.5.  Review Signature Generation and Verification  . . . . . .  12
     3.6.  Originator Signature  . . . . . . . . . . . . . . . . . .  13
   4.  Domain-based S/MIME Encryption and Decryption . . . . . . . .  13
     4.1.  Key Management for DCA Encryption . . . . . . . . . . . .  14
     4.2.  Key Management for DCA Decryption . . . . . . . . . . . .  15
   5.  Applying a Domain Signature when Mail List Agents are Present  15
     5.1.  Examples of Rule Processing . . . . . . . . . . . . . . .  18
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
     6.1.  SMTP URI registration . . . . . . . . . . . . . . . . . .  20
     6.2.  SUBMIT URI registration . . . . . . . . . . . . . . . . .  21
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  22
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  23
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  23
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  23
   Appendix A.  Changes from RFC 3183  . . . . . . . . . . . . . . .  25
Show full document text