OLE@SRI-NIC.ARPA (Ole Jorgen Jacobsen) (11/21/86)
Folks,
Attached is an updated copy of the RFC sets I sent out recently.
This file is now kept in [SRI-NIC.ARPA]NETINFO:RFC-SETS.TXT, is available
via Anonymous FTP and will be updated when appropriate. If you do not
have access to FTP, send a message to me or NIC@SRI-NIC.ARPA requesting
the file. I do not plan to send the file to the entire list again after
this.
Also attached is a new file: [SRI-NIC.ARPA]NETINFO:TCP-IP-BIB.TXT
which contains a bibliography of recent articles pertaining to TCP/IP,
X.25, TP-4, and other standards.
Cheers,
Ole
-------------------------------------------------------------------------
[ NETINFO:RFC-SETS.TXT ] [ 11/86, OJJ ]
RFC SETS
DDN Network Information Center
SRI International, Room EJ291
333 Ravenswood Avenue
Menlo Park, CA 94025
(800) 235-3155 or (415) 859-3695
NIC@SRI-NIC.ARPA
If you are ordering RFCs individually, the attached sets of RFCs can guide you
in ordering a complete list of RFCs by topic, such as "mail" and "gateways".
Related RFCs are grouped together within each set. Call the DDN Network
Information Center if you need assistance in ordering RFCs. RFCs which are
marked with an asterisk (*) are not included in the 1985 DDN Protocol Handbook.
MAJOR RFCs
RFC-791 Internet Protocol (IP)
RFC-792 Internet Control Message Protocol (ICMP)
RFC-793 Transmission Control Protocol (TCP)
RFC-768 User Datagram Protocol (UDP)
RFC-854 Telnet Protocol (see also many Telnet Options
in the RFC index)
RFC-959 File Transfer Protocol (FTP)
RFC-821 Simple Mail Transfer Protocol (SMTP)
RFC-822 Standard for the Format of ARPA Internet Text Messages
RFC-990 Assigned Numbers
RFC-991 Official ARPA Internet Protocols
MAIL RFCs
RFC-821 Simple Mail Transfer Protocol (SMTP)
RFC-822 Standard for the Format of ARPA Internet Text Messages
RFC-886 * Proposed Standard for Message Header Munging
RFC-915 * Network Mail Path Services
RFC-934 * Proposed Standard for Message Encapsulation
RFC-937 Post Office Protocol Version 2
RFC-974 * Mail Routing and the Domain System
RFC-976 * UUCP Mail Interchange Format Standard
RFC-987 * Mapping between X.400 and RFC 822
NAMING AND DOMAIN RFCs
RFC-882 * Domain Names - Concepts and Facilities
RFC-883 Domain Names - Implementation Specification
RFC-920 * Domain Requirements
RFC-921 * Domain Name System Implementation Schedule - Revised
RFC-973 * Domain System Changes and Observations
RFC-974 * Mail Routing and the Domain System
RFC-952 Internet Host Table Specification
RFC-953 Hostnames Server
GATEWAY RFCs
IEN-109 * How to build a gateway
RFC-792 Internet Control Message Protocol (ICMP)
RFC-823 The DARPA Internet Gateway (GGP)
RFC-890 * Exterior Gateway Protocol Implementation Schedule
RFC-904 Exterior Gateway Protocol Formal Specification (EGP)
RFC-911 * EGP Gateway under Berkeley UNIX 4.2
RFC-975 * Autonomous Confederations
RFC-985 * Requirements for Internet Gateways -- Draft
LOCAL AREA, SUBNET and BROADCAST RFCs
RFC-894 A Standard for the Transmission of IP Datagrams
over Ethernet Networks
RFC-895 Standard for the Transmission of IP Datagrams over
Experimental Ethernet Networks
RFC-948 Two Methods for the Transmission of IP Datagrams over
IEEE 802.3 Networks
RFC-826 An Ethernet Address Resolution Protocol
RFC-903 A Reverse Address Resolution Protocol
RFC-925 * Multi-LAN Address Resolution Protocol
RFC-917 * Internet Subnets
RFC-940 * Toward an Internet Standard Scheme for Subnetting
RFC-950 * Internet Standard Subnetting Procedure
RFC-919 * Broadcasting Internet Datagrams
RFC-922 * Broadcasting Internet Datagrams in the Presence of Subnets
RFC-947 * Multi-network Broadcasting within the Internet
RFC-966 * Host Groups: A Multicast Extension to the Internet Protocol
RFC-988 * Host Extensions for IP Multicasting
BACKGROUND RFCs
IEN-48 The Catenet Model for Internetworking
IEN-137 * On Holy Wars and a Plea for Peace
IEN-140 * Mutual Encapsulation of Internetwork Protocols
RFC-896 * Congestion Control in IP/TCP
RFC-970 * On Packet Switches with Infinite Storage
RFC-813 Window and Acknowledgement Strategy in TCP
RFC-814 Name, Addresses, Ports, and Routes
RFC-815 IP Datagram Reassembly Algorithms
RFC-816 Fault Isolation and Recovery
RFC-817 Modularity and Efficiency in Protocol Implementation
RFC-871 * A Perspective on the ARPANET Reference Model
RFC-872 * TCP-ON-A-LAN
RFC-873 * The Illusion of Vendor Support
RFC-874 * A Critique of X.25
RFC-875 * Gateways, Architectures, and Heffalumps
RFC-980 * Protocol Documentation Order Information
TOWARDS INTERNATIONAL STANDARDS
RFC-905 * ISO Transport Protocol Specification
RFC-942 * Transport Protocols for Department of Defense Data Networks
RFC-939 * Executive Summary of the NRC Report on Transport Protocols
for Department of Defense Data Networks
RFC-945 * DoD Statement on the NRC Report
RFC-983 * ISO Transport Services on Top of the TCP
RFC-941 * Addendum to the Network Service Definition Covering
Network Layer Addressing
RFC-987 * Mapping between X.400 and RFC 822
RFC-926 * Protocol for Providing the Connectionless-Mode
Network Services
-------------------------------------------------------------------------
[ NETINFO:TCP-IP-BIB.TXT ] [ 11/86, OJJ ]
BACKGROUND READING
DDN Network Information Center
SRI International, Room EJ291
333 Ravenswood Avenue
Menlo Park, CA 94025
(800) 235-3155 or (415) 859-3695
NIC@SRI-NIC.ARPA
The attached bibliography of recent articles pertaining to TCP and IP, X.25,
the Transport Protocol (TP-4), OSI and other standards was compiled by the DDN
Network Information Center (NIC) as a background reading list for vendors. The
bibliography cites articles, mostly from the open literature, representing a
variety of viewpoints. It has not been sanctioned by any government agency,
nor does it contain references to the Requests for Comments (RFCs). The NIC
does not provide copies of these articles because they are readily available in
the open literature. The NIC has copies of the DDN Protocol Handbook, the RFC
index, and the OSD (Office of the Secretary of Defense) directives pertaining
to the DoD protocol suite.
-------------------------------------------------------------------------------
Bolt Beranek and Newman, Inc. Features of internetwork protocol [Draft].
Washington, DC: National Bureau of Standards, Inst. for Computer Sciences
and Technology; 1980 July; Rpt. No. ICST/HLNP-80-8. 67 p.
Burruss, J. Features of the transport and session protocols [Draft report].
Washington, DC: National Bureau of Standards, Inst. for Computer Sciences
and Technology; 1980 March; Rpt. No. ICST/HLNP-80-1 and BBN Rpt. No. 4361.
71 p.
Cashin, J. DDN answers the protocol call. Software News. 4(12): 16-17;
1984 December.
Cerf, V.; Cain, E. DoD Internet architecture model. Comput. Networks. 7(5):
307-318; 1983 October.
Cerf, V.; Lyons, R.E. Military requirements for packet switched networks and
their implications for protocol standardization. Comput. Networks. 7(5):
293-306; 1983 October.
Comer, D.; Korb, J.T. CSNET protocol software: The IP-to-X.25 interface.
Communications Architectures and Protocols; SIGCOMM '83 Symposium; 1983
March 8-9; Austin, Tx. New York: Association for Computing Machinery;
1983: 154-159.
Eslam, E.S. Defense Data Network hits its stride. Telecommunications. 20(5):
121-123; 1986 May.
Estrin, J. Networking standards end confusion. Unix/World. 3(10): 26-31;
1986 October.
Estrin, J.; Carrico, W. TCP/IP protocols address LAN needs. Mini-Micro Syst.
19(7): 111-119; 1986 May.
Groenbaek, I. Conversion between the TCP and ISO tranport protocols as a
method of achieving interoperability between data communications systems.
IEEE J. Sel. Areas Commun. SAC4(2): 288-296; 1986 March.
Groenbaek, I. TCP and ISO transport service: A brief description and
comparison; The Hague, Netherlands: SHAPE Technical Center; 1984 February;
STC TM-726. 37 p.
Grossman, D.B. Comments on "Congestion control in TCP/IP internetworks".
Comput. Commun. Rev. 15(2): 3-7; 1985 April/May.
Haverty, J.; Tauss, G. How good is TCP/IP? Gov. Data Syst. 15(3): 54-58;
1986 April-May.
Haverty, J.; Gurwitz, R. Protocols and their implementation: A matter of
choice. Data Commun. 12(3): 153-166; 1983 March.
Herman, J.G.; McQuillan, J.M. How to expand and modernize a global network.
Data Commun. 14(13): 171-190; 1985 December.
Horwitt, E. Military acts to speed OSI. Computerworld. 20(33): 1-4; 1986
August 18.
Horwitt, E. OSI substitute lures net users. Computerworld. 20(30): 1-8; 1986
July 28.
Ladermann, D. Not yet time for trusty TCP/IP to be shunted aside. Gov.
Comput. News. 5(19): 46-47; 1986 September 26
Lynch, C.A. Protocols in perspective. Bull. Am. Soc. Inf. Sci. 11(6): 9-11;
1985 August.
Moskowitz, R.A. TCP/IP: Stairway to OSI. Computer Decisions. 18(9): 50-51;
1986 April 22.
Nagle, J. Congestion control in IP/TCP internetworks. Comput. Commun. Rev.
14(4); 11-17; 1984 October.
National Bureau of Standards, Inst. for Computer Sciences and Technology.
Computer networks program. Washington, DC: NBS-ICST; 1986 February. 36 p.
National Bureau of Standards, Inst. for Computer Sciences and Technology.
Implementation guide for ISO transport protocol. Washington, DC: NBS-ICST;
1985 December. ICST/SNA-85-18. 90 p.
National Bureau of Standards, Inst. for Computer Sciences and Technology.
Military supplement to ISO transport protocol. Washington, DC: NBS-ICST;
1985 December. ICST/SNA-85-17. 31 p.
Nelson, S. DOD net uses unique protocols. Gov. Comput. News. 4: 88; 1985
March 8.
Nelson-Rowe, L. National Bureau of Standards OKs first U.S. E-mail
specification. Commun. Week: 16; 1986 August 18.
Postel, J.B. Internetwork applications using the DARPA protocol suite.
Marina del Rey, CA: University of Southern California, Information
Sciences Inst.; 1985 April; ISI/RS-85-151. 13 p.
Postel, J.B. Internetwork protocol approaches. In: Tutorial: Computer
communications: Architectures, protocols, and standards; By Stallings,
W. Silver Spring, MD: IEEE Computer Society Press; 1985: 223-230.
Rauch-Hindin, W. Communication standards: OSI is not a paper tiger. Systems
and Software. 4(3); 64-86; 1985 March.
Rose, M.T. Comments on "Comments on 'Congestion control in TCP/IP
internetworks'" or The Holy Wars begin again. Comput. Commun. Rev. 15(5);
2-9; 1985 October/November.
Rudin, H. Informal overview of formal protocol specification. IEEE Commun.
Mag. 23(3): 46-52; 1985 March.
Santos, P.J. Jr. (Comments)2 on "Congestion control in IP/TCP internetworks".
Comput. Commun. Rev. 15(3); 3-5; 1985 July/August.
Selvaggi, P.S. Department of Defense data protocol standardization program.
Comput. Networks. 7(5): 319-328; 1983 October.
Sirbu, M.A.; Zwimpfer, L.E. Standards setting for computer communication:
The Case of X.25. IEEE Commun. Mag. 23(3): 35-45; 1985 March.
Stallings, W. Can we talk? Datamation. 31(20): 101-106; 1985 October 15.
Stallings, W. Primer: Understanding transport protocols. Data Commun. 13(11):
201-215; 1984 November.
Tauss, G.; Kane, J. Agencies handle data transfer with packet tech. Gov.
Comput. News. 5: 37-38; 1986 January 17.
Tully, J. XNS and TCP/IP protocols on Ethernet. Networks 85: Proceedings of
the European Computer Communications Conference; 1985; London. Pinner,
England: Online Publications; 1985: 103-112.
Wood, H.M. Network protocol standards: The U.S. government approach.
J. Telecommun. Networks. 1(2): 189-190; 1982 June.
Zhang, L. Why TCP timers don't work well. Communications Architectures and
Protocols; SIGCOMM '86 Symposium; 1986 August 5-7; Stowe, VT: Association
for Computing Machinery; 1986.
-------