0% found this document useful (0 votes)
16 views9 pages

Understanding Internet Network Layer Protocols

Uploaded by

ishikaprail
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views9 pages

Understanding Internet Network Layer Protocols

Uploaded by

ishikaprail
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

28-05-2024

Module - 4
(Network Layer in the Internet)

Module - 4
(Network Layer in the Internet)
• IPv4 protocol, IP addresses, IPv6,
• Internet Control Protocols - Internet
Control Message Protocol (ICMP), Address
Resolution Protocol (ARP), Dynamic Host
Configuration Protocol (DHCP).
• Open Shortest Path First (OSPF) Protocol,
Border Gateway Protocol (BGP), Internet
multicasting.

1
28-05-2024

Network Layer in the Internet


• In the network layer, the Internet can be
viewed as a collection of networks
• The glue that holds the whole Internet
together is the network layer protocol, IP
(Internet Protocol).
• IP was designed from the beginning with
internetworking in mind

Network Layer in the Internet


• Communication in the Internet :
– The transport layer takes data streams and breaks them up
so that they may be sent as IP packets.
• In theory, packets can be up to 64KB each, but in practice they are
usually not more than 1500 bytes (so they fit in one Ethernet
frame).
– IP routers forward each packet through the Internet, along
a path from one router to the next, until the destination is
reached.
– When all the pieces finally get to the destination machine,
they are reassembled by the network layer into the
original datagram and handed over to transport layer.
– The Transport layer handover the data to the receiving
process.

2
28-05-2024

The IP Version 4 Protocol


• An IPv4 datagram consists of a header part and a body or
payload part.
• The header has a 20-byte fixed part and a variable-length
optional part.

The IP Version 4 Protocol Header


• Version field - keeps track of which version of the
protocol the datagram belongs to.
– IPV4 or IPV6
– By including the version at the start of each datagram, it
becomes possible to have a transition between versions.
• IHL - -provided to tell how long the header is, in 32-
bit words.
– The minimum value is 5, which applies when no options
are present.
– The maximum value of this 4-bit field is 15 which limits
the header to 60 bytes, and thus the Options field to 40
bytes.

3
28-05-2024

The IP Version 4 Protocol Header


• Differentiated services field -
– Originally called Type of service (TOS) field – 8 bits,
intended to distinguish between different classes of
service. Various combinations of reliability and speed
are possible.
– For digitized voice, fast delivery is more important
than accurate delivery.
– For file transfer, error-free transmission is more
important than fast transmission.
– The ‘Type of service’ field provided 3 bits to indicate
priority and 3 bits to indicate whether a host cared
more about delay, throughput, or reliability.
– They were left unused for many years.

The IP Version 4 Protocol Header


• Differentiated services field -
– It was changed to ‘differentiated services’ field by
IETF, which reused this field.
– Now, the top 6 bits are used to mark the packet
with its service class.
– The bottom 2 bits are used to carry explicit
congestion notification Information, such as
whether the packet has experienced congestion

4
28-05-2024

The IP Version 4 Protocol Header


• Total length - includes everything in the
datagram - both header and data.
– The maximum length is 65,535 bytes.
• Identification field - is needed to allow the
destination host to determine which packet a
newly arrived fragment belongs to.
– All the fragments of a packet contain the same
Identification value.

The IP Version 4 Protocol Header


• Unused bit - proposed to detect malicious traffic.
– Unfortunately, network security is not this simple
• Then come two 1-bit fields related to fragmentation.
• DF bit
– DF stands for Don’t Fragment. It is an order to the routers not
to fragment the packet.
– Originally, it was intended to support hosts incapable of putting
the pieces back together again.
– By marking the datagram with the DF bit, the sender knows it
will either arrive in one piece, or an error message will be
returned to the sender.
• MF bit - stands for More Fragments.
– All fragments except the last one have this bit set. It is needed
to know when all fragments of a datagram have arrived.

5
28-05-2024

The IP Version 4 Protocol Header


• Fragment offset - tells where in the current
packet this fragment belongs.
– All fragments except the last one in a datagram
must be a multiple of 8 bytes, the elementary
fragment unit.
– Since 13 bits are provided, there is a maximum of
8192 fragments per datagram, supporting a
maximum packet length up to the limit of the total
length field.
– Working together, the Identification, MF, and
Fragment offset fields are used to implement
fragmentation.

The IP Version 4 Protocol Header


• TTL (Time to live) field - is a counter used to limit
packet lifetimes.
– It was originally supposed to count time in seconds,
allowing a maximum lifetime of 255 sec.
• It must be decremented on each hop and is supposed
to be decremented multiple times when a packet is
queued for a long time in a router.
• In practice, it just counts hops. When it hits zero, the
packet is discarded and a warning packet is sent back
to the source host.
• This feature prevents packets from wandering around
forever.

6
28-05-2024

The IP Version 4 Protocol Header


• Protocol field – stores the protocol number –
which tells the network layer to which
transport process to give the packet to.
– TCP or UDP or some other protocol.
– The numbering of protocols is global across the
entire Internet.
– Protocol numbers are contained in [Link].

The IP Version 4 Protocol Header Num.

7
28-05-2024

The IP Version 4 Protocol Header


• Header Checksum - Since the header carries
vital information such as addresses, it
computes the header information checksum
for protection.
– The checksum is useful for detecting errors while
the packet travels through the network.
– Note that it must be recomputed at each hop
because at least one field always changes (eg the
Time to live field).

The IP Version 4 Protocol Header


• Source address and Destination address
indicate the IP address of the source and
destination network interfaces.
• Options field - was designed to test
subsequent versions of the protocol to include
information not present in the original design,
to permit experimenters to try out new ideas.

8
28-05-2024

IP addresses
• IPv4 is 32-bit address.
• Every host and router on the Internet has an IP
address that can be used in the Source address
and Destination address fields of IP packets.
• IP address does not actually refer to a host. It
really refers to a network interface, so if a host is
on two networks, it must have two IP addresses.
• However, in practice, most hosts are on one
network and thus have one IP address.
• In contrast, routers have multiple interfaces and
thus multiple IP addresses.

Common questions

Powered by AI

The IETF changed the interpretation of the Type of Service field by converting it into a 'Differentiated Services' field. Initially intended to distinguish between different classes of service, it provided bits to prioritize based on delay, throughput, and reliability. Over time, these were left largely unused. The new structure under IETF usage repurposed the top 6 bits to classify service classes, while the bottom 2 bits are now used to convey explicit congestion notification information.

Using different classes of service within the Differentiated Services field allows networks to prioritize traffic based on the requirements for speed, reliability, or delay. This prioritization enables network devices to make informed decisions on handling packets, ensuring resources are optimally allocated to meet diverse service requirements. For example, digitized voice packets might be prioritized for speed over file transfer, which might prioritize reliability, increasing efficiency and service quality in varied operational contexts.

The TTL field ensures efficient packet routing by preventing packets from circulating indefinitely in the network. Originally intended as a time measure, it is practically used to count hops. Each hop decrements the TTL value, and packets are discarded once TTL reaches zero. This helps avoid endless looping of packets within the network and informs the source of a failure through a warning packet.

IPv4 handles packet fragmentation using the Identifications, Fragment Offset, DF, and MF fields. The Identification field allows the destination host to determine which fragments belong to which original datagram. The Fragment Offset helps to reassemble packets by indicating where each fragment belongs within the original datagram. The DF (Don't Fragment) bit instructs routers not to fragment the packet, ensuring it arrives whole or returns an error. All fragments except the last have the MF (More Fragments) bit set, which indicates more fragments are on their way.

Internet Control Protocols like ICMP, ARP, and DHCP perform essential support functions within the Network Layer. ICMP is used for error messages and operational queries. ARP translates IP addresses into MAC addresses, facilitating communication on local networks. DHCP dynamically assigns IP addresses to devices within a network, ensuring efficient IP address management and network configuration. Together, these protocols support the reliable and efficient functioning of the Network Layer.

The significance of IP addresses referring to network interfaces rather than hosts lies in the need for flexible addressing in network connections. This model allows devices with multiple network connections, such as routers, to manage multiple network interfaces and addresses efficiently. This flexibility supports complex network architectures essential in routing and network scalability.

OSPF and BGP serve distinct roles within the Internet's network layer. OSPF is an internal gateway protocol that finds the most efficient path for packet delivery within a single autonomous system by utilizing a link-state routing algorithm. Conversely, BGP operates between autonomous systems as an external gateway protocol, focusing on determining the best path across multiple systems through path vector routing. Their complementary usage allows for comprehensive management of routing information within and between networks.

The Source and Destination Address fields are pivotal for maintaining communication integrity on the Internet. They ensure that packets are routed accurately from the origin to the intended recipient. Accurate addressing prevents data loss, enables proper routing decisions, facilitates traceability, and supports security measures by verifying source authenticity and preventing fraudulent activities. These functions collectively maintain the reliability and security of Internet communications.

The IHL (Internet Header Length) field in the IPv4 header indicates the length of the header in 32-bit words, allowing routers and hosts to quickly determine where the header ends and the payload begins. This precise delineation is crucial for the correct processing and forwarding of IP datagrams across varied networks, ensuring that subsequent header components are accurately interpreted and understood within diverse network configurations.

The Header Checksum in IPv4 ensures data integrity by detecting errors in the packet header during transit. Each hop requires a recalculation of the checksum because certain fields in the header, such as the TTL field, change as the packet moves through the network. This recalculation maintains the validity of header data at each hop, ensuring that the route information is accurate and prevents corrupted packets from proceeding.

You might also like