Internet Society Frontpage

Search/Site Map Membership
About the Internet Standards
Publications Public Policy
About ISOC Education

Publications 

Become an ISOC Member

Internet Documents

RFCs 800 - 899s

RFCs All DocumentsSTDs Internet Standards DocumentsBCPs Best Current Practice DocumentsFYIs Informational Documents
 

 
RFC 800 Request For Comments summary notes: 700-799
 
Authors:J. Postel, J. Vernon.
Date:November 1982
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 0800
This RFC is a slightly annotated list of the 100 RFCs from RFC 700 through RFC 799. This is a status report on these RFCs.
 
RFC 801 NCP/TCP transition plan
 
Authors:J. Postel.
Date:November 1981
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0801
This RFC discusses the conversion of hosts from NCP to TCP. And making available the principle services: Telnet, File Transfer, and Mail. These protocols allow all hosts in the ARPA community to share a common interprocess communication environment.
 
RFC 802 ARPANET 1822L Host Access Protocol
 
Authors:A.G. Malis.
Date:November 1981
Formats:txt pdf
Obsoleted by:RFC 0851
Status:UNKNOWN
DOI:10.17487/RFC 0802
This document proposed two major changes to the current ARPANET host access protocol. The first change will allow hosts to use logical addressing (i.e., host addresses that are independent of their physical location on the ARPANET) to communicate with each other, and the second will allow a host to shorten the amount of time that it may be blocked by its IMP after it presents a message to the network (currently, the IMP can block further input from a host for up to 15 seconds). See RFCs 852 and 851.
 
RFC 803 Dacom 450/500 facsimile data transcoding
 
Authors:A. Agarwal, M.J. O'Connor, D.L. Mills.
Date:November 1981
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0803
The first part of this RFC describes in detail the Dacom 450 data compression algorithms and is an update and correction to an earlier memorandum. The second part of this RFC describes briefly the Dacom 500 data compression algorithm as used by the INTELPOST electronic-mail network under development by the US Postal Service and several foreign administrators.
 
RFC 804 CCITT draft recommendation T.4
 
Authors:International Telegraph and Telephone Consultative Committee of the International Telecommunication Union.
Date:January 1981
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0804
This is the CCITT standard for group 3 facsimile encoding. This is useful for data compression of bit map data.
 
RFC 805 Computer mail meeting notes
 
Authors:J. Postel.
Date:February 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0805
This RFC consists of notes from a meeting that was held at USC Information Sciences Institute on 11 January 1982, to discuss addressing issues in computer mail. The major conclusion reached at the meeting is to extend the "username@hostname" mailbox format to "username@host.domain", where the domain itself can be further strutured.
 
RFC 806 Proposed Federal Information Processing Standard: Specification for message format for computer based message systems
 
Authors:National Bureau of Standards.
Date:September 1981
Formats:txt pdf
Obsoleted by:RFC 0841
Status:UNKNOWN
DOI:10.17487/RFC 0806
This RFC deals with Computer Based Message systems which provides a basis for interaction between different CBMS by defining the format of messages passed between them. This RFC is replaced by RFC 841.
 
RFC 807 Multimedia mail meeting notes
 
Authors:J. Postel.
Date:February 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0807
This RFC consists of notes from a meeting held at USC Information Sciences Institute on the 12th of January to discuss common interests in multimedia computer mail issues and to agree on some specific initial experiments.
 
RFC 808 Summary of computer mail services meeting held at BBN on 10 January 1979
 
Authors:J. Postel.
Date:March 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0808
This RFC is a very belated attempt to document a meeting that was held three years earlier to discuss the state of computer mail in the ARPA community and to reach some conclusions to guide the further development of computer mail systems such that a coherent total mail service would continue to be provided.
 
RFC 809 UCL facsimile system
 
Authors:T. Chang.
Date:February 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0809
This RFC describes the features of the computerised facsimile system developed in the Department of Computer Science at UCL. First its functions are considered and the related experimental work are reported. Then the disciplines for system design are discussed. Finally, the implementation of the system are described, while detailed description are given as appendices.
 
RFC 810 DoD Internet host table specification
 
Authors:E.J. Feinler, K. Harrenstien, Z. Su, V. White.
Date:March 1982
Formats:txt pdf
Obsoletes:RFC 0608
Obsoleted by:RFC 0952
Status:UNKNOWN
DOI:10.17487/RFC 0810
This RFC specifies a new host table format applicable to both ARPANET and Internet needs. In addition to host name to host address translation and selected protocol information, we have also included network and gateway name to address correspondence, and host operating system information. This RFC obsoletes the host table described in RFC 608.
 
