MSA and MTA S/MIME signing & encryption
draft-melnikov-smime-msa-to-mda-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in sec area)
Last updated 2014-02-05 (latest revision 2014-01-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
IESG IESG state In Last Call
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 - Review Needed
IANA action state None
Network Working Group                                         W. Ottaway
Internet-Draft                                                   QinetiQ
Intended status: Standards Track                        A. Melnikov, Ed.
Expires: July 18, 2014                                         Isode Ltd
                                                        January 14, 2014

                MSA and MTA S/MIME signing & encryption
                   draft-melnikov-smime-msa-to-mda-02

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).

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 July 18, 2014.

Copyright Notice

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

   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.

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   4
     2.1.  Domain Signature  . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Domain Encryption and Decryption  . . . . . . . . . . . .   5
     2.3.  Signature Encapsulation . . . . . . . . . . . . . . . . .   5
     2.4.  Naming Conventions  . . . . . . . . . . . . . . . . . . .   6
   3.  MSA/MTA S/MIME signing  . . . . . . . . . . . . . . . . . . .   7
     3.1.  Naming Conventions and Signature Types  . . . . . . . . .   7
       3.1.1.  Signature Type Attribute  . . . . . . . . . . . . . .   8
     3.2.  Domain Signature Generation and Verification  . . . . . .   9
   4.  MSA-to-MDA S/MIME Encryption and Decryption . . . . . . . . .  10
     4.1.  Key Management for DCA Encryption . . . . . . . . . . . .  11
     4.2.  Key Management for DCA Decryption . . . . . . . . . . . .  12
   5.  Applying a Domain Signature when Mail List Agents are Present  12
     5.1.  Examples of Rule Processing . . . . . . . . . . . . . . .  15
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  18
   Appendix A.  Changes from RFC 3183  . . . . . . . . . . . . . . .  20
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   The S/MIME [RFC5750][RFC5751] series of standards define a data
   encapsulation format for the provision of a number of security
   services including data integrity, confidentiality, and
   authentication.  S/MIME is designed for use by messaging clients to
   deliver security services to distributed messaging applications.

   The mechanisms described in this document are designed to solve a
   number of interoperability problems and technical limitations that
   arise when different security domains wish to communicate securely,
   for example when two domains use incompatible messaging technologies
   such as the X.400 series and SMTP/MIME [RFC5322], or when a single
   domain wishes to communicate securely with one of its members
   residing on an untrusted domain.  The main scenario covered by this
   document is domain-to-domain, although it is also applicable to
   individual-to-domain and domain-to-individual communications.  This
   document is also applicable to organizations and enterprises that
   have internal PKIs which are not accessible by the outside world, but
Show full document text