[Uta] FW: RFC 7817 on Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols

"Orit Levin (CELA)" <oritl@microsoft.com> Thu, 24 March 2016 22:47 UTC

Return-Path: <oritl@microsoft.com>
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 10FA712D97B for <uta@ietfa.amsl.com>; Thu, 24 Mar 2016 15:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 IGjtrU7y5b6s for <uta@ietfa.amsl.com>; Thu, 24 Mar 2016 15:47:45 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0732.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::732]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5160E12D937 for <uta@ietf.org>; Thu, 24 Mar 2016 15:47:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2Mb75zS8lDBilzbOIKDw/WJyURFEAq6okHS+GJqNW4s=; b=oLcQmmuJnfEOgl21nLCC6cqk17vjLjKz5i1fEsBhO2NB8msGCfVw3Zb5hqLqKeIvKz1GV3US5M9LtU4EU/8j9Ngz8nrEPZG8GKWeXC2BBn0uxzWUd+Tuxqva+U6CrJncSiVaR4yA6MZLSvyO/jp6bdZQ/W4FjGosKDndw9UObdM=
Received: from BN3PR0301MB0867.namprd03.prod.outlook.com (10.160.155.141) by BN3PR0301MB0867.namprd03.prod.outlook.com (10.160.155.141) with Microsoft SMTP Server (TLS) id 15.1.443.12; Thu, 24 Mar 2016 22:47:25 +0000
Received: from BN3PR0301MB0867.namprd03.prod.outlook.com ([10.160.155.141]) by BN3PR0301MB0867.namprd03.prod.outlook.com ([10.160.155.141]) with mapi id 15.01.0443.015; Thu, 24 Mar 2016 22:47:25 +0000
From: "Orit Levin (CELA)" <oritl@microsoft.com>
To: "uta@ietf.org" <uta@ietf.org>
Thread-Topic: RFC 7817 on Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols
Thread-Index: AQHRhh6pmINqY1WvhEy/hz0eQLsOyZ9pMgXA
Date: Thu, 24 Mar 2016 22:47:25 +0000
Message-ID: <BN3PR0301MB0867BBB1A29C585AE6ABEB9DAD820@BN3PR0301MB0867.namprd03.prod.outlook.com>
References: <20160324224314.BFA85180092@rfc-editor.org>
In-Reply-To: <20160324224314.BFA85180092@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:5::21e]
x-ms-office365-filtering-correlation-id: 7a9961ce-c844-49da-b748-08d35436453c
x-microsoft-exchange-diagnostics: 1; BN3PR0301MB0867; 5:Bex9B5yqjDSI564l7agf2rvkUcZobdN7/RbG7STCshY30mCks4TyOZZcyVf96VrRW24zXPXYPc0p0nSlVonw5DTFVaE10nHJVBInyhOundr7XTPhMibh6va6gaq1Vn9C8si16bl+YERVzSHf0yMyzw==; 24:HJy2yfF2sbvwIPZ9ODxt8JU7x5Ol5GRrKRgOIbg5iBvnOi6YTuX3lrPjzJsfiMkZtgG79/g+idyU21q7hXf3p5ZddW/7m7xeoE4rLPv+7WE=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN3PR0301MB0867;
x-microsoft-antispam-prvs: <BN3PR0301MB0867D3A04CA8B10D9195947FAD820@BN3PR0301MB0867.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(61426038)(61427038); SRVR:BN3PR0301MB0867; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0301MB0867;
x-forefront-prvs: 0891BC3F3D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(13464003)(15650500001)(2420400007)(2501003)(87936001)(110136002)(189998001)(5004730100002)(33656002)(2906002)(7110500001)(19580395003)(19580405001)(5002640100001)(10090500001)(10400500002)(3660700001)(76576001)(5005710100001)(3280700002)(107886002)(10290500002)(5003600100002)(92566002)(5640700001)(1220700001)(102836003)(2900100001)(6116002)(122556002)(1096002)(74316001)(586003)(2950100001)(106116001)(77096005)(81166005)(5008740100001)(1730700002)(11100500001)(15975445007)(2351001)(76176999)(54356999)(450100001)(50986999)(86362001)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0301MB0867; H:BN3PR0301MB0867.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Mar 2016 22:47:25.4383 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0301MB0867
Archived-At: <http://mailarchive.ietf.org/arch/msg/uta/ACfDTTcCPrJzwWz0ixhFiGgUkVU>
Subject: [Uta] FW: RFC 7817 on Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 24 Mar 2016 22:47:48 -0000


-----Original Message-----
From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org] 
Sent: Thursday, March 24, 2016 3:43 PM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: rfc-editor@rfc-editor.org; uta@ietf.org
Subject: RFC 7817 on Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols

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