RFC 811 Hostnames Server
 
Authors:K. Harrenstien, V. White, E.J. Feinler.
Date:March 1982
Formats:txt pdf
Obsoleted by:RFC 0953
Status:UNKNOWN
DOI:10.17487/RFC 0811
This RFC gives a description of what the Hostnames Server is and how to access it. The function of this particular server is to deliver machine-readable name/address information describing networks, gateways, hosts, and eventually domains, within the internet environment.
 
RFC 812 NICNAME/WHOIS
 
Authors:K. Harrenstien, V. White.
Date:March 1982
Formats:txt pdf
Obsoleted by:RFC 0954, RFC 3912
Status:UNKNOWN
DOI:10.17487/RFC 0812
This RFC gives a description of what the NICNAME/WHOIS Server is and how to access it. This server together with the corresponding Identification Data Base provides online directory look-up equivalent to the ARPANET Directory.
 
RFC 813 Window and Acknowledgement Strategy in TCP
 
Authors:D.D. Clark.
Date:July 1982
Formats:txt pdf
Obsoleted by:RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 0813
This RFC describes implementation strategies to deal with two mechanisms in TCP, the window and the acknowledgement. It also presents a particular set of algorithms which have received testing in the field, and which appear to work properly with each other. With more experience, these algorithms may become part of the formal specification, until such time their use is recommended.
 
RFC 814 Name, addresses, ports, and routes
 
Authors:D.D. Clark.
Date:July 1982
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 0814
This RFC gives suggestions and guidance for the design of the tables and algorithms necessary to keep track of these various sorts of identifiers inside a host implementation of TCP/IP.
 
RFC 815 IP datagram reassembly algorithms
 
Authors:D.D. Clark.
Date:July 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0815
This RFC describes an alternate approach of dealing with reassembly which reduces the bookkeeping problem to a minimum, and requires only one buffer for storage equal in size to the final datagram being reassembled, which can reassemble a datagram from any number of fragments arriving in any order with any possible pattern of overlap and duplication, and which is appropriate for almost any sort of operating system.
 
RFC 816 Fault isolation and recovery
 
Authors:D.D. Clark.
Date:July 1982
Formats:txt pdf
Obsoleted by:RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 0816
This RFC describes the portion of fault isolation and recovery which is the responsibility of the host.
 
RFC 817 Modularity and efficiency in protocol implementation
 
Authors:D.D. Clark.
Date:July 1982
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 0817
This RFC will discuss some of the commonly encountered reasons why protocol implementations seem to run slowly.
 
RFC 818 Remote User Telnet service
 
Authors:J. Postel.
Date:November 1982
Formats:txt pdf
Status:HISTORIC
DOI:10.17487/RFC 0818
This RFC is the specification of an application protocol. Any host that implements this application level service must follow this protocol.
 
RFC 819 The Domain Naming Convention for Internet User Applications
 
Authors:Z. Su, J. Postel.
Date:August 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0819
This RFC is an attempt to clarify the generalization of the Domain Naming Convention, the Internet Naming Convention, and to explore the implications of its adoption for Internet name service and user applications.
 
RFC 820 Assigned numbers
 
Authors:J. Postel.
Date:August 1982
Formats:txt pdf
Obsoletes:RFC 0790
Obsoleted by:RFC 0870
Status:HISTORIC
DOI:10.17487/RFC 0820
This RFC is an old version, see RFC 870.
 
RFC 821 Simple Mail Transfer Protocol
 
Authors:J. Postel.
Date:August 1982
Formats:txt pdf
Obsoletes:RFC 0788
Obsoleted by:RFC 2821
Also:STD 0010
Status:INTERNET STANDARD
DOI:10.17487/RFC 0821
The objective of Simple Mail Transfer Protocol (SMTP) is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. Obsoletes RFC 788, 780, and 772.
 
RFC 822 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
 
Authors:D. Crocker.
Date:August 1982
Formats:txt pdf
Obsoletes:RFC 0733
Obsoleted by:RFC 2822
Updated by:RFC 1123, RFC 2156, RFC 1327, RFC 1138, RFC 1148
Also:STD 0011
Status:INTERNET STANDARD
DOI:10.17487/RFC 0822
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 823 DARPA Internet gateway
 
Authors:R.M. Hinden, A. Sheltzer.
Date:September 1982
Formats:txt pdf
Updates:IEN109, IEN30
Status:HISTORIC
DOI:10.17487/RFC 0823
This RFC is a status report on the Internet Gateway developed by BBN. It describes the Internet Gateway as of September 1982. This memo presents detailed descriptions of message formats and gateway procedures, however, this is not an implementation specification, and such details are subject to change.
 
