RFC Abstracts

RFC0817 - Modularity and efficiency in protocol implementation
This RFC will discuss some of the commonly encountered reasons why protocol implementations seem to run slowly.
RFC0816 - Fault isolation and recovery
This RFC describes the portion of fault isolation and recovery which is the responsibility of the host.
RFC0815 - IP datagram reassembly algorithms
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.
RFC0814 - Name, addresses, ports, and routes
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.
RFC0813 - Window and Acknowledgement Strategy in TCP
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.
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.
RFC0811 - Hostnames Server
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.
RFC0810 - DoD Internet host table specification
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.
RFC0809 - UCL facsimile system
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.
RFC0808 - Summary of computer mail services meeting held at BBN on 10 January 1979
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.
RFC0807 - Multimedia mail meeting notes
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.
RFC0806 - Proposed Federal Information Processing Standard: Specification for message format for computer based message systems
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.
RFC0805 - Computer mail meeting notes
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.
RFC0804 - CCITT draft recommendation T.4
This is the CCITT standard for group 3 facsimile encoding. This is useful for data compression of bit map data.
RFC0803 - Dacom 450/500 facsimile data transcoding
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.
RFC0802 - ARPANET 1822L Host Access Protocol
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.
RFC0801 - NCP/TCP transition plan
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.
RFC0800 - Request For Comments summary notes: 700-799
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.
RFC0698 - Telnet extended ASCII option
Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs.
RFC0697 - CWD command of FTP
Discusses FTP login access to "files only" directories.
RFC0696 - Comments on the IMP/Host and Host/IMP Protocol changes
Observations on current international standards recommendations from IFIP working group 6.1; see also RFCs 692, 690, 687.
RFC0695 - Official change in Host-Host Protocol
Corrects ambiguity concerning the ERR command; changes NIC 8246 and NIC 7104.
RFC0694 - Protocol information
References to documents and contacts concerning the various protocols used in the ARPANET, as well as recent developments; updates RFC 661.
RFC0692 - Comments on IMP/Host Protocol changes (RFCs 687 and 690)
A proposed solution to the problem of combined length of IMP and Host leaders; see also RFCs 696, 690 and 687.
RFC0691 - One more try on the FTP
Slight revision of RFC 686, on the subject of print files; see also RFCs 640, 630, 542, 454, 448, 414, 385 and 354.
RFC0690 - Comments on the proposed Host/IMP Protocol changes
Comments on suggestions in RFC 687; see also RFCs 692 and 696.
RFC0689 - Tenex NCP finite state machine for connections
Describes the internal states of an NCP connection in the TENEX implementation.
RFC0687 - 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.
RFC0686 - Leaving well enough alone
Discusses difference between early and later versions of FTP; see also RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354.
RFC0685 - Response time in cross network debugging
The contribution of ARPANET communication to response time.
RFC0684 - Commentary on procedure calling as a network protocol
Issues in designing distributed computing systems. Shortcomings of RFC 674; see also RFCs 542 and 354.
RFC0683 - FTPSRV - Tenex extension for paged files
Defines an extension to FTP for page-mode transfers between TENEX systems; also discusses file transfer reliability.
RFC0681 - Network UNIX
Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP, Hardware/Software requirements, reliability, availability.
RFC0680 - Message Transmission Protocol
Extends message field definition beyond RFC 561 attempts to establish syntactic and semantic standards for ARPANET; see also RFCs 733 and 822.
RFC0679 - February, 1975, survey of New-Protocol Telnet servers
An earlier poll of Telnet server implementation status. Updates RFCs 701, 702 and 669; see also RFC 703.
RFC0678 - Standard file formats
For transmission of documents across different environments.
RFC0675 - Specification of Internet Transmission Control Program
The first detailed specification of TCP; see RFC 793.
RFC0674 - Procedure call documents: Version 2
Host level protocol used in the NSW--a slightly constrained version of ARPANET Host-to-Host protocol, affecting allocation, RFNM wait, and retransmission; see also RFC 684.
RFC0672 - Multi-site data collection facility
Applicability of TIP/TENEX protocols beyond TIP accounting.
RFC0671 - Note on Reconnection Protocol
Experience with implementation in RSEXEC context.
RFC0669 - 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.
RFC0667 - Host Ports
Approved scheme to connect host ports to the network.
RFC0666 - Specification of the Unified User-Level Protocol
Discusses and proposes a common command language.
RFC0663 - Lost message detection and recovery protocol
Proposed extension of host-host protocol; see also RFCs 534, 516, 512, 492 and 467.
RFC0662 - Performance improvement in ARPANET file transfers from Multics
Experimenting with host output buffers to improve throughput.
RFC0661 - Protocol information
An old version; see RFC 694.
RFC0660 - Some changes to the IMP and the IMP/Host interface
Decoupling of message number sequences of hosts; host-host access control; message number window; messages outside normal mechanism; see also BBN 1822.
RFC0659 - Announcing additional Telnet options
Options defined in RFCs 651-658.
RFC0647 - Proposed protocol for connecting host computers to ARPA-like networks via front end processors
Approaches to Front-End protocol processing using available hardware and software.
RFC0645 - Network Standard Data Specification syntax
Providing a mechanism for specifying all attributes of a collection of bits; see also RFC 615.