Thus, Kahn decided to develop a new version of the protocol which could meet the needs of an open-architecture network environment. This protocol would eventually be called the
Transmission Control Protocol/Internet Protocol (TCP/IP). While NCP tended to act like a device driver, the new protocol would be more like a communications protocol.
Four ground rules were critical to Kahn's early thinking:
Each distinct network would have to stand on its own and
no internal changes could be required to any such network to connect it to the Internet.
Communications would be on a best effort basis. If a packet didn't make it to the final destination, it would shortly be retransmitted from the source.
Black boxes would be used to connect the networks; these would later be called gateways and routers. There would be no information retained by the gateways about the individual flows of packets passing through them, thereby keeping them simple and avoiding complicated adaptation and recovery from various failure modes.
There would be no global control at the operations level.
Other key issues that needed to be addressed were:
Algorithms to prevent lost packets from permanently disabling communications and enabling them to be successfully retransmitted from the source.
Providing for host to host "pipelining" so that multiple packets could be enroute from source to destination at the discretion of the participating hosts, if the intermediate networks allowed it.
Gateway functions to allow it to forward packets appropriately. This included interpreting IP headers for routing, handling interfaces, breaking packets into smaller pieces if necessary, etc.
The need for end-end checksums, reassembly of packets from fragments and detection of duplicates, if any.
The need for global addressing
Techniques for host to host flow control.
Interfacing with the various operating systems
There were also other concerns, such as implementation efficiency, internetwork performance, but these were secondary considerations at first.
Bookmarks