Re: [v6ops] Happy Eyeballs, v3!

Hi Jordi,

Thanks for the review.

You certainly can feel free to open some issues on the repo (https://github.com/tfpauly/draft-happy-eyeballs-v3/issues) to incorporate other points! If we decide to adopt this effort for a -bis, it’s a good opportunity to update things.

Personally, I think any mechanism like the ones you linked to that are adding active reporting protocol actions would be better as a separate document (since the core of HE is a local-only algorithm), but I think we could have the main HE document refer to these other techniques.

Best,
Tommy

> On Oct 23, 2023, at 1:08 PM, jordi.palet@consulintel.es <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
> 
> Hi,
> 
> I like the new ideas incorporated in HEv3 and I think they are useful.
> 
> However, as indicated in section 10.3, HE hides operational issues and we know it for a long time. I think this document is a big opportunity to tackle that.
> 
> Possible solutions were depicted in:
> https://datatracker.ietf.org/doc/draft-palet-v6ops-he-reporting/
> https://datatracker.ietf.org/doc/html/draft-xie-v6ops-network-happyeyeballs-01
> Of course, we can do that continuing with those documents apart form HEv3, but I think it will be wiser to incorporate the solution in HEv3 already.
> 
> What HEv3 authors and others think?
> 
> 
> Regards,
> Jordi
> 
> @jordipalet
> 
> 
>> El 23 oct 2023, a las 11:38, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org> escribió:
>> 
>> Hello v6ops,
>> 
>> We’ve just published a new draft for “Happy Eyeballs Version 3”, which is intended as a -bis document to RFC 8305 (which was developed in this WG). There are a few major points that needed updating:
>> 
>> - Describing how to incorporate SVCB / HTTPS RRs
>> 	- Priority
>> 	- v4/v6 hints
>> 	- Affect on various timers, etc
>> 	- ECH, ALPN, etc
>> - Describing how happy eyeballs applies to QUIC (and also TLS over TCP)
>> 
>> The bulk of the document is the same as RFC 8305, but updates the logic and algorithm for these changes.
>> 
>> Please take a look! We’d love to discuss at IETF 118 as time permits.
>> 
>> Best,
>> Tommy
>> 
>>> Begin forwarded message:
>>> 
>>> From: internet-drafts@ietf.org
>>> Subject: New Version Notification for draft-pauly-v6ops-happy-eyeballs-v3-00.txt
>>> Date: October 23, 2023 at 9:34:00 AM PDT
>>> To: David Schinazi <dschinazi.ietf@gmail.com>, Kenichi Ishibashi <bashi@google.com>, Nidhi Jaju <nidhijaju@google.com>, Tommy Pauly <tpauly@apple.com>
>>> 
>>> A new version of Internet-Draft draft-pauly-v6ops-happy-eyeballs-v3-00.txt has
>>> been successfully submitted by Tommy Pauly and posted to the
>>> IETF repository.
>>> 
>>> Name:     draft-pauly-v6ops-happy-eyeballs-v3
>>> Revision: 00
>>> Title:    Happy Eyeballs Version 3: Better Connectivity Using Concurrency
>>> Date:     2023-10-23
>>> Group:    Individual Submission
>>> Pages:    18
>>> URL:      https://www.ietf.org/archive/id/draft-pauly-v6ops-happy-eyeballs-v3-00.txt
>>> Status:   https://datatracker.ietf.org/doc/draft-pauly-v6ops-happy-eyeballs-v3/
>>> HTML:     https://www.ietf.org/archive/id/draft-pauly-v6ops-happy-eyeballs-v3-00.html
>>> HTMLized: https://datatracker.ietf.org/doc/html/draft-pauly-v6ops-happy-eyeballs-v3
>>> 
>>> 
>>> Abstract:
>>> 
>>>   Many communication protocols operating over the modern Internet use
>>>   hostnames.  These often resolve to multiple IP addresses, each of
>>>   which may have different performance and connectivity
>>>   characteristics.  Since specific addresses or address families (IPv4
>>>   or IPv6) may be blocked, broken, or sub-optimal on a network, clients
>>>   that attempt multiple connections in parallel have a chance of
>>>   establishing a connection more quickly.  This document specifies
>>>   requirements for algorithms that reduce this user-visible delay and
>>>   provides an example algorithm, referred to as "Happy Eyeballs".  This
>>>   document updates the algorithm description in RFC 8305.
>>> 
>>> 
>>> 
>>> The IETF Secretariat
>>> 
>>> 
>> 
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops