I can't believe we've already arrived at the end of this module.
That went really quick. But don't worry,
as this was just a primer for what we're about to jump into. Right now,
we're still in the shallow end of the kids' pool,
but we're just about ready to dive headfirst into the deep end
of our Olympic‑size TCP/UDP swimming pool.
But before we take that extra deep dive,
let's take a moment and review everything we've covered so far.
First, we learned about the role TCP and UDP play within our daily lives,
whether it's a 911 application,
utilizing TCP and reliably routing that to an
ambulance or that crucial cell phone call.
Or it could even be a video conferencing session, both utilizing UDP.
our critical and not so critical applications, step counter app, I'm
talking to you, depends on a correct and proper operation. And if any
metric is not working as expected,
you'll be the one looked at to successfully
troubleshoot and correct the operation.
Next,
we learned that a port is actually a service that is being
offered on a server and how it's similar to a supermarket
aisle offering multiple goods.
Just remember to check that expiration date on the milk.
Next, we saw a substantive, high‑level overview of TCP.
During this high‑level overview,
we learned how TCP provides reliable communications through the
establishment and termination of sessions.
We were also presented with a high‑level overview of an actual TCP session.
We also discovered how TCP can request missing data.
Finally,
we completed a high‑level overview of UDP and learned that UDP provides best
effort lightweight traffic to successfully deliver its payload.
Remember, UDP is best effort.
It's not an unreliable protocol.
We were also presented with a high‑level overview of
an actual UDP DHCP request session.
Well,
I hope you're as excited as I am for the next module, as we are
going to dive deep into the theory of TCP and UDP and do a
complete breakdown of each protocol.
Let's hop off our giant rubber duck floaties. It's time to dive in.