Protocol

Protocol

1. IMAP - INTERNET MESSAGE ACCESS PROTOCOL

   • Allows management of an email box.
   • Created as a POP.
   • The server will then delete the data that has been sent.
   • The server will respond with the data which will then be stored on the clients device.
   • IMAP was designed by Mark Crispin in 1986 as a remote mailbox protocol, in contrast to the widely used POP, a protocol for retrieving the contents of a mailbox.

2. POP - POST OFFICE PROTOCOL

   • Used for emails.
   • Client server communication.
   • The server will respond with the data which will then be stored on the clients device.
   • The server will then delete the data that has been sent.

3. FTP(s) - FILE TRANSFER PROTOCOL

   • Network protocol for file sharing across a server / network.
   • Client side communication.
   • May require a login for file sharing for security.
   • Can be encrypted

4. HTTP(s) - HYPER TEXT TRANSFER PROTOCOL

   • Almost all sites use HTTP/HTTP(s)
   • Client Side communication
   • Sends requests from client to server .
   • Responses are sent back from the server to the client

5. IP - INTERNET PROTOCOL

   • Responsible for delivering packets.
   • Tells the instructions on how packets are created.
   • Also responsible for routing the Packets as it travels across a network.

6. TCP - TRANSMISSION CONTROL PROTOCOL

   • Responsible for communication between Applications and the Internet Protocol.
   • Makes sure that packets go through.
   • Is reliable
   • Made for accuracy and speed.

7. SMTP - SIMPLE MAIL TRANSFER PROTOCOL

   • Used by servers to send and receive email from other servers
   • Standard for emailing these days.
   • Used by clients to send email to a server.
   • Clients will still use IMAP / POP to receive email from a server.