perm filename INDEX[RFC,NET]6 blob
sn#747680 filedate 1984-03-16 generic text, type C, neo UTF8
COMMENT ⊗ VALID 00004 PAGES
C REC PAGE DESCRIPTION
C00001 00001
C00002 00002 RFC Author Date Title (899:800)
C00034 00003 RFC Author Date Title (799:700)
C00060 00004 RFC Author Date Title (699:600)
C00081 ENDMK
C⊗;
RFC Author Date Title (899:800)
--- ------ ---- -----
∂897 J. Postel Mar 84 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.
∂896 J. Nagel Feb 84 Congestion Control in IP/TCP Internetworks
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.
∂892 ISO Dec 83 ISO Transport Protocol Specification
This document specifies the Transport Protocol developed by the ISO.
It is presented in RFC form for the information of the ARPA Internet
community. This is not an ARPA Internet standard.
∂891 D. Mills Dec 83 DCN Local-Network Protocols
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.
∂890 J. Postel Feb 84 Exterior Gateway Protocol Implementation Schedule
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.
∂889 D. Mills Dec 83 Internet Delay Experiments
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.
∂888 L. Seamonson Jan 84 Stub Exterior Gateway Protocol
& E. Rosen
This note defines the protocol that stub gateways use with core
gateways to exchange routing information. This is an ARPA official
protocol. All gateway designers and implementers should study this
document carefully.
∂885 J. Postel Dec 83 Telnet End of Record Option
This RFC specifies a standard for the ARPA Internet community. Hosts on the
ARPA Internet that need to mark record boundaries within Telnet protocol data
are expected to adopt and implement this standard.
∂884 Solomon & Dec 83 Telnet Terminal Type Option
Wimmers
This RFC specifies a standard for the ARPA Internet community. Hosts on the
ARPA Internet that exchange terminal type information within the Telnet
protocol are expected to adopt and implement this standard.
∂883 Mockapetris Nov 83 Domain Names - Implementation and Specification
This memo 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.
∂882 Mockapetris Nov 83 Domain Names - Concepts and Facilities
This RFC introduces domain style names, their use for ARPA Internet
mail and host address support, and the protocols and servers used to
implement domain name facilities.
∂881 J. Postel Nov 83 The Domain Names Plan and Schedule
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.
∂880 Reynolds&Postel Oct 83 Official Protocols
This RFC identifies the documents specifying the official protocols used in
the Internet. Obsoletes: RFC 840
∂879 J. Postel Nov 83 The TCP Maximum Segment Size and Related Topics
This RFC clarifies the TCP specification and provides some advice to
implementers. In particular, the relationship between the TCP
maximum segment size and the IP maximum datagram size is discussed
and defined.
∂878 A. Malis Dec 83 The ARPANET 1822L Host Access Protocol
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.
∂877 J. T. Korb Sep 83 A Standard for the Transmission of IP
Datagrams Over Public Data Networks
This memo specifies the standard encapsulation for transmission of IP
Datagrams in X.25 Packets over Public Data Networks.
∂876 D. Smallberg Sep 83 Survey of SMTP Implementations
This memo reports the results of a survey of implementations of the
mail transport protocol. The features checked were: (1) the
interaction with an ARPANET host (a host on a class A network), (2)
the interaction with a ISI-NET host (a host on a class B net), (3)
the implementation of the VRFY command, (4) the implementation of the
Postmaster mailbox, and (5) the treatment of a bad recipient name.
∂875 M. Padlipsky 82/83 Gateways, Architectures, and Heffalumps
This memo discusses Gateways and Protocol Translation.
∂874 M. Padlipsky 82/83 A Critique of X.25
This memo is a discussion of the CCITT X.25 protocol and its
attendant conceptual framework, the ISO Reference Model.
∂873 M. Padlipsky 82/83 The Illusion of Vendor Support
This memo argues that vendor supplied software for computer
networking based on the ISO Reference Model is not worth waiting for,
especially in light of the existing ARPA family of protocols.
∂872 M. Padlipsky 82/83 TCP-ON-A-LAN (Local Area Net)
This memo discusses the use of TCP on a local area network.
∂871 M. Padlipsky 82/83 A Perspective on the Arpanet Reference Model
This memo describes the development of the ARPA protocols, and
compares and contrasts the ARPA protocol reference model with the ISO
Reference Model.
∂870 Reynolds&Postel Oct 83 Assigned Numbers
This RFC documents the currently assigned values from several series of
numbers used in network protocol implementations. Obsoletes RFCs: 820, 790,
776, 770, 762, 758, 755, 750, 739, 604, 503, 433, 349
∂869 R. Hinden Dec 83 A Host Monitoring Protocol
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.
∂868 Postel&Harrenstein May 83 Time Protocol
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet that choose to provide this service are expected
to adopt and implement this standard. This specification obsoletes
IEN 142.
∂867 Postel May 83 Daytime Protocol
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet that choose to provide this service are expected
to adopt and implement this standard.
∂866 Postel May 83 Active Users Protocol
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet that choose to provide this service are expected
to adopt and implement this standard.
∂865 Postel May 83 Quote of the Day Protocol
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet that choose to provide this service are expected
to adopt and implement this standard.
∂864 Postel May 83 Character Generator Protocol
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet that choose to provide this service are expected
to adopt and implement this standard. This specification obsoletes
RFC 429.
∂863 Postel May 83 Discard Protocol
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet that choose to provide this service are expected
to adopt and implement this standard. This specification obsoletes
RFC 348.
∂862 Postel May 83 Echo Protocol
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet that choose to provide this service are expected
to adopt and implement this standard. This specification obsoletes
RFC 347.
∂861 Postel&Reynolds May 83 Telnet Extended Options List Option
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet are expected to adopt and implement this
standard. This specification obsoletes NIC 16239.
∂860 Postel&Reynolds May 83 Telnet Timing Mark Option
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet are expected to adopt and implement this
standard. This specification obsoletes NIC 16238.
∂859 Postel&Reynolds May 83 Telnet Status Option
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet are expected to adopt and implement this
standard. This specification obsoletes NIC 31154 = RFC 651.
∂858 Postel&Reynolds May 83 Telnet Supress Go Ahead Option
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet are expected to adopt and implement this
standard. This specification obsoletes NIC 15392.
∂857 Postel&Reynolds May 83 Telnet Echo Option
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet are expected to adopt and implement this
standard. This specification obsoletes NIC 15390.
∂856 Postel&Reynolds May 83 Telnet Binary Transmission Option
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet are expected to adopt and implement this
standard. This specification obsoletes NIC 15389.
∂855 Postel&Reynolds May 83 Telnet Option Specifications
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet are expected to adopt and implement this
standard. This specification obsoletes NIC 18640.
∂854 Postel&Reynolds May 83 Telnet Protocol Specification
This RFC specifies a standard for the ARPA Internet community. Hosts
in the ARPA Internet are expected to adopt and implement this
standard. This specification obsoletes NIC 18639.
∂853:851 [unknown]
∂850 M. Horton Jun 83 Standard for Interchange of USENET Messages
This RFC specifies the standard format for news articles in USENET.
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.
∂849 M. Crispin May 83 Suggestions for Improved Host Table Distribution
This memo make a few suggestions for different procedures for
distributing host table information. This memo is indended to
stimulate thought and discussion, it does not propose or establish
any standard.
∂848:842 [unknown]
∂841 NBS Jun 83 Specification for Message Format for
Computer Based Message Systems
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.
∂840:836 [unknown]
∂835 Smallberg Dec 82 Who Talks TCP?
The list of hosts was taken from the NIC hostname table of 2-Dec-82.
The tests were run on 28-Dec-82 from ~12:01 pm to ~8:10 pm PST. Dead,
refused, and unreachable hosts were retried 29-Dec-82 from ~8:00 am to
~7:40 pm PST.
∂834:832 [unknown]
∂832 Smallberg Dec 82 Who Talks TCP?
The list of hosts was taken from the NIC hostname table of 2-Dec-82.
The tests were run on 7-Dec-82 from ~12:01 am to ~2:15 am PST and from
~12:30 pm to ~7:00 pm PST. Dead, refused, and unreachable hosts were
retried 8-Dec-82 from ~3:15 pm to ~4:30 pm PST.
∂831 [unknown]
∂830 Su Aug 82 A Distributed System for Internet Name Service
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.
∂829 [unknown]
∂828 Owen Aug 82 Data Communications: IFIP's International
"Network" of Experts
[ 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. ]
A vital common thread which runs through virtually all current advances
in implementing and operating computer-based systems is that of data
communications. The interconnection of the various elements of
complete systems in new ways has become the driving force behind a
substantial research and development effort.
∂827 Rosen Oct 82 Exterior Gateway Protocol (EGP)
It 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.
∂826 [unknown]
∂825 Postel Nov 82 Request for Comments on Requests for Comments
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.
∂824 [unknown]
∂823 Hinden&Sheltzer Sep 82 DARPA Internet Gateway
This document explains the design of the Internet gateway used in the
Defense Advanced Research Project Agency (DARPA) Internet program. The
gateway design was originally documented in IEN-30, "Gateway Routing:
An Implementation Specification" [2], and was later updated in IEN-109,
"How to Build a Gateway" [3]. This document reflects changes made both
in the internet protocols and in the gateway design since these
documents were released. It supersedes both IEN-30 and IEN-109.
∂822 Crocker 13 Aug 82 Standard for ARPA Internet Text Messages
This standard specifies a syntax for text messages that are sent among
computer users, within the framework of "electronic mail". The
standard supersedes the one specified in ARPANET Request for Comments
#733, "Standard for the Format of ARPA Network Text Messages".
∂821 Postel Aug 82 Simple Mail Transfer Protocol
The objective of Simple Mail Transfer Protocol (SMTP) is to transfer
mail reliably and efficiently. This is the official Internet mail
transfer protocol.
∂820 Postel&Vernon Jan 83 Assigned Numbers
This Network Working Group Request for Comments documents the currently
assigned values from several series of numbers used in network protocol
implementations. This RFC will be updated periodically, and in any
case current information can be obtained from Jon Postel. The
assignment of numbers is also handled by Jon, subject to the agreement
between DARPA/IPTO and DDN/PMO about number allocation, documented in
Appendix A of this RFC. If you are developing a protocol or
application that will require the use of a link, socket, port,
protocol, or network number please contact Jon to receive a number
assignment.
∂819 Su/Postel Aug 82 The Domain Naming Convention for
Internet User Applications
For many years, the naming convention "<user>@<host>" has served the
ARPANET user community for its mail system, and the substring
"<host>" has been used for other applications such as file transfer
(FTP) and terminal access (Telnet). With the advent of network
interconnection, this naming convention needs to be generalized to
accommodate internetworking. A decision has recently been reached to
replace the simple name field, "<host>", by a composite name field,
"<domain>" [2]. This note is an attempt to clarify this generalized
naming convention, the Internet Naming Convention, and to explore the
implications of its adoption for Internet name service and user
applications.
∂818 Postel Nov 82 The Remote User Telnet Service
In the ARPANET Host-to-Host Network Control Protocol (NCP) and in the
Internet Transmission Control Protocol (TCP) well known sockets or
ports are used to identify services. The general notion is that there
are a few types of services that are distinct and useful enough to use
the NCP or TCP demultiplexing mechanism directly.
The most common of these is the Server Telnet which generally speaking
defines the network terminal access procedure for a system executive.
That is, making a connection to the server Telnet port actually puts
the caller in contact with the system executive, for example, the
TOPS20 EXEC or the Unix Shell.
On some small hosts there may be very limited functionality and no
executive. In such cases it may be useful to designate specific well
known ports for specific applications.
This memo specifies that the specific service of User Telnet may be
accessed (on hosts that choose to provide it) by opening a connection
to port 107 (153 octal). The Telnet Protocol is to be used on the
connection from the originating user to the server.
∂817:812 [unknown]
∂811 NIC 1 Mar 82 Hostnames Server
The NIC Internet Hostnames Server is an NCP/TCP-based host
information program and protocol running on the SRI-NIC
machine. It is one of a series of ARPANET/Internet name
services maintained by the Network Information Center (NIC) at
SRI International on behalf of the Defense Communications
Agency (DCA). 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. As currently implemented, the server
provides the information outlined in the DoD Internet Host
Table Specification (RFC 810).
∂810 NIC 1 Mar 82 DoD Internet Host Table Specification
The ARPANET Official Network Host Table, as outlined in RFC 608, no
longer suits the needs of the DoD community, nor does it follow a
format suitable for internetting. This paper 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 Host Table is utilized by the DoD Host Name Server maintained by
the ARPANET Network Information Center (NIC) on behalf of the Defense
Communications Agency (DCA) (RFC 811). It obsoletes the host table
described in RFC 608.
∂809:801 [unknown]
∂800 Postel 1983 Summary of RFCs 700:799
RFC Author Date Title (799:700)
--- ------ ---- -----
∂799 Mills Sep 81 Internet Name Domains
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.
∂798 Katz Sep 81 Decoding Facsimile Data From the
Rapicom 450
A description of the encoding/decoding procedure for Rapicom450
facsimile machine.
∂797 Katz Sep 81 Format for Bitmap Files
The description of a simple file format for bitmap data.
∂796 Postel Sep 81 Address Mappings
A description of the way the addresses of a few actual networks are
mapped into internet addresses.
∂795 Postel Sep 81 Service Mappings
A description of how the internet type of service is mapped into the
actual service parameters of a few particular networks, and vice
versa.
∂794 Cerf Sep 81 Pre-Emption
Discusses how pre-emption of TCP connection can be implemented.
Replaces IEN 125.
∂793 Postel Sep 81 Transmission Control Protocol
The specification of TCP. Replaces RFCs 761 and 675.
∂792 Postel Sep 81 Internet Control Message Protocol
The specification of ICMP. Replaces RFCs 777 and 760.
∂791 Postel Sep 81 Internet Protocol
The specification of IP. Replaces RFC 760.
∂790 Postel Sep 81 Assigned Numbers
An old version; see RFC 870.
∂789 Rosen Jul 81 Vulnerabilities of Network Control
Protocols: An Example
A description of an outage in ARPANET service and the process of
determining the cause; also, subtleties of designing network
protocols.
∂788 Postel Nov 81 Simple Mail Transfer Protocol
An old version; see RFC 821.
∂787 Chapin July 81 Connectionless Data Transmission
Survey/Tutorial
A discussion of datagram service. Intended for submission to
international standards bodies.
∂786 Sluizer July 81 Mail Transfer Protocol: ISI TOPS20
MTP-NIMAIL Interface
The description of the way mail is passed between the MTP and the
NIMAIL programs in ISI TOPS20. Outdated.
∂785 Sluizer July 81 Mail Transfer Protocol: ISI TOPS20
File Definitions
The description of the file format for passing mail to the MTP program
from user mail programs in ISI TOPS20. Outdated.
∂784 Sluizer July 81 Mail Transfer Protocol: ISI TOPS20
Implementation
The description of the program structure for the MTP implementation in
the ISI TOPS20. Outdated.
∂783 Sollins June 81 The TFTP Protocol Revision 2
The specification of TFTP. Replaces RFCs 768, 764 and IEN 133.
∂782 Nabielsky undated A Virtual Terminal Management Model
A description of the elements of a virtual terminal and the management
of communications between them.
∂781 Su May 81 A Specification of the Internet
Protocol IP Timestamp Option
The description of IP Timestamp option, now included in the IP
specification (RFC 791).
∂780 Sluizer May 81 Mail Transfer Protocol
An outdated Mail protocol; see RFC 821.
∂779 Killian Apr 81 TELNET SEND-LOCATION Option
Definition of this Telnet option.
∂778 Mills 18 Apr 81 DCNet Internet Clock Service
Specifies a format and procedure for the exchange of messages to
maintain synchronized clocks.
∂777 Postel Apr 81 Internet Control Message Protocol
An old version; see RFC 792.
∂776 Postel Jan 81 Assigned Numbers
An old version; see RFC 870.
∂775 Mankins Dec 80 Directory Oriented FTP Commands
The definition of additional FTP Commands related to directory
management.
∂774 Postel Oct 80 Internet Protocol Handbook Table of
Contents
An out-of-date table of contents for an Internet Protocol Handbook.
∂773 Cerf Oct 80 Comments on NCP/TCP Mail Service
Transition Strategy
A discussion of issues in the transition from NCP to TCP, particularly
as related to MAIL Service.
∂772 Sluizer Sep 80 Mail Transfer Protocol
An old version of a Mail Protocol; see RFC 821.
∂771 Cerf Sep 80 Mail Transition Plan
A plan for supporting mail service in the transition from NCP to TCP;
see also RFC 801.
∂770 Postel Sep 80 Assigned Numbers
An old version; see RFC 870.
∂769 Postel 26 Sep 80 Rapicom 450 Facsimile File Format
The definition of the exchange format of the encoded facsimile data of
the Rapicom 450; see also RFC 798.
∂768 Postel 28 Aug 80 User Datagram Protocol
The specification of the UDP.
∂767 Postel Aug 80 A Structured Format for Transmission
of Multi-Media Documents
The definition of the format for the document of a multimedia message.
∂766 Postel Jul 80 Internet Protocol Handbook
An out-of-date table of contents for the Internet Protocol Handbook.
∂765 Postel Jun 80 File Transfer Protocol
The specification of FTP.
∂764 Postel Jun 80 Telnet Protocol Specification
The specification of Telnet.
∂763 Abrams 7 May 80 Role Mailboxes
A call for mailboxes with role names, such as "Management".
∂762 Postel Jan 80 Assigned Numbers
An old version; see RFC 870.
∂761 Postel Jan 80 DOD Standard Transmission Protocol
An old version; see RFC 793.
∂760 Postel Jan 80 DOD Standard Internet Protocol
An old version; see RFC 791.
∂759 Postel Aug 80 Internet Message Protocol
The definition of the protocol and format for the exchange of
multimedia mail. Replaces RFC 753.
∂758 Postel Aug 79 Assigned Numbers
An old version; see RFC 870.
∂757 Deutsch 10 Sep 79 A Suggested Solution to the Naming,
Addressing, and Delivery Problem for
ARPANET Message Systems
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.
∂756 Pickens Jul 79 The NIC Name server--A Datagram-Based
Information Utility
Describes a Host Name to Address look up service.
∂755 Postel 3 May 79 Assigned Numbers
An old version; see RFC 870.
∂754 Postel 6 Apr 79 Out-of-Net Host Addresses for Mail
A discussion of options for addressing computer mail beyond the
ARPANET.
∂753 Postel Mar 79 Internet Message Protocol
An old version; see RFC 759.
∂752 Crispin 3 Jan 79 A Universal Host Table
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.
∂751 Lebling 10 Dec 78 Survey of FTP Mail and MLFL
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.
∂750 Postel 26 Sep 78 Assigned Numbers
An old version; see RFC 870.
∂749 Greenberg 18 Sep 78 Telnet SUPDUP-OUTPUT Option
Updates RFC 736; see also RFCs734, 746 and 747.
∂748 Crispin 1 Apr 78 TELNET RANDOMLY-LOSE Option
Defines this Telnet option (note the date of this memo).
∂747 Crispin 21 Mar 78 Recent Extensions to the SUPDUP
Protocol
An update to the SUPDUP protocol (RFC 734); see also RFCs 749, 746 and
736.
∂746 Stallman 17 Mar 78 The SUPDUP Graphics Extension
An extension of SUPDUP for Graphics; see also RFCs 734, 736, 747 and
749.
∂745 Beeler 30 Mar 78 JANUS Interface Specifications
The specification of a symmetrical 1822 style interface.
∂744 Sattley 8 Jan 78 MARS - A Message Archiving and
Retrieval Service
The description of a database service for computer mail messages,
which operates via computer mail.
∂743 Harrenstien 30 Dec 77 FTP extension: XRSQ/XRCP
An extension to FTP mail to allow more efficient transmission of
computer mail. Now incorporated into SMTP; see RFC788.
∂742 Harrenstien 30 Dec 77 NAME/FINGER Protocol
Defines the Name or Finger Protocol which allows one to get "who is
on" or "where is user x" information from another host.
∂741 Cohen 22 Nov 77 Specifications for the Network Voice
Protocol NVP
Defines the protocol used in the ARPANET packet speech experiments.
∂740 Braden 22 Nov 77 NETRJS Protocol
Defines the protocol used for Remote Job Entry on the UCLA CCN IBM
system; replaces RFCs 599 and 189.
∂739 Postel 11 Nov 77 Assigned Numbers
An old version; see RFC 870.
∂738 Harrenstien 31 Oct 77 Time Server
Defines the Time Server Protocol; see IEN 142 for the TCP and VDP
versions.
∂737 Harrenstien 31 Oct 77 FTP Extension: XSEN
An extenion to the Mail procedures. This function is incorporated in
the SMTP; see also RFC 821.
∂736 Crispin 31 Oct 77 TELNET SUPDUP Option
Defines the procedure for negotiating to use the SUPDUP, protocol as a
TELNET option; see also RFCs 734, 746, 747 and 749.
∂735 Crocker 3 Nov 77 Revised TELNET Byte Macro Option
Obsoletes 40306
Defines a Telnet option for assigning codes to stand for strings in
Telnet connections. Replaces RFC 729.
∂734 Crispin 7 Oct 77 SUPDUP Protocol
Description of a terminal control protocol used at STANFORD and MIT;
see also RFCs 736, 746-749.
∂733 Crocker 21 Nov 77 Standard for the Format of ARPA Network
Text Messages
Specification of the format for the headers of computer mail. An old
version; see RFC 822.
∂732 Day 12 Sep 77 TELNET Data Entry Terminal Option
The specification of a Telnet Option for the control of a data entry
display terminal. Replaces RFC 731.
∂731 Day 27 Jun 77 TELNET Data Entry Terminal Option
An old version; see RFC 732.
∂730 Postel 20 May 77 Extensible Field Addresing
Discusses some ideas on addressing that come up in the context of
changing from 8-bit to 24-bit network addresses.
∂729 Crocker 13 May 77 TELNET Byte Macro Option
An old version; see RFC 735.
∂728 Day 27 Apr 77 A Minor Pitfall in the Telnet Protocol
Warns of the possibility of an unexpected occurence in Telnet
resulting from the interaction between option subnegotiations and the
telnet SYNCH operation.
∂727 Crispin 27 Apr 77 TELNET Logout Option
Defines a telnet option for causing a logout.
∂726 Postel 8 Mar 77 Remote Controlled Transmission and
Echoing Telnet Option
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.
∂725 Day 1 Mar 77 An RJE Protocol for a Resource Sharing
Network
Describes a possible Remote Job Entry protocol.
∂724 Crocker 12 May 77 Proposed Official Standard for the
Format of ARPA Network Messages
An old version; see RFC 822.
∂723 [??? Omitted from summary?]
∂722 Haverty 16 Sep 76 Thoughts on Interactions in Distributed
Services
A discussion on the design of interactive distributed services and the
kinds of primitive operations that are needed.
∂721 Garlick 1 Sep 76 Out of Band Control Signals in a Host
to Host Protocol
A discussion of the control signals in transport protocols (e.g.,
NCP's Interrupt or TCP's Urgent).
∂720 Crocker 5 Aug 76 Address Specification Syntax for
Network Mail
A discussion of computer mail addresses, with comments on real names
vs. mailboxes, and mailing lists; see also RFC 819.
∂719 Postel 22 Jul 76 Discussion on RCTE
A short discussion of RCTE implementation issues; see also RFCs 726
and 718.
∂718 Postel 30 Jun 76 Comments on RCTE from the TENEX
Implementation Experience
A short note on the Tenex implementation of RCTE; see also RFCs 726
and 719.
∂717 Postel 1 Jul 76 Assigned Network Numbers
An old version; see RFC 870.
∂716 Levin 24 May 76 Interim Revision to Appendix F of BBN
1822
A short note updating the specification of the very Distant Host 1822
interface.
∂715 [??? Omitted from summary?]
∂714 McKenzie 21 Apr 76 A Host/Host Protocol for an
ARPANET-type Network
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.
∂713 Haverty 6 Apr 76 MSDTP -- Message Services Data
Transmission Protocol
The specification of a set of Data Primitives for building interactive
services.
∂712 Donnelley 5 Feb 76 A Distributed Capability Computing
System DCCS
A description of a Distributed Capability based computing system.
∂711 [??? Omitted from summary?]
∂710 [??? Omitted from summary?]
∂709 [??? Omitted from summary?]
∂708 White 5 Jan 76 Elements of a Distributed Programming
System
A description of a Distributed programming system; see also RFC 707.
∂707 White 23 Dec 75 A High-Level Framework for
Network-Based Resource Sharing
A description of a programming environment for network-based programs;
see also RFC 708.
∂706 Postel 8 Nov 75 On the Junk Mail Problem
A short note pointing out that the ARPANET maybe subject to a "denial
of service" attack by a misbehaving host.
∂705 Bryan 5 Nov 75 Front-End Protocol
Describes a protocol used between a PDP-11 (the ARPANET front end) and
a B6700 to support network communication.
∂704 Santos 15 Sep 75 IMP/Host and Host/IMP Protocol Change
Describes the changes to the 1822 interface to eliminate the
restriction of 63 IMPs.
∂703 Dodds 11 Jul 75 Survey of New-Protocol Telnet Servers
A poll of Telnet servers to check implementation status and Telnet
options. Updates RFCs 702, 701, 679 and 669.
∂702 Dodds 25 Sep 74 Survey of New-Protocol Telnet Servers
An earlier poll of Telnet server implementation status; see also
RFC's703, 701, 679, and 669.
∂701 Dodds Aug 74 Survey of New-Protocol Telnet Servers
An earlier poll of Telnet server implementation status; see also RFCs
703, 702, 679 and 669.
∂700 Mader Aug 74 A Protocol Experiment
Describes a protocol based loosely on a very early version of TCP,
used to send data to a printer server.
RFC Author Date Title (699:600)
--- ------ --------- -----
∂699 Postel 10 Nov 82 Requests for Comments Summary
Notes: 600-699
This summary.
∂698 Tovar 23 Jul 75 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.
∂697 Lieb 14 Jul 75 CWD Command of FTP
Discusses FTP login access to "files only" directories.
∂696 Cerf 17 Jul 75 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.
∂695 Krilanovich 5 Jul 75 Official Change in Host-Host Protocol
Corrects ambiguity concerning the ERR command; changes NIC 8246 and
NIC 7104.
∂694 Postel 18 Jun 75 Protocol Information
References to documents and contacts concerning the various protocols
used in the ARPANET, as well as recent developments; updates RFC 661.
∂693 Not Issued
∂692 Wolfe 20 Jun 75 Comments on IMP/Host Protocol Changes
A proposed solution to the problem of combined length of IMP and Host
leaders; see also RFCs 696, 690 and 687.
∂691 Harvey 28 May 75 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.
∂690 Postel 6 Jun 75 Comments on the proposed Host/IMP
Protocol Changes
Comments on suggestions in RFC 687; see also RFCs 692 and 696.
∂689 Clements 23 May 75 TENEX NCP Finite State Machine for
Connections
Describes the internal states of an NCP connection in the TENEX
implementation.
∂688 Walden 4 Jun 75 Tentative Schedule for the New TELNET
Implementation for the TIP
∂687 Walden 2 Jun 75 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.
∂686 Harvey 10 May 75 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.
∂685 Beeler 16 Apr 75 Response Time in Cross-network
Debugging
The contribution of ARPANET communication to response time.
∂684 Schantz 15 Apr 75 A Commentary on Procedure Calling as a
Network Protocol
Issues in designing distributed computing systems. Shortcomings of
RFC 674; see also RFCs 542 and 354.
∂683 Clements 3 Apr 75 FTPSRV -- TENEX Extension for Paged
Files
Defines an extension to FTP for page-mode transfers between TENEX
systems; also discusses file transfer reliability.
∂682 Not Issued
∂681 Holmgren 14 May 75 Network Unix
Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP,
Hardware/Software requirements, reliability, availability.
∂680 Myer 30 Apr 75 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.
∂679 Dodds 21 Feb 75 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.
∂678 Postel 18 Dec 74 Standard File Formats
For transmission of documents across different environments.
∂677 Johnson 27 Jan 75 The Maintenance of Duplicate Databases
∂676 Not Issued
∂675 Cerf 16 Dec 74 Specification of Internet Transmission
Control Program
The first detailed specification of TCP; see RFC 793.
∂674 Postel 12 DEC 74 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.
∂673 Not Issued
∂672 Schantz 6 Dec 74 A Multi-Site Data Collection Facility
Applicability of TIP/TENEX protocols beyond TIP accounting.
∂671 Schantz 6 Dec 74 A Note on Reconnection Protocol
Experience with implementation in RSEXEC context.
∂670 Not Issued
∂669 Dodds 4 Dec 74 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.
∂668 Not Issued
∂667 Chipman Dec 74 BBN Host Ports
Approved scheme to connect host ports to the network.
∂666 Padlipsky 26 Nov 74 Specification of the Unified User-Level
Protocol
Discusses and proposes a common command language.
∂665 Not Issued
∂664 Not Issued
∂663 Kanodia 29 Nov 74 A Lost Message Detection and Recovery
Protocol
Proposed extension of host-host protocol; see also RFCs 534, 516, 512,
492 and 467.
∂662 Kanodia 26 Nov 74 Performance Improvement in ARPANET File
Transfers from Multics
Experimenting with host output buffers to improve throughput.
∂661 Postel 23 Nov 74 Protocol Information
An old version; see RFC 694.
∂660 Walden 23 Oct 74 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.
∂659 Postel 18 Oct 74 Announcing Additional Telnet Options
Options defined in RFCs 651-658.
∂658 Crocker 25 Oct 74 Telnet Output Line Feed Disposition
∂657 Crocker 25 Oct 74 Telnet Output Vertical Tab Disposition
Option
∂656 Crocker 25 Oct 74 Telnet Output Vertical Tab Stops Option
∂655 Crocker 25 Oct 74 Telnet Output Form Feed Disposition
Option
∂654 Crocker 25 Oct 74 Telnet Output Horizontal Tab
Disposition Option
∂653 Crocker 25 Oct 74 Telnet Output Horizontal Tab Stops
Option
∂652 Crocker 25 Oct 74 Telnet Output Carriage Return
Disposition Option
∂651 Crocker 25 Oct 74 Revised Telnet Status Option
∂650 Not Issued
∂649 Not Issued
∂648 Not Issued
∂647 Padlipsky 12 Nov 74 A 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.
∂646 Not Issued
∂645 Crocker 26 Jun 74 Network Standard Data Specification
Syntax
Providing a mechanism for specifying all attributes of a collection of
bits; see also RFC 615.
∂644 Thomas 22 Jul 74 On The Problem of Signature
Authentication for Network Mail
∂643 Mader 5 Jul 74 Network Debugging Protocol
To be used in an implementation of a PDP-11 network bootstrap device
and a cross-network debugger.
∂642 Burchfiel 5 Jul 74 Ready Line Philosophy and
Implementation
∂641 Not Issued
∂640 Postel 5 Jun 74 Revised FTP Reply Codes
Updates RFC 542.
∂639 Not Issued
∂638 McKenzie 25 Apr 74 IMP/TIP Preventive Maintenance Schedule
Corrects RFC 633.
∂637 McKenzie 23 Apr 74 Change of Network Address for SU-DSL
∂636 Burchfiel 10 Jun 74 TIP/TENEX Reliability Improvements
Obtaining/maintaining connections; recovery from lost connections;
connection-state changes.
∂635 Cerf 22 Apr 74 An Assessment of ARPANET Protocols
Theoretical and practical motivation for redesign. Multipacket
messages; host retransmission; duplicate detection; sequencing;
acknowledgement.
∂634 McKenzie 10 Apr 74 Change in Network Address for Haskins
Lab.
∂633 McKenzie 18 Mar 74 IMP/TIP Preventive Maintenance Schedule
An old version; see RFC 638.
∂632 Opderbeck 20 May 74 Throughput Degradations for Single
Packet Messages
∂631 Danthine 17 Apr 74 Call for Papers: International Meeting
on Minicomputers and Data Communication
∂630 Sussman 10 Apr 74 FTP Error Code Usage for More Reliable
Mail Service
Describes FTP reply-code usage in TENEX mail processing.
∂629 North 27 Mar 74 Scenario for Using the Network Journal
∂628 Keeney 27 Mar 74 Status of RFC Numbers and a Note on
Pre-assigned Journal Numbers
∂627 Feinler 25 Mar 74 ASCII Text File of Hostnames
See also RFCs 606, 608, 623 and 625.
∂626 Kleinrock 14 Mar 74 On a possible Lockup Condition in Imp
Subnet due to Message Sequencing
∂625 Feinler 7 Mar 74 On Line Hostnames Service
See also RFCs 606, 608, 623 and 627.
∂624 Krilanovich 28 Feb 74 Comments on the File Transfer Protocol
Design changes and slight modifications. Replaces RFC 607; see also
RFCs 614, 542 and 640.
∂623 Krilanovich 22 Feb 74 Comments on On-Line Host Name Service
See also RFCs 627, 625, 608 and 606.
∂622 McKenzie 13 Mar 74 Scheduling IMP/TIP Down Time
Modification of previous policy.
∂621 Kudlick 6 Mar 74 NIC User Directories at SRI-ARC
See also RFCs 620 and 609.
∂620 Ferguson 1 Mar 74 Request for Monitor Host Table Updates
In conjunction with moving NIC users to OFFICE-1; see also RFCs 621
and 609.
∂619 Naylor 7 Mar 74 Mean Round-Trip Times in the ARPANET
Actual measurements of round-trip times.
∂618 Taft 19 Feb 74 A Few Observations on NCP Statistics
Distribution of NCP and IMP message types by actual measurement.
∂617 Taft 19 Feb 74 A Note on Socket Number Assignment
Danger of imposing more fixed socket number requirements; see also
RFCs 542, 503 and 451.
∂616 Walden 11 Feb 74 Latest Network Maps
∂615 Crocker 1 Mar 74 Proposed Network Standard Data Pathname
Syntax
∂614 Pogran 28 Jan 74 Response to RFC 607 (NIC-21255),
"Comments on the FTP"
See also RFCs 624, 542 and 640.
∂613 McKenzie 21 Jan 74 Network Connectivity: A Response to RFC603
∂612 McKenzie 16 Jan 74 Traffic Statistics Dec. 1973
∂611 Walden 14 Feb 74 Two Changes to the IMP/Host Protocol
Expansion of Host-Going-Down and addition of Dead-Host-Status Message.
∂610 Winter 15 Dec 73 Further Datalanguage Design Concepts
Preliminary results of the language design; a model for data languagea
semantics; future considerations.
∂609 Ferguson 10 Jan 74 Statement of Upcoming Move of NIC/NLS
Service
See also RFCs 621 and 620.
∂608 Feinler 10 Jan 73 Host Names On-Line
Response to RFC 606; see also RFCs 627, 625 and 623.
∂607 Krilanovich 7 Jan 73 NIC-21255 Comments on the File
Transfer Protocol
An old version; see RFC 624; see also RFCs 614, 542 and 640.
∂606 Deutsch 29 Dec 73 Host Names On-Line
Resolving differences in hostname-address mappings; see also RFCs 627,
625, 623 and 608.
∂605 Not Issued
∂604 Postel 26 Dec 73 Assigned Link Numbers
Modifies official host-host protocol. Replaces RFC 377.
∂603 Burchfiel 31 Dec 73 Response to RFC 597: Host Status
Questions about the ARPANET topology described in RFC 597.
∂602 Metcalfe 27 Dec 73 "The Stockings Were Hung by the Chimney
With Care"
Susceptibility of ARPANET to security violations.
∂601 McKenzie 14 Dec 73 Traffic Statistics November 1973
∂600 Berggreen 26 Nov 73 Interfacing an Illinois Plasma Terminal
to the ARPANET
Discusses some unusual interface issues for the Plato terminal.