Re: [TLS] [Iot-directorate] [Last-Call] Iotdir last call review of draft-ietf-tls-md5-sha1-deprecate-04

Sean Turner <sean@sn3rd.com> Fri, 30 July 2021 23:32 UTC

Return-Path: <sean@sn3rd.com>
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 CC3BB3A16B9 for <tls@ietfa.amsl.com>; Fri, 30 Jul 2021 16:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 HRDNS7PVzPHV for <tls@ietfa.amsl.com>; Fri, 30 Jul 2021 16:32:02 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFB9C3A16A7 for <tls@ietf.org>; Fri, 30 Jul 2021 16:32:01 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id t68so11051984qkf.8 for <tls@ietf.org>; Fri, 30 Jul 2021 16:32:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QErpKC9POmetNcCXgAxg30qa6zYMS0KM3deSiytsM7U=; b=i1yoEfY0Bk+0OVnXvs6pDEyfFqJDmeE3isg53RaELaTzs/kyhJ3wkNrSN12O2AORRi YyKfY64QRajxIfSIk8Dt+MMJRT7Biojwl5xks00t3qKwVm2ea8ZUrr8kY5h/k5t7RIPz bAlc9sU9Nv2xYtmwnzel+12cnwF1URZI1ZRbs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QErpKC9POmetNcCXgAxg30qa6zYMS0KM3deSiytsM7U=; b=BAnhE1CQS/KWXBCX5ZxbkEp28PktIGBuv0rG5wY2Pp3KnTIAS8SOlhbAb2XyqJX4Ry jC/h7iRrCg10veJRkQF2M0COLB8G4fqzedhgXnkaj21PNRyk2ykYPVoN5/80eVBSnnwE Ru2QqCJj/g7eQyfdkWe+YtcjtG/g/zzVTtyhKKcDZumFo/p7HCarO0py9CFsytSDJZwP g8iBUgzaf9g9qBBMxBkhSeYe+FP3BH+CXH5aFuuwJF4fceQ004EcKtGiYLge0DhL6P+I eUW4wni6SKmFvjLXCf/Axl70gtMIAhb5Capcy3avLIFVKV7Ae4RuUaLaLGBVC/2EkttU Fi9g==
X-Gm-Message-State: AOAM533d1Ol6tKaGC1IVuTI9qd1c3PiKjNGEQs8siLUdGBRkk9nzLC52 ELqyuswKMSlf0kSY/ppXh0icRQ==
X-Google-Smtp-Source: ABdhPJwbTPWGxq4oQSQfVhEyEdmZKDi4AhVGf4MteroNLtUuL9NiwJVB+mMh3H4DWd4DCGNBrMiZYg==
X-Received: by 2002:a37:2d04:: with SMTP id t4mr4718354qkh.463.1627687919398; Fri, 30 Jul 2021 16:31:59 -0700 (PDT)
Received: from smtpclient.apple (pool-71-178-177-131.washdc.fios.verizon.net. [71.178.177.131]) by smtp.gmail.com with ESMTPSA id q11sm1636221qkm.56.2021.07.30.16.31.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jul 2021 16:31:58 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <DBBPR08MB5915AE02B525DE00B05F9EBEFAEC9@DBBPR08MB5915.eurprd08.prod.outlook.com>
Date: Fri, 30 Jul 2021 19:31:57 -0400
Cc: Russ Housley <housley@vigilsec.com>, TLS List <tls@ietf.org>, "iot-directorate@ietf.org" <iot-directorate@ietf.org>, "draft-ietf-tls-md5-sha1-deprecate.all@ietf.org" <draft-ietf-tls-md5-sha1-deprecate.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AAD2078-4005-440E-8D79-EFDCFF492FC9@sn3rd.com>
References: <160380837029.27888.4435196327617929302@ietfa.amsl.com> <9EA8797E-2487-4465-9608-6CCB6E565BEE@sn3rd.com> <CADZyTk=_WSrc+UfKmZ6b=HzmfEvitu1p6Q9N7GvkHUn3619dnw@mail.gmail.com> <CAOp4FwRyd7tAcbQJR3Td_N=SgdUionwvbXfva2_tnvXcvHWkvA@mail.gmail.com> <CADZyTknQhh=yNf2isOutZa1XKoHtk6dOvE6hgXni8JowsJm=eQ@mail.gmail.com> <C93021E9-3F50-4448-8659-EE6688C3A9E0@sn3rd.com> <C9D655C0-BD5E-4E52-BFF4-BD88D281B34B@sn3rd.com> <CADZyTknWs-kNp4EO39souKQwHsT=EAWOQ_E5Z4J77KFgudhhhg@mail.gmail.com> <CADZyTk=tgThJ7RJ_=K=gdDYcUWkhy0AjcLB_Nvf1=UEUBrzAUQ@mail.gmail.com> <32892AD4-EA0B-49F2-9CFD-FA9509FA3010@sn3rd.com> <A48DAF03-F2CB-4448-B9E8-6AE4ECB77565@vigilsec.com> <DBBPR08MB5915AE02B525DE00B05F9EBEFAEC9@DBBPR08MB5915.eurprd08.prod.outlook.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/JPfVHJjIF3djv1Z-2AtQrSw-Er4>
Subject: Re: [TLS] [Iot-directorate] [Last-Call] Iotdir last call review of draft-ietf-tls-md5-sha1-deprecate-04
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: Fri, 30 Jul 2021 23:32:10 -0000


