| |
| RFC 10 | Documentation conventions |
| |
|
| |
| RFC 16 | M.I.T |
| |
|
| |
| RFC 24 | Documentation Conventions |
| |
|
| |
| RFC 27 | Documentation Conventions |
| |
|
| |
| RFC 33 | New Host-Host Protocol |
| |
|
| |
| RFC 36 | Protocol Notes |
| |
|
| |
| RFC 52 | Updated distribution list |
| |
| Authors: | J. Postel, S.D. Crocker. |
| Date: | July 1970 |
| Formats: | txt pdf |
| Updated by: | RFC 0069 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 54 | Official Protocol Proffering |
| |
| Authors: | S.D. Crocker, J. Postel, J. Newkirk, M. Kraley. |
| Date: | June 1970 |
| Formats: | txt pdf |
| Updated by: | RFC 0057 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 66 | NIC - third level ideas and other noise |
| |
|
| |
| RFC 70 | Note on Padding |
| |
| Authors: | S.D. Crocker. |
| Date: | October 1970 |
| Formats: | txt pdf |
| Updated by: | RFC 0228 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 74 | Specifications for Network Use of the UCSB On-Line System |
| |
| Authors: | J.E. White. |
| Date: | October 1970 |
| Formats: | pdf |
| Updated by: | RFC 0217, RFC 0225 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 80 | Protocols and Data Formats |
| |
|
| |
| RFC 86 | Proposal for a Network Standard Format for a Data Stream to Control Graphics Display |
| |
| Authors: | S.D. Crocker. |
| Date: | January 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0125 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 98 | Logger Protocol Proposal |
| |
| Authors: | E. Meyer, T. Skinner. |
| Date: | February 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0123 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 99 | Network Meeting |
| |
| Authors: | P.M. Karp. |
| Date: | February 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0116 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 101 | Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971 |
| |
|
| |
| RFC 102 | Output of the Host-Host Protocol glitch cleaning committee |
| |
| Authors: | S.D. Crocker. |
| Date: | February 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0107 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 105 | Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB |
| |
| Authors: | J.E. White. |
| Date: | March 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0217 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 107 | Output of the Host-Host Protocol Glitch Cleaning Committee |
| |
|
| |
| RFC 110 | Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts |
| |
| Authors: | J.M. Winett. |
| Date: | March 1971 |
| Formats: | pdf |
| Updated by: | RFC 0135 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 111 | Pressure from the Chairman |
| |
|
| |
| RFC 113 | Network activity report: UCSB Rand |
| |
| Authors: | E. Harslem, J.F. Heafner, J.E. White. |
| Date: | April 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0227 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 114 | File Transfer Protocol |
| |
|
| |
| RFC 116 | Structure of the May NWG Meeting |
| |
|
| |
| RFC 122 | Network specifications for UCSB's Simple-Minded File System |
| |
|
| |
| RFC 123 | Proffered Official ICP |
| |
|
| |
| RFC 125 | Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream |
| |
|
| |
| RFC 127 | Comments on RFC 123 |
| |
|
| |
| RFC 129 | Request for comments on socket name structure |
| |
| Authors: | E. Harslem, J. Heafner, E. Meyer. |
| Date: | April 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0147 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 137 | Telnet Protocol - a proposed document |
| |
| Authors: | T.C. O'Sullivan. |
| Date: | April 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0139 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 139 | Discussion of Telnet Protocol |
| |
|
| |
| RFC 140 | Agenda for the May NWG meeting |
| |
| Authors: | S.D. Crocker. |
| Date: | May 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0149 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 145 | Initial Connection Protocol Control Commands |
| |
|
| |
| RFC 158 | Telnet Protocol: A Proposed Document |
| |
|
| |
| RFC 165 | Proffered Official Initial Connection Protocol |
| |
|
| |
| RFC 171 | The Data Transfer Protocol |
| |
| Authors: | A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, J. Melvin, B. Sundberg, D. Watson, J. White. |
| Date: | June 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0264 |
| Updates: | RFC 0114 |
| Updated by: | RFC 0238 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 172 | The File Transfer Protocol |
| |
| Authors: | A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White. |
| Date: | June 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0265 |
| Updates: | RFC 0114 |
| Updated by: | RFC 0238 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 177 | Device independent graphical display description |
| |
|
| |
| RFC 189 | Interim NETRJS specifications |
| |
|
| |
| RFC 193 | NETWORK CHECKOUT |
| |
| Authors: | E. Harslem, J.F. Heafner. |
| Date: | July 1971 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0198 |
| Updated by: | RFC 0198 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 204 | Sockets in use |
| |
| Authors: | J. Postel. |
| Date: | August 1971 |
| Formats: | txt pdf |
| Updated by: | RFC 0234 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 212 | NWG meeting on network usage |
| |
| Authors: | Information Sciences Institute University of Southern California. |
| Date: | August 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0207 |
| Updated by: | RFC 0222 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 222 | Subject: System programmer's workshop |
| |
| Authors: | R.M. Metcalfe. |
| Date: | September 1971 |
| Formats: | txt pdf |
| Updates: | RFC 0212 |
| Updated by: | RFC 0234 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 264 | The Data Transfer Protocol |
| |
| Authors: | A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, B. Sundberg, D. Watson, J. White. |
| Date: | January 1972 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0171 |
| Obsoleted by: | RFC 0354 |
| Updated by: | RFC 0310 |
| Also: | RFC 0265 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 265 | The File Transfer Protocol |
| |
| Authors: | A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White. |
| Date: | November 1971 |
| Formats: | txt pdf |
| Obsoletes: | RFC 0172 |
| Obsoleted by: | RFC 0354 |
| Updated by: | RFC 0281, RFC 0294, RFC 0310 |
| Also: | RFC 0264 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 288 | Network host status |
| |
|
| |
| RFC 318 | Telnet Protocols |
| |
|
| |
| RFC 319 | Network Host Status |
| |
|
| |
| RFC 323 | Formation of Network Measurement Group (NMG) |
| |
| Authors: | V. Cerf. |
| Date: | March 1972 |
| Formats: | txt pdf |
| Updated by: | RFC 0388 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 330 | Network Host Status |
| |
|
| |
| RFC 354 | File Transfer Protocol |
| |
|
| |
| RFC 370 | Network Host Status |
| |
|
| |
| RFC 381 | Three aids to improved network operation |
| |
| Authors: | J.M. McQuillan. |
| Date: | July 1972 |
| Formats: | txt pdf |
| Updated by: | RFC 0394 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 385 | Comments on the File Transfer Protocol |
| |
|
| |
| RFC 387 | Some experiences in implementing Network Graphics Protocol Level 0 |
| |
| Authors: | K.C. Kelley, J. Meir. |
| Date: | August 1972 |
| Formats: | txt pdf |
| Updated by: | RFC 0401 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 396 | Network Graphics Working Group Meeting - Second Iteration |
| |
| Authors: | S. Bunch. |
| Date: | November 1972 |
| Formats: | txt pdf |
| Updated by: | RFC 0474 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 404 | Host Address Changes Involving Rand and ISI |
| |
| Authors: | A.M. McKenzie. |
| Date: | October 1972 |
| Formats: | txt pdf |
| Updated by: | RFC 0405 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 442 | Current flow-control scheme for IMPSYS |
| |
| Authors: | V. Cerf. |
| Date: | January 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0449 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 467 | Proposed change to Host-Host Protocol: Resynchronization of connection status |
| |
| Authors: | J.D. Burchfiel, R.S. Tomlinson. |
| Date: | February 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0492 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 482 | Traffic statistics (February 1973) |
| |
| Authors: | A.M. McKenzie. |
| Date: | March 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0497 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 495 | Telnet Protocol specifications |
| |
|
| |
| RFC 538 | Traffic statistics (June 1973) |
| |
| Authors: | A.M. McKenzie. |
| Date: | July 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0556 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 542 | File Transfer Protocol |
| |
|
| |
| RFC 560 | Remote Controlled Transmission and Echoing Telnet option |
| |
| Authors: | D. Crocker, J. Postel. |
| Date: | August 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0581 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 561 | Standardizing Network Mail Headers |
| |
| Authors: | A.K. Bhushan, K.T. Pogran, R.S. Tomlinson, J.E. White. |
| Date: | September 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0680 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 566 | Traffic statistics (August 1973) |
| |
| Authors: | A.M. McKenzie. |
| Date: | September 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0579 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 567 | Cross Country Network Bandwidth |
| |
| Authors: | L.P. Deutsch. |
| Date: | September 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0568 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 579 | Traffic statistics (September 1973) |
| |
| Authors: | A.M. McKenzie. |
| Date: | November 1973 |
| Formats: | pdf |
| Updates: | RFC 0566 |
| Updated by: | RFC 0586 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 580 | Note to Protocol Designers and Implementers |
| |
| Authors: | J. Postel. |
| Date: | October 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0582 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 597 | Host status |
| |
| Authors: | N. Neigus, E.J. Feinler. |
| Date: | December 1973 |
| Formats: | txt pdf |
| Updated by: | RFC 0603 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 603 | Response to RFC 597: Host status |
| |
| Authors: | J.D. Burchfiel. |
| Date: | December 1973 |
| Formats: | txt pdf |
| Updates: | RFC 0597 |
| Updated by: | RFC 0613 |
| Status: | UNKNOWN |
|
Questions about the ARPANET topology described in RFC 597. |
|
| |
| RFC 607 | Comments on the File Transfer Protocol |
| |
| Authors: | M. Krilanovich, G. Gregg. |
| Date: | January 1974 |
| Formats: | txt pdf |
| Obsoleted by: | RFC 0624 |
| Updated by: | RFC 0614 |
| Status: | UNKNOWN |
|
An old version; see RFC 624; see also RFCs 614, 542 and 640. |
|
| |
| RFC 661 | Protocol information |
| |
| Authors: | J. Postel. |
| Date: | November 1974 |
| Formats: | pdf |
| Updated by: | RFC 0694 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 669 | November, 1974, survey of New-Protocol Telnet servers |
| |
|
|
An earlier poll of Telnet server implementation status. Updates RFC 702; see also RFCs 703 and 679. |
|
| |
| RFC 679 | February, 1975, survey of New-Protocol Telnet servers |
| |
| Authors: | D.W. Dodds. |
| Date: | February 1975 |
| Formats: | pdf |
| Updates: | RFC 0669 |
| Updated by: | RFC 0703 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 687 | IMP/Host and Host/IMP Protocol changes |
| |
|
|
Addressing hosts on more than 63 IMPs, and other backwards compatible expansions; see also RFCs 690 and 692. |
|
| |
| RFC 690 | Comments on the proposed Host/IMP Protocol changes |
| |
|
|
Comments on suggestions in RFC 687; see also RFCs 692 and 696. |
|
| |
| RFC 701 | August, 1974, survey of New-Protocol Telnet servers |
| |
| Authors: | D.W. Dodds. |
| Date: | August 1974 |
| Formats: | txt pdf |
| Updated by: | RFC 0702 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 702 | September, 1974, survey of New-Protocol Telnet servers |
| |
|
| |
| RFC 732 | Telnet Data Entry Terminal option |
| |
|
| |
| RFC 760 | DoD standard Internet Protocol |
| |
| Authors: | J. Postel. |
| Date: | January 1980 |
| Formats: | txt pdf |
| Obsoletes: | IEN 123 |
| Obsoleted by: | RFC 0791 |
| Updated by: | RFC 0777 |
| Status: | UNKNOWN |
|
|
|
| |
| RFC 791 | Internet Protocol |
| |
|
| |
| RFC 792 | Internet Control Message Protocol |
| |
|
| |
| RFC 793 | Transmission Control Protocol |
| |
|
| |
| RFC 822 | STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES |
| |
|
|
This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952. |
|
| |
| RFC 826 | Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware |
| |
|
|
The purpose of this RFC is to present a method of Converting Protocol Addresses (e.g., IP addresses) to Local Network Addresses (e.g., Ethernet addresses). This is an issue of general concern in the ARPA Internet Community at this time. The method proposed here is presented for your consideration and comment. This is not the specification of an Internet Standard. |
|
| |
| RFC 827 | Exterior Gateway Protocol (EGP) |
| |
| Authors: | E.C. Rosen. |
| Date: | October 1982 |
| Formats: | txt pdf |
| Updated by: | RFC 0904 |
| Status: | UNKNOWN |
|
This RFC is proposed to establish a standard for Gateway to Gateway procedures that allow the Gateways to be mutually suspicious. This document is a DRAFT for that standard. Your comments are strongly encouraged. |
|
| |
| RFC 843 | Who talks TCP? - survey of 8 February 83 |
| |
|
|
This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 8-Feb-83 and on 9-Feb-83 from ISI-VAXA.ARPA. |
|
| |
| RFC 854 | Telnet Protocol Specification |
| |
|
|
This is the specification of the Telnet protocol used for remote terminal access in the ARPA Internet. The purpose of the TELNET Protocol is to provide a fairly general, bi-directional, eight-bit byte oriented communications facility. Its primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. It is envisioned that the protocol may also be used for terminal-terminal communication ("linking") and process-process communication (distributed computation). This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 18639. |
|
| |
| RFC 881 | Domain names plan and schedule |
| |
| Authors: | J. Postel. |
| Date: | November 1983 |
| Formats: | txt pdf |
| Updated by: | RFC 0897 |
| Status: | UNKNOWN |
|
This RFC outlines a plan and schedule for the implementation of domain style names throughout the DDN/ARPA Internet community. The introduction of domain style names will impact all hosts on the DDN/ARPA Internet. |
|
| |
| RFC 882 | Domain names: Concepts and facilities |
| |
|
|
This RFC introduces domain style names, their use for ARPA Internet mail and host address support, and the protocol and servers used to implement domain name facilities. |
|
| |
| RFC 883 | Domain names: Implementation specification |
| |
|
|
This RFC discusses the implementation of domain name servers and resolvers, specifies the format of transactions, and discusses the use of domain names in the context of existing mail systems and other network software. |
|
| |
| RFC 888 | "STUB" Exterior Gateway Protocol |
| |
| Authors: | L. Seamonson, E.C. Rosen. |
| Date: | January 1984 |
| Formats: | txt pdf |
| Updated by: | RFC 0904 |
| Status: | UNKNOWN |
|
This RFC describes the Exterior Gateway Protocol used to connect Stub Gateways to an Autonomous System of core Gateways. This document specifies the working protocol, and defines an ARPA official protocol. All implementers of Gateways should carefully review this document. |
|
| |
| RFC 897 | Domain name system implementation schedule |
| |
|
|
This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is a partial update of RFC 881. The intent of this memo is to detail the schedule for the implementation for the Domain Style Naming System. The names of hosts will be changed to domain style names. Hosts will begin to use domain style names on 14-Mar-84, and the use of old style names will be completely phased out before 2-May-84. This applies to both the ARPA research hosts and the DDN operational hosts. This is an official policy statement of the ICCB and the DARPA. |
|
| |
| RFC 907 | Host Access Protocol specification |
| |
| Authors: | Bolt Beranek and Newman Laboratories. |
| Date: | July 1984 |
| Formats: | txt pdf |
| Updated by: | RFC 1221 |
| Also: | STD 0040 |
| Status: | STANDARD |
|
This document specifies the Host Access Protocol (HAP). Although HAP was originally designed as the network-access level protocol for the DARPA/DCA sponsored Wideband Packet Satellite Network, it is intended that it evolve into a standard interface SATNET and TACNET (aka MATNET) as well as the Wideband Network. HAP is an experimental protocol, and will undergo further revision as new capabilities are added and/or different satellite networks are suported. Implementations of HAP should be performed in coordination with satellite network development and operations personnel. |
|
| |
| RFC 908 | Reliable Data Protocol |
| |
| Authors: | D. Velten, R.M. Hinden, J. Sax. |
| Date: | July 1984 |
| Formats: | txt pdf |
| Updated by: | RFC 1151 |
| Status: | EXPERIMENTAL |
|
The Reliable Data Protocol (RDP) is designed to provide a reliable data transport service for packet-based applications. This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvemts. |
|
| |
| RFC 951 | Bootstrap Protocol |
| |
| Authors: | W.J. Croft, J. Gilmore. |
| Date: | September 1985 |
| Formats: | txt pdf |
| Updated by: |
| |
