13 hours 57 minutes
Hello. Welcome back to I see into you one interconnecting Cisco networking devices. Part one.
This is up sewed 11 to T C P I p model. I am trending Daryl and I will be the instructor for this course
in the last video of one over some basic questions about the TCP I P model and also the OS I model.
In this episode, we're gonna be covered on Lee the TCP I p model
learning objectives for this episode,
we're gonna learn the layers of TCP epi model.
We're gonna go over the history of it.
And lastly, we're gonna look at the common protocols in each layer.
All right, so first, we're gonna get into a quick pre assessment.
So we're gonna look up the layers of the TCP I P model. Hopefully, by now, you kind of got a general idea by looking up some of the other questions.
Otherwise, I'll give you a few moments here to pause the video and look it up.
Okay. Hopefully you got it already. We're gonna go ahead and continue. I'm gonna bring up the answer.
All right, So this is actually the updated TCP I P model some of the models you might see, you might see the data link in the physical layer or physical network layer
combined it a one just called the Linklater Sometimes.
Well, you're gonna have your application. Layer your transport, layer your Internet layer your data link layer on your physical network layer.
So we're gonna go over the quick history of C C P I. P. Model. Originally, when networking first started, we had these vendor specific protocols that only supported their equipment.
And network engineers not only had to learn each of these protocols, but they had to support them as well.
So if a company used two different vendors for computer systems, he never comes near now, had to create two different networks for those systems.
So you see, if you had multiple companies and you had mergers that all had to create different networks and I had to find a way to communicate those networks, it was a little difficult.
Now he's vendor Specific protocols worked pretty well for their products with the International Organization for Standardization. R I S O started work on the OS I model in the late 19 seventies to try and create a standard model in order to get all the computers to be able to talk to each other
instead of going down this vendor specific model.
Now, I did get a little traction, but didn't, you know, didn't quite take off. But the d o. D actually contract out the work on another model in the early eighties.
And that actually got more attraction, which later became the TCP I P model.
In the early nineties, these company had both the O S I and the TCP I p model and their service is and their devices.
But by the late nineties, the TCP I P model had become successor between Aussie TCP
of some vendor Specific protocols do exist still like the Apple Talk protocol,
but they're not quite as used, and they still have the other T c P I P stack, as it might be called
other devices. That way they can communicate on the Internet.
So a t c p I p model. Here we have the two. You see the two different models. The top one is the new model or the updated model.
And on the bottom, you see the older bottle that combines the link
layer or the data links layer and the physical Aaronson link or network interface layer.
So the one good thing that T c p i p model does. They didn't trying to rewrite the book out everything. You know, they already used the existing IEEE standards that were in place, like 802.3. Ethan, that standard, they didn't try and rewrite it. They just took it, you know? So that was already there
and use it. Utilize it.
The original T Z P I. P model is actually defined in our C 11 22.
So if we look at the bottom picture there, you can kind of see,
So when you're sending data out, you're gonna go from the application layer
and then when you're getting information back in here, you're gonna go up the stack like this.
But if you look at some of these protocols for each layer,
remind this this is oh aside for now,
we're looking at TCP.
So if we look at application layer looking ftp or your file transfer protocol telling, that's which, hopefully you're not using too much anymore S and M P
http ss a chair throwing that transport looking a TCP verses UDP
the Internet layer You're looking at I p r. But I see MPRP is the address resolution protocols we said in the last video,
and we're gonna learn about that in this course, So don't worry. I see appears like your ping command. Almost. If you don't think of it like that,
the data link layers your point, the point protocol, and you're IEEE able to to physical network. They're gonna be looking at, you know, physical standards like the actual Ethernet standards like the U T. P cabling
the categories in token ring Zara's to 30 twos.
So finally we get to the post assessment here, which d c p I P layer deals with common user programs.
This one hopefully shouldn't take you too long, But I'll give you just a moment deposit video and go back to it.
All right, so hopefully figure it out.
I should be the application layer.
As we said in the previous slides,
looking at http
and other programs that users commonly use
on the next episode, we're gonna be talking about T C I p model layers. That's gonna be the application layer transport layer Internet layer. The network access layer, which you gotta remember. The Ark axis layer is also broken up into the data link and physical layer.
And once again, if you guys have questions, you need help. Or if you have a funny photos, go ahead and feel free to contact me. Thank you. And I look forward to seeing you and Nice, of course.
This course will enable students to understand virtualization and cloud services, and network programmability related to LAN, access and core segments.