IETF Logo Mail Archive

Re: [TLS] WGLC for draft-ietf-tls-rfc8446bis and draft-ietf-tls-rfc8447bis

Eric Rescorla <ekr@rtfm.com> Wed, 05 April 2023 19:28 UTC

Return-Path: <ekr@rtfm.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 69E2FC1522D3 for <tls@ietfa.amsl.com>; Wed, 5 Apr 2023 12:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XFlfx1-goBL for <tls@ietfa.amsl.com>; Wed, 5 Apr 2023 12:28:39 -0700 (PDT)
Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE2ABC151B3B for <TLS@ietf.org>; Wed, 5 Apr 2023 12:28:39 -0700 (PDT)
Received: by mail-yb1-xb29.google.com with SMTP id p203so43824794ybb.13 for <TLS@ietf.org>; Wed, 05 Apr 2023 12:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; t=1680722919; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=VQlHlSbji8DKgfExcIyWy2OVe7La9ngOtwo5boywuPE=; b=ENH/cgxrgvVctH5PGPwNYP4XWN8T20IwDdajswvQCyp3IOyqIELOab9HH5qLMw33jR TjiuShhyYMAD/1sPBdXDU9qrQw3423p7ju9lMeef6JUbpWpAcHtrEjkrpERlhc07vyIQ 6MkrLZWqtcEtvCsy8ejtKo2dhb6HQ77OB9m634v0PUunrTjeGgRzYWmdc+YI5KT+IgKD YvyR4obu4m6aKjwv9xpNtt1OX5eyu9tWMYSlNqzRrHmwThHUa31CYUNGhi8qr+LJa9+C nyxr7LD7KSdnLiGNJfqlvxkd0xuQ6h2RMb4rtzdgYs4HfaMwElH/waQLrsu6wJuXqTPC QFrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680722919; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=VQlHlSbji8DKgfExcIyWy2OVe7La9ngOtwo5boywuPE=; b=qcLtAS+GziFQTZUf78xyFGibb8EQmSCmT1CXnD4e+55cYew4F1nJrO6nEVvuoDW13g hHOTL8grA27yks9p2yyGqHgnDkb/PRAIenVboD61EKcqdQm0s0DSprePuN3rr542Dinq f8bX4UYuQoWsurondqnj5mM4pT4d1JxF2qUJ65MLKM3ALBICcHpjXuRL8EM05bTy4GRp CiEWr3eMGyvcM6/67dvn7tdYis2pD+aAB/oscdk/nOjioR+BaTWofySb+TwafG86wDQo mik/TtMk2oTmX1gPeFVbZdDw9E4xARq9RMHlX0sEGwZLBMsuwcg5MgEsOghMoW/NocpA jmkA==
X-Gm-Message-State: AAQBX9f1/d54OOYzveM4XG2GaXtl86wERGwcsOH5hmW8YgkiF5+PmKbN CtCTNYDSlTfDqreirM0qJ67jYFrFPdnt4lruSuoL3z0hpwppOSWj
X-Google-Smtp-Source: AKy350ZrAfwT8yDVHCCRR/vuqFv/8yTTa6AbJjk/GBCxeDYeK1B/qUdIssT4TTGw+afmkBvIS6ekCSCWNuMdi9B4Zeg=
X-Received: by 2002:a25:d14f:0:b0:b8b:ee74:c9d4 with SMTP id i76-20020a25d14f000000b00b8bee74c9d4mr279754ybg.12.1680722918761; Wed, 05 Apr 2023 12:28:38 -0700 (PDT)
MIME-Version: 1.0
References: <E7A22BA0-4EDD-4B0D-B5D1-6FA7AF466398@heapingbits.net> <5CBA62B3-CFD0-4062-B66D-AFA6F887128B@sn3rd.com> <d3ccffd1-2f92-f2e2-0e96-32ee6f5cd7b3@cs.tcd.ie>
In-Reply-To: <d3ccffd1-2f92-f2e2-0e96-32ee6f5cd7b3@cs.tcd.ie>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 05 Apr 2023 12:28:02 -0700
Message-ID: <CABcZeBMrms4rxmtCAruUs=nzdO6z0F-wDKmoF0HB9jjY9DVPUg@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Sean Turner <sean@sn3rd.com>, TLS List <TLS@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000089faeb05f89bccb3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/dOPnecUHHW52sUzbMQ3kK-MDA10>
Subject: Re: [TLS] WGLC for draft-ietf-tls-rfc8446bis and draft-ietf-tls-rfc8447bis
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 05 Apr 2023 19:28:40 -0000

This was discussed extensively when 8446 was published and there wasn't
consensus
to make such a change. If the chairs want to re-open this issue, please
weigh in.

-Ekr


On Tue, Apr 4, 2023 at 7:32 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> Hiya,
>
> On 05/04/2023 02:47, Sean Turner wrote:
> > A post IETF 116 bump to make sure folks get their reviews in. If you
> > look at the diffs from RFC 8446 you can see not that much has
> > changed. We will also take “I read it and it looks good” response.
>
> I looked at the diff between 8446bis-07 and 8446 and it seems
> fine to me. My only comment is that C.4 says one "SHOULD NOT
> reuse a key share" - I'd be happier if that was a "MUST NOT"
> but understand if we stick with SHOULD NOT. If there were a
> good reference showing that it's quite feasible to never
> deliberately re-use a key share, even at scale, that'd be a fine
> addition. (I don't have such a reference to offer,
> sorry;-)
>
> Cheers,
> S.
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>

v2.46.0 | Report a Bug | By Email | System Status