RFC 824 CRONUS Virtual Local Network
 
Authors:W.I. MacGregor, D.C. Tappan.
Date:August 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0824
The purpose of this note is to describe the CRONUS Virtual Local Network, especially the addressing related features. These features include a method for mapping between Internet Addresses and Local Network addresses. This is a topic of current concern in the ARPA Internet community. This note is intended to stimulate discussion. This is not a specification of an Internet Standard.
 
RFC 825 Request for comments on Requests For Comments
 
Authors:J. Postel.
Date:November 1982
Formats:txt pdf
Obsoleted by:RFC 1111, RFC 1543, RFC 2223
Status:UNKNOWN
DOI:10.17487/RFC 0825
This RFC is intended to clarify the status of RFCs and to provide some guidance for the authors of RFCs in the future. It is in a sense a specification for RFCs.
 
RFC 826 Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware
 
Authors:D. Plummer.
Date:November 1982
Formats:txt pdf
Updated by:RFC 5227, RFC 5494
Also:STD 0037
Status:INTERNET STANDARD
DOI:10.17487/RFC 0826
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
DOI:10.17487/RFC 0827
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 828 Data communications: IFIP's international "network" of experts
 
Authors:K. Owen.
Date:August 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0828
This RFC is distributed to inform the ARPA Internet community of the activities of the IFIP technical committee on Data Communications, and to encourage participation in those activities.
 
RFC 829 Packet satellite technology reference sources
 
Authors:V.G. Cerf.
Date:November 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0829
This RFC describes briefly the packet satellite technology developed by the Defense Advanced Research Projects Agency and several other participating organizations in the U.K. and Norway and provides a bibliography of relevant papers for researchers interested in experimental and operational experience with this dynamic satellite-sharing technique.
 
RFC 830 Distributed system for Internet name service
 
Authors:Z. Su.
Date:October 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0830
This RFC proposes a distributed name service for DARPA Internet. Its purpose is to focus discussion on the subject. It is hoped that a general consensus will emerge leading eventually to the adoption of standards.
 
RFC 831 Backup access to the European side of SATNET
 
Authors:R.T. Braden.
Date:December 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0831
The purpose of this RFC is to focus discussion on a particular Internet problem: a backup path for software maintenance of the European sector of the Internet, for use when SATNET is partitioned. We propose a mechanism, based upon the Source Routing option of IP, to reach European Internet sites via the VAN Gateway and UCL. This proposal is not intended as a standard at this time.
 
RFC 832 Who talks TCP?
 
Authors:D. Smallberg.
Date:December 1982
Formats:txt pdf
Obsoleted by:RFC 0833
Status:UNKNOWN
DOI:10.17487/RFC 0832
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 2-Dec-82. The tests were run on 7-Dec-82.
 
RFC 833 Who talks TCP?
 
Authors:D. Smallberg.
Date:December 1982
Formats:txt pdf
Obsoletes:RFC 0832
Obsoleted by:RFC 0834
Status:UNKNOWN
DOI:10.17487/RFC 0833
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 2-Dec-82. The tests were run on 14-Dec-82.
 
RFC 834 Who talks TCP?
 
Authors:D. Smallberg.
Date:December 1982
Formats:txt pdf
Obsoletes:RFC 0833
Obsoleted by:RFC 0835
Status:UNKNOWN
DOI:10.17487/RFC 0834
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 2-Dec-82. The tests were run on 22-Dec-82.
 
RFC 835 Who talks TCP?
 
Authors:D. Smallberg.
Date:December 1982
Formats:txt pdf
Obsoletes:RFC 0834
Obsoleted by:RFC 0836
Status:UNKNOWN
DOI:10.17487/RFC 0835
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 2-Dec-82. The tests were run on 28-Dec-82 through 5-Jan-83.
 
RFC 836 Who talks TCP?
 
Authors:D. Smallberg.
Date:January 1983
Formats:txt pdf
Obsoletes:RFC 0835
Obsoleted by:RFC 0837
Status:UNKNOWN
DOI:10.17487/RFC 0836
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 20-Dec-82. The tests were run on 4-Jan-83 through 5-Jan-83.
 
RFC 837 Who talks TCP?
 
Authors:D. Smallberg.
Date:January 1983
Formats:txt pdf
Obsoletes:RFC 0836
Obsoleted by:RFC 0838
Status:UNKNOWN
DOI:10.17487/RFC 0837
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 31-Dec-82. The tests were run on 11-Jan-83.
 
RFC 838 Who talks TCP?
 
Authors:D. Smallberg.
Date:January 1983
Formats:txt pdf
Obsoletes:RFC 0837
Obsoleted by:RFC 0839
Status:UNKNOWN
DOI:10.17487/RFC 0838
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 31-Dec-82. The tests were run on 18-Jan-83.
 
RFC 839 Who talks TCP?
 
Authors:D. Smallberg.
Date:January 1983
Formats:txt pdf
Obsoletes:RFC 0838
Obsoleted by:RFC 0842
Status:UNKNOWN
DOI:10.17487/RFC 0839
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 31-Dec-82. The tests were run on 25-Jan-83.
 
RFC 840 Official protocols
 
Authors:J. Postel.
Date:April 1983
Formats:txt pdf
Obsoleted by:RFC 0880
Status:HISTORIC
DOI:10.17487/RFC 0840
This RFC has been revised, see RFC 880.
 
RFC 841 Specification for message format for Computer Based Message Systems
 
Authors:National Bureau of Standards.
Date:January 1983
Formats:txt pdf
Obsoletes:RFC 0806
Status:UNKNOWN
DOI:10.17487/RFC 0841
This RFC is FIPS 98. The purpose of distributing this document as an RFC is to make it easily accessible to the ARPA research community. This RFC does not specify a standard for the ARPA Internet. Obsoletes RFC 806.
 
RFC 842 Who talks TCP? - survey of 1 February 83
 
Authors:D. Smallberg.
Date:February 1983
Formats:txt pdf
Obsoletes:RFC 0839
Obsoleted by:RFC 0843
Status:UNKNOWN
DOI:10.17487/RFC 0842
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 28-Jan-83. The tests were run on 1-Feb-83 and on 2-Feb-83 ISI-VAXA.ARPA.
 
RFC 843 Who talks TCP? - survey of 8 February 83
 
Authors:D. Smallberg.
Date:February 1983
Formats:txt pdf
Obsoletes:RFC 0842
Obsoleted by:RFC 0845
Updated by:RFC 0844
Status:UNKNOWN
DOI:10.17487/RFC 0843
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 844 Who talks ICMP, too? - Survey of 18 February 1983
 
Authors:R. Clements.
Date:February 1983
Formats:txt pdf
Updates:RFC 0843
Status:UNKNOWN
DOI:10.17487/RFC 0844
This survey determines how many hosts are able to respond to TELENET connections from a user at a class C site. This requires, in addition to IP and TCP, participation in gateway routing via ICMP and handling of Class C addresses. The list of hosts was taken from RFC 843, extracting only those hosts which are listed there as accepting TELNET connection. The tests were run on 18-Feb-83.
 
RFC 845 Who talks TCP? - survey of 15 February 1983
 
Authors:D. Smallberg.
Date:February 1983
Formats:txt pdf
Obsoletes:RFC 0843
Obsoleted by:RFC 0846
Status:UNKNOWN
DOI:10.17487/RFC 0845
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 15-Feb-83 from ISI-VAXA.ARPA.
 
RFC 846 Who talks TCP? - survey of 22 February 1983
 
Authors:D. Smallberg.
Date:February 1983
Formats:txt pdf
Obsoletes:RFC 0845
Obsoleted by:RFC 0847
Status:UNKNOWN
DOI:10.17487/RFC 0846
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 18-Feb-83. The tests were run on 22-Feb-83 from ISI-VAXA.ARPA.
 
RFC 847 Summary of Smallberg surveys
 
Authors:A. Westine, D. Smallberg, J. Postel.
Date:February 1983
Formats:txt pdf
Obsoletes:RFC 0846
Status:UNKNOWN
DOI:10.17487/RFC 0847
This is a summary of the surveys of Telnet, FTP and Mail (SMTP) servers conducted by David Smallberg in December 1982, January and February 1983 as reported in RFC 832-843, 845-846. This memo extracts the number of hosts that accepted the connection to their server for each of Telnet, FTP, and SMTP, and compares it to the total host in the Internet (not counting TACs or ECHOS).
 
RFC 848 Who provides the "little" TCP services?
 
Authors:D. Smallberg.
Date:March 1983
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0848
This RFC lists those hosts which provide any of these "little" TCP services: The list of hosts were taken from the NIC hostname table of 24-Feb-83. The tests were run on February 23 and 24, and March 3 and 5 from ISI-VAXA.ARPA.
 
RFC 849 Suggestions for improved host table distribution
 
Authors:M.R. Crispin.
Date:May 1983
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0849
This RFC actually is a request for comments. The issue dealt with is that of a naming registry update procedure, both as exists currently and what could exist in the future. None of the proposed solutions are intended as standards at this time; rather it is hoped that a general consensus will emerge as the appropriate solution, leaving eventually to the adoption of standards.
 
