Re: [Uta] Adoption call for draft-lvelvindron-tls-for-email-02

Patrick Mevzek <mevzek@uniregistry.com> Thu, 08 November 2018 21:23 UTC

Return-Path: <mevzek@uniregistry.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 BD3B712D7F8 for <uta@ietfa.amsl.com>; Thu, 8 Nov 2018 13:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uniregistry.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 dJFXFqxVyaNF for <uta@ietfa.amsl.com>; Thu, 8 Nov 2018 13:23:06 -0800 (PST)
Received: from a.mx.uniregistry.net (a.mx.uniregistry.net [64.96.177.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 899C712D4E8 for <uta@ietf.org>; Thu, 8 Nov 2018 13:23:06 -0800 (PST)
Abuse: Forward to abuse@uniregistry.com with full headers
X-Virus-Scanned: Content filter at a.mx.uniregistry.net
Powered-By: https://www.uniregistry.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uniregistry.com; s=bravo; t=1541712185; bh=pZz8Xu28oxqQp+rdEaoCodHVyBzsC+sb109+MQber3o=; h=Subject:To:References:From:Date:In-Reply-To; b=BsI6rwN/OqHExYqcjiT/gFSFgjX9WsoSl+L1IkbR/9vksz3UQVDP8RL3VkiH24hR1 P8kqaueSm9ZVC1ipn6k8ym0dI858PT7SYNDaZwIRWM1Su+X5zMfbvd3wXTNiSmS4A+ 4YzT8RbynTrGh8CxCUdzowWdnSyEtR5d2YPmpTmNlIjYi856+TxNHGlWnmelmNEmVv 73BuqQxJqm+9HP02PEPCxHwoziy7tE2HgBnvOZc+ESsrHpI3wRGiVRkMU3MDzCpcv4 Gjy25lTvpctHyaK9r/wEHv3ECyLa7yVO9AmZHYIYCgJdrH4wDVHDInSIWu6ro09czA riEQHBeaNZ92g==
Received: from PatrickM.local ([66.54.123.66]) (authenticated bits=0) by a.mx.uniregistry.net (8.15.2/8.15.2/Debian-8) with ESMTPSA id wA8LN42g043629 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 8 Nov 2018 21:23:05 GMT
To: uta@ietf.org
References: <034501d47727$50e4d170$f2ae7450$@smyslov.net>
From: Patrick Mevzek <mevzek@uniregistry.com>
Organization: Uniregistry
Message-ID: <902c3653-e95e-8d9a-daf8-a81c6589f3ae@uniregistry.com>
Date: Thu, 08 Nov 2018 16:23:02 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <034501d47727$50e4d170$f2ae7450$@smyslov.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/-y0Hm3OySCNhKc7eyBn_7yHq0lM>
Subject: Re: [Uta] Adoption call for draft-lvelvindron-tls-for-email-02
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: Thu, 08 Nov 2018 21:23:08 -0000

On 2018-11-08 00:52 -0500, Valery Smyslov wrote:> the chairs received a 
request for adoption of> draft-lvelvindron-tls-for-email-02 [1] as UTA 
WG document.> The draft seems to be in scope of UTA WG and follows the 
IETF trend to> deprecate using insecure protocols.

In the TLS WG there is indeed 
draft-ietf-tls-oldversions-deprecate-01.txt floating around, whose 
abstract starts with:
This document, if approved, formally deprecates Transport Layer
    Security (TLS) versions 1.0 [RFC2246] and 1.1 [RFC4346] and moves
    these documents to the historic state


It has a long list of RFCs it updates due to the above, but 8314 is not 
among its list of RFCs.

HTH,

-- 
Patrick Mevzek