SMTP TLS Reporting
draft-ietf-uta-smtp-tlsrpt-00

The information below is for an old version of the document
Document Type Active Internet-Draft (uta WG)
Last updated 2016-05-14
Replaces draft-brotman-smtp-tlsrpt
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
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)
Using TLS in Applications                                    D. Margolis
Internet-Draft                                               Google, Inc
Intended status: Standards Track                              A. Brotman
Expires: November 13, 2016                                  Comcast, Inc
                                                         B. Ramakrishnan
                                                             Yahoo!, Inc
                                                                J. Jones
                                                          Microsoft, Inc
                                                               M. Risher
                                                             Google, Inc
                                                            May 13, 2016

                           SMTP TLS Reporting
                     draft-ietf-uta-smtp-tlsrpt-00

Abstract

   A number of protocols exist for establishing encrypted channels
   between SMTP Mail Transfer Agents, including STARTTLS [RFC3207], DANE
   [RFC6698], and SMTP MTA STS (TODO: Add ref).  These protocols can
   fail due to misconfiguration or active attack, leading to undelivered
   messages or delivery over unencrypted or unauthenticated channels.
   This document describes a reporting mechanism and format by which
   sending systems can share statistics and specific information about
   potential failures with recipient domains.  Recipient domains can
   then use this information to both detect potential attackers and
   diagnose unintentional misconfigurations.

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 October 20, 2016.

Margolis, et al.        Expires October 20, 2016                [Page 1]
Internet-Draft                 SMTP-TLSRPT                    April 2016

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Related Technologies  . . . . . . . . . . . . . . . . . . . .   3
   3.  Reporting Policy  . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Example Reporting Policy  . . . . . . . . . . . . . . . .   4
       3.1.1.  Report using MAILTO . . . . . . . . . . . . . . . . .   4
       3.1.2.  Report using HTTPS  . . . . . . . . . . . . . . . . .   5
   4.  Reporting Schema  . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Result Types  . . . . . . . . . . . . . . . . . . . . . .   6
       4.1.1.  Success Type  . . . . . . . . . . . . . . . . . . . .   6
       4.1.2.  Routing Failures  . . . . . . . . . . . . . . . . . .   6
       4.1.3.  Negotiation Failures  . . . . . . . . . . . . . . . .   6
       4.1.4.  Policy Failures . . . . . . . . . . . . . . . . . . .   7
   5.  Report Delivery . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  Appendix 1: JSON Report Schema  . . . . . . . . . . . . . . .   8
   9.  Appendix 2: Example JSON Report . . . . . . . . . . . . . . .   9
   10. Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The STARTTLS extension to SMTP [RFC3207] allows SMTP clients and
   hosts to establish secure SMTP sessions over TLS.  The protocol
   design is based on "Opportunistic Security" (OS) [RFC7435], which
   provides interoperability for clients that do not support STARTTLS
   but means that any attacker who can delete parts of the SMTP session
Show full document text