IETF · RFC

Modularity and efficiency in protocol implementation

Modularity and efficiency in protocol implementation

This RFC will discuss some of the commonly encountered reasons why protocol implementations seem to run slowly.

Fault isolation and recovery

Fault isolation and recovery

This RFC describes the portion of fault isolation and recovery which is the responsibility of the host.

IP datagram reassembly algorithms

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…

Name, addresses, ports, and routes

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.

Window and Acknowledgement Strategy in TCP

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.

NICNAME/WHOIS

NICNAME/WHOIS

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.

Hostnames Server

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.

DoD Internet host table specification

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.

UCL facsimile system

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.

Summary of computer mail services meeting held at BBN on 10 January 1979

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.

Multimedia mail meeting notes

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.

Proposed Federal Information Processing Standard: Specification for message format for computer based message systems

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.

Computer mail meeting notes

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.

CCITT draft recommendation T.4

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.

Dacom 450/500 facsimile data transcoding

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.

ARPANET 1822L Host Access Protocol

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 netw…

NCP/TCP transition plan

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.

Request For Comments summary notes: 700-799

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.

Internet name domains

Internet name domains

Decoding facsimile data from the Rapicom 450

Decoding facsimile data from the Rapicom 450

Format for Bitmap files

Format for Bitmap files

Address mappings

Address mappings

Service mappings

Service mappings

Pre-emption

Pre-emption

Transmission Control Protocol

Transmission Control Protocol

Internet Control Message Protocol

Internet Control Message Protocol

Internet Protocol

Internet Protocol

Assigned numbers

Assigned numbers

Vulnerabilities of network control protocols: An example

Vulnerabilities of network control protocols: An example

Simple Mail Transfer Protocol

Simple Mail Transfer Protocol