RFC 850 Standard for interchange of USENET messages
 
Authors:M.R. Horton.
Date:June 1983
Formats:txt pdf
Obsoleted by:RFC 1036
Status:UNKNOWN
DOI:10.17487/RFC 0850
This memo is distributed as an RFC only to make this information easily accessible to researchers in the ARPA community. It does not specify an Internet standard. This RFC defines the standard format for interchange of Network News articles among USENET sites. It describes the format for articles themselves, and gives partial standards for transmission of news. The news transmission is not entirely standardized in order to give a good deal of flexibility to the individual hosts to choose transmission hardware and software, whether to batch news and so on.
 
RFC 851 ARPANET 1822L Host Access Protocol
 
Authors:A.G. Malis.
Date:April 1983
Formats:txt pdf
Obsoletes:RFC 0802
Obsoleted by:RFC 0878
Status:UNKNOWN
DOI:10.17487/RFC 0851
This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. 1822L allows ARPANET hosts to use logical names as well as 1822's physical port locations to address each other. This RFC is also being presented as a solicitation of comments on 1822L, especially from host network software implementers and maintainers. Obsoletes RFC 802.
 
RFC 852 ARPANET short blocking feature
 
Authors:A.G. Malis.
Date:April 1983
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0852
This RFC specifies the ARPANET Short Blocking Feature, which will allow ARPANET hosts to optionally shorten the IMP's host blocking timer. This Feature is a replacement of the ARPANET non-blocking host interface, which was never implemented, and will be available to hosts using either the 1822 or 1822L Host Access Protocol. This RFC is also being presented as a solicitation of comments on the Short Blocking Feature, especially from host network software implementers and maintainers.
 
RFC 854 Telnet Protocol Specification
 
Authors:J. Postel, J.K. Reynolds.
Date:May 1983
Formats:txt pdf
Obsoletes:RFC 0764
Updated by:RFC 5198
Also:STD 0008
Status:INTERNET STANDARD
DOI:10.17487/RFC 0854
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 855 Telnet Option Specifications
 
Authors:J. Postel, J.K. Reynolds.
Date:May 1983
Formats:txt pdf
Obsoletes:NIC_18640
Also:STD 0008
Status:INTERNET STANDARD
DOI:10.17487/RFC 0855
This memo specifies the general form for Telnet options and the directions for their specification. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651, NIC 18640.
 
RFC 856 Telnet Binary Transmission
 
Authors:J. Postel, J. Reynolds.
Date:May 1983
Formats:txt pdf
Obsoletes:NIC_15389
Also:STD 0027
Status:INTERNET STANDARD
DOI:10.17487/RFC 0856
This Telnet Option enables a binary data mode between the Telnet modules. 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 15389.
 
RFC 857 Telnet Echo Option
 
Authors:J. Postel, J. Reynolds.
Date:May 1983
Formats:txt pdf
Obsoletes:NIC_15390
Also:STD 0028
Status:INTERNET STANDARD
DOI:10.17487/RFC 0857
This Telnet Option enables remote echoing by the other Telnet module. 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 15390.
 
RFC 858 Telnet Suppress Go Ahead Option
 
Authors:J. Postel, J. Reynolds.
Date:May 1983
Formats:txt pdf
Obsoletes:NIC_15392
Also:STD 0029
Status:INTERNET STANDARD
DOI:10.17487/RFC 0858
This Telnet Option disables the exchange of go-ahead signals between the Telnet modules. 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 15392.
 
RFC 859 Telnet Status Option
 
Authors:J. Postel, J. Reynolds.
Date:May 1983
Formats:txt pdf
Obsoletes:RFC 0651
Also:STD 0030
Status:INTERNET STANDARD
DOI:10.17487/RFC 0859
This Telnet Option provides a way to determine the other Telnet module's view of the status of options. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651 (NIC 31154).
 
RFC 860 Telnet Timing Mark Option
 
Authors:J. Postel, J. Reynolds.
Date:May 1983
Formats:txt pdf
Obsoletes:NIC_16238
Also:STD 0031
Status:INTERNET STANDARD
DOI:10.17487/RFC 0860
This Telnet Option provides a way to check the roundtrip path between two Telnet modules. 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 16238.
 
RFC 861 Telnet Extended Options: List Option
 
Authors:J. Postel, J. Reynolds.
Date:May 1983
Formats:txt pdf
Obsoletes:NIC_16239
Also:STD 0032
Status:INTERNET STANDARD
DOI:10.17487/RFC 0861
This Telnet Option provides a mechanism for extending the set of possible options. 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 16239.
 
