Network Working Group J. Postel Request for Comments: 800 J. Vernon ISI November 1982
A suggestion that, as the internet grows, the space of host names cannot remain a flat space of globally unique names, and that a hierarchy of name domains be introduced; see also RFC 822.
A description of the encoding/decoding procedure for Rapicom450 facsimile machine.
The description of a simple file format for bitmap data.
A description of the way the addresses of a few actual networks are mapped into internet addresses.
A description of how the internet type of service is mapped into the actual service parameters of a few particular networks, and vice versa.
Discusses how pre-emption of TCP connection can be implemented. Replaces IEN 125.
The specification of TCP. Replaces RFCs 761 and 675.
The specification of ICMP. Replaces RFCs 777 and 760.
The specification of IP. Replaces RFC 760.
The list of numbers assigned for networks, protocols, etc. Replaces RFCs 776, 770, 762, 758, 755, 750, 739, 604.
A description of an outage in ARPANET service and the process of determining the cause; also, subtleties of designing network protocols.
An old version; see RFC 821.
A discussion of datagram service. Intended for submission to international standards bodies.
The description of the way mail is passed between the MTP and the NIMAIL programs in ISI TOPS20. Outdated.
The description of the file format for passing mail to the MTP program from user mail programs in ISI TOPS20. Outdated.
The description of the program structure for the MTP implementation in the ISI TOPS20. Outdated.
The specification of TFTP. Replaces RFCs 768, 764 and IEN 133.
A description of the elements of a virtual terminal and the management of communications between them.
The description of IP Timestamp option, now included in the IP specification (RFC 791).
An outdated Mail protocol; see RFC 821.
Definition of this Telnet option.
Specifies a format and procedure for the exchange of messages to maintain synchronized clocks.
An old version; see RFC 792.
An old version; see RFC 790.
The definition of additional FTP Commands related to directory management.
An out-of-date table of contents for an Internet Protocol Handbook.
A discussion of issues in the transition from NCP to TCP, particularly as related to MAIL Service.
An old version of a Mail Protocol; see RFC 821.
A plan for supporting mail service in the transition from NCP to TCP; see also RFC 801.
An old version; see RFC 790.
The definition of the exchange format of the encoded facsimile data of the Rapicom 450; see also RFC 798.
The specification of the UDP.
The definition of the format for the document of a multimedia message.
An out-of-date table of contents for the Internet Protocol Handbook.
The specification of FTP.
The specification of Telnet.
A call for mailboxes with role names, such as "Management".
An old version; see RFC 790.
An old version; see RFC 793.
An old version; see RFC 791.
The definition of the protocol and format for the exchange of multimedia mail. Replaces RFC 753.
An old version; see RFC 790.
Discusses several proposals for handing the name to address to route processing for computer mail. Favors a solution based on unique-ids and a data base, see also RFCs 759, 821 and 822.
Describes a Host Name to Address look up service.
An old version; see RFC 790.
A discussion of options for addressing computer mail beyond the ARPANET.
An old version; see RFC 759.
Describes the host table used at MIT and Stanford. This has several extensions and generalizations from the NIC standard and the table used by most Tenex and TOPS20 hosts.
A survey of hosts' responses to probes of their FTP servers to see if servers (a) accept mail for unknown users and (b) support the MAIL and MLFL commands.
An old version; see RFC 790.
Updates RFC 736; see also RFCs734, 746 and 747.
Defines this Telnet option (note the date of this memo).
An update to the SUPDUP protocol (RFC 734); see also RFCs 749, 746 and 736.
An extension of SUPDUP for Graphics; see also RFCs 734, 736, 747 and 749.
The specification of a symmetrical 1822 style interface.
The description of a database service for computer mail messages, which operates via computer mail.
An extension to FTP mail to allow more efficient transmission of computer mail. Now incorporated into SMTP; see RFC788.
Defines the Name or Finger Protocol which allows one to get "who is on" or "where is user x" information from another host.
Defines the protocol used in the ARPANET packet speech experiments.
Defines the protocol used for Remote Job Entry on the UCLA CCN IBM system; replaces RFCs 599 and 189.
An old version; see RFC 790.
Defines the Time Server Protocol; see IEN 142 for the TCP and VDP versions.
An extenion to the Mail procedures. This function is incorporated in the SMTP; see also RFC 821.
Defines the procedure for negotiating to use the SUPDUP, protocol as a TELNET option; see also RFCs 734, 746, 747 and 749.
Defines a Telnet option for assigning codes to stand for strings in Telnet connections. Replaces RFC 729.
Description of a terminal control protocol used at STANFORD and MIT; see also RFCs 736, 746-749.
Specification of the format for the headers of computer mail. An old version; see RFC 822.
The specification of a Telnet Option for the control of a data entry display terminal. Replaces RFC 731.
An old version; see RFC 732.
Discusses some ideas on addressing that come up in the context of changing from 8-bit to 24-bit network addresses.
An old version; see RFC 735.
Warns of the possibility of an unexpected occurence in Telnet resulting from the interaction between option subnegotiations and the telnet SYNCH operation.
Defines a telnet option for causing a logout.
Defines a Telnet option for controlling the transmission and echoing of data to smooth the response to use in high transmission delay environments; see also RFCs 719 and 718.
Describes a possible Remote Job Entry protocol.
An old version; see RFC 822.
A discussion on the design of interactive distributed services and the kinds of primitive operations that are needed.
A discussion of the control signals in transport protocols (e.g., NCP's Interrupt or TCP's Urgent).
A discussion of computer mail addresses, with comments on real names vs. mailboxes, and mailing lists; see also RFC 819.
A short discussion of RCTE implementation issues; see also RFCs 726 and 718.
A short note on the Tenex implementation of RCTE; see also RFCs 726 and 719.
An old version; see RFC 790.
A short note updating the specification of the very Distant Host 1822 interface.
A specification of a NCP-like protocol for an ARPA-like network. Interesting to compare to the NCP specification to see what the author would do differently.
The specification of a set of Data Primitives for building interactive services.
A description of a Distributed Capability based computing system.
A description of a Distributed programming system; see also RFC 707.
A description of a programming environment for network-based programs; see also RFC 708.
A short note pointing out that the ARPANET maybe subject to a "denial of service" attack by a misbehaving host.
Describes a protocol used between a PDP-11 (the ARPANET front end) and a B6700 to support network communication.
Describes the changes to the 1822 interface to eliminate the restriction of 63 IMPs.
A poll of Telnet servers to check implementation status and Telnet options. Updates RFCs 702, 701, 679 and 669.
An earlier poll of Telnet server implementation status; see also RFC's703, 701, 679, and 669.
An earlier poll of Telnet server implementation status; see also RFCs 703, 702, 679 and 669.
Describes a protocol based loosely on a very early version of TCP, used to send data to a printer server.