[TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls-dtls-rrc-18: (with DISCUSS and COMMENT)
Achim Kraus <achimkraus@gmx.net> Mon, 07 July 2025 06:17 UTC
Return-Path: <achimkraus@gmx.net>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2CE0D3F733C5; Sun, 6 Jul 2025 23:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 0.771
X-Spam-Level:
X-Spam-Status: No, score=0.771 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_SBL_CSS=3.335, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.232, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmx.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aoGEpc7ePYiC; Sun, 6 Jul 2025 23:17:17 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 672533F733B4; Sun, 6 Jul 2025 23:17:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.net; s=s31663417; t=1751869033; x=1752473833; i=achimkraus@gmx.net; bh=LMZa0i/KEtW1Q4uBlG4+EyrBvOmvynG0RTE9JFARNIk=; h=X-UI-Sender-Class:Message-ID:Date:MIME-Version:Subject:To:Cc: References:From:In-Reply-To:Content-Type: Content-Transfer-Encoding:cc:content-transfer-encoding: content-type:date:from:message-id:mime-version:reply-to:subject: to; b=Mjr6LJ4V9VhVPSOyVYfmQQrqN/BClDZYDZoJfR1z97QXqL3IvKUbCLxXSgpT8N9l FrqDppRRJtO3xsXQ0xmRWk82jnVjN6VMWs2rn1E8pWbMQ7bjbNcc/9j/sXQ53Xdym SdbbtBm9LfXjfuUHf7ncVHmIYHt5AAcRA6npmoH3SwQr3DxGxkqjyqP84pv3WilnR KnmD6fFwRFrg16PPZnKeEyTOcsrDwf6hTjhSdjzSGPFOFGyrSfqZ848qXqtGTVAEH cYmpJMxEt7JWQFLzzPXRGpVgyu4f6lOafQr9q8aNRCFqpOYIuER3v33WekV4x33+U 98RQV6mJtUiibzhD7w==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from [192.168.178.10] ([88.152.185.171]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MDywu-1uQvO83zHg-003w4r; Mon, 07 Jul 2025 08:17:13 +0200
Message-ID: <007d3f6f-a04c-4d13-8b1a-131587401ed8@gmx.net>
Date: Mon, 07 Jul 2025 08:17:12 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, Thomas Fossati <thomas.fossati@linaro.org>
References: <175154470587.1120568.12931412045773088416@dt-datatracker-6fcb845cd4-p6tkq> <hfsxcip2yklknt25vpmkaliijct6ldpbo7ifj6sbvyuhqjh65i@jrorzcs7ajqh> <PH0PR11MB4966ACC59281A00856B4A5A1A94FA@PH0PR11MB4966.namprd11.prod.outlook.com>
Content-Language: de-AT-frami
From: Achim Kraus <achimkraus@gmx.net>
In-Reply-To: <PH0PR11MB4966ACC59281A00856B4A5A1A94FA@PH0PR11MB4966.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:m2/FknF24nW6afhR//3ipACFqrrN4XUiNY7OpBLBwMs6kit2Nl3 VIKrmWAiI5p3tqFBEy/B4mP/WiVgVKTNnW2elnM9m4/6Ti/zpiV/Bnwg61o4xdxFtqk45Zw 49XkSrzd7mUJwy1ulNR8VcRVYackmDKMQPAd+TUOUm52GxIuM60BytYaQs/E1WIjbCk3uFX v0O6SxWiqCyND4MepqDLQ==
UI-OutboundReport: notjunk:1;M01:P0:Hd0V4oC46ok=;OqUGj9KQiLPfivywc2OQemq+NLc pSRt9iJPVt58Lv/5Zt28lp55/01JIwftiu+WPtoqauXdMCJG4laE6hWnfRmBGY5Ua3+ot8oLZ isJJQpye1gfzBFyjnI0rqFKkFAXOo2Y4sJjvdnjfV6dG1kMZzF/D9zDxxCM6mtXzof3tLyXiT hU1ldbCP5uJvRWQVF6i8USVVtLlUfpqtGUbCp7rUAefnX8bbUolrbTviBHfDclmPsJyLPHjRH TxmTb4WjM3VD6pVz+KBRp2g3d3JoO/EjKtCV2wVUMozp58Yyog7OE2KV0vwse6l3mJqqIAMMg BNvqbc4o0Lej+eUbI3RV8any7BuBfUbWhps3eWiKwNkEHriTXh0+p1btnf9BrjC4FwlI/VscS Gt+Di5vRNABJ/VLaoWtKVGz7L/mjcsv38XZiNGRQoRipnaK+2dUvKi+4blX9dAbaeHAG3JV6+ ivaQgkH00zOJKvduW1G+woJJYyKjb4KEnvc+mFNU5WfI5HJOvzBzEGGwUWeQANawUn0hc8c+z CmykYNOJ8O+Mv/OMCY7/Vh4yEB6nWFDKYZzptwFwQ/zxWA6MNS+H2nQ4jM4Q24ovMG0Ynhpph rwM08Vytt/azVClgVq38IjDWFvdhn9wrJHpPNPpYnew+br6fiV/F6aSZWf4/Ujg6J5cWYNgde AuwGeoiKkrWm2hY2dRTfAQWk1fY+UsQdUlNkY3eQVu4CfPQmc/dbrnIsxj+ga+eNOciC0wFqw n+0VRVrmxiQxo9BZ6BvhRFkW6QdPV2hVKMxk//cOmkvUcDgJIq05ShzUXLCrR86zxohK68VPm VlK7EUGJb48MQMx4TUg8CbByG9A879yakOwRsdizS2SfHdJTAkt73Qlrq0jkAPE/ZQ2Fl4NFQ 5xi+Dzn2neEPT3ApSgt1BPRe4kqPQH68DzeIfUWmszfNJfyPFyfB8drT1dSNp8Acw+udMuzfT iO/dfwxx6p4wH7GVkAcYcBfRaxLKNSwFL2x8tHkeWiIM1PcQS0E7XIZ3Bq/vzX4VWKFMpQX+N EaPk6SXr4eky6kANUV7HNn/dbnkCsIc9eAMCUDvZyIeqS4CDodjJdQs25qoRAiu4AEnzxye3O zJcXzJ0teCaacoJ4roBsjH3UhiXmY0PQ+4ozorG6NTkhLAdY0RQudGrdhf+cfORPvgtNbkBb7 KnVUCmzPWsibR8YHVQAsos18vkGI4ILXVZXtjVKROu9vYgGdTYUI5iOzvM9xsuJeDKLY9L754 fs8V6xLYWJ8U6xUKY8FADsa3xi/EwLS+XVbwjcZVVlRO3Od1dAhDYVY+cYG1Pm9Tk5k25R/1W 5K+hYsp4Evm0bWfhsApoPX/eqOKLtUq1qC4xnXHJFSpgqW+TBYj/160J9oGhlYUxSzG7DJxTF lCzTRmnmK7HTwSG+rKE6QzYizp72AkekKOOZRl/XqU1gx6h/B7xPwuFTl3klbGz2oz+dS2cHe sWtsi148p8o89OLRXqcg94n0MeG0nSwxkh+rAT0/+pjyFUwLVnYF1VUCGCorwzP+8LmFd+kEt lWHwbGywMA83UG5M+x0bPQCMU25X3n4Y1G7tIwYYpyzQ1yObeiJBag0rOxTFbkBHJUjWbWpzu rW3nHp9P455/J4H33ZEvEo3coVdKH1w36mTDs6bcbntq0d3n8KqhxtWOBFROhLrB7cuCI/Zsd cQKD0xhRx3IAfJAUyaqPdCqtLu6fiRTUrhUoc3g2OkGOP0BZjqOVjCVzqATysrk83X9k0FCWr feQejaG6qdltVMRV9WdGNe/Fm7YCvtMeJ0eCLDQwuvrLf3VUkjytaria2e5CFAliqXyJg/c99 I5sZY8Vx7mAlz4tci2Pg9cNXRpmuLY3MzxsxgIfz7SoRI6a7U1dDxf/jSjoUdYkf8sV18w+cr a3qr5uZonea6MzpcUWEnabrJryJo/qQ3kr9zaOHOLSE5aRu45FlDr+nzGexy51Vuh05EEhglp eclcBB9p9sTuOIkLQmkyC9gsPT9Tk/l7kYvVf3sjK2Hc+sKBp9V9QZO2Mb2wS3jCcavjKWJPe 35ft4zTBUg7JhQjvPzoohtyaooTguuogmAy89DWAwPkuFEd5LNtWMZ6cg5hUzW9nWZVQiOlCW OO5QDISSju2M1dZdK6pXLCrXGkBJINjY69T/ctDNB+t1sbU8uyr+NcxhaLyEFidxR0mICZAIq 4IEAcbN5TcR3xZm9B5q2GmJCTV1BRzVtoiS+CuuqFuQD0PQTGbnbLehIiN38ex2Vb7qkvzhg6 73QtEqPWaJFvGmARKMOxeP4TSp7/SYhVi6k8h7Ci2/Lu9mA4biA4AqQKBCo6WEDt3XL8k7e1P WK/nYKNzxjgASVsZQHaZ0Ziiyh0PX00RgveTuOHsFg/8PUDJCwkjiwmTAGOAABP79fQ4Qh3rd VV4OnM/+w3uiZNt+DFxtlCoCpSqcasZWQAgEYvmSTNJ7GLO551Sd4Lzc6T3teOBsS3vG9BjHY F+KxbFpmVMtj/9ripBV3/s6wzuU0vkpAoBFVA1oGMxDVTREDReRiOm7qNgtcAdrjEtAnONpCu 48bqmPXgfeNwlsu3mscpd3DL54gxyPOzGIkXmDGaWK5xpOZV+cDu3vrbz/esRq4iIBVxsJjaJ xQHdKLIyjiq0t79HWVMm0Rbay28jtPJBh/n3l3pPbRln2x+lYlI7a0Pz1rQStxTqw3GZUXNq6 9IVZYSGIl+JCFNLJ+brbYUQkrBBk6DQNHajGnYwlp278C2QKX0+7znRU9p0PbZ56fXGsD1Ym/ bdwqco15CCPzuua6jKtlHywcaBNzYPNDIm0i+zwWqqpkXuf/bRO74SGTysepz1U7kjrreKNta wiay5XpjO2dtEOvKUwA1qYG/Le/ToPa1GphpGKMFHmCsPIbZO8NcbPndmV4GjzjKXjfJok45G nVvhKqgI9Q2d3fF2rzaAc8AxVNG9Uam2fOrXGm90JuDGtHIxKHlXvTxEHrF+sI3PtTrPwm2wl wPK4z0c6xxJUnECO1DpbnLZKQ9qDHJP8zINQk8btXQxw4FcBgmw61VYYdq9IUnYhloP9nDQlM PvjeghmZa7kp+ZXdBokpxWfWvkr9DcWOwAGq/HiI/mCdXFnoWe3ndCVjP2DiqhgBM2bYqkTJQ x8gfHpG6TkdU41IVq45So6IA1e9hJIo5RvtCfBiXOvZmUaU9EIYYfEtFF8NeQ95uktgq8Ngft YhIj2rnrJK8/oqZp7pjkQjSzO3T1dlvKh1sqn0uDr3B5LK/d5yDr8AnnhQ9LDo5UP5Z3SKgpp PMXQ4Ye/jEz2IfK1Qi9pfK/eY8KP3ewfW4oQBwklpl60TKzFBEMF8VOyn+QthPq1pDZl5nsdF jZsKKAwxItm3or1QmGgp0ddv5/N5CC7jCH06pYsSA9m8Tn1Y1UHXO5pNYiCPmzmW9tQPAKmAL BWUhIVKi8taDrJfVxEn5FEjNUT25/gE6YdOPNN4gXBbnUiaAkOyjnannGgCzlsuS98SUeaMq6 IsmgHfxnwYZ5ErQPbzhYXhE790Fo0qtOOI7PYWmw9r00ZZKwJHgHqGwwMIRiL0Hjo5u6GsXZA oQN3tBj72brkCv5OuZ6z8b8=
Message-ID-Hash: Q2C33BOKSCVX44TTIUAE7LCVX6DXDJTW
X-Message-ID-Hash: Q2C33BOKSCVX44TTIUAE7LCVX6DXDJTW
X-MailFrom: achimkraus@gmx.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, "draft-ietf-tls-dtls-rrc@ietf.org" <draft-ietf-tls-dtls-rrc@ietf.org>, "tls-chairs@ietf.org" <tls-chairs@ietf.org>, "tls@ietf.org" <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls-dtls-rrc-18: (with DISCUSS and COMMENT)
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/CjdR6AlK0Pio_96R5cdQE72YyUY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>
Hello Éric, while the explanation, how a NAT works, is well, I mot sure, why "The action to be taken depends on whether or not the path through which the message was received is still the preferred one." needs to be amended by "or has not changed". What's the "preferred one" is left to the peer (e.g. chosing/switching between network interfaces from cellular to wlan). And in the simplest case, if there is no intended change, the "preferred one" is obviously the "not changed" one. But if we add "or has not changed", I miss how a peer will then do such a proactive switch, when both paths are still valid. br Achim Am 07.07.25 um 07:45 schrieb Eric Vyncke (evyncke): > Hello Thomas, > > I am afraid that the PR 97 does not completely address my concern. In > short, if there is a NAT rebinding (NAT44, NAT64, or even NPTv6), then > the responder will receive the challenge on the previous address/port > even if the initiator saw a new public/global/outside address/port. > > May I suggest in bullet 3 of section 6.2: > > * s/which the message was received is still the preferred one/which > the message was received is still the preferred one or is unchanged/ > * s/If the path through which the message was received is preferred/If > the path through which the message was received is preferred or has > not changed/ > * add somewhere in this section an explanation why the initiator may > see a change of address/port while the responder does not see any change > > Hope this helps > > Regards, > > -éric > > *From: *Thomas Fossati <thomas.fossati@linaro.org> > *Date: *Thursday, 3 July 2025 at 17:50 > *To: *Eric Vyncke (evyncke) <evyncke@cisco.com> > *Cc: *The IESG <iesg@ietf.org>, draft-ietf-tls-dtls-rrc@ietf.org > <draft-ietf-tls-dtls-rrc@ietf.org>, tls-chairs@ietf.org > <tls-chairs@ietf.org>, tls@ietf.org <tls@ietf.org>, sean@sn3rd.com > <sean@sn3rd.com> > *Subject: *Re: Éric Vyncke's Discuss on draft-ietf-tls-dtls-rrc-18: > (with DISCUSS and COMMENT) > > Hi Éric, thanks a lot for your review and comments. > > Please see the replies below and let us know what you think. > > cheers! > > On Thu, Jul 03, 2025 at 05:11:45AM +0100, Éric Vyncke via Datatracker wrote: >> ---------------------------------------------------------------------- >> DISCUSS: >> ---------------------------------------------------------------------- >> ## DISCUSS (blocking) >> >> ### Section 6.2 >> >> In the case of NAT rebinding, how can a responder behind a NAT detect >> that its external address/port has changed as seen by the initiator: >> it still receives the other peers packet sent to its unchanged >> address/port ? What am I missing ? >> >> This could probably be addressed by some more text before `The action >> to be taken depends on whether or not the path through which the >> message was received is still the preferred one`. > > This looks very similar to Med's comment "Impossibility to adhere with a > MUST". > > Can you please have a look at the discussion (sub)thread at [1] and the > proposed fix [2]? > > If we are lucky we may have already solved this :-) > > [1] > https://mailarchive.ietf.org/arch/msg/tls/JyslZqlHwQFdCo0mmBiQvo_6wmI/ > <https://mailarchive.ietf.org/arch/msg/tls/JyslZqlHwQFdCo0mmBiQvo_6wmI/> > [2] https://github.com/tlswg/dtls-rrc/pull/97/commits/03935ba17 > <https://github.com/tlswg/dtls-rrc/pull/97/commits/03935ba17> > >> ---------------------------------------------------------------------- >> COMMENT: >> ---------------------------------------------------------------------- >> >> ## COMMENTS (non-blocking) >> >> ### FATT process ? >> >> Out of curiosity, I still wonder what `FATT process` and `FATT review` mean in >> the shepherd write-up. > > FATT is TLS's formal analysis triage panel. See [3]. > > [3] https://github.com/tlswg/tls-fatt/tree/main > <https://github.com/tlswg/tls-fatt/tree/main> > >> ### Use of "path" >> >> Probably too late to change, but the choice of "path" rather than "anchor" or >> "socket" (or something else) is poor... the actual path (the set of network >> links and devices) keeps changing in an IP network. > > Yes, in hindsight I can see that this wasn't an ideal choice. It seems > a bit too late now to go back and do a terminology revamp. Hopefully, > this won't create too much confusion. > >> ### Section 1 >> >> A small graphical (packet exchange) would be useful even if the text is clear. > > Perhaps we could add a forward link to the "Example" section. > >> ### Section 3 >> >> What is the expected server behavior when the client sends the rcc extension >> without offering the connection_id extension ? Is the whole handshake stopped >> or is the option ignored ? Please be specific. > > The server will not echo the rrc extension. > >> ### Section 4 >> >> Probably due to my lack of familiarity with the used syntax, but it seems that >> the enum part is not really part of the figure 1 legend of `Return Routability >> Check Message`. It seems more like an addition to TLS Content Type registry. >> Suggest to split this figure in two figures with 2 distinct legends. > > I like the fact that all the relevant TLS presentation language is > packed together. Rather than splitting the figures, I'd slightly extend > the legend to read "Return Routability Check Message and Content Type". > >> ### Section 5 >> >> s/has faster routing/has faster forwarding/ ? > > In the editor's copy we currently have "faster fowarding path". Would > that work for you? > >> ### Section 5.1.1 >> >> Related to `the original packet still reaches the intended destination`, does >> this mean that an attacker can prevent rebinding to a new address/port by >> sending the packet from the 'old' address/port ? > > Not really. We assume that an attacker does not posses the session key > material necessary to forge a valid path_response that would convince > the peer to rebind. > >> ### Section 5.2.1 >> >> What is "AP" in figures 5 and 6? > > Access Point. > >> ### Section 10.2 >> >> As this section ends with a recommendation, should it clearly be in >> the protocol specification part rather than in operational >> considerations ? > > Another approach might be to provide more context for the > recommendation. For example: > "Therefore, when using RRC in DTLS 1.2 *and middlebox interference is a > concern*, it is recommended that CID is enabled in both directions." > > t >
- [TLS] Éric Vyncke's Discuss on draft-ietf-tls-dtl… Éric Vyncke via Datatracker
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… Thomas Fossati
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… Thomas Fossati
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… Eric Vyncke (evyncke)
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… Eric Vyncke (evyncke)
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… Achim Kraus
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… Thomas Fossati
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… mohamed.boucadair
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… Thomas Fossati
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… Eric Vyncke (evyncke)
- [TLS] Re: Éric Vyncke's Discuss on draft-ietf-tls… Thomas Fossati