Deployable Enhanced Email Privacy (DEEP)
draft-ietf-uta-email-deep-00

The information below is for an old version of the document
Document Type Active Internet-Draft (uta WG)
Last updated 2015-02-13
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           K. Moore
Internet-Draft                                          Network Heretics
Updates: 1939, 3464, 3501, 5068, 6186                          C. Newman
         (if approved)                                            Oracle
Intended status: Standards Track                       February 13, 2015
Expires: August 17, 2015

                Deployable Enhanced Email Privacy (DEEP)
                    draft-ietf-uta-email-deep-00.txt

Abstract

   This specification defines a set of requirements and facilities
   designed to improve email privacy.  This provides mechanisms intended
   to increase use of already deployed Transport Layer Security (TLS)
   technology, provide a model for mail user agent's confidentiality
   assurance, and enable mail service providers to advertise improved
   TLS privacy facilities.

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 17, 2015.

Copyright Notice

   Copyright (c) 2015 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

Moore & Newman           Expires August 17, 2015                [Page 1]
Internet-Draft  Deployable Enhanced Email Privacy (DEEP)   February 2015

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Terminology Used in This Document . . . . . .   4
   3.  Mail Account Confidentiality Assurance Level  . . . . . . . .   4
     3.1.  High Confidentiality Assurance  . . . . . . . . . . . . .   5
     3.2.  Certificate Pinning . . . . . . . . . . . . . . . . . . .   6
     3.3.  No Confidentiality Assurance  . . . . . . . . . . . . . .   6
     3.4.  Other Confidentiality Assurance Levels  . . . . . . . . .   6
   4.  Implicit TLS  . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Implicit TLS for POP  . . . . . . . . . . . . . . . . . .   7
     4.2.  Implicit TLS for IMAP . . . . . . . . . . . . . . . . . .   7
     4.3.  Implicit TLS for SMTP Submission  . . . . . . . . . . . .   8
     4.4.  Implicit TLS Connection Closure for POP, IMAP and SMTP  .   8
   5.  Email Security Upgrading Using Security Latches . . . . . . .   8
     5.1.  Email Security Tags . . . . . . . . . . . . . . . . . . .   9
     5.2.  Initial Set of Email Security Tags  . . . . . . . . . . .  10
     5.3.  Server DEEP Status  . . . . . . . . . . . . . . . . . . .  10
     5.4.  Email Security Tag Latch Failures . . . . . . . . . . . .  10
   6.  Recording TLS Cipher Suite in Received Header . . . . . . . .  11
   7.  Extensions for DEEP Status and Reporting  . . . . . . . . . .  11
     7.1.  IMAP DEEP Extension . . . . . . . . . . . . . . . . . . .  12
     7.2.  POP DEEP Extension  . . . . . . . . . . . . . . . . . . .  14
     7.3.  SMTP DEEP Extension . . . . . . . . . . . . . . . . . . .  15
     7.4.  SMTP Error Extension  . . . . . . . . . . . . . . . . . .  16
   8.  Use of SRV records in Establishing Configuration  . . . . . .  16
   9.  Implementation Requirements . . . . . . . . . . . . . . . . .  17
     9.1.  All Implementations (Client and Server) . . . . . . . . .  17
       9.1.1.  Client Certificate Authentication . . . . . . . . . .  18
     9.2.  Mail Server Implementation Requirements . . . . . . . . .  18
     9.3.  Mail User Agent Implementation Requirements . . . . . . .  19
     9.4.  Non-configurable MUAs and nonstandard access protocols  .  20
     9.5.  DEEP Compliance for Anti-Virus/Anti-Spam Software and
           Services  . . . . . . . . . . . . . . . . . . . . . . . .  20
   10. Mail Service Provider Requirements  . . . . . . . . . . . . .  20
     10.1.  Server Requirements  . . . . . . . . . . . . . . . . . .  20
     10.2.  MSPs MUST provide Submission Servers . . . . . . . . . .  20
Show full document text