Did TCP just CHANGE???
HTML-код
- Опубликовано: 8 сен 2022
- In August 2022, a new RFC covering the TCP protocol was released. Is this a new version of TCP, or just an update? In this video we look at the new standard and discuss what has changed and why a new RFC was needed.
www.rfc-editor.org/info/rfc9293
Want some hands on with TCP? Consider taking one of my courses.
== More On-Demand Training from Chris ==
▶Getting Started with Wireshark - bit.ly/udemywireshark
▶Getting Started with Nmap - bit.ly/udemynmap
== Live Wireshark Training ==
▶TCP/IP Deep Dive Analysis with Wireshark - bit.ly/virtualwireshark
== Private Wireshark Training ==
Let's get in touch - packetpioneer.com/product/pri... 
Наука
There is a new TCP RFC in town! What?!? Let's take a look to see what changed. www.rfc-editor.org/info/rfc9293
Thanks Chris! This is actually good! I always had to shuffle through multiple RFCs to completely understand TCP. Having it in one pretty good.
Thanks for the comment Hussein, totally agree that it is nice to have this all in one spot!
Thanks for keeping us educated on the changing landscape of all of the OSI Layers!!!
Thanks for watching!
Hi Chris, love your videos buddy!! Would be great to see a series of yours on routing protocols with the main focus on packet captures to deep dive into the important bits we should be inspecting!
Great colab with David ;) We need more videos like that :)
Thank you! More to come for sure
i was 14 in 1981 sorry chris i m older than u b ut i m learning great stuff from u so God bless u
Once again, very good job explaining the process/changes.
In 1981, I started high school.
The best IT Channel I follow! Thanks for all the work here! ;-)
Thanks for the comment!
your videos is super great, makes me much educated, thanks for the work!
Thank you!
Thanks Mr. Greer for the timely reporting of this change.
You’re welcome!
Your just an amazing teacher. I really get excited when you drop a new video.🤘
Thank you!
Thank You Chris!
Thanks for the TCP video Chris 👍....keep doing videos ...keep us educating 👏
More to come!
Tha is for the content on this Chris! Can't wait for the next deep dive super low level video! 😋
I’ll keep it coming.
Well, I was 19 in '81... Started in networking at age 20... On mostly IBM 3270, in the days of VTAM, 2400bps modems, acoustic couplers and all that fun stuff. Great channel chap.
Great intro, thanks
Thanks for the comment!
Thanks for reminding, what about new rev of MTCP?
I was 12 in 1981, dialing up BBSs with my Atari 1200XL. Good times, but I'm sure glad we no longer communicate at 300 Baud.
Hey Chris thanks again for you video and for helping us being better network engineers. 1981, i was minus 9 xD
Can one decrypt ios / android mobile data transferred via windows laptop hotspot where wire shark installed on the laptop
awesome. didn't even know they released a new RFC for tcp
wasn't even here back in 1981
awesome thumbnail btw!! 😁😁😁
Thanks! Yeah no joke. This RFC almost slipped by me too.
I was there that year
Networking and OSI are super interesting. I love that I saw "change to TCP?" and I had to click on it right away.
Hey Chris. Do you think that WCNA certification along with Network+ and Public cloud networking certs (AWS, GCP, Azure) would be good substitute for CCNA?
I would just do CCNA
I don't think the WCNA is a good replacement for a proper networking cert. I'd go NET+, CCNA, Cloud to start!
The thing about CCNA is it's VERY common for employers and job advertisements to specifically request CCNA cert or CCNA level knowledge. Everybody knows what it is, so it's what employers look for.
chris in 1981 my mother was teenage
RFC 793, Sept 1981. I was 17 going on 18, and in US Navy Basic Electricity and Electronics school at Great Lakes Naval Training Center, in North Chicago IL.
From one Vet to another, thank you for your service brother!
@Dwayne I was attending that same school but in 2000. Thank you for your service!
@@Shalom_Mike Thanks to both of you.
Thanks @MikeL, @Victor and @Fred for your kind words. I served in (more or less) peacetime (well, there was that little dust-up in the Falkland in '82, the attack on the Marine Barracks in Beirut in '83) while I was in, but nothing like the late 90's through today.
Nice one. Does the real world network now days depend in PMTU discovery ? I had done capture for a Realtime issue and couldn't see any ICMP type 4 and code 3 messages(no FW in between). In this case how the TCP decides the MSS ?
I don't see PMTU too much in the wild these days. Mostly since things have standardized quite a bit across IP networks. As mentioned in this RFC - www.rfc-editor.org/rfc/rfc6691 - The TCP MSS is based off of the IP MTU. If the IP MTU is 1500, then the TCP MSS will be 1500 - 40 - (other IP or TCP options). You can tinker with this value by adjusting the IP MTU on your NIC. If you made that value 1300 for example, the TCP SYNs your machine sends out will likely be 1260.
@@ChrisGreer Thanks a lot Chris. That's interesting. I've seen most of TCP flows having DF bit set. So in case of any additional overheads (MPLS/VXLAN) can cause the TCP packet to be dropped(since df bit set) ? How the TCP MSS will be adjusted dynamically (in absence of PMTU)?
@@alanh6168 Try search on TCP MTU black hole detection.
1981? I was, (cough, cough - gasping for breath), 35 years old, Sir.
I wonder what the practical impact it will have with network stack drivers. That’s a LOT of old equipment out there which is running but no longer supported and no software updates will be forthcoming.
That equipment will be fine. TCP establishes all the stuff in the handshake.
no impact since this RFC is just a "unified document" of several TCP changes over the years that where spread through multiple RFCs. Nothing changed in TCP itself with this RFC.
Nice
Not going to lie here, the first thing I thought of, was QUIC going to play a bigger role with TCP... nope, awesome vid Chris!!
Thank you!
Was 5 years before production in 81
I was 7 in '81.
wow, a piece of History right here. Thanks Chris, I'm waiting and wagging my tail for that master course you promised on Mr. Bombal's channel :3
Nice, thanks for the reminder. In the meantime - have you checked out the Udemy course? It goes into TCP and all the important stuff.
@@ChrisGreer in honor to honesty, only if you help me with that course to get a job haha. We all gonna appreciate it Chris, thank you and blessings :)
i was born in April '82 so i was a mere glint in the milkman's eye in '81
Haha! I was 1 just learning to walk so... not much further into life.
I was 5
Whats new in this new rfc?
Nothing important. This RFC is just a "unified document" of several TCP changes over the years that where spread through multiple RFCs. Nothing changed in TCP itself with this RFC.
It’s putting TCP in one place. Like the video shows, there are lots of outdated or obsolete things that are not in modern implementations, as well as current stuff that is spread across several RFCs.
I was minus 2 in 1981
I was -19 years old 😁
Amazonaws and Cloudfront are gonna hate this, no that they have been DDOSing this past 2 years ;-)
-9 years in 1981!
in 81 I was 10 :/
Young boy at 1 yo! 🙂👍
Me too!
@@ChrisGreer and still young! 😉
First Like👍
I'm from 1988(( Not so old as TCP guy.
troubles sleeping? Not enough stress and confusion in your life? Want to feel like a real moron? Try reading an RFC like this one. Holly cow it just goes on and on and on.
Haha! It’s true. A great cure for insomnia. However it’s nothing like the QUIC RFC!
I remember reading 802.11b while trying to troubleshoot a wireless mesh network that was preferring its weakest links. Holy tedium, what a garbled mix of optimizations for reliability and reasonably fast failure.
Please don't do the stupid youtube thumbnail face
Thanks for the insights dude
Thanks Faran!
Thanks Cris, you have a good way to explain things. PD: The RFC 793 is older than me. 🥹