IETF Logo Mail Archive

[v6ops] Re: Dispatching Happy Eyeballs Version 3

Philip Homburg <pch-v6ops-13@u-1.phicoh.com> Tue, 16 July 2024 11:28 UTC

Return-Path: <pch-b538D2F77@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39A06C14F749; Tue, 16 Jul 2024 04:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 9RSnodhLBNpO; Tue, 16 Jul 2024 04:28:14 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [IPv6:2a10:3781:2413:1:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6838BC14F6EC; Tue, 16 Jul 2024 04:27:45 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #158) id m1sTgLE-0000MmC; Tue, 16 Jul 2024 13:27:32 +0200
Message-Id: <m1sTgLE-0000MmC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-13@u-1.phicoh.com>
Sender: pch-b538D2F77@u-1.phicoh.com
References: <35C7852E-FF43-4600-BD93-B05DF82E3AF3@apple.com> <6E2B8558-CD88-4E26-AA6E-60978A886DB3@apple.com> <FB1ECCA9-0776-4928-955F-8EC22EEBE19E@consulintel.es> <BL1PR18MB42779FE990A919F054C3B4FAACA22@BL1PR18MB4277.namprd18.prod.outlook.com> <m1sTeUw-0000MgC@stereo.hq.phicoh.net> <ec4cde3ddb634943b8354cce04b7f944@huawei.com> <m1sTfBo-0000KeC@stereo.hq.phicoh.net> <f01c4003b2da44379c0533667ea30b75@huawei.com>
In-reply-to: Your message of "Tue, 16 Jul 2024 10:20:58 +0000 ." <f01c4003b2da44379c0533667ea30b75@huawei.com>
Date: Tue, 16 Jul 2024 13:27:29 +0200
Message-ID-Hash: SDQUQKGQFBDWHMP5AUYPTCRMKLE72HQL
X-Message-ID-Hash: SDQUQKGQFBDWHMP5AUYPTCRMKLE72HQL
X-MailFrom: pch-b538D2F77@u-1.phicoh.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Alldispatch@ietf.org" <Alldispatch@ietf.org>, "draft-pauly-v6ops-happy-eyeballs-v3@ietf.org" <draft-pauly-v6ops-happy-eyeballs-v3@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [v6ops] Re: Dispatching Happy Eyeballs Version 3
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/RjI7MuPw2uIXo7inMO3pVblwY6o>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>

> Nobody proposes "Recording
> a user's traffic".  What I proposed is logging the reason IPv6 is
> not selected, e.g. AAAA record not available, IPv6 connection setup
> times out, etc.  The purpose is clear, and I am sure we can find
> a mutually acceptable solution.

That's is just a security or privacy disaster waiting to happen.

There are plenty of countries where visiting certain sites has a very 
high risk to the user. All it takes is one (possibly deliberate) connection
failure and the user ends up with incriminating data on his own device.

We should stay very far from that.

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