
329
14.1 Protocols
14
Key terms
Protocol – a set of rules governing communication
across a network: the rules are agreed by both sender
and recipient.
HTTP – hypertext transfer protocol.
Packet – a message/data is split up into smaller groups
of bits for transmission over a network.
Segment (transport layer) – this is a unit of data
(packet) associated with the transport layer protocols.
FTP – file transfer protocol.
SMTP – simple mail transfer protocol.
Push protocol – protocol used when sending emails, in
which the client opens the connection to the server and
keeps the connection active all the time, then uploads
new emails to the server.
Binary file – a file that does not contain text only. The
file is machine-readable but not human-readable.
MIME – multi-purpose internet mail extension. A
protocol that allows email attachments containing
media files as well as text to be sent.
POP – post office protocol.
IMAP – internet message access protocol.
TCP – transmission control protocol.
Pull protocol – protocol used when receiving emails,
in which the client periodically connects to a server,
checks for and downloads new emails from a server
and then closes the connection.
Host-to-host – a protocol used by TCP when
communicating between two devices.
Host – a computer or device that can communicate with
other computers or devices on a network.
BitTorrent – protocol used in peer-to-peer networks
when sharing files between peers.
Peer – a client who is part of a peer-to-peer
network/file sharing community.
Metadata – a set of data that describes and gives
information about other data.
Pieces – splitting up of a file when using peer-to-peer
file sharing.
Tracker – central server that stores details of all other
computers in the swarm.
Swarm – connected peers (clients) that share a
torrent/tracker.
Seed – a peer that has downloaded a file (or pieces of a
file) and has then made it available to other peers in the
swarm.
Leech – a peer with negative feedback from swarm
members.
Lurker – user/client that downloads files but does not
supply any new content to the community.
14.1.1 The need for protocols
When communicating over networks, it is essential that some form of protocol
is used by the sender and receiver of the data. Both parties need to agree
the protocol being used to ensure successful communication takes place. In
Chapter6, we discussed parity checking as a way of determining whether
data was transmitted correctly. With this method, it was essential to agree
the protocol: even or odd parity. Without agreeing this protocol, it would be
impossible to use parity checking. Many different protocols exist since there
are several activities taking place over the internet.
The next section considers one of the most common sets of protocols, which
are implemented by using a stack structure with several layers.
14.1.2 TCP/IP protocols
This is the four-layer structure for TCP/IP protocols:
DARPA (Defense Advanced Research
Projects Agency) Layers
4 APPLICATION LAYER
3 TRANSPORT LAYER
2 INTERNET (NETWORK) LAYER
1 LINK NETWORK
V Figure 14.1 Four layer structure for TCP/IP
Sending Receiving