IETF Logo Mail Archive

Re: [TLS] Last Call: <draft-ietf-tls-oldversions-deprecate-09.txt> (Deprecating TLSv1.0 and TLSv1.1) to Best Current Practice

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 28 November 2020 15:13 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23DDB3A109F for <tls@ietfa.amsl.com>; Sat, 28 Nov 2020 07:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 PBPS3NjLCuI4 for <tls@ietfa.amsl.com>; Sat, 28 Nov 2020 07:13:43 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D6273A109D for <tls@ietf.org>; Sat, 28 Nov 2020 07:13:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9022ABE2F; Sat, 28 Nov 2020 15:13:39 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ER9u871hpqfs; Sat, 28 Nov 2020 15:13:33 +0000 (GMT)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 6D6E0BE2E; Sat, 28 Nov 2020 15:13:33 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1606576413; bh=9m0MhUGajY+gKQPFRpBXckT7+NlCghOem/CxqKrzLAQ=; h=Subject:To:References:From:Date:In-Reply-To:From; b=j36dby+4E2/ZOoXJqWdFzbxy0Ey47Tg2S7F4dWRENYokC206k0bAyOSUKZUOE0Aci b0ogzKgGh/6/oSygwUXPLiy2U0rypGhOsDTcs7INda7aUiLJYzlsRv5drMm/nNVfEI RQ4I+C1OAIW9BGsitf40MY2ku1bnxbrVC1EeaVxs=
To: Gary Gapinski <ietf=40garygapinski.com@dmarc.ietf.org>, tls@ietf.org
References: <160496076356.8063.5138064792555453422@ietfa.amsl.com> <e1d0bdf5-9a05-4143-4289-eb3b6b7fb052@garygapinski.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <697d43c7-a86e-f303-87e4-3453c44d2030@cs.tcd.ie>
Date: Sat, 28 Nov 2020 15:13:32 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <e1d0bdf5-9a05-4143-4289-eb3b6b7fb052@garygapinski.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="pjn1bGXS0qcuLCQTzuEWto9Ay3DYsf7GS"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Q7nmbV4hq1wrrWiOVb_U_NmLK5Q>
Subject: Re: [TLS] Last Call: <draft-ietf-tls-oldversions-deprecate-09.txt> (Deprecating TLSv1.0 and TLSv1.1) to Best Current Practice
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Nov 2020 15:13:46 -0000

Hiya,

On 28/11/2020 04:39, Gary Gapinski wrote:
> Looking at https://tools.ietf.org/html/draft-ietf-tls-oldversions-deprecate-09
> <https://tools.ietf.org/html/draft-ietf-tls-oldversions-deprecate-09> §2:
> 
>    * §2 ¶5 has «TLS 1.3, specified in TLSv1.3 [RFC8446]…».
>    * §2 ¶4 has «TLSv1.2, specified in RFC5246 [RFC5246]…»
>    * §2 ¶3 has «TLS 1.1, specified in [RFC4346]…»
> 
> Were these variant ( specified in plaintext+[link], specified in link+[link],
> specified in [link] ) citation forms deliberate?

Nope. We'll make 'em more consistent.

> TLS 1.2 was given a "v" for version; the others not.

Ack,

> §2 ¶1 cites RFC 7457 twice with hyperlinks.
> 
> The document references in square brackets link directly to the documents;
> elsewhere in the document, many square-bracketed document references are
> intra-document links to §10, though RFC references seem mostly to be direct
> (i.e., not intra-document). Perhaps all square-bracketed links should be
> intra-document links to §10? RFC 7322
> <https://www.rfc-editor.org/rfc/rfc7322.html> seems adopt the same seemingly
> arbitrary (some links are direct; some intra-document) hyperlinking without any
> related etiquette guidance.

Those links are tool-generated and not part of the document
source. I'll double check but I think the change required
there is a tooling change and nothing to do with this draft.

Thanks,
S.


> 
> Regards,
> 
> Gary
> 
> 
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>

v2.23.0 | Report a Bug | By Email