RFC 7817 on Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols
rfc-editor@rfc-editor.org Thu, 24 March 2016 22:43 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 6556612D965; Thu, 24 Mar 2016 15:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 OIch4mYGFoxR; Thu, 24 Mar 2016 15:43:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0C3E12D87E; Thu, 24 Mar 2016 15:43:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BFA85180092; Thu, 24 Mar 2016 15:43:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7817 on Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160324224314.BFA85180092@rfc-editor.org>
Date: Thu, 24 Mar 2016 15:43:14 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/q3vEe3X57l4WZ3DiWGIxW8z3R0s>
Cc: uta@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Thu, 24 Mar 2016 22:43:30 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7817
Title: Updated Transport Layer Security (TLS)
Server Identity Check Procedure for Email-Related
Protocols
Author: A. Melnikov
Status: Standards Track
Stream: IETF
Date: March 2016
Mailbox: alexey.melnikov@isode.com
Pages: 13
Characters: 29855
Updates: RFC 2595, RFC 3207, RFC 3501, RFC 5804
I-D Tag: draft-ietf-uta-email-tls-certs-09.txt
URL: https://www.rfc-editor.org/info/rfc7817
DOI: http://dx.doi.org/10.17487/RFC7817
This document describes the Transport Layer Security (TLS) server
identity verification procedure for SMTP Submission, IMAP, POP, and
ManageSieve clients. It replaces Section 2.4 (Server Identity Check)
of RFC 2595 and updates Section 4.1 (Processing After the STARTTLS
Command) of RFC 3207, Section 11.1 (STARTTLS Security Considerations)
of RFC 3501, and Section 2.2.1 (Server Identity Check) of RFC 5804.
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