> On 26. Aug 2024, at 22:46, Martin Duke <[email protected]> wrote: > > Thanks to everyone who's provided feedback! I hope to publish draft-01 soon. > > I have a strange question: does it ever make any sense to bind or connect to > an IPv4-mapped IPv6 address (i.e. ::ffff:<Ipv4_address>)? I've been > experimenting with this, and the results are Sure. You are using a single AF_INET6 socket, but connect to an IPv4 address. That is a valid use case.
Best regards Michael > sometimes goofy for each platform. Is this even worth addressing in the > draft, or is it too silly of a use case? > > On Fri, Aug 23, 2024 at 12:39 PM Martin Duke <[email protected]> wrote: > Hi TSVWG and QUIC, > > I've made it some of the way through implementing receive ECN for Chromium, > which involved quite a bit of trial and error in figuring out the quirks of > the Apple and Windows UDP socket APIs. > > This is an informational draft that tries to capture some of that learning, > since hopefully more QUIC implementations will add ECN support across > multiple platforms. > > Obviously, this is a work in progress. People that have worked with other > OSes, or that can see into the kernel code and update/correct/refute some of > my statements here, are welcome to contribute. > > My guess is that it fits into TSVWG, although it is mostly of relevance to > QUIC folks. If people are really interested in it, we could adopt it TSVWG. > If not, at least there's a record somewhere so that others don't have to > suffer as I did. > > Martin > > ---------- Forwarded message --------- > From: <[email protected]> > Date: Fri, Aug 23, 2024 at 12:33 PM > Subject: New Version Notification for draft-duke-tsvwg-udp-ecn-00.txt > To: Martin Duke <[email protected]> > > > A new version of Internet-Draft draft-duke-tsvwg-udp-ecn-00.txt has been > successfully submitted by Martin Duke and posted to the > IETF repository. > > Name: draft-duke-tsvwg-udp-ecn > Revision: 00 > Title: Configuring UDP Sockets for ECN for Common Platforms > Date: 2024-08-23 > Group: Individual Submission > Pages: 9 > URL: https://www.ietf.org/archive/id/draft-duke-tsvwg-udp-ecn-00.txt > Status: https://datatracker.ietf.org/doc/draft-duke-tsvwg-udp-ecn/ > HTMLized: https://datatracker.ietf.org/doc/html/draft-duke-tsvwg-udp-ecn > > > Abstract: > > Explicit Congestion Notification (ECN) applies to all transport > protocols in principle. However, it had limited applications for UDP > until QUIC became widely deployed. As a result, documentation of UDP > socket APIs for ECN on various platforms is sparse. This document > records the results of experimenting with these APIs in order to get > ECN working on UDP for Chromium on Apple, Linux, and Windows > platforms. > > > > The IETF Secretariat > >
