internet protocol suite

References

Summary

It tells computers how to interact over a network

It's made up of 4 layers:

  1. Application
  2. Transport
  3. Internet
  4. Link

As data gets passed through each of the layers, it gets encapsulated —- new data gets added to it

1. Application

How the user interacts with the network

HTTP (hypertext transfer protocol)

The browser sends a GET or POST request to the server

HTTPS uses TLS/SSL to encrypt the HTTP data

Uses port 443

Internet Service Providers use caching proxies: if someone else on th network downloaded something, the ISP will retain a local copy in its cache

HTTP is very lightweight

SSH (Secure Shell)

Used for remote administration Creates a persistent, encrypted session.

Uses public/private keys

Once you have the SSH set up, you can send things through it

DNS (Domain Name System)

When you type a URL, the system sends a DNS query for the corresponding IP address

FTP/SFTP (File Transfer Protocol)

HTTP wasn't originally designed for file transfer; FTP was

FTP is stateful

Original FTP sends everything in plain text, while SFTP uses SSH

FTP uses 2 connections:

  1. Commands
  2. Data

There are some issues with FTP

Because FTP was designed for file transfer, it has built-in tools for things like

Backing Up Files

Google Drive and Dropbox use HTTPS

Private servers often use SFTP

You use SFTP when you already have a secure shell set up

2. Transport

User Datagram Protocol (UDP)

Prioritizes speed over accuracy

It's a connectionless protocol: UDP doesn't know where the packets get sent or what gets sent.

The headers are very small:

And have some optional data:

Transmission Control Protocol (TCP)

This protocol is very precise — it checks that every single individual packet is received.

TCP is connection-oriented

Handshake

The headers have an extra piece

Contains far more information than UDP

3. Internet

4. Network Access