IETF Logo Mail Archive

Re: [TLS] 2nd WG Last Call for draft-ietf-tls-dtls-rrc

Thomas Fossati <thomas.fossati@linaro.org> Mon, 09 October 2023 09:42 UTC

Return-Path: <thomas.fossati@linaro.org>
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 E95D0C151067 for <tls@ietfa.amsl.com>; Mon, 9 Oct 2023 02:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=linaro.org
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 TqeHmkKqkWt9 for <tls@ietfa.amsl.com>; Mon, 9 Oct 2023 02:42:52 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 23664C14CEF9 for <tls@ietf.org>; Mon, 9 Oct 2023 02:42:51 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id 38308e7fff4ca-2c012232792so51925891fa.0 for <tls@ietf.org>; Mon, 09 Oct 2023 02:42:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1696844570; x=1697449370; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=YM5QLChHDH4EX0+PrYs1tEw6Vv76PCRekBszc8Uia+c=; b=ICTnWoSxjm20ZDX4rHuhtM0k8jDEEjq7mApHbJn2/PQOKyHlkhqHa6cfJb8dxUnjhI gpTdwHFZbR2oKiE4ZMvi5JIwyjp0D+FMugRfGKZR1QGLPLxKTS6BIg04YuvDFFlEUbem NqIZJEFo255NTGFgc5Vk7LQyNATj0pWsJ0LVpS1tz1OqlHm4Q+x5p40IHMyZn4xCFqlV 9YjkWuoTpfbtEhoY2tNBUzhWve1uc03sUbFs4Xg9CdVq8PmJ8JrCYJqLXEIn0QkSl+I9 IlRSkFTNro/sEqm036x/dL4QubczwEPRLTrIEih606zUW/SZxsI0TMLZvVvj1Cm5UwGw IUXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696844570; x=1697449370; h=content-transfer-encoding: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=YM5QLChHDH4EX0+PrYs1tEw6Vv76PCRekBszc8Uia+c=; b=wKOK0JVI9OZMB8Zh1XV7s8RA8jUSLLZswf6Mg9Gt5XejoB6jQks6XRdUq46bTLILXT UPQwZSXX5VPTGFw0405O2pmSD4o8jR5E6bYzaEK8SNW+YQjK8ZwCWGdSAoTo++IWhhEo wpGh16zW7q8yJf33ZiIAJpAkhg34EsWWICYSHB8IkhlSK6qXOik6Hsc1ng5En/NGt3s1 X00MneIbouX7HQyEXBrairy35/TGQRpGHcw4LcPfFnxAGAgKqPcqR/jQ+3H2QyAVjy0y +DRg4HS0AUGqIe2DZZ42GqQ6nx7FyMS3i/kV1KTCAflIgbM/iB+bW1u251BH0CxW7qZ5 k2Vg==
X-Gm-Message-State: AOJu0Yw3VrE2/qfdqQDimGaA46Lq0zcTEqGWH4zuydVRTx8DXOLKrsFg AIArc0lsYQEbdMGBfPzn2DtOG13oaNk36VE9T68o5ETfg1u5ErBjtGmBJg==
X-Google-Smtp-Source: AGHT+IEaqTfG8nrV1DFnnRnYlucIlMhdud201k7ohy/4IjnuUICSq/VwdfG4ykKex3hDvB7hCelWhu28txZwlTzgM98=
X-Received: by 2002:a2e:a168:0:b0:2bf:f985:7725 with SMTP id u8-20020a2ea168000000b002bff9857725mr13736889ljl.15.1696844569753; Mon, 09 Oct 2023 02:42:49 -0700 (PDT)
MIME-Version: 1.0
References: <50990212-57EB-4228-A259-BB8FEA6AC364@sn3rd.com> <e72afcd5-d3bf-2d85-7cee-5f42684b9981@ri.se>
In-Reply-To: <e72afcd5-d3bf-2d85-7cee-5f42684b9981@ri.se>
From: Thomas Fossati <thomas.fossati@linaro.org>
Date: Mon, 09 Oct 2023 11:42:33 +0200
Message-ID: <CA+1=6yeLgfDMaV0pXkSvN5JtnUtp3eiWOv6F71rdZq-z6=bMXQ@mail.gmail.com>
To: Marco Tiloca <marco.tiloca=40ri.se@dmarc.ietf.org>
Cc: Sean Turner <sean@sn3rd.com>, TLS List <tls@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/fwv9aN80yo0AkHxQ3zIDWQNkNj8>
Subject: Re: [TLS] 2nd WG Last Call for draft-ietf-tls-dtls-rrc
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: Mon, 09 Oct 2023 09:42:56 -0000

Hi Marco,

We think we have addressed all your comments (but one, see below).
Could you please check that the PR at [1] is good to go?

[1] https://github.com/tlswg/dtls-rrc/pull/63/files

The one comment we wanted to have a bit more discussion before
deciding how to proceed is this:

On Tue, 3 Oct 2023 at 15:50, Marco Tiloca
<marco.tiloca=40ri.se@dmarc.ietf.org> wrote:
> [Section 7.4]
>
> * I think that another requirement should be that the initiator MUST NOT act on more than one valid path_response or path_drop message for each path_challenge message that it has sent.

§7.4 currently says:  "The responder MUST send exactly one
path_response or path_drop message for each received path_challenge."

So it's not clear how a situation with multiple occurrences of
path_drop/path_challenge could come off, if the responder obeys the
specified MUST?

Could you clarify your concern a bit more?

> [Section 10]
>
> * You will need to add a new subsection that provides expert review instructions, for the Designated Experts assigned to the new subregistry defined in Section 10.3.

Thanks: this made us realise that expert review was a bit too
lightweight, therefore we moved to STD required.

cheers, thanks!

v2.23.0 | Report a Bug | By Email