> On Jul 30, 2021, at 05:08, Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
> 
> I have no problem with the suggestion.
> 
> A few other observations:
> 
> 1. FWIW: The reference to [Wang] is incomplete.

The same ref was used in RFC 6194, but we could also use:
https://www.iacr.org/archive/crypto2005/36210017/36210017.pdf

> 2. The references to the other papers use the websites of the authors or project websites. I would use more stable references.

We can replace:

http://shattered.io/static/shattered.pdf

with 

https://eprint.iacr.org/2017/190

and (is the INRIA site better?)

ttps://www.mitls.org/downloads/transcript-collisions.pdf

with

https://hal.inria.fr/hal-01244855/document

> 3. Kathleen's affiliation is also outdated.

Ah I thought we fixed that. Anyway we’ll change it to: CIS

> 4. Is the update to RFC 7525 relevant given that there is an update of RFC 7525 in progress (see https://datatracker.ietf.org/doc/html/draft-ietf-uta-rfc7525bis-01) and even near completion?

I do not have a problem moving the text. I might also solve the can a standard update a BCP question.

What do people think?

> 5. The title of the draft gives the impression that this update only refers to TLS 1.2 but later in the draft DTLS is also included via the reference to RFC 7525. Should the title be changed to "Deprecating MD5 and SHA-1 signature hashes in TLS/DTLS 1.2"?

We could do (D)TLS 1/2 too.

> Ciao
> Hannes
> 
> -----Original Message-----
> From: Iot-directorate <iot-directorate-bounces@ietf.org> On Behalf Of Russ Housley
> Sent: Wednesday, July 28, 2021 10:34 PM
> To: Sean Turner <sean@sn3rd.com>om>; IETF TLS <tls@ietf.org>
> Cc: iot-directorate@ietf.org; draft-ietf-tls-md5-sha1-deprecate.all@ietf.org; last-call@ietf.org
> Subject: Re: [Iot-directorate] [TLS] [Last-Call] Iotdir last call review of draft-ietf-tls-md5-sha1-deprecate-04
> 
>>  In Section 7.1.4.1: the following text is removed:
> 
>     If the client supports only the default hash and signature algorithms
>     (listed in this section), it MAY omit the signature_algorithms
>     extension.
> 
>>  Since it’s a MAY, I am a-okay with deleting. Anybody else see harm?
> 
> I don't see any harm.
> 
> Russ
> 
> --
> Iot-directorate mailing list
> Iot-directorate@ietf.org
> https://www.ietf.org/mailman/listinfo/iot-directorate
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.