W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2021

Re: UDP source ports for HTTP/3 and QUIC

From: Willy Tarreau <w@1wt.eu>
Date: Thu, 15 Jul 2021 11:29:37 +0200
To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
Cc: Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20210715092937.GC27830@1wt.eu>
On Thu, Jul 15, 2021 at 10:56:28AM +0200, Mikkel Fahnøe Jørgensen wrote:
> It is perhaps worth noting that due to QUIC (optionally) having unique
> connection identifiers, it is feasible to have many connections on the same
> source port. Therefore that could be a recommendation in cases where some
> source ports might be blocked.

I think that this is an excellent idea! The simple fact that this is
being discussed precisely is because the source port serves no purpose
here other than being compatible with UDP. So basically we could have
a recommendation that each application preferably uses a single socket
and source port for outgoing communication. This will also lower the
stress on source port allocation (and recycling) as well as the need
for file descriptors.

Received on Thursday, 15 July 2021 09:30:05 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 15 July 2021 09:30:06 UTC