RFC 862 Echo Protocol
 
Authors:J. Postel.
Date:May 1983
Formats:txt pdf
Also:STD 0020
Status:INTERNET STANDARD
DOI:10.17487/RFC 0862
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Echo Protocol are expected to adopt and implement this standard. The Echo service simply sends back to the originating source any data it receives.
 
RFC 863 Discard Protocol
 
Authors:J. Postel.
Date:May 1983
Formats:txt pdf
Also:STD 0021
Status:INTERNET STANDARD
DOI:10.17487/RFC 0863
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Discard Protocol are expected to adopt and implement this standard. The Discard service simply throws away any data it receives.
 
RFC 864 Character Generator Protocol
 
Authors:J. Postel.
Date:May 1983
Formats:txt pdf
Also:STD 0022
Status:INTERNET STANDARD
DOI:10.17487/RFC 0864
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Character Generator Protocol are expected to adopt and implement this standard. The Character Generator service simply sends data without regard to the input.
 
RFC 865 Quote of the Day Protocol
 
Authors:J. Postel.
Date:May 1983
Formats:txt pdf
Also:STD 0023
Status:INTERNET STANDARD
DOI:10.17487/RFC 0865
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Quote of the Day Protocol are expected to adopt and implement this standard. The Quote of the Day service simply sends a short message without regard to the input.
 
RFC 866 Active users
 
Authors:J. Postel.
Date:May 1983
Formats:txt pdf
Also:STD 0024
Status:INTERNET STANDARD
DOI:10.17487/RFC 0866
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement an Active Users Protocol are expected to adopt and implement this standard. The Active Users service simply sends a list of the currently active users on the host without regard to the input.
 
RFC 867 Daytime Protocol
 
Authors:J. Postel.
Date:May 1983
Formats:txt pdf
Also:STD 0025
Status:INTERNET STANDARD
DOI:10.17487/RFC 0867
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Daytime Protocol are expected to adopt and implement this standard. The Daytime service simply sends the current date and time as a character string without regard to the input.
 
RFC 868 Time Protocol
 
Authors:J. Postel, K. Harrenstien.
Date:May 1983
Formats:txt pdf
Also:STD 0026
Status:INTERNET STANDARD
DOI:10.17487/RFC 0868
This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Time Protocol are expected to adopt and implement this standard. This protocol provides a site-independent, machine readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900.
 
RFC 869 Host Monitoring Protocol
 
Authors:R. Hinden.
Date:December 1983
Formats:txt pdf
Status:HISTORIC
DOI:10.17487/RFC 0869
This RFC specifies the Host Monitoring Protocol used to collect information from various types of hosts in the Internet. Designers of Internet communications software are encouraged to consider this protocol as a means of monitoring the behavior of their creations.
 
RFC 870 Assigned numbers
 
Authors:J.K. Reynolds, J. Postel.
Date:October 1983
Formats:txt pdf
Obsoletes:RFC 0820
Obsoleted by:RFC 0900
Status:HISTORIC
DOI:10.17487/RFC 0870
This RFC documents the list of numbers assigned for networks, protocols, etc. Obsoletes RFCs 820, 790, 776, 770, 762, 758, 755, 750, 739, 604.
 
RFC 871 Perspective on the ARPANET reference model
 
Authors:M.A. Padlipsky.
Date:September 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0871
This RFC is primarily intended as a perspective on the ARM and points out some of the differences between the ARM and the ISORM which were expressed by members in NWG general meetings, NWG protocol design committee meetings, the ARPA Internet Working Group, and private conversations over the intervening years. Originally published as M82-47 by the MITRE Corporation, Bedford, Massachusetts.
 
RFC 872 TCP-on-a-LAN
 
Authors:M.A. Padlipsky.
Date:September 1982
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 0872
This memo attacks the notion that TCP cannot be appropriate for use on a Local Area Network. Originally published as M82-48 by the MITRE Corporation, Bedford Massachusetts.
 
RFC 873 Illusion of vendor support
 
Authors:M.A. Padlipsky.
Date:September 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0873
This memo takes issue with the claim that international standards in computer protocols presently provide a basis for low cost vendor supported protocol implementations. Originally published as M82-49 by the MITRE Corporation, Bedford, Massachusetts.
 
RFC 874 Critique of X.25
 
Authors:M.A. Padlipsky.
Date:September 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0874
This RFC is an analysis of X.25 pointing out some problems in the conceptual model, particularly the conflict between the interface aspects and the end-to-end aspects. The memo also touches on security, and implementation issues. Originally published as M82-50 by the MITRE Corporation, Bedford, Massachusetts.
 
