ACM Home Page
Please provide us with feedback. Feedback
The design philosophy of the DARPA internet protocols
Full text PdfPdf (1.18 MB)
Source ACM SIGCOMM Computer Communication Review archive
Volume 18 ,  Issue 4  (August 1988) table of contents
Pages: 106 - 114  
Year of Publication: 1988
ISSN:0146-4833
Also published in ...
Author
D. Clark  Massachusetts Institute of Technology, Cambridge, MA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 74,   Downloads (12 Months): 701,   Citation Count: 0
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/52325.52336
What is a DOI?

ABSTRACT

The Internet protocol suite, TCP/IP, was first proposed fifteen years ago. It was developed by the Defense Advanced Research Projects Agency (DARPA), and has been used widely in military and commercial systems. While there have been papers and specifications that describe how the protocols work, it is sometimes difficult to deduce from these why the protocol is as it is. For example, the Internet protocol is based on a connectionless or datagram mode of service. The motivation for this has been greatly misunderstood. This paper attempts to capture some of the early reasoning which shaped the Internet protocols.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
V. Cerf, and R. Kahn, "A Protocol for Packet Network Intercommunication", IEEE Transactions on Communications, Vol. Com-22, No. 5, May 1974, pp. 637-648.
 
2
ISO, "Transport Protocol Specification", Tech. report IS-8073, International Orgamzation for Standardization, September 1984.
 
3
ISO, "Protocol for Providing the Connectionless- Mode Network Service", Tech. report DIS8473, International Organization for Standardization, 1986.
 
4
R. Callon, "Intemetwork Protocol", Proceedings of the IEEE, Vol. 71, No. 12, December 1983, pp. 1388-1392.
 
5
Jonathan B. Postel, "Intemetwork Protocol Approaches", IEEE Transactions on Communications, Vol. Com-28, No. 4, April 1980, pp. 605-611.
 
6
Jonathan B. Postel, Carl A. Sunshine, Danny Cohen, "The ARPA lntemet Protocol' ', Computer Networks 5, Vol. 5, No. 4, July 1981, pp. 261-271.
 
7
Alan Sheltzer, Robert Hinden, and Mike Brescia, "Connecting Different Types of Networks with Gateways", Data Communications, August 1982.
 
8
J. McQuillan and D. Walden, "The ARPA Network Design Decisions", Computer Networks, Vol. 1, No. 5, August 1977, pp. 243-289.
 
9
R.E. Kahn, S.A. Gronemeyer, J. Burdifiel, E.V. Hoversten, "Advances in Packet Radio Technology", Proceedings of the IEEE, Vol. 66, No. 11, November 1978, pp. 1408-1496.
 
10
B.M. Leiner, D.L. Nelson, F.A. Tobagi, "Issues in Packet Radio Design", Proceedings of the IEEE, Vol. 75, No. 1, January 1987, pp. 6-20.
 
11
- "Transmission Control Protocol RFC-793", 19DN Protocol Handbook, Vol. 2, September 1981, pp. 2.179-2.198.
 
12
Jack Haverty, "XNET Formats for Intemet Protocol Version 4 IEN 158", DDN Protocol Handbook, Vol. 2, October 1980, pp. 2-345 to 2-348.
 
13
Jonathan Postel, "User Datagram Protocol NIC- RFC-768", DDN Protocol Handbook, Vol. 2. August 1980, pp. 2.175-2.177.
 
14
I. Jacobs, R. Binder, and E. Hoversten, "General Purpose Packet Satellite Networks", Proceedings of the IEEE, Vol. 66, No. 11, November 1978, pp, 1448-1467.
 
15
C. Topolcic and J. Kaiser, "The SATNET Momtoring System", Proceedings of the IEEE- MILCOM Boston, MA, October 1985, pp. 26.1.1-26.1.9.
16
 
17
David D. Clark, "Window and Acknowledgment Strategy in TCP NIC-RFC-813", DDN Protocol Handbook, Vol. 3, July 1982, pp. 3-5 to 3-26.
 
18
David D. Clark, "Name, Addresses, Ports, and Routes NIC-RFC-814", DDN Protocol Handbook, Vol. 3, July 1982, pp. 3-27 to 3-40.

CITED BY  105