Internet Protocol version 4 (IPv4) is the fourth version of the "Internet Protocol (IP). It is one of the core protocols of standards-based internetworking methods in the "Internet, and was the first version deployed for production in the "ARPANET in 1983. It still routes most Internet traffic today, despite the ongoing deployment of a successor protocol, "IPv6. IPv4 is described in "IETF publication RFC 791 (September 1981), replacing an earlier definition (RFC 760, January 1980).
IPv4 is a "connectionless protocol for use on "packet-switched networks. It operates on a "best effort delivery model, in that it does not guarantee delivery, nor does it assure proper sequencing or avoidance of duplicate delivery. These aspects, including data integrity, are addressed by an "upper layer transport protocol, such as the "Transmission Control Protocol (TCP).
|"Internet protocol suite|
IPv4 addresses may be represented in any notation expressing a 32-bit integer value. They are most often written in the "dot-decimal notation, which consists of four "octets of the address expressed individually in "decimal numbers and separated by "periods. The "CIDR notation standard combines the address with its routing prefix in a compact format, in which the address is followed by a slash character (/) and the count of consecutive 1 bits in the routing prefix (subnet mask).
For example, the quad-dotted IP address 192.0.2.235 represents the 32-bit "decimal number 3221226219, which in "hexadecimal format is 0xC00002EB. This may also be expressed in dotted hex format as 0xC0.0x00.0x02.0xEB, or with octal byte values as 0300.0000.0002.0353.
In the original design of IPv4, an IP address was divided into two parts: the network identifier was the most significant (highest order) octet of the address, and the host identifier was the rest of the address. The latter was also called the rest field. This structure permitted a maximum of 256 network identifiers, which was quickly found to be inadequate.
To overcome this limit, the most-significant address octet was redefined in 1981 to create network classes, in a system which later became known as "classful networking. The revised system defined five classes. Classes A, B, and C had different bit lengths for network identification. The rest of the address was used as previously to identify a host within a network, which meant that each network class had a different capacity for addressing hosts. Class D was defined for "multicast addressing and Class E was reserved for future applications.
Starting around 1985, methods were devised to subdivide IP networks. One method that has proved flexible is the use of the variable-length subnet mask ("VLSM). Based on the IETF standard RFC 1517 published in 1993, this system of classes was officially replaced with "Classless Inter-Domain Routing (CIDR), which expressed the number of bits (from the "most significant) as, for instance, /24, and the class-based scheme was dubbed classful, by contrast. CIDR was designed to permit repartitioning of any address space so that smaller or larger blocks of addresses could be allocated to users. The hierarchical structure created by CIDR is managed by the "Internet Assigned Numbers Authority (IANA) and the "regional Internet registries (RIRs). Each RIR maintains a publicly searchable "WHOIS database that provides information about IP address assignments.
The "Internet Engineering Task Force (IETF) and the "Internet Assigned Numbers Authority (IANA) have restricted from general use various "reserved IP addresses for special purposes. Some are used for maintenance of "routing tables, for "multicast traffic, operation under "failure modes, or to provide addressing space for public, unrestricted uses on private networks.
|0.0.0.0/8||Current network (only valid as source address)||RFC 6890|
|10.0.0.0/8||"Private network||RFC 1918|
|100.64.0.0/10||Shared Address Space||RFC 6598|
|172.16.0.0/12||"Private network||RFC 1918|
|192.0.0.0/24||IETF Protocol Assignments||RFC 6890|
|192.0.2.0/24||TEST-NET-1, documentation and examples||RFC 5737|
|188.8.131.52/24||"IPv6 to IPv4 relay (includes 2002::/16)||RFC 3068|
|192.168.0.0/16||"Private network||RFC 1918|
|198.18.0.0/15||Network benchmark tests||RFC 2544|
|198.51.100.0/24||TEST-NET-2, documentation and examples||RFC 5737|
|203.0.113.0/24||TEST-NET-3, documentation and examples||RFC 5737|
|184.108.40.206/4||"IP multicast (former Class D network)||RFC 5771|
|240.0.0.0/4||Reserved (former Class E network)||RFC 1700|
Of the approximately four billion addresses defined in IPv4, three ranges are reserved for use in "private networks. Packets addresses in these ranges are not routable in the public Internet, because they are ignored by all public routers. Therefore, private hosts cannot directly communicate with public networks, but require "network address translation at a routing gateway for this purpose.
|Name||Address range||Number of addresses||"Classful description||Largest "CIDR block|
|24-bit block||10.0.0.0 – 10.255.255.255||16777216||Single Class A||10.0.0.0/8|
|20-bit block||172.16.0.0 – 172.31.255.255||1048576||Contiguous range of 16 Class B blocks||172.16.0.0/12|
|16-bit block||192.168.0.0 – 192.168.255.255||65536||Contiguous range of 256 Class C blocks||192.168.0.0/16|
Since two private networks, e.g., two branch offices, cannot directly interoperate via the public Internet, the two networks must be bridged across the Internet via a "virtual private network (VPN) or an "IP tunnel, which "encapsulate the packet in a protocol layer during transmission across the public network. Additionally, encapsulated packets may be encrypted for the transmission across public networks to secure the data.
RFC 3927 defines the special address block 169.254.0.0/16 for "link-local addressing. These addresses are only valid on links (such as a local network segment or point-to-point connection) connected to a host. These addresses are not routable. Like private addresses, these addresses cannot be the source or destination of packets traversing the internet. These addresses are primarily used for address autoconfiguration ("Zeroconf) when a host cannot obtain an IP address from a DHCP server or other internal configuration methods.
When the address block was reserved, no standards existed for address autoconfiguration. "Microsoft created an implementation called Automatic Private IP Addressing (APIPA), which was deployed on millions of machines and became a "de facto standard. Many years later, in May 2005, the "IETF defined a formal standard in RFC 3927, entitled Dynamic Configuration of IPv4 Link-Local Addresses.
The class A network 127.0.0.0 (classless network 127.0.0.0/8) is reserved for "loopback. IP packets whose source addresses belong to this network should never appear outside a host. The "modus operandi of this network expands upon that of a loopback interface:
Networks with subnet masks of at least 24 bits, i.e. Class C networks in classful networking, and networks with CIDR suffixes /24 to /32 (255.255.255.0–255.255.255.255) may not have an address ending in 0 or 255.
Classful addressing prescribed only three possible subnet masks: Class A, 255.0.0.0 or /8; Class B, 255.255.0.0 or /16; and Class C, 255.255.255.0 or /24. For example, in the subnet 192.168.5.0/255.255.255.0 (192.168.5.0/24) the identifier 192.168.5.0 commonly is used to refer to the entire subnet. To avoid ambiguity in representation, the address ending in the octet 0 is reserved.
A "broadcast address is an address that allows information to be sent to all interfaces in a given subnet, rather than a specific machine. Generally, the broadcast address is found by obtaining the bit complement of the subnet mask and performing a bitwise OR operation with the network identifier. In other words, the broadcast address is the last address in the address range of the subnet. For example, the broadcast address for the network 192.168.5.0 is 192.168.5.255. For networks of size /24 or larger, the broadcast address always ends in 255.
However, this does not mean that every address ending in 0 or 255 cannot be used as a host address. For example, in the /16 subnet 192.168.0.0/255.255.0.0, which is equivalent to the address range 192.168.0.0–192.168.255.255, the broadcast address is 192.168.255.255. One can use the following addresses for hosts, even though they end with 255: 192.168.1.255, 192.168.2.255, etc. Also, 192.168.0.0 is the network identifier and must not be assigned to an interface. The addresses 192.168.1.0, 192.168.2.0, etc., may be assigned, despite ending with 0.
In the past, conflict between network addresses and broadcast addresses arose because some software used non-standard broadcast addresses with zeros instead of ones.
In networks smaller than /24, broadcast addresses do not necessarily end with 255. For example, a CIDR subnet 203.0.113.16/28 has the broadcast address 203.0.113.31.
Hosts on the "Internet are usually known by names, e.g., www.example.com, not primarily by their IP address, which is used for routing and network interface identification. The use of domain names requires translating, called resolving, them to addresses and vice versa. This is analogous to looking up a phone number in a phone book using the recipient's name.
The translation between addresses and domain names is performed by the "Domain Name System (DNS), a hierarchical, distributed naming system which allows for subdelegation of name spaces to other DNS servers.
Since the 1980s, it was apparent that the pool of available IPv4 addresses was being depleted at a rate that was not initially anticipated in the original design of the network address system. The main market forces which accelerated IPv4 address depletion included:
The threat of exhaustion motivated the introduction of a number of remedial technologies, such as "classful networks, "Classless Inter-Domain Routing (CIDR) methods, "network address translation (NAT) and strict usage-based allocation policies. To provide a long-term solution to the pending address exhaustion, "IPv6 was created in the 1990s, which made many more addresses available by increasing the address size to 128 bits. IPv6 has been in commercial deployment since 2006.
The primary address pool of the Internet, maintained by "IANA, was exhausted on 3 February 2011, when the last 5 blocks were allocated to the 5 RIRs. "APNIC was the first RIR to exhaust its regional pool on 15 April 2011, except for a small amount of address space reserved for the transition to IPv6, which will be allocated under a much more restricted policy.
The accepted and standard long term solution is to use "IPv6 which increased the address size to 128 bits, providing a vastly increased address space that also allows improved route aggregation across the Internet and offers large subnetwork allocations of a minimum of 264 host addresses to end-users. However IPv4-only hosts cannot directly communicate with IPv6-only hosts so IPv6 alone does not provide an immediate solution to the IPv4 exhaustion problem. Migration to IPv6 is in progress but completion is expected to take considerable time.["citation needed]
An IP "packet consists of a header section and a data section.
An IP packet has no data checksum or any other footer after the data section. Typically the "link layer encapsulates IP packets in frames with a CRC footer that detects most errors, and typically the end-to-end TCP layer checksum detects most other errors.
The IPv4 packet header consists of 14 fields, of which 13 are required. The 14th field is optional and aptly named: options. The fields in the header are packed with the most significant byte first ("big endian), and for the diagram and discussion, the most significant bits are considered to come first ("MSB 0 bit numbering). The most significant bit is numbered 0, so the version field is actually found in the four most significant bits of the first byte, for example.
|8||64||Time To Live||Protocol||Header Checksum|
|12||96||Source IP Address|
|16||128||Destination IP Address|
|20||160||Options (if IHL > 5)|
When a packet arrives at a router, the router decreases the TTL field. Consequently, the router must calculate a new checksum. RFC 791 defines the checksum calculation:
The checksum field is the 16-bit "one's complement of the one's complement sum of all 16-bit words in the header. For purposes of computing the checksum, the value of the checksum field is zero.
For example, consider hex 16 (20 bytes IP header), using a machine which uses standard two's complement arithmetic: 4500003044224000800600008C7C19ACAE241E2B
To validate a header's checksum the same algorithm may be used – the checksum of a header which contains a correct checksum field is a word containing all zeros (value 0):
|Copied||1||Set to 1 if the options need to be copied into all fragments of a fragmented packet.|
|Option Class||2||A general options category. 0 is for "control" options, and 2 is for "debugging and measurement". 1, and 3 are reserved.|
|Option Number||5||Specifies an option.|
|Option Length||8||Indicates the size of the entire option (including this field). This field may not exist for simple options.|
|Option Data||Variable||Option-specific data. This field may not exist for simple options.|
The following two options are discouraged because they create security concerns: "Loose Source and Record Route (LSRR) and "Strict Source and Record Route (SSRR). Many routers block packets containing these options.
The data portion of the packet is not included in the packet checksum. Its contents are interpreted based on the value of the Protocol header field.
Some of the common protocols for the data portion are listed below:
|Protocol Number||Protocol Name||Abbreviation|
|1||"Internet Control Message Protocol||ICMP|
|2||"Internet Group Management Protocol||IGMP|
|6||"Transmission Control Protocol||TCP|
|17||"User Datagram Protocol||UDP|
|89||"Open Shortest Path First||OSPF|
|132||"Stream Control Transmission Protocol||SCTP|
See "List of IP protocol numbers for a complete list.
The Internet Protocol enables networks to communicate with one another. The design accommodates networks of diverse physical nature; it is independent of the underlying transmission technology used in the Link Layer. Networks with different hardware usually vary not only in transmission speed, but also in the "maximum transmission unit (MTU). When one network wants to transmit datagrams to a network with a smaller MTU, it may "fragment its datagrams. In IPv4, this function was placed at the "Internet Layer, and is performed in IPv4 routers, which thus only require this layer as the highest one implemented in their design.
In contrast, "IPv6, the next generation of the Internet Protocol, does not allow routers to perform fragmentation; hosts must determine the path MTU before sending datagrams.
When a router receives a packet, it examines the destination address and determines the outgoing interface to use and that interface's MTU. If the packet size is bigger than the MTU, and the Do not Fragment (DF) bit in the packet's header is set to 0, then the router may fragment the packet.
The router divides the packet into fragments. The max size of each fragment is the MTU minus the IP header size (20 bytes minimum; 60 bytes maximum). The router puts each fragment into its own packet, each fragment packet having following changes:
For example, for an MTU of 1,500 bytes and a header size of 20 bytes, the fragment offsets would be multiples of (1500–20)/8 = 185. These multiples are 0, 185, 370, 555, 740, ...
It is possible for a packet to be fragmented at one router, and for the fragments to be fragmented at another router. For example, consider a Transport layer segment with size of 4,500 bytes, no options, and IP header size of 20 bytes. So the IP packet size is 4,520 bytes. Assume that the packet travels over a link with an MTU of 2,500 bytes. Then it will become two fragments:
|Fragment||Total bytes||Header bytes||Data bytes||"More fragments" flag||Fragment offset (8-byte blocks)|
Note that the fragments preserve the data size: 2480 + 2020 = 4500.
Note how we get the offsets from the data sizes:
Assume that these fragments reach a link with an MTU of 1,500 bytes. Each fragment will become two fragments:
|Fragment||Total bytes||Header bytes||Data bytes||"More fragments" flag||Fragment offset (8-byte blocks)|
Note that the fragments preserve the data size: 1480 + 1000 = 2480, and 1480 + 540 = 2020.
Also in this case, the More Fragments bit remains 1 for ALL the fragments that came with 1 in them and for the last fragment that arrives, it works as usual, that is the MF bit is set to 0 only in the last one. And of course, the Identification field continues to have the same value in all re-fragmented fragments. This way, even if fragments are re-fragmented, the receiver knows they have initially all started from the same packet.
Note how we get the offsets from the data sizes:
We can use the last offset and last data size to calculate the total data size: 495*8 + 540 = 3960 + 540 = 4500.
A receiver knows that a packet is a fragment if at least one of the following conditions is true:
The receiver identifies matching fragments using the foreign and local internet address, the protocol ID, and the identification field. The receiver will reassemble the data from fragments with the same ID using both the fragment offset and the more fragments flag. When the receiver receives the last fragment (which has the "more fragments" flag set to 0), it can calculate the length of the original data payload, by multiplying the last fragment's offset by eight, and adding the last fragment's data size. In the example above, this calculation was 495*8 + 540 = 4500 bytes.
When the receiver has all the fragments, it can put them in the correct order, by using their offsets. It can then pass their data up the stack for further processing.
The Internet Protocol is the protocol that defines and enables "internetworking at the "Internet Layer and thus forms the Internet. It uses a logical addressing system. IP addresses are not tied in any permanent manner to hardware identifications and, indeed, a network interface can have multiple IP addresses. Hosts and routers need additional mechanisms to identify the relationship between device interfaces and IP addresses, in order to properly deliver an IP packet to the destination host on a link. The "Address Resolution Protocol (ARP) performs this IP-address-to-hardware-address translation for IPv4. (A hardware address is also called a "MAC address.) In addition, the reverse correlation is often necessary. For example, when an IP host is booted or connected to a network it needs to determine its IP address, unless an address is preconfigured by an administrator. Protocols for such inverse correlations exist in the "Internet Protocol Suite. Currently used methods are "Dynamic Host Configuration Protocol (DHCP), "Bootstrap Protocol (BOOTP) and, infrequently, "reverse ARP.
|Wikiversity has learning resources about IPv4|