[{"author": "Dave Plonka", "text": "<p>In Shenzhen, can hear Jen, Eric, and Tim fine.</p>", "time": "2026-03-18T01:01:39.000Z"}, {"author": "Lars Eggert", "text": "<p>michael, three rooms and we basically voted. top three sessions get rooms.</p>", "time": "2026-03-18T01:03:06.000Z"}, {"author": "Lars Eggert", "text": "<p>~40 people in tokyo, only hub i know of</p>", "time": "2026-03-18T01:03:31.000Z"}, {"author": "Tim Chown", "text": "<p>thanks Dave</p>", "time": "2026-03-18T01:04:19.000Z"}, {"author": "Dave Plonka", "text": "<p>aside re:note taking, my ability to type in the HedgeDoc has stopped; when i type there it does nothing (cursor does not move) either embedded in Meetecho or opened in a separate window.</p>", "time": "2026-03-18T01:19:08.000Z"}, {"author": "Dave Plonka", "text": "<p>OK, working again. whew</p>", "time": "2026-03-18T01:19:25.000Z"}, {"author": "Tim Chown", "text": "<p>from charter \"platform-specific or<br>\ndeployment-specific considerations should be included in the core algorithm<br>\ndocument\"</p>", "time": "2026-03-18T01:20:25.000Z"}, {"author": "Tim Chown", "text": "<p>but also \"While the algorithm may apply to scenarios<br>\nwith multiple network links, or pools of multiple connections, specific<br>\nmechanisms for such scenarios are out of scope for the working group\"</p>", "time": "2026-03-18T01:21:25.000Z"}, {"author": "Brian Carpenter", "text": "<p>I don't see that _mentioning_ multiple interfaces as a side issue is forbidden by the charter. Solving multihoming in general is a disaster area, but that isn't what this does.</p>", "time": "2026-03-18T01:25:46.000Z"}, {"author": "Tim Chown", "text": "<p>we do have some text in the doc about VPN issues, in 8.5.</p>", "time": "2026-03-18T01:36:12.000Z"}, {"author": "Philipp Tiesel", "text": "<p>+1 to Lorenzo's proposal to mention PvD issue and remove Interfaces</p>", "time": "2026-03-18T01:37:34.000Z"}, {"author": "Jen Linkova", "text": "<p>Yes. I think it's a very good idea. It makes the scope exolicit</p>", "time": "2026-03-18T01:41:33.000Z"}, {"author": "altanai", "text": "<p>does any one have the link to the research paper that was mentioned to have compared the implementations?</p>", "time": "2026-03-18T01:44:47.000Z"}, {"author": "Nidhi Jaju", "text": "<p><a href=\"https://arxiv.org/pdf/2412.00263\">https://arxiv.org/pdf/2412.00263</a></p>", "time": "2026-03-18T01:45:26.000Z"}, {"author": "altanai", "text": "<p>TY Nidhi</p>", "time": "2026-03-18T01:46:44.000Z"}, {"author": "Mirja K\u00fchlewind", "text": "<p>Actually would be interesting to understand what people wouldn\u2019t implement and why</p>", "time": "2026-03-18T01:53:30.000Z"}, {"author": "Dave Plonka", "text": "<p>Re: @mirja's comment, it would be interesting to know why HEv2 was found to be unimplemented except by one browser (Safari) per the TU-Munich research paper linked above.</p>", "time": "2026-03-18T01:56:32.000Z"}, {"author": "Tim Chown", "text": "<p>if you want to ask specific questions please go ahead, or we can ask for you.</p>", "time": "2026-03-18T01:58:55.000Z"}, {"author": "Dave Plonka", "text": "<p>My assumption is that people thought it was complicated and/or low priority (in browsers in recent years, perhaps because IPv6 brokenness has declined, e.g., in commercial ISPs.)</p>", "time": "2026-03-18T01:59:10.000Z"}, {"author": "Tim Chown", "text": "<p>but now of course it's not just about v4/v6</p>", "time": "2026-03-18T02:00:19.000Z"}, {"author": "Dave Plonka", "text": "<p>agreed, and (potentially) even more complicated.</p>", "time": "2026-03-18T02:01:24.000Z"}, {"author": "Tim Chown", "text": "<p>indeed</p>", "time": "2026-03-18T02:01:34.000Z"}, {"author": "Lucas Pardue", "text": "<p>reminds me a bit of how RFC 9002 defines various algorithms related to QUIC loss detection and CC</p>", "time": "2026-03-18T02:03:40.000Z"}, {"author": "Tommy Pauly", "text": "<p>Yeah this is like loss and recovery algorithms</p>", "time": "2026-03-18T02:03:59.000Z"}, {"author": "Lucas Pardue", "text": "<p>so theres an implemention that piick an mixing different things, with different tunables. Its nice to have an algorithm that is just 1 line of pseudocode, even though it doesn't mean much in total isolation e.g. <a href=\"https://datatracker.ietf.org/doc/html/rfc9002#section-6.2.1\">https://datatracker.ietf.org/doc/html/rfc9002#section-6.2.1</a></p>", "time": "2026-03-18T02:05:27.000Z"}, {"author": "altanai", "text": "<p>interestingly there was a IRTF talk about this </p>\n<p>What IPv6 RFCs Don\u2019t Say About VPNs</p>\n<p>How missing guidance led to IPv6 de-preference</p>\n<p><a href=\"https://datatracker.ietf.org/meeting/125/materials/slides-125-maprg-what-ipv6-rfcs-dont-say-about-vpns-02\">https://datatracker.ietf.org/meeting/125/materials/slides-125-maprg-what-ipv6-rfcs-dont-say-about-vpns-02</a></p>", "time": "2026-03-18T02:06:46.000Z"}, {"author": "Bing Sun", "text": "<blockquote>\n<p>\"We notice that with VPNs, v6 is often de-preferred severely\"</p>\n</blockquote>", "time": "2026-03-18T02:10:03.000Z"}, {"author": "Lars Eggert", "text": "<p>So technically, \"MUST\" means \"you need to implement it in this way to be able to claim conformance to this RFC\". So we're fine :-)</p>", "time": "2026-03-18T02:13:03.000Z"}, {"author": "Benjamin Schwartz", "text": "<p>FWIW, I don't _want_ everyone to implement the same client behavior.  That would be boring.  We should have experimentation and diversity.</p>", "time": "2026-03-18T02:15:12.000Z"}, {"author": "Lars Eggert", "text": "<p>@Ben I think there is no danger of that :-)</p>", "time": "2026-03-18T02:16:05.000Z"}, {"author": "Tim Chown", "text": "<p>the way the draft is written is more bcp-like than a strict spec.</p>", "time": "2026-03-18T02:16:07.000Z"}, {"author": "altanai", "text": "<p>yet +1 to your suggestion to add sample implementation algorithms</p>", "time": "2026-03-18T02:16:08.000Z"}, {"author": "Lucas Pardue", "text": "<p>things won't stop evolving, I expect in practice we'll get happy eyeball v3', v3'', etc.</p>", "time": "2026-03-18T02:17:57.000Z"}, {"author": "Tommy Pauly", "text": "<p>I don't think we can make people implement it one place or the other...</p>", "time": "2026-03-18T02:18:27.000Z"}, {"author": "Philipp Tiesel", "text": "<p>@jordi I don't see that for linux\u2026 whishfull thinking rarely brought us anywhere</p>", "time": "2026-03-18T02:19:46.000Z"}, {"author": "Benjamin Schwartz", "text": "<p>I think the greatest value of HEv3 is in (1) reminding people of all the other RFCs they need to comply with, (2) identifying some workarounds for broken/weird configs, and (3) providing a vocabulary for talking about the connection process.</p>\n<p>With all of those things in place, the actual algorithm is pretty trivial and is not where the value is.</p>", "time": "2026-03-18T02:20:19.000Z"}, {"author": "Lars Eggert", "text": "<p>I nominate this as the HE3 logo: <a href=\"https://static.wikia.nocookie.net/kingdomhearts/images/f/f3/LGM_KHIII.png/revision/latest?cb=20200312040146\">https://static.wikia.nocookie.net/kingdomhearts/images/f/f3/LGM_KHIII.png/revision/latest?cb=20200312040146</a></p>", "time": "2026-03-18T02:22:23.000Z"}, {"author": "Mike English", "text": "<p><span aria-label=\"eyes\" class=\"emoji emoji-1f440\" role=\"img\" title=\"eyes\">:eyes:</span></p>", "time": "2026-03-18T02:25:29.000Z"}, {"author": "Mike English", "text": "<p><span aria-label=\"slight smile\" class=\"emoji emoji-1f642\" role=\"img\" title=\"slight smile\">:slight_smile:</span></p>", "time": "2026-03-18T02:25:59.000Z"}, {"author": "Lucas Pardue", "text": "<p>\"deterministic, no side effects\" sounds like the small print on a medicine advert <span aria-label=\"joy\" class=\"emoji emoji-1f602\" role=\"img\" title=\"joy\">:joy:</span></p>", "time": "2026-03-18T02:26:19.000Z"}, {"author": "Brian Trammell", "text": "<p>(side quest for the WG: get a three-eyeballs-looking emoji added to Unicode)</p>", "time": "2026-03-18T02:26:33.000Z"}, {"author": "Tommy Pauly", "text": "<p>Deterministic medicine sounds... concerning</p>", "time": "2026-03-18T02:26:35.000Z"}, {"author": "Benjamin Schwartz", "text": "<p>Stochastic medicine is also not reassuring</p>", "time": "2026-03-18T02:26:58.000Z"}, {"author": "Mike English", "text": "<p>talk to your optometrist to see if mozilla/happy-eyeballs is right for you</p>", "time": "2026-03-18T02:26:59.000Z"}, {"author": "Lucas Pardue", "text": "<p><a href=\"https://simpsons.fandom.com/wiki/Blinky\">https://simpsons.fandom.com/wiki/Blinky</a></p>", "time": "2026-03-18T02:27:28.000Z"}, {"author": "Tommy Pauly", "text": "<p>This is great, Max! Looking forward to seeing telemetry</p>", "time": "2026-03-18T02:28:25.000Z"}, {"author": "Lucas Pardue", "text": "<p>good work, would love to dig into the telemtry but not enough time</p>", "time": "2026-03-18T02:28:49.000Z"}, {"author": "Lucas Pardue", "text": "<p>does firfox support the concept of origin trials?</p>", "time": "2026-03-18T02:30:39.000Z"}, {"author": "Lars Eggert", "text": "<p>We ARE open source, you know. PRs welcome, Eric.</p>", "time": "2026-03-18T02:31:06.000Z"}, {"author": "Brian Trammell", "text": "<p>+1, firefox telemetry has always been a fascinating rabbithole</p>", "time": "2026-03-18T02:31:07.000Z"}, {"author": "Benjamin Schwartz", "text": "<p>A hash is not an encryption algorithm???</p>", "time": "2026-03-18T02:44:37.000Z"}, {"author": "Max Inden", "text": "<blockquote>\n<p>does firfox support the concept of origin trials?</p>\n</blockquote>\n<p>@lucas Firefox does support origin trials That said, I don't think we would offer it for HEv3 given the amount of effort involved.</p>\n<p><a href=\"https://wiki.mozilla.org/Origin_Trials\">https://wiki.mozilla.org/Origin_Trials</a></p>", "time": "2026-03-18T02:44:44.000Z"}, {"author": "Brian Carpenter", "text": "<p>@Ben, there are non-crypto hashes, yes. e.g. RFC9923</p>", "time": "2026-03-18T02:46:32.000Z"}, {"author": "Benjamin Schwartz", "text": "<p>I meant that this is a very weak obfuscation that does not seem to accomplish the privacy goal</p>", "time": "2026-03-18T02:47:09.000Z"}, {"author": "Tim Chown", "text": "<p>10 mins left so locking q to allow wrap up time</p>", "time": "2026-03-18T02:49:38.000Z"}, {"author": "Benjamin Schwartz", "text": "<p>There's always UDP...</p>", "time": "2026-03-18T02:54:45.000Z"}, {"author": "Brian Carpenter", "text": "<p>@chairs, please upload Max's slides to the agenda, thanks</p>", "time": "2026-03-18T02:55:08.000Z"}, {"author": "xiejieling", "text": "<p>If I use ping for a domain name,  when  send a dns query timeout it can retry 3 times after  how is the TTL of ping determined      then the TTL data for ping result is not right</p>", "time": "2026-03-18T02:55:09.000Z"}, {"author": "Benjamin Schwartz", "text": "<p>SCONE seems to think that UDP is sufficient for Client&lt;-&gt;Path signals...</p>", "time": "2026-03-18T02:56:02.000Z"}, {"author": "Lucas Pardue", "text": "<p>\"Distribute NEL policies with DNS\"</p>\n<p><a href=\"https://github.com/w3c/network-error-logging/issues/173#issuecomment-1839433018\">https://github.com/w3c/network-error-logging/issues/173#issuecomment-1839433018</a></p>", "time": "2026-03-18T02:56:52.000Z"}, {"author": "Philipp Tiesel", "text": "<p>For the enterprise use case, just adding \"hey, IPv6/QUIC keeps failing\" to the system logging service would already be very useful</p>", "time": "2026-03-18T03:04:34.000Z"}, {"author": "Max Inden", "text": "<p><a href=\"https://www.happy-eyeballs.net/\">https://www.happy-eyeballs.net/</a></p>", "time": "2026-03-18T03:04:36.000Z"}, {"author": "Max Inden", "text": "<p>Happy Eyeball tester Eric is mentioning</p>", "time": "2026-03-18T03:04:46.000Z"}, {"author": "KHAN Md", "text": "<p>hey <span class=\"user-mention\" data-user-id=\"1556\">@Max Inden</span> , really enjoyed the Firefox talk! you mentioned having some trouble on macOS and Windows 10 right now, what's going on there? are there bugs filed or is it still being figured out?</p>", "time": "2026-03-18T03:04:58.000Z"}, {"author": "Tommy Pauly", "text": "<p>Thanks!</p>", "time": "2026-03-18T03:05:15.000Z"}]