37 minutes ago, TexasToast wrote
Where do you get this idea? I want to design a network which sucks, drops packets and breaks connections? Nobody wanted this so it is not by design. Its not collisions that cause problems but networks where packets exceed throughput.
I'll do some more digging on this to find out if the "Internet" definition is inclusive of the TCP/IP protocol running across the network. If it is then I stand corrected as the TCP/IP protocol is what does the retries. When I wrote the comment I was under the assumption the "Internet" was an Ethernet network (which doesn't necessarily specify the protocols running on top).
Addition: Yep. Internet protocol suite does specify TCP/IP. http://en.wikipedia.org/wiki/Internet_protocol_suite
"The layers of the protocol suite near the top are logically closer to the user application, while those near the bottom are logically closer to the physical transmission of the data. Viewing layers as providing or consuming a service is a method of abstraction to isolate upper layer protocols from the details of transmitting bits over, for example, Ethernet and collision detection, while the lower layers avoid having to know the details of each and every application and its protocol."
Thanks Toast. I hadn't realized it was restricted in this way.
Okay. After some more reading it does look like the stack stops as IP. Thanks Figs. I was thinking I just got old or something.
"The Internet layer has the task of exchanging datagrams across network boundaries. It provides a uniform networking interface that hides the actual topology (layout) of the underlying network connections. It is therefore also referred to as the layer that establishes internetworking, indeed, it defines and establishes the Internet. This layer defines the addressing and routing structures used for the TCP/IP protocol suite. The primary protocol in this scope is the Internet Protocol, which defines IP addresses. Its function in routing is to transport datagrams to the next IP router that has the connectivity to a network closer to the final data destination."
"IP is not designed to be reliable and is a best effort delivery protocol. This means that all transport layer implementations must choose whether or how to provide reliability. UDP provides data integrity via a checksum but does not guarantee delivery; TCP provides both data integrity and delivery guarantee by retransmitting until the receiver acknowledges the reception of the packet."