: 'The source of all things networking'
Subject: RE: QUIC, Connection IDs and NAT
The first thing that comes to mind is to check the NAT timers.
By default, TCP is 86400 seconds or 24h.
Udp is usually shorter at around 300 seconds or 5 minutes.
This is not a standard, but it seems to
ject: QUIC, Connection IDs and NAT
QUIC has Connection IDs independent from IP. This was done to make it
easier to move from one IP network to another while keeping connections
active, as most here will know.
Does the existence of Connection IDs separate from IP mean that the host/IP
contention ratio in
the 5tuple includes protocol so increased adoption of QUIC alongside
TCP bound services effectively does increase the potential size of the
NAT binding table but if we're really a single-browser model and all
going to QUIC enabled webs, the effective outcome is to burn the port
space in UDP, not in
It appears that Robert Brockway said:
>Does the existence of Connection IDs separate from IP mean that
>the host/IP contention ratio in CGNAT can be higher? IE, can a single
>CGNAT device provide Internet access for a greater number of end-users?
No, QUIC runs over UDP which runs over IP. QUI
QUIC has Connection IDs independent from IP. This was done to
make it easier to move from one IP network to another while keeping
connections active, as most here will know.
Does the existence of Connection IDs separate from IP mean that
the host/IP contention ratio in CGNAT can be higher? I
5 matches
Mail list logo