RFC 875 Gateways, architectures, and heffalumps
 
Authors:M.A. Padlipsky.
Date:September 1982
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0875
This RFC is a discussion about the role of gateways in an internetwork, especially the problems of translating or mapping protocols between different protocol suites. The discussion notes possible functionality mis-matches, undesirable routing "singularity points", flow control issues, and high cost of translating gateways. Originally published as M82-51 by the MITRE Corporation, Bedford, Massachusetts.
 
RFC 876 Survey of SMTP implementations
 
Authors:D. Smallberg.
Date:September 1983
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0876
This RFC is a survey of implementation status. It does not specify an official protocol, but rather notes the status of implementation of aspects of a protocol. It is expected that the status of the hosts reported on will change. This information must be treated as a snapshot of the state of these implemetations.
 
RFC 877 Standard for the transmission of IP datagrams over public data networks
 
Authors:J.T. Korb.
Date:September 1983
Formats:txt pdf
Obsoleted by:RFC 1356
Status:UNKNOWN
DOI:10.17487/RFC 0877
This RFC specifies a standard adopted by CSNET, the VAN gateway, and other organizations for the transmission of IP datagrams over the X.25-based public data networks.
 
RFC 878 ARPANET 1822L Host Access Protocol
 
Authors:A.G. Malis.
Date:December 1983
Formats:txt pdf
Obsoletes:RFC 0851
Status:UNKNOWN
DOI:10.17487/RFC 0878
This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. The 1822L procedure allows ARPANET hosts to use logical identifiers as well as 1822 physical interface identifiers to address each other.
 
RFC 879 The TCP Maximum Segment Size and Related Topics
 
Authors:J. Postel.
Date:November 1983
Formats:txt pdf
Obsoleted by:RFC 7805
Updated by:RFC 6691
Status:HISTORIC
DOI:10.17487/RFC 0879
This RFC discusses the TCP Maximum Segment Size Option and related topics. The purposes is to clarify some aspects of TCP and its interaction with IP. This memo is a clarification to the TCP specification, and contains information that may be considered as "advice to implementers".
 
RFC 880 Official protocols
 
Authors:J.K. Reynolds, J. Postel.
Date:October 1983
Formats:txt pdf
Obsoletes:RFC 0840
Obsoleted by:RFC 0901
Status:HISTORIC
DOI:10.17487/RFC 0880
This RFC identifies the documents specifying the official protocols used in the ARPA Internet. Annotations identify any revisions or changes planned. Obsoletes RFC 840.
 
RFC 881 Domain names plan and schedule
 
Authors:J. Postel.
Date:November 1983
Formats:txt pdf
Updated by:RFC 0897
Status:UNKNOWN
DOI:10.17487/RFC 0881
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
 
Authors:P.V. Mockapetris.
Date:November 1983
Formats:txt pdf
Obsoleted by:RFC 1034, RFC 1035
Updated by:RFC 0973
Status:UNKNOWN
DOI:10.17487/RFC 0882
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
 
Authors:P.V. Mockapetris.
Date:November 1983
Formats:txt pdf
Obsoleted by:RFC 1034, RFC 1035
Updated by:RFC 0973
Status:UNKNOWN
DOI:10.17487/RFC 0883
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 884 Telnet terminal type option
 
Authors:M. Solomon, E. Wimmers.
Date:December 1983
Formats:txt pdf
Obsoleted by:RFC 0930
Status:UNKNOWN
DOI:10.17487/RFC 0884
This RFC specifies a standard for the ARPA Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol.
 
RFC 885 Telnet end of record option
 
Authors:J. Postel.
Date:December 1983
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 0885
This RFC specifies a standard for the ARPA Internet community. It specifies a method for marking the end of records in data transmitted on Telnet connections.
 
RFC 886 Proposed standard for message header munging
 
Authors:M.T. Rose.
Date:December 1983
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0886
This RFC specifies a draft standard for the ARPA Internet community. It describes the rules to be used when transforming mail from the conventions of one message system to those of another message system. In particular, the treatment of header fields, and recipient addresses is specified.
 
RFC 887 Resource Location Protocol
 
Authors:M. Accetta.
Date:December 1983
Formats:txt pdf
Status:EXPERIMENTAL
DOI:10.17487/RFC 0887
This RFC specifies a draft standard for the ARPA Internet community. It describes a resource location protocol for use in the ARPA Internet. It is most useful on networks employing technologies which support some method of broadcast addressing, however it may also be used on other types of networks. For maximum benefit, all hosts which provide significant resources or services to other hosts on the Internet should implement this protocol. Hosts failing to implement the Resource Location Protocol risk being ignored by other hosts which are attempting to locate resources on the Internet.
 
