Discover

The 'Internet Protocol' ('IP') is a data-oriented protocol used for communicating data across a packet-switched internetwork.
IP is a network layer protocol in the Internet protocol suite and is encapsulated in a data link layer protocol (e.g., Ethernet).
As a lower layer protocol, IP provides the service of ''communicable'' unique global addressing amongst computers.

Contents

Packetization

Services provided by IP

Reliability

IP addressing and routing

Version history

See also

References

External links

Packetization

Data from an upper layer protocol is encapsulated inside one or more packets/datagrams (the terms are basically synonymous in IP).
No circuit setup is needed before a host tries to send packets to a host it has previously not communicated with (this is the point of a packet-switched network), thus IP (Internet protocol) is a connectionless protocol.
This is quite unlike Public Switched Telephone Networks that require the setup of a circuit before a phone call may go through (a ''connection-oriented'' protocol).

Services provided by IP

Because of the abstraction provided by encapsulation, IP can be used over a heterogeneous network (i.e., a network connecting two computers can be any mix of Ethernet, ATM, FDDI, Wi-Fi, token ring, etc.) and it makes no difference to the upper layer protocols.
Each data link layer can (and does) have its own method of addressing (or possibly the complete lack of it), with a corresponding need to resolve IP addresses to data link addresses. This address resolution is handled by the Address Resolution Protocol (ARP).

Reliability

IP provides an ''unreliable'' service (i.e., best effort delivery). This means that the network makes no guarantees about the packet and none, some, or all of the following may apply:

★ data corruption

★ out of order (packet A may be sent before packet B, but B can arrive before A)

★ duplicate arrival

★ lost or dropped/discarded
In terms of reliability the only thing IP does is ensure the IP packet's header is error-free through the use of a checksum. This has the side-effect of 'discarding' packets with bad headers on the spot, and with no required notification to either end (though an ICMP message may be sent).
To address any of these reliability issues, an upper layer protocol must handle it. For example, to ensure in-order delivery the upper layer may have to cache data until it can be passed up in order.
If the upper layer protocol does not self-police its own size by first looking at the Layer 2 Maximum Transmission Unit (MTU) size, and sends the IP layer too much data, IP is forced to fragment the original datagram into smaller fragments for transmission. IP ''does'' provide re-ordering of any fragments that arrive out of order by using the fragmentation flags and offset^[1]. Transmission Control Protocol (TCP) is a good example of a protocol that will adjust its segment size to be smaller than the MTU. User Datagram Protocol (UDP) and Internet Control Message Protocol (ICMP) are examples of protocols that disregard MTU size thereby forcing IP to fragment oversized datagrams.^[2]
The primary reason for the lack of reliability is to reduce the complexity of routers. While this does give routers ''carte blanche'' to do as they please with packets, anything less than ''best effort'' yields a poorer experience for the user. So, even though no guarantees are made, the better the effort made by the network, the better the experience for the user. Most protocols are built around the idea that error checking is best done at each end of the communication line, see End-to-end principle.

IP addressing and routing

Perhaps the most complex aspects of IP are IP addressing and routing. Addressing refers to how end hosts become assigned IP addresses and how subnetworks of IP host addresses are divided and grouped together. IP routing is performed by all hosts, but most importantly by internetwork routers, which typically use either interior gateway protocols (IGPs) or external gateway protocols (EGPs) to help make 'IP datagram' forwarding decisions across IP connected networks.

Version history

IP is the common element found in today's public Internet. The current and most popular network layer protocol in use today is IPv4; this version of the protocol is assigned version 4. IPv4 RFC-791 was adopted by the United States Department of Defense as MIL-STD-1777.
IPv6 is the proposed successor to IPv4 whose most prominent change is the addressing. IPv4 uses 32-bit addresses (~4 billion addresses) while IPv6 uses 128-bit addresses (~3.4×10³⁸ addresses). Although adoption of IPv6 has been slow, as of 2008, all United States government systems must support IPv6 (if only at the backbone level). ^[3]
Version numbers 0 through 3 were development versions of IPv4 used between 1977 and 1979. Version number 5 was used by the Internet Stream Protocol (IST), an experimental stream protocol. Version numbers 6 through 9 were assigned to experimental protocols designed to replace IPv4: SIPP (known nowadays as IPv6), TP/IX, PIP, and TUBA. Except for IPv6, the other ones are not used any more.

See also

: ''Main lists: List of basic internet topics and List of Internet topics''

★ Connectionless protocol

★ IANA

★ Internet protocol suite

★ IPv4

★ IPv5

★ IPv6

★ IP address

★

★ TCP and UDP port numbers

★ Transmission Control Protocol

★ ip - the ip structure for the C programming language

★ Internet

★ Country IP database

References

1. Siyan, Karanjit. ''Inside TCP/IP'', New Riders Publishing, 1997. ISBN 1-56205-714-6
2. http://www.securityfocus.com/infocus/1870
3. http://www.gcn.com/print/25_16/41051-1.html

External links

★

★ RFC 791