Network Portion in The Top Bits and A Host Portion in The Bottom Bits. The Network
Network Portion in The Top Bits and A Host Portion in The Bottom Bits. The Network
Network Portion in The Top Bits and A Host Portion in The Bottom Bits. The Network
network portion in the top bits and a host portion in the bottom bits. The network
portion has the same value for all hosts on a single network, such as an Ethernet LAN. This
means that a network corresponds to a contiguous block of IP address space. This block is
called a prefix.
IP addresses are written in dotted decimal notation. In this format, each of the 4 bytes is
written in decimal, from 0 to 255.
IP Version 6 Goals:
The Payload length field tells how many bytes follow the 40-byte header
This field tells which of the (currently) six extension headers, if any, follow this one. If this
header is the last IP header, the Next header field tells which transport protocol handler
(e.g., TCP, UDP) to pass the packet to.
The Hop limit field is used to keep packets from living forever.
IPv6 extension headers
In addition to IP, which is used for data transfer, the Internet has several companion control
protocols that are used in the network layer. They include ICMP, ARP, and DHCP.
ARP (as well as other Internet protocols) makes the assumption that hosts are configured
with some basic information, such as their own IP addresses.
How do hosts get this information? It is possible to manually configure each computer, but
that is tedious and error-prone. There is a better way, and it is called DHCP (Dynamic Host
Configuration Protocol).
With DHCP, every network must have a DHCP server that is responsible for configuration.
When a computer is started, it has a built-in Ethernet or other link layer address embedded
in the NIC, but no IP address. Much like ARP, the computer broadcasts a request for an IP
address on its network. It does this by using a DHCP DISCOVER packet.
This packet must reach the DHCP server. If that server is not directly attached to the
network, the router will be configured to receive DHCP broadcasts and relay them to the
DHCP server, wherever it is located.
When the server receives the request, it allocates a free IP address and sends it to the host
in a DHCP OFFER packet (which again may be relayed via the router). To be able to do this
work even when hosts do not have IP addresses, the server identifies a host using its
Ethernet address (which is carried in the DHCP DISCOVER packet).
The generic MPLS header is 4 bytes long and has four fields. Most important is the Label
field, which holds the index. The QoS field indicates the class of service. The S field relates
to stacking multiple labels .
The TtL field indicates how many more times the packet may be forwarded. It is
decremented at each router, and if it hits 0, the packet is discarded. This feature prevents
infinite looping in the case of routing instability.
MPLS falls between the IP network layer protocol and the PPP link layer protocol. It is not
really a layer 3 protocol because it depends on IP or other network layer addresses to set up
label paths.
When an MPLS-enhanced packet arrives at a LSR (Label Switched Router), the label is
used as an index into a table to determine the outgoing line to use and also the new label to
use.
The ARPANET switched over to a link state protocol in May 1979 because of these problems,
and
in 1988 IETF began work on a link state protocol for intradomain routing. That protocol,
called OSPF (Open Shortest Path First), became a standard in 1990. It drew on a
protocol called IS-IS (Intermediate-System to Intermediate-System), which became an
ISO standard.