Hi, I would like to support this proposal as well. We at number 0 have implemented this draft already for use in iroh [0]. We are currently in the first stage of rolling this out and it is currently enabled in production next to STUN. We have also done successful interoperability testing between our implementation and the one in picoquic. And we are in the process of upstreaming this work into Quinn [1].
The motivation for us to adopt this is basically laid out in the introduction of the draft: QAD is encrypted and uses a reliable transport. Getting back the grease bit (eventually) and having it event driven rather than STUN's request-reply are very nice bonuses. So it would be great if this can be adopted. Cheers, Floris [0] https://iroh.computer [1] https://github.com/quinn-rs/quinn/pull/2043 On Tue 11 Feb 2025 at 02:59 +0000, Lucas Pardue wrote: > Hello QUIC WG, > > During IETF 121 we discussed draft-seemann-quic-address-discovery [1] and the > sense in the room was that this is something the WG should work on. > > This is a formal adoption call that will run for 2 weeks, ending on February > 25 2025 at 23:59 anywhere on earth[2]. Please respond to this email thread > with any comments indicating support or objection. In either case, > elucidation of your opinion would be appreciated. > > Kind regards > Lucas & Matt > QUIC WG Chairs > > [1] - https://datatracker.ietf.org/doc/draft-seemann-quic-address-discovery/ > [2] - https://time.is/Anywhere_on_Earth
