Shopping Cart Shopping Cart 0 items
Item Details
DoD Standard Transmission Control Protocol, TCP, January 1980, DARPA document RFC 761. Jon Postel.

DoD Standard Transmission Control Protocol, TCP, January 1980, DARPA document RFC 761.

prepared for DARPA, information processing techniques office, Arlington VA, by Information Sciences Institute, Univ. of Southern California, 1980; 84 pages, some diagrams.
Condition: Very Good, light green cardstock covers, three-hole punched at margin, stapled upper right. Some wear along paper spine, staple rust; pages clean and unmarked.
Price: $950.00
Item no. R328
Item Description
RFC 761 - DoD standard Transmission Control Protocol. January 1980 RFC:761 IEN:129 Prepared for DARPA, Defense Advanced Research Projects Agency

This document describes the DoD Standard Transmission Control Protocol (TCP). There have been eight earlier editions of the ARPA TCP specifications on which this standard is based, and the present text draws heavily from them. There have been many contributors to this work both in terms of concepts and in terms of texts. This edition incorporates the addition of security, compartmentation, and precedence concepts into the TCP specification. (from the Preface by Postel)

The Transmission Control Protocol (TCP) is intended for use as a highly reliable host-to-host protocol between hosts in packet-switched computer communications networks, and especially in interconnected systems of such networks. This document describes the functions to be performed by the Transmission Control Protocol, the program that implements it, and its interface to programs or users that require its services. (from the Introduction)

In 1982, TCP/IP became a Department of Defense (DoD) standard for all military computer networks, and was referred to as DoD TCP/IP. TCP/IP was fully applied to ARPANET on the 1st of January 1983, a date that is referred to as 'the day the Internet was born'. ...

When TCP/IP was released in the early 1980s, the amount of protocols available was a 'barebone' of protocols, and it was only by the mid-1980s that the model was 'fleshed out' to include the likes of POP and DNS. In the mid 1980s, when TCP/IP networks were interconnected - NSFNET, ARPANET, CSNET - the expansion of IP networks resulted in the need for a new naming system for hosts (Domain Name System) and superior mailing protocols (SMTP and POP). By the 1990s, when access to the Internet was opened to the general public, new services were designed for the Internet: most notable the World Wide Web (HTTP). By 2000, more protocols had been developed: such as Voice-over-Internet Protocols for Voice 2.0 applications. There came a point in time that TCP and IP, while being the core protocols of the Internet, did not accurately describe the full collection of Internet protocols, and TCP/IP was renamed as the Internet Protocol Suite. (

1980 -- IETF releases two documents, RFC 760 (Internet Protocol) and RFC 761 (Transmission Control Protocol). This is the beginning of TCP/IP. Jon Postel, editor of both RFCs, mentions in RFC 760, an implementation should be conservative in its sending behavior, and liberal in its receiving behavior(The Robustness Principle) In RFC 761, he says in a section named Robustness Principle, be conservative in what you do, be liberal in what you accept from others. Postel's Law. (