RFC 8997 on Deprecation of TLS 1.1 for Email Submission and Access

rfc-editor@rfc-editor.org Tue, 23 March 2021 17:51 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C075D3A0EB2; Tue, 23 Mar 2021 10:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 58710kY6ZyXt; Tue, 23 Mar 2021 10:51:01 -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 C63B83A0E18; Tue, 23 Mar 2021 10:51:01 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6FB6AF40723; Tue, 23 Mar 2021 10:50:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg5OTcgb24gRGVwcmVjYXRpb24gb2YgVExTIDEuMSBmb3IgRW1haWwgU3VibWlzc2lvbiBhbmQgQWNjZXNz?=
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: <20210323175057.6FB6AF40723@rfc-editor.org>
Date: Tue, 23 Mar 2021 10:50:57 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/GGb94E77Boes9UWUjunO3CIhH70>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2021 17:51:11 -0000

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

        
        RFC 8997

        Title:      Deprecation of TLS 1.1 for 
                    Email Submission and Access 
        Author:     L. Velvindron,
                    S. Farrell
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2021
        Mailbox:    logan@cyberstorm.mu,
                    stephen.farrell@cs.tcd.ie
        Pages:      6
        Updates:    RFC 8314

        I-D Tag:    draft-ietf-uta-tls-for-email-05.txt

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

        DOI:        10.17487/RFC8997

This specification updates the current recommendation for the use of
the Transport Layer Security (TLS) protocol to provide
confidentiality of email between a Mail User Agent (MUA) and a Mail
Submission Server or Mail Access Server. This document updates RFC
8314.

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