User Datagram Protocol
Internet protocolWikipedia
123
MENTIONS
33
EPISODES
27
PODCASTS
Search complete. 123 mentions across 33 episodes found for "User Datagram Protocol".
Oct 3, 2026
speaker_0HOST
Moving away from TCP...
speaker_1GUEST
Yeah, there is a massive engineering movement pushing away from TCP entirely, moving toward UDP-based protocols like QUIC and WebTransport.
speaker_1GUEST
These newer protocols allow for independent streams of data, completely eliminating head-of-line blocking.
speaker_0HOST
So the very protocol that made the real-time web possible might eventually be abandoned for something even faster.
Eric DavisGUEST
Yeah.
Rip SohanGUEST
So let's talk about ECMP, right? So right now in the TCP world, how do I load balance my flows across the network? What I do is I set up my flows and I make sure that the UDP source port of these flows is not the same, right? So from a given source to a given destination in terms of layer three, I am making sure that...
Rip SohanGUEST
even though the source and destination IP address is the same, I'm perturbing the UDP source port.
Rip SohanGUEST
And by perturbing the UDP source port, I'm able to spread my flows across networks.
Rip SohanGUEST
Now, what we're doing today in TCP is that for a given flow, that UDP source port is exactly the same for all the packets for that flow.
Rip SohanGUEST
MRC takes that a step further.
Rip SohanGUEST
It makes that a per packet decision.
Rip SohanGUEST
So same flow, right? Flow number one, but each packet has a different UDP source port number.
Rip SohanGUEST
Yeah.
Rip SohanGUEST
So, so let's talk about ECMP, right? So right now in the TCP world, how do I load balance my flows across the network? What I do is, I, I set up my flows, and I make sure that the UDP source port of these flows is not the same, right? So from a given source to a given destination in terms of layer three, um, I am making sure that, uh, um, uh, even though the source and destination IP address is the same, I'm perturbing the UDP source port, and by perturbing the U- UDP source port, I am able to spread my flows across networks.
Rip SohanGUEST
Now, what, what we are doing today in TCP is that for a given flow, that UDP source port is exactly the same for all the packets for that flow.
Rip SohanGUEST
MRC takes that a step further.
Rip SohanGUEST
It makes that a per packet decision.
Rip SohanGUEST
So same flow, right? Uh, flow number one, but each U- each, each packet has a, has a different UDP source port number.
Rip SohanGUEST
The existing ECMP hashing still works as, as intended, but what happens is rather than on a flow level, on a packet level, things get spread all over the network.
Ethan BanksHOST
Mm.
Rip SohanGUEST
Yeah.
Rip SohanGUEST
So, so let's talk about ECMP, right? So right now in the TCP world, how do I load balance my flows across the network? What I do is I, I set up my flows, and I make sure that the UDP source port of these flows is not the same, right? So from a given source to a given destination in terms of Layer 3, um, I am making sure that, uh, um, uh, even though the source and destination IP address is the same, I'm perturbing the UDP source port, and by perturbing the U- UDP source port, I am able to spread my flows across networks.
Rip SohanGUEST
Now, what, what we are doing today in TCP is that for a given flow, that UDP source port is exactly the same for all the packets for that flow.
Rip SohanGUEST
MRC takes that a step further.
Rip SohanGUEST
It makes that a per packet decision.
Rip SohanGUEST
So same flow, right? Uh, flow number one, but each U- each, each packet has a, has a different UDP source port number.
Rip SohanGUEST
The existing ECMP hashing still works as, as intended, but what happens is rather than on a flow level, on a packet level, things get spread all over the network.
Ethan BanksHOST
Mm.
George MichaelsonGUEST
It's an interesting,
Colin DoyleGUEST
if I can pause you, it's an interesting contradiction that streaming, I think most of us would naturally associate with UDP.
Colin DoyleGUEST
So the terminology flips a little bit there.
Colin DoyleGUEST
It does.
9 MINS LATER
George MichaelsonGUEST
He's not.
George MichaelsonGUEST
He's listening on one hole and he's talking serially down a whole chunk of them.
Colin DoyleGUEST
Well, and certainly with like discovery protocols, you kind of blend both where you can use the UDP side of this to push just really simple discovery messages.
Colin DoyleGUEST
And then when you get responses, those responses give you the information you need to then establish that session connection.
Brian JohnsonHOST
So once that list is set up, everything is allowed.
Brian JohnsonHOST
The IPs get a TCP/UDP scan.
Brian JohnsonHOST
They get a Shodan scan.
Brian JohnsonHOST
All those-- Uh, oh, and a N- and a Nessus scan.
JustinHOST
Uh, one technical piece, and then we'll jump into some, uh, bug bounty [laughs] drama that is happening i- in the community right now.
JustinHOST
But, um, so recently, uh, the Port Swigger team dropped Turbo Intruder 2, uh, which optimizes, um, the HTTP request even further using HTTP3, which is a UDP-based protocol.
JustinHOST
And [laughs] the write-up says that they have achieved 100,000 requests per second using, uh, Wi-Fi.
JustinHOST
[laughs] Just, like, normal Wi-Fi, not even like a-
JustinHOST
Y- you know, I don't know.
JustinHOST
And I was t- I, I was looking into it a little bit because I was like, man, I, you know, I, I'm, I feel like I'm just now getting a grip on HTTP2, and now they're talking about HTTP3, you know? And, uh, it, it is, um, it is, it is tricky, man.
JustinHOST
Uh, so this is a UDP-based HTTP, right, um, uh, as well.
JustinHOST
And, uh, man, it, it seems like that solves a lot of the speed, you know, issues because-
Justin BrodleyHOST
The Azure Application Gateway now supports HTTP3 over QUIC in public preview, and reducing connection setup time and latency for web apps, APIs, and mobile experiences.
Justin BrodleyHOST
This is by changing the way the TCP handshake occurs on your HTTP3 request versus the TCP-based HTTP2 connections, because it is UDP-based.
Justin BrodleyHOST
Configuration happens at the listener level, giving customers granular control to enable HTTP slash three selectively on basic listeners rather than the gateway wide.
Justin BrodleyHOST
During preview, setup is available through the Azure portal or REST API.
Andy JhaHOST
It has 18 attack methods total that were advertised.
Andy JhaHOST
HTTP floods, slow HTTP connections, TCP and UDP floods, TLS stress, reflections, amplification attacks, kind of a standard DDoS toolbox.
Adam BrewerHOST
Mm-hmm.
Andy JhaHOST
But it also had a stealer.
BaluHOST
It provides two static anycast IP addresses that act as a fixed front door and don't change, and it offers fast regional failover based on health.
BaluHOST
Crucially, it's ideal for non-cacheable traffic, including TCP and UDP workloads, which is exactly what the question describes here.
BaluHOST
Now let's eliminate the others.
BaluHOST
Option A, CloudFront is a content delivery network that caches content at the edge.
BaluHOST
It's excellent for cacheable content like images and video, but the question specifically calls out for non-cacheable TCP and UDP traffic and static anycast IPs, which is global accelerators domain, not CloudFronts.
BaluHOST
Option B, Route 53 simple routing just returns a DNS record with no performance acceleration, static IPs or failover.
BaluHOST
And option C, a network load balancer alone is regional and doesn't route traffic globally over the AWS backbone with static anycast IPs.
BaluHOST
The keywords here are route over AWS global network, static anycast IP addresses, fast regional failover, and non-cacheable TCP and UDP.
23 more episodes mention User Datagram Protocol.
Create an account to see the whole feed, search across every transcript, and follow the entities you care about.