The Internet Protocol (IP) is a data-oriented protocol used by source and destination server for communicating data across a packet-switched internetwork. Data in an IP internetwork are sent in blocks referred to as packets or datagrams (the terms are basically synonymous in IP). In particular, in IP no setup is needed before a host tries to send packets to a host it has previously not communicated with. The Internet Protocol provides an ''unreliable'' datagram service (also called ''best effort''); i.e. it makes almost no guarantees about the packet. The packet may arrive damaged, it may be out of order (compared to other packets sent between the same hosts), it may be duplicated, or it may be dropped entirely. If an application needs reliability, it is provided by other means. Packet switches, or internetwork routers, forward IP datagrams across interconnected layer 2 networks. The lack of any delivery guarantees means that the design of packet switches is made much simpler. (Note that if the network does drop, reorder or otherwise damage a lot of packets, the performance seen by the user will be poor, so most network elements do try hard to not do these things - hence the ''best effort'' term. However, an occasional error will produce no noticeable effect.) 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. IPv6 is the proposed successor to IPv4; the Internet is slowly running out of addresses, and IPv6 has 128-bit source and destination addresses, providing more addresses than IPv4's 32 bits. Versions 0 through 3 were either reserved or unused. Version 5 was used for an experimental stream protocol. Other version numbers have been assigned, usually for experimental protocols, but have not been widely used. == IP addressing and routing == Perhaps the most complex aspects of IP are addressing and routing. Addressing refers to how end hosts are 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. ==See also== *IPv4 *IPv6 *IP address *Internet protocol suite *List of well-known ports (computing) *IANA * Connectionless protocol ==External links== *[RFC 791], [http://www.rfcsearch.org/rfcview/RFC/791.html RFC0791 in html format] *[http://www.iana.org Internet Assigned Numbers Authority (IANA)] *[http://ip-number.com Show your IP address] *[http://www.myipaddress.in Displays IP address] [http://www.showmyip.com Show your IP address] *[http://checkip.dyndns.org/ Simple IP check tool] *[http://www.iptool.us My IP Tool] Firefox extension. *[http://www.airhive.net/modules.php?name=Web_Links&l_op=visit&lid=1475 Flash/audio] showing some basic IP configuration options typically available in the Linksys WRT54G routers. zh-cn:互联网协议 Internet standards Internet architecture Internet protocols Computer networks Information technology
==ST description== I described ST as a "stream" protocol rather than "multicast" since IPv4 supports multicast too; the essential difference in ST is that it requires setup in the switches/routers before any data can be sent. User:Jnc 05:09, 24 Aug 2003 (UTC) ==OSIModel== Should we add the {OSIModel} thing to this page? It's on some of the others. User:BrokenSegue 22:23, 21 Sep 2004 (UTC) : No reason not to. User:Jnc 14:44, 4 Oct 2004 (UTC) == Moving header format to IPv4 page == Given that we have IPv4 and IPv6 pages, I think a lot of the detail on IPv4 (header formats, etc) should be moved to that page, and simply referred to from here. This page would then contain just generic internetwork-level concepts. Is everyone OK with this? User:Jnc 14:44, 4 Oct 2004 (UTC) : I agree with these changes. *think* : Though, there are a couple of ways of thinking about it. Personally, I feel that IP should now be thought of as a sort of generic term that refers to several different network layer protocols, and there ought to be links to the specifics of those protocols. But, OTOH, whenever anybody talks about IP right now, they mean IPv4. I hope that won't be the case in the future, but the fact is, it is the case right now. : --User:Omnifarious 05:31, 2004 Oct 5 (UTC) == Fragmentation/reassembly confusion == [Discussion moved to Talk:IPv4 as it is no longer germane to this page after the reorg mentioned above/below. User:Jnc 21:19, 21 Oct 2004 (UTC)] Now I guess I should cut-n-paste this into the page! :-) Alas, since only IPv4 has fragmentation, I'm going to have to do the "move the packet format to the IPv4 page", since IPv6 doesn't have fragmentation in the basic header. User:Jnc 20:38, 21 Oct 2004 (UTC) ==Packets/datagrams== 'packets or datagrams (the terms are basically synonymous in IP)' can someone explain why? User:Helix84 15:31, 11 Jan 2005 (UTC) : Does clicking on the link to Packet, and reading the article there, help? User:Jnc User_talk:Jnc 21:13, 11 Jan 2005 (UTC)
#REDIRECT internet protocol suite
See other meanings of words starting from letter:
Words begining with Internet_Protocol:
Internet_Protocol
Internet_Protocol
Internet_protocol
Internet_protocols
Internet_Protocol_address
Internet_protocol_address
Internet_protocol_spoofing
Internet_protocol_spoofing
Internet_protocol_suite
Internet_protocol_suite
Internet Protocol
The Internet Protocol (IP) is a data-oriented protocol used by source and destination server for communicating data across a packet-switched internetwork. Data in an IP internetwork are sent in blocks referred to as packets or datagrams (the terms are basically synonymous in IP). In particular, in IP no setup is needed before a host tries to send packets to a host it has previously not communicated with. The Internet Protocol provides an ''unreliable'' datagram service (also called ''best effort''); i.e. it makes almost no guarantees about the packet. The packet may arrive damaged, it may be out of order (compared to other packets sent between the same hosts), it may be duplicated, or it may be dropped entirely. If an application needs reliability, it is provided by other means. Packet switches, or internetwork routers, forward IP datagrams across interconnected layer 2 networks. The lack of any delivery guarantees means that the design of packet switches is made much simpler. (Note that if the network does drop, reorder or otherwise damage a lot of packets, the performance seen by the user will be poor, so most network elements do try hard to not do these things - hence the ''best effort'' term. However, an occasional error will produce no noticeable effect.) 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. IPv6 is the proposed successor to IPv4; the Internet is slowly running out of addresses, and IPv6 has 128-bit source and destination addresses, providing more addresses than IPv4's 32 bits. Versions 0 through 3 were either reserved or unused. Version 5 was used for an experimental stream protocol. Other version numbers have been assigned, usually for experimental protocols, but have not been widely used. == IP addressing and routing == Perhaps the most complex aspects of IP are addressing and routing. Addressing refers to how end hosts are 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. ==See also== *IPv4 *IPv6 *IP address *Internet protocol suite *List of well-known ports (computing) *IANA * Connectionless protocol ==External links== *[RFC 791], [http://www.rfcsearch.org/rfcview/RFC/791.html RFC0791 in html format] *[http://www.iana.org Internet Assigned Numbers Authority (IANA)] *[http://ip-number.com Show your IP address] *[http://www.myipaddress.in Displays IP address] [http://www.showmyip.com Show your IP address] *[http://checkip.dyndns.org/ Simple IP check tool] *[http://www.iptool.us My IP Tool] Firefox extension. *[http://www.airhive.net/modules.php?name=Web_Links&l_op=visit&lid=1475 Flash/audio] showing some basic IP configuration options typically available in the Linksys WRT54G routers. zh-cn:互联网协议 Internet standards Internet architecture Internet protocols Computer networks Information technology
Internet Protocol
==ST description== I described ST as a "stream" protocol rather than "multicast" since IPv4 supports multicast too; the essential difference in ST is that it requires setup in the switches/routers before any data can be sent. User:Jnc 05:09, 24 Aug 2003 (UTC) ==OSIModel== Should we add the {OSIModel} thing to this page? It's on some of the others. User:BrokenSegue 22:23, 21 Sep 2004 (UTC) : No reason not to. User:Jnc 14:44, 4 Oct 2004 (UTC) == Moving header format to IPv4 page == Given that we have IPv4 and IPv6 pages, I think a lot of the detail on IPv4 (header formats, etc) should be moved to that page, and simply referred to from here. This page would then contain just generic internetwork-level concepts. Is everyone OK with this? User:Jnc 14:44, 4 Oct 2004 (UTC) : I agree with these changes. *think* : Though, there are a couple of ways of thinking about it. Personally, I feel that IP should now be thought of as a sort of generic term that refers to several different network layer protocols, and there ought to be links to the specifics of those protocols. But, OTOH, whenever anybody talks about IP right now, they mean IPv4. I hope that won't be the case in the future, but the fact is, it is the case right now. : --User:Omnifarious 05:31, 2004 Oct 5 (UTC) == Fragmentation/reassembly confusion == [Discussion moved to Talk:IPv4 as it is no longer germane to this page after the reorg mentioned above/below. User:Jnc 21:19, 21 Oct 2004 (UTC)] Now I guess I should cut-n-paste this into the page! :-) Alas, since only IPv4 has fragmentation, I'm going to have to do the "move the packet format to the IPv4 page", since IPv6 doesn't have fragmentation in the basic header. User:Jnc 20:38, 21 Oct 2004 (UTC) ==Packets/datagrams== 'packets or datagrams (the terms are basically synonymous in IP)' can someone explain why? User:Helix84 15:31, 11 Jan 2005 (UTC) : Does clicking on the link to Packet, and reading the article there, help? User:Jnc User_talk:Jnc 21:13, 11 Jan 2005 (UTC)
Internet protocol
#REDIRECT internet protocol suite
See other meanings of words starting from letter:
I
IA | IB | IC | ID | IE | IF | IG | IH | IJ | IK | IL | IM | IN | IO | IP | IR | IS | IT | IU | IW | IX | IY | IZ |Words begining with Internet_Protocol:
Internet_Protocol
Internet_Protocol
Internet_protocol
Internet_protocols
Internet_Protocol_address
Internet_protocol_address
Internet_protocol_spoofing
Internet_protocol_spoofing
Internet_protocol_suite
Internet_protocol_suite
These materials are based on Wikipedia and licensed under the GNU FDL
YouTube.com videos better site than Turbo Tax 2007
