Internet Protocol: Difference between revisions
Jump to navigation
Jump to search
imported>LizardJr8 m Reverted edit by 2A03:D000:42A6:EB02:1:0:3D84:2546 (talk) to last version by ShatteredNode |
imported>Kvng simplify link. para. |
||
| Line 1: | Line 1: | ||
{{Short description|Communication protocol that allows connections between networks}} | {{Short description|Communication protocol that allows connections between networks}} | ||
{{Use American English|date=November 2025}} | |||
{{IPstack}} | {{IPstack}} | ||
The '''Internet Protocol''' ('''IP''') is the [[network layer]] [[communications protocol]] in the [[Internet protocol suite]] for relaying [[datagram]]s across network boundaries. Its [[routing]] function enables [[internetworking]], and essentially establishes the [[Internet]]. | The '''Internet Protocol''' ('''IP''') is the [[network layer]] [[communications protocol]] in the [[Internet protocol suite]] for relaying [[datagram]]s across network boundaries. Its [[routing]] function enables [[internetworking]], and essentially establishes the [[Internet]]. | ||
IP has the task of delivering [[Packet (information technology)|packets]] from the source [[Host (network)|host]] to the destination host solely based on the [[IP address]]es in the | IP has the task of delivering [[Packet (information technology)|packets]] from the source [[Host (network)|host]] to the destination host solely based on the [[IP address]]es in the [[packet header]]s. For this purpose, IP defines packet structures that [[Encapsulation (networking)|encapsulate]] the data to be delivered. It also defines addressing methods that are used to label the datagram with source and destination information. | ||
IP was the [[connectionless]] datagram service in the original ''[[Transmission Control Program]]'' introduced by [[Vint Cerf]] and [[Bob Kahn]] in 1974, which was complemented by a [[connection-oriented]] service that became the basis for the [[Transmission Control Protocol]] (TCP). The Internet protocol suite is therefore often referred to as ''TCP/IP''. | IP was the [[connectionless]] datagram service in the original ''[[Transmission Control Program]]'' introduced by [[Vint Cerf]] and [[Bob Kahn]] in 1974, which was complemented by a [[connection-oriented]] service that became the basis for the [[Transmission Control Protocol]] (TCP). The Internet protocol suite is therefore often referred to as ''TCP/IP''. | ||
| Line 24: | Line 25: | ||
== Version history == | == Version history == | ||
[[File:TCP and IP protocols development timeline-en.svg|thumb|right|A timeline for the development of the transmission control Protocol TCP and Internet Protocol IP]] | [[File:TCP and IP protocols development timeline-en.svg|thumb|right|class=skin-invert-image|A timeline for the development of the transmission control Protocol TCP and Internet Protocol IP]] | ||
[[File:First Internet Demonstration, 1977.jpg|thumb|right|First Internet demonstration, linking the [[ARPANET]], [[PRNET]], and [[SATNET]] on November 22, 1977]] | [[File:First Internet Demonstration, 1977.jpg|thumb|right|class=skin-invert-image|First Internet demonstration, linking the [[ARPANET]], [[PRNET]], and [[SATNET]] on November 22, 1977]] | ||
In May 1974, the [[Institute of Electrical and Electronics Engineers]] (IEEE) published a paper entitled "A Protocol for Packet Network Intercommunication".<ref>{{Cite journal|last1=Cerf|first1=V.|last2=Kahn|first2=R.|date=1974|title=A Protocol for Packet Network Intercommunication|url=https://www.cs.princeton.edu/courses/archive/fall06/cos561/papers/cerf74.pdf|journal=IEEE Transactions on Communications|volume=22|issue=5|pages=637–648|doi=10.1109/TCOM.1974.1092259|issn=1558-0857|quote=The authors wish to thank a number of colleagues for helpful comments during early discussions of international network protocols, especially R. Metcalfe, R. Scantlebury, D. Walden, and H. Zimmerman; D. Davies and L. Pouzin who constructively commented on the fragmentation and accounting issues; and S. Crocker who commented on the creation and destruction of associations.|access-date=2020-04-06|archive-date=2017-01-06|archive-url=https://web.archive.org/web/20170106204542/http://www.cs.princeton.edu/courses/archive/fall06/cos561/papers/cerf74.pdf|url-status=live}}</ref> The paper's authors, [[Vint Cerf]] and [[Bob Kahn]], described an [[internetworking]] protocol for sharing resources using [[packet switching]] among [[network node]]s. A central control component of this model was the Transmission Control Program that incorporated both connection-oriented links and datagram services between hosts. The monolithic Transmission Control Program was later divided into a modular architecture consisting of the [[Transmission Control Protocol]] and [[User Datagram Protocol]] at the [[transport layer]] and the Internet Protocol at the [[internet layer]]. The model became known as the ''Department of Defense (DoD) Internet Model'' and ''[[Internet protocol suite]]'', and informally as ''TCP/IP''. | In May 1974, the [[Institute of Electrical and Electronics Engineers]] (IEEE) published a paper entitled "A Protocol for Packet Network Intercommunication".<ref>{{Cite journal|last1=Cerf|first1=V.|last2=Kahn|first2=R.|date=1974|title=A Protocol for Packet Network Intercommunication|url=https://www.cs.princeton.edu/courses/archive/fall06/cos561/papers/cerf74.pdf|journal=IEEE Transactions on Communications|volume=22|issue=5|pages=637–648|doi=10.1109/TCOM.1974.1092259|issn=1558-0857|quote=The authors wish to thank a number of colleagues for helpful comments during early discussions of international network protocols, especially R. Metcalfe, R. Scantlebury, D. Walden, and H. Zimmerman; D. Davies and L. Pouzin who constructively commented on the fragmentation and accounting issues; and S. Crocker who commented on the creation and destruction of associations.|access-date=2020-04-06|archive-date=2017-01-06|archive-url=https://web.archive.org/web/20170106204542/http://www.cs.princeton.edu/courses/archive/fall06/cos561/papers/cerf74.pdf|url-status=live}}</ref> The paper's authors, [[Vint Cerf]] and [[Bob Kahn]], described an [[internetworking]] protocol for sharing resources using [[packet switching]] among [[network node]]s. A central control component of this model was the Transmission Control Program that incorporated both connection-oriented links and datagram services between hosts. The monolithic Transmission Control Program was later divided into a modular architecture consisting of the [[Transmission Control Protocol]] and [[User Datagram Protocol]] at the [[transport layer]] and the Internet Protocol at the [[internet layer]]. The model became known as the ''Department of Defense (DoD) Internet Model'' and ''[[Internet protocol suite]]'', and informally as ''TCP/IP''. | ||
| Line 49: | Line 50: | ||
===IP version numbers=== | ===IP version numbers=== | ||
{{Main|List of IP version numbers}} | |||
{{#section:List of IP version numbers|IP-version-numbers}} | |||
|- | |||
==Reliability== | ==Reliability== | ||
| Line 109: | Line 58: | ||
As a consequence of this design, the Internet Protocol only provides [[best-effort delivery]] and its service is characterized as [[Reliability (computer networking)|unreliable]]. In network architectural parlance, it is a [[connectionless protocol]], in contrast to [[connection-oriented communication]]. Various fault conditions may occur, such as [[data corruption]], [[packet loss]] and duplication. Because routing is dynamic, meaning every packet is treated independently, and because the network maintains no state based on the path of prior packets, different packets may be routed to the same destination via different paths, resulting in [[out-of-order delivery]] to the receiver. | As a consequence of this design, the Internet Protocol only provides [[best-effort delivery]] and its service is characterized as [[Reliability (computer networking)|unreliable]]. In network architectural parlance, it is a [[connectionless protocol]], in contrast to [[connection-oriented communication]]. Various fault conditions may occur, such as [[data corruption]], [[packet loss]] and duplication. Because routing is dynamic, meaning every packet is treated independently, and because the network maintains no state based on the path of prior packets, different packets may be routed to the same destination via different paths, resulting in [[out-of-order delivery]] to the receiver. | ||
All fault conditions in the network must be detected and compensated by the participating end nodes. The [[upper layer protocol]]s of the Internet protocol suite are responsible for resolving reliability issues. For example, a host may [[Data buffer|buffer]] network data to ensure correct ordering before the data is delivered to an application. | All fault conditions in the network must be detected and compensated for by the participating end nodes. The [[upper layer protocol]]s of the Internet protocol suite are responsible for resolving reliability issues. For example, a host may [[Data buffer|buffer]] network data to ensure correct ordering before the data is delivered to an application. | ||
IPv4 provides safeguards to ensure that the header of an IP packet is error-free. A routing node discards packets that fail a header [[checksum]] test. Although the [[Internet Control Message Protocol]] (ICMP) provides notification of errors, a routing node is not required to notify either end node of errors. IPv6, by contrast, operates without header checksums, since current [[link layer]] technology is assumed to provide sufficient error detection. | IPv4 provides safeguards to ensure that the header of an IP packet is error-free. A routing node discards packets that fail a header [[checksum]] test. Although the [[Internet Control Message Protocol]] (ICMP) provides notification of errors, a routing node is not required to notify either end node of errors. IPv6, by contrast, operates without header checksums, since current [[link layer]] technology is assumed to provide sufficient error detection.{{Ref RFC|1726|rsection=6.2}}{{Ref RFC|8200}} | ||
==Link capacity and capability== | ==Link capacity and capability== | ||
| Line 131: | Line 80: | ||
* [[Next-generation network]] | * [[Next-generation network]] | ||
* [[New IP]] (proposal) | * [[New IP]] (proposal) | ||
* [[Timeline of the history of the Internet]] | |||
==References== | ==References== | ||