now that we know about our t c S T c P I P suite. And we talked about how we have our TCP versus UDP communications protocols and we talked about our ports and how our ports our communications in points. Now let's take a look at some of our protocols with utilize our ports
and thus our TCP or UDP communications protocols.
So our first protocol that we have is ftp
FTP stands for file transfer protocol. And it's the It's a protocol that we're going to be using when we're just transferring standard files. So FTP is going to be used over port 21 typically, and it's gonna be TCP now. Why? Well, think about this for a second. Why would f t p b A T c p protocol?
TCP is connection oriented
and make sure that we have a connection to our in point first, and then it starts sending the files.
TCP also make sure that the files get there, they're not corrupted and they're in the right order.
That's what we want more transferring a file. We want to make sure the files get there. They're in the right order. That if there's any retransmission needed that we can do the re transmission. So
FTP is going to be file transfer protocol we're gonna want to use TCP for,
and we're going to use DCP for
for standard FTP. There's no encoding our overhead. There's no additional encoding or no additional
encryption of the data that's going on with FTP, so that makes it a bit insecure. If we're transferring files over FTP, that data's clear text, which means that anyone that can be listening in on that data can take that data and interpret it and just download those files, too.
So F t p a report. 21 TCP file transfer protocol No encoding overhead. But that also means bit insecure.
Next, we have T F T P T F T P stands for Trivial file transfer protocol,
and that is going to allow us to send to multiple clients at once.
Trivial file transfer protocol is going to be a report 69
and it's going to be UDP now.
When we talked about TCP, we mentioned that TCP is a 1 to 1 connection.
Trivial FTP allows us to send too many clients at once. That's not a 1 to 1 connection. So for a trivial FTP, we're going to be using UDP
a little bit easier. Way to think about it is if something's trivial, it's not very important.
So we don't really We aren't super concerned if it gets there or not.
What protocol do we use it for? Not super concerned if something gets there or not.
Ew dp because you'd if he doesn't. UDP is a connection list communication protocol. So does not verify that that that that package gets there, So
ew dp our connection Lis Communications Protocol is going to be in charge of taking our t FTP connection. Breaking up those packages and just sending them rather than verifying that they get there and t f t p is going to be again over Port 69.
Next, we have s f t P s f T P stands for secure file transfer protocol, and this is typically typically going to be over. Port 22.
Now s FTP secure. FTP is going to encrypt our data using sshh
s S H stands for secure shell and we'll talk a little bit more about secure shells and another protocol we get into later. But s FTP runs over port 22 it's TCP again. This is not a trivial file transfer protocol. This is a file that we want to make sure gets there. So we're going to be running it over.
We're going to be using our TCP communications protocol
in order to verify that when we break up that packet it gets there gets in the right order, especially since it's encrypted, because that data needs to be exactly right so that when we decrypt it, it's not corrupted.
So again it encrypts using SS H report 22. And it's more secure, obviously than FTP because it encrypts the data using sshh. So if we have data that we're file transfers that were encrypting we're using sending those over sftp on, we're encrypting them with sshh secure shell.
Next up, we have some of our male protocols.
Now, these are going to be SMTP
pop three, and I map that we have that we're gonna start a start off with right now.
SMTP stands for simple male transfer protocol. Simple male transfer protocol allows us to send email from a client such as outlook to a server and also allows those servers to send email between each other. So
from our outlook computer for our computer, from outlook to Microsoft
servers to the Yahoo servers if we're sending an email to a Yahoo client
is going to be SMTP Simple male transfer protocol.
Now we want to make sure that email messages get there and get there in the right order and that all the packets get assembled correctly. So that's going to be
Think anything that we would be extremely upset if that didn't get there or it was corrupted.
It's typically going to be TCP because we want to make sure it gets there and gets her in the right order.
SMTP runs over Port 25
SMTP knowing the port in up the vault port number for that is very important, especially for opening up firewall rules to allow outbound SMTP traffic. SMTP Port 25
TCP Protocol an SMTP again, a simple male transfer protocol, and it's e mailing. It's the email messages transmitting between servers and from our client sending to a server.
Next, we have getting the email from our servers Pop. Three and I map. This is going to be when we pull the email's down from our server to our client. They're not gonna be when we send our They're not the protocols we use. When we're pushing the emails to our server,
our first protocol, pop three, is going to be running a report 1 10
and his TCP again. We want to make sure that we get it and get in the right order.
Pop. Three stands for post office protocol version three.
Pretty easy to remember that it's an email protocol. Post office, post office protocol version three.
This is gonna be a client download from the server. So
we now are in the situation where we got sent an email to our server and we're going to download it onto our computer. We're gonna pull that email down into our in box on our computer, and we're using pop three.
is a little bit less robust
protocol to pull email with because by default, pop, three is going to copy the email down from the server to our client, and then it's gonna delete it off the server.
this is not as this Not very good if we have multiple devices that were pulling email's down from our server with because they're not going to coordinate between our different devices. If those email inboxes air the same because if we pull e mails from our server on one device and then try to pull them from a different device,
then we're gonna have Oh, I have e mails here that I don't have on this device. And I hav e mails on this device that I don't have on this device
because they're not going to coordinate between our different devices to make sure that our in boxes are the same across all of our devices. But this can be changed,
pop three. The default is to copy, then delete, but that can be changed on our server side.
But just remember that by default it does copy and then delete
on and then pop three Port 1 10
um, client download from the server.
And then lastly, we have I'm at I'm at
is our more robust version of pop three,
and it's gonna be running over port 1 43 and it's going to be TCP now. The reason we say I map is a bit more robust is because it allows us more configuration ability than pop. Three. Does I'm at is going to by default keep a copy of the message on the server before it delivers it to our client.
So we're down. It's the same as Pop three, where we're downloading
a message from the server to our client. But I'm app is going to download that message,
and it's going to keep a copy on the server. So if we have multiple devices that air pulling via my map from our server, then we're going to be pulling those messages and our server's gonna keep a copy, and that can help us be consistent across all of our different devices. So
of our email protocols SMTP is sending from our client to our server and then, in between our servers. It's a report 25 it's TCP
pop. Three is post Office Protocol three. It's going to be over Port 1 10 and it's TCP is going to download, then delete and I'm app downloads but keeps a copy on our server, and it's a report 1 43 and it's also TCP