RFC 888 "STUB" Exterior Gateway Protocol
 
Authors:L. Seamonson, E.C. Rosen.
Date:January 1984
Formats:txt pdf
Updated by:RFC 0904
Status:UNKNOWN
DOI:10.17487/RFC 0888
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 889 Internet Delay Experiments
 
Authors:D.L. Mills.
Date:December 1983
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 0889
This memo reports on some measurements of round-trip times in the Internet and suggests some possible improvements to the TCP retransmission timeout calculation. This memo is both a status report on the Internet and advice to TCP implementers.
 
RFC 890 Exterior Gateway Protocol implementation schedule
 
Authors:J. Postel.
Date:February 1984
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0890
This memo is a policy statement on the implementation of the Exterior Gateway Protocol in the Internet. This is an official policy statement of ICCB and DARPA. After 1-Aug-84 there shall be no dumb gateways in the Internet. Every gateway must be a member of some autonomous system. Some gateway of each autonomous system must exchange routing information with some gateway of the core autonomous system using the Exterior Gateway Protocol.
 
RFC 891 DCN Local-Network Protocols
 
Authors:D.L. Mills.
Date:December 1983
Formats:txt pdf
Also:STD 0044
Status:INTERNET STANDARD
DOI:10.17487/RFC 0891
This RFC provides a description of the DCN protocols for maintaining connectivity, routing, and clock information in a local network. These procedures may be of interest to the designers and implementers of other local networks.
 
RFC 892 ISO Transport Protocol specification
 
Authors:International Organization for Standardization.
Date:December 1983
Formats:txt pdf
Obsoleted by:RFC 0905
Status:UNKNOWN
DOI:10.17487/RFC 0892
This is a draft version of the transport protocol being standardized by the ISO. This version also appeared in the ACM SIGCOMM Computer Communication Review (V.12, N.3-4) July-October 1982. This version is now out of date.
 
RFC 893 Trailer encapsulations
 
Authors:S. Leffler, M.J. Karels.
Date:April 1984
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0893
This RFC discusses the motivation for use of "trailer encapsulations" on local-area networks and describes the implementation of such an encapsulation on various media. This document is for information only. This is NOT an official protocol for the ARPA Internet community.
 
RFC 894 A Standard for the Transmission of IP Datagrams over Ethernet Networks
 
Authors:C. Hornig.
Date:April 1984
Formats:txt pdf
Also:STD 0041
Status:INTERNET STANDARD
DOI:10.17487/RFC 0894
This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Ethernet. This RFC specifies a standard protocol for the ARPA-Internet community.
 
RFC 895 Standard for the transmission of IP datagrams over experimental Ethernet networks
 
Authors:J. Postel.
Date:April 1984
Formats:txt pdf
Also:STD 0042
Status:INTERNET STANDARD
DOI:10.17487/RFC 0895
This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Experimental Ethernet. This RFC specifies a standard protocol for the ARPA Internet community.
 
RFC 896 Congestion Control in IP/TCP Internetworks
 
Authors:J. Nagle.
Date:January 1984
Formats:txt pdf
Obsoleted by:RFC 7805
Status:HISTORIC
DOI:10.17487/RFC 0896
This memo discusses some aspects of congestion control in IP/TCP Internetworks. It is intended to stimulate thought and further discussion of this topic. While some specific suggestions are made for improved congestion control implementation, this memo does not specify any standards.
 
RFC 897 Domain name system implementation schedule
 
Authors:J. Postel.
Date:February 1984
Formats:txt pdf
Updates:RFC 0881
Updated by:RFC 0921
Status:UNKNOWN
DOI:10.17487/RFC 0897
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 898 Gateway special interest group meeting notes
 
Authors:R.M. Hinden, J. Postel, M. Muuss, J.K. Reynolds.
Date:April 1984
Formats:txt pdf
Status:UNKNOWN
DOI:10.17487/RFC 0898
This memo is a report on the Gateway Special Interest Group Meeting that was held at ISI on 28 and 29 February 1984. Robert Hinden of BBNCC chaired, and Jon Postel of ISI hosted the meeting. Approximately 35 gateway designers and implementors attended. These notes are based on the recollections of Jon Postel and Mike Muuss. Under each topic area are Jon Postel's brief notes, and additional details from Mike Muuss. This memo is a report on a meeting. No conclusions, decisions, or policy statements are documented in this note.
 
RFC 899 Request For Comments summary notes: 800-899
 
Authors:J. Postel, A. Westine.
Date:May 1984
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 0899