[Uta] RFC 8460 on SMTP TLS Reporting

rfc-editor@rfc-editor.org Wed, 26 September 2018 16:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D72EA12958B; Wed, 26 Sep 2018 09:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6yDBAmKtTEd7; Wed, 26 Sep 2018 09:52:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96653130FB1; Wed, 26 Sep 2018 09:52:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D99E4B81209; Wed, 26 Sep 2018 09:52:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, uta@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180926165217.D99E4B81209@rfc-editor.org>
Date: Wed, 26 Sep 2018 09:52:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/vY8lVKTiivGEU-gIzdHggS6Mnuc>
Subject: [Uta] RFC 8460 on SMTP TLS Reporting
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Sep 2018 16:52:37 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8460

        Title:      SMTP TLS Reporting 
        Author:     D. Margolis, 
                    A. Brotman,
                    B. Ramakrishnan,
                    J. Jones,
                    M. Risher
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2018
        Mailbox:    dmargolis@google.com, 
                    alex_brotman@comcast.com, 
                    prbinu@yahoo.com,
                    janet.jones@microsoft.com, 
                    risher@google.com
        Pages:      34
        Characters: 67126
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-uta-smtp-tlsrpt-23.txt

        URL:        https://www.rfc-editor.org/info/rfc8460

        DOI:        10.17487/RFC8460

A number of protocols exist for establishing encrypted channels
between SMTP Mail Transfer Agents (MTAs), including STARTTLS, DNS-
Based Authentication of Named Entities (DANE) TLSA, and MTA Strict
Transport Security (MTA-STS).  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 attacks and diagnose
unintentional misconfigurations.

This document is a product of the Using TLS in Applications Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC