perm filename INDEX[RFC,NET]66 blob
sn#861140 filedate 1988-09-14 generic text, type C, neo UTF8
COMMENT ⊗ VALID 00012 PAGES
C REC PAGE DESCRIPTION
C00001 00001
C00003 00002 ∂RFC Date Author Title (1099:1000)
C00058 00003 ∂RFC Date Author Title (999:900)
C00153 00004 RFC Author Date Title (899:800)
C00212 00005 RFC Author Date Title (799:700)
C00241 00006 RFC Author Date Title (699:600)
C00262 00007 RFC NIC number Date Author Title (599:500)
C00275 00008 RFC NIC number Date Author Title (499:400)
C00288 00009 RFC NIC number Date Author Title (399:300)
C00302 00010 RFC NIC number Date Author Title (299:200)
C00315 00011 RFC NIC number Date Author Title (199:100)
C00331 00012 RFC NIC number Date Author Title (099:000)
C00360 ENDMK
C⊗;
∂RFC Date Author Title (1099:1000)
---- ---- ------ -----
∂1071 Sep 88 Braden/Borman/Partridge Computing the Internet Checksum
This RFC summarizes techniques and algorithms for efficiently computing
the Internet checksum. It is not a standard, but a set of useful
implementation techniques. Distribution of this memo is unlimited.
∂1068 Aug 88 DeSchon/Braden Background File Transfer Program (BFTP)
This RFC describes an Internet background file transfer service that
is built upon the third-party transfer model of FTP. No new protocols
are involved. The purpose of this memo is to stimulate discussion on
new Internet service modes. Distribution of this memo is unlimited.
∂1067 Aug 88 Case/Fedor/Schoffstall A Simple Network Management Protocol
This RFC defines a simple protocol by which management information for
a network element may be inspected or altered by logically remote
users. In particular, together with its companion memos which
describe the structure of management information along with the
initial management information base, these documents provide a simple,
workable architecture and system for managing TCP/IP-based internets
and in particular, the Internet.
∂1066 Aug 88 McCloghrie/Rose Management Information Base for Network
Management of TCP/IP-based internets
This RFC provides the initial version of the Management Information
Base (MIB) for use with network management protocols in TCP/IP-based
internets in the short-term. In particular, together with its
companion memos which describe the structure of management information
along with the initial network management protocol, these documents
provide a simple, workable architecture and system for managing
TCP/IP-based internets, and in particular, the Internet.
∂1065 Aug 88 Rose/McCloghrie Structure and Identification of Management
Information for TCP/IP-based internets
This RFC provides the common definitions for the structure and
identification of management information for TCP/IP-based internets.
In particular, together with its companion memos, which describe the
initial management information base along with the initial network
management protocol, these documents provide a simple, working
architecture and system for managing TCP/IP-based internets and in
particular, the Internet.
∂1064 Jul 88 M. Crispin Interactive Mail Access Protocol - Version 2
This memo suggests a method for workstations to dynamically access mail
from a mailbox server ("repository"). This RFC specifies a standard for
the SUMEX-AIM community and a proposed experimental protocol for the
Internet community. Discussion and suggestions for improvement are
requested. Distribution of this memo is unlimited.
∂1063 Jul 88 J. Mogul IP MTU Discovery Options
A pair of IP options that can be used to learn the minimum MTU of a path
through an internet is described, along with its possible uses. This is
a proposal for an Experimental protocol. Distribution of this memo is
unlimited.
∂1062 Aug 88 Romano,Stahl,Recker Internet Numbers
This memo is an official status report on the network numbers and
gateway autonomous system numbers used in the Internet community.
Distribution of this memo is unlimited.
∂1059 Jul 88 D. Mills Network Time Protocol (Version 1)
Specification and Implementation
This memo describes the Network Time Protocol (NTP), specifies its
formal structure and summarizes information useful for its
implementation. NTP provides the mechanisms to synchronize time and
coordinate time distribution in a large, diverse internet operating at
rates from mundane to lightwave. It uses a returnable-time design in
which a distributed subnet of time servers operating in a
selforganizing, hierarchical master-slave configuration synchronizes
logical clocks within the subnet and to national time standards via
wire or radio. The servers can also redistribute reference time via
local routing algorithms and time daemons.
The NTP architectures, algorithms and protocols which have evolved
over several years of implementation and refinement are described in
this document. The prototype system, which has been in regular
operation in the Internet for the last two years, is described in an
Appendix along with performance data which shows that timekeeping
accuracy throughout most portions of the Internet can be ordinarily
maintained to within a few tens of milliseconds, even in cases of
failure or disruption of clocks, time servers or nets. This is a
Draft Standard for an Elective protocol. Distribution of this memo is
unlimited.
∂1058 Jun 88 C. Hedrick Routing Information Protocol
This RFC describes an existing protocol for exchanging routing
information among gateways and other hosts. It is intended to be used
as a basis for developing gateway software for use in the Internet
community. Distribution of this memo is unlimited.
∂1057 Jun 88 Sun Microsystems RPC: Remote Procedure Call
Protocol Specification Version 2
This memo specifies version two of the message protocol used in Sun's
Remote Procedure Call (RPC). This RFC describes a standard that Sun
Microsystems and others are using and is one they wish to propose for the
Internet's consideration. It is not an Internet standard at this time.
Distribution of this memo is unlimted.
∂1056 Jun 88 M. Lambert PCMAIL: A Distributed Mail System
for Personal Computers
This RFC is a discussion of the Pcmail workstation based distributed
mail system. It is identical to the discussion in RFC-993, save that a
new, much simpler mail transport protocol is described. The new
transport protocol is the result of continued research into ease of
protocol implementation and use issues. Distribution of this memo is
unlimited.
∂1055 Jun 88 J. Romkey A Nonstandard for Transmission of IP
Datagrams Over Serial Lines: SLIP
The TCP/IP protocol family runs over a variety of network media: IEEE
802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellite links,
and serial lines. There are standard encapsulations for IP packets defined
for many of these networks, but there is no standard for serial lines.
SLIP, Serial Line IP, is a currently a de facto standard, commonly used for
point-to-point serial connections running TCP/IP. It is not an Internet
standard. Distribution of this memo is unlimited.
∂1054 May 88 S. Deering Host Extensions for IP Multicasting
This memo specifies the extensions required of a host implementation
of the Internet Protocol (IP) to support multicasting. IP
multicasting is the transmission of an IP datagram to a "host group",
a set hosts identified by a single IP destination address. A
multicast datagram is delivered to all members of its destination host
group with the same "best-efforts" reliability as regular unicast IP
datagrams. It is proposed as a standard for IP multicasting in the
Internet. This specification is a major revision of RFC-988.
Distribution of this memo is unlimited.
∂1053 Apr 88 Levy & Jacobson Telnet X.3 PAD Option
This RFC proposes a new option to Telnet for the Internet community, and
requests discussion and suggestions for improvements. Distribution of
this memo is unlimited.
∂1052 Apr 88 V. Cerf IAB Recommendations for the Development of
Internet Network Management Standards
This RFC is intended to convey to the Internet community and other
interested parties the recommendations of the Internet Activities Board
(IAB) for the development of network management protocols for use in the
TCP/IP environment. This memo does NOT, in and of itself, define or
propose an Official Internet Protocol. It does reflect, however, the
policy of the IAB with respect to further network management development
in the short and long term. Distribution of this memo is unlimited.
∂1051 Mar 88 P. Prindeville A Standard for the Transmission of IP Datagrams
and ARP Packets over ARCNET Networks
This memo specifies a standard method of encapsulating Internet Protocol
(IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET. This
RFC is a standard protocol for the Internet community. Distribution of
this memo is unlimited.
∂1050 Apr 88 Sun Microsystems RPC: Remote Procedure Call Protocol Specification
This memo specifies a message protocol used in implementing Sun's Remote
Procedure Call (RPC) package. This RFC describes a standard that Sun
Microsystems and others are using and is one they wish to propose for
the Internet's consideration. It is not an Internet standard at this
time. Distribution of this memo is unlimited.
∂1049 Mar 88 M. Sirbu A Content-Type Header Field for Internet Messages
This memo suggests proposed additions to the Internet Mail Protocol,
RFC-822, for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.
∂1048 Feb 88 P. Prindeville BOOTP Vendor Information Extensions
This memo proposes an addition to the Bootstrap Protocol (BOOTP).
Comments and suggestions for improvements are sought. Distribution of
this memo is unlimited.
∂1047 Feb 88 C. Partridge Duplicate Messages and SMTP
An examination of a synchronization problem in the Simple Mail Transfer
Protocol (SMTP) is presented in this memo. This synchronization problem
can cause a message to be delivered multiple times. A method for
avoiding this problem is suggested. Nodding familiarity with the SMTP
specification (RFC-821) is required. Distribution of this memo is
unlimited.
∂1046 Feb 88 Prue and Postel A Queuing Algorithm to Provide Type-of-Service
for IP Links
This memo is intended to explore how Type-of-Service might be
implemented in the Internet. The proposal describes a method of queuing
which can provide the different classes of service. The technique also
prohibits one class of service from consuming excessive resources or
excluding other classes of service. This is an "idea paper" and
discussion is strongly encouraged. Distribution of this memo is
unlimited.
∂1045 Feb 88 David Cheriton VMTP: Versatile Message Transaction Protocol
Protocol Specification
This memo specifies the Versatile Message Transaction Protocol (VMTP)
[Version 0.7 of 19-Feb-88], a transport protocol specifically designed
to support the transaction model of communication, as exemplified by
remote procedure call (RPC). The full function of VMTP, including
support for security, real-time, asynchronous message exchanges,
streaming, multicast and idempotency, provides a rich selection to the
VMTP user level. Subsettability allows the VMTP module for particular
clients and servers to be specialized and simplified to the services
actually required. Examples of such simple clients and servers include
PROM network bootload programs, network boot servers, data sensors and
simple controllers, to mention but a few examples. This RFC describes a
protocol proposed as a standard for the Internet community. Comments
are encouraged. Distribution of this document is unlimited.
∂1044 Feb 88 Hardwick/Lekashman Internet Protocol on Network Systems
HYPERchannel Protocol Specification
This memo intends to provide a complete discussion of the protocols
and techniques used to embed DoD standard Internet Protocol datagrams
(and its associated higher level protocols) on Network Systems
Corporation's HYPERchannel equipment. This document is directed
toward network planners and implementors who are already familiar with
the TCP/IP protocol suite and the techniques used to carry TCP/IP
traffic on common networks such as the DDN or the Ethernet. No great
familiarity with NSC products is assumed; an appendix is devoted to a
review of NSC technologies and protocols. Distribution of this memo
is umlimited.
∂1043 Feb 88 Yasuda, Thompson TELNET Data Entry Terminal Option
DODIIS Implementation
This RFC suggests a proposed protocol on the TELNET Data Entry Terminal (DET)
Option - DODIIS Implementation for the Internet community. It is intended
that this specification be compatible with the specification of DET Option in
RFC-732. Discussion and suggestions for improvements are encouraged.
Distribution of this memo is unlimited.
∂1042 Feb 88 J. Postel A Standard for the Transmission of IP Datagrams
over IEEE 802 Networks
This RFC specifies a standard method of encapsulating the Internet
Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests
and replies on IEEE 802 Networks to allow compatible and interoperable
implementations. This RFC specifies a protocol standard for the
Internet community. Distribution of this memo is unlimited.
∂1041 Jan 88 J. Rekhter Telnet 3270 Regime Option
This RFC specifies a proposed standard for the Internet community.
Hosts on the Internet, that want to support 3270 data stream within
the Telnet protocol, are expected to adopt and implement this
standard. Distribution of this memo is unlimited.
∂1040 Jan 88 J. Linn Privacy Enhancement for Internet Electronic Mail:
Part I: Message Encipherment and Authentication
Procedures
This RFC is the outgrowth of a series of IAB Privacy Task Force
meetings and of internal working papers distributed for those
meetings. This memo defines message encipherment and authentication
procedures, as the initial phase of an effort to provide privacy
enhancement services for electronic mail transfer in the Internet.
Detailed key management mechanisms to support these procedures will be
defined in a subsequent RFC. As a goal of this initial phase, it is
intended that the procedures defined here be compatible with a wide
range of key management approaches, including both conventional
(symmetric) and public-key (asymmetric) approaches for encryption of
data encrypting keys. Use of conventional cryptography for message
text encryption and/or integrity check computation is anticipated.
∂1039 Jan 88 D. Latham A DoD Statement on Open Systems Interconection Protocols
This RFC reproduces a memorandum issued on 2-JUL-87 from the
Assistant Secretary of Defense for Command, Control, Communications,
and Intelligence (ASDC31) to the Director of the Defense
Communications Agency (DCA). This memo is distributed for
information only. Distribution of this memo is unlimited.
∂1038 Jan 88 M. St. Johns Draft Revised IP Security Option
This memo is a pre-publication draft of the revised Internet Protocol
Security Option. This RFC reflects the version as approved by the
Protocol Standards Steering group, and is provided for informational
purposes only. The final version of this document will be available
from Navy publications and should not differ from this document in any
major fashion. This document will be published as a change to the
MIL-STD 1777, "Internet Protocol". Distribution of this memo is
unlimited.
∂1037 Dec 87 Greenberg, Keene NFILE - A File Access Protocol
This document includes a specification of the NFILE file access protocol
and its underlying levels of protocol, the Token List Transport Layer
and Byte Stream with Mark. The goal of this specification is to promote
discussion of the ideas described here, and to encourage designers of
future file protocols to take advantage of these ideas. A secondary
goal is to make the specification available to sites that might benefit
from implementing NFILE. Distribution of this memo is unlimited.
∂1036 Dec 87 Horton, Adams Standard for Interchange of USENET Messages
This memo defines the standard format for the interchange of network
News messages among USENET hosts. It updates and replaces RFC-850,
reflecting version B2.11 of the News program. This document is
distributed as an RFC to make this information easily accessible to the
Internet community. It does not specify an Internet standard.
Distribution of this memo is unlimited.
∂1035 Nov 87 P. Mockapetris Domain Names - Implementation and Specification
This RFC is the revised specification of the protocol and
formats used in the implementation of the Domain Name System.
It obsoletes RFC-883. This memo documents the details of
the domain name client - server communication. Distribution
of this memo is unlimited.
∂1034 Nov 87 P. Mockapetris Domain Names - Concepts and Facilities
This RFC is the revised basic definition of The Domain Name
System. It obsoletes RFC-882. This memo describes the domain
style names and their use for host address look up and
electronic mail forwarding. It discusses the clients and
servers in the domain name system and the protocol used
between them. Distribution of this memo is unlimited.
∂1033 Nov 87 Mark Lottor Domain Administrators Operations Guide
This RFC provides guidelines for domain administrators in operating a
domain server and maintaining their portion of the hierarchical
database. Familiarity with the domain system is assumed (see RFCs
1031, 1032, 1034, and 1035). Distribution of this memo is unlimited.
∂1032 Nov 87 Mary Stahl Domain Adminstrators Guide
Domains are adminstrative entities that proved decentralized management
of host naming and addressing. The domain-naming system is distributed
and hierarchical. This memo describes procedures for registering a
domain with the Network Information Center and offers guidelines to
domain admistrators on the establishment and administration of a domain.
These guidelines should also be used by domain administrators in the
establishment and control of second-level domains. This role of the
domain adminstrator is that of coordinator, manager, and technician.
If his domain is established at the second level or lower in the tree,
the domain administrator must register by interacgin with the management
of the domain directly above his. Distitution of this memo is
unlimited.
∂1031 Nov 87 W. Lazear Milnet Name Domain Transition
This RFC consolidates information necessary for the implementation of
domain style names throughout the DDN/MILNET Internet community. The
introduction of domain style names will impact all hosts in the
DDN/MILNET Internet. This RFC is designed as an aid to implementors
and administrators by providing 1) an overview of the transition
process from host tables to domains, 2) a timetable for the
transition, and 3) references to documentation and software relating
to the domain system. Distribution of the RFC is unlimited.
∂1030 Nov 87 M. Lambert On Testing the NETBLT Protocol over Divers Networks
This memo describes the results gathered from testing NETBLT over
three networks of differing bandwidths and round-trip delays. The
results are not complete, but the information gathered so far has been
promising. The NETBLT protocol is specified in RFC-998; this document
assumes an understanding of the specification as described in RFC-998.
Distribution of this memo is unlimited.
∂1029 May 88 G. Parr A More Fault Tolerant Approach to Address
Resolution for A Multi-Lan System of Ethernets
This memo discusses an extension to a Bridge Protocol to detect and disclose
changes in neighbouring host address parameters in a Multi-LAN system of
ethernets. The problem is one which is appearing more and more regularly as
the interconnected systems grow larger on Campuses and in Commercial
Institutions. This RFC suggests a protocol enhancement for the Internet
community, and requests discussion and suggestions for improvements.
Distribution of this memo is unlimited.
∂1027 Oct 87 Carl-Mitchell(etc) Using ARP to Implement Transparent Subnet Gateways
This RFC describes the use of the Address Resolution Protocol (ARP) by
subnet gateways to permit hosts on the connected subnets to communicate
without being aware of the existence of subnets, using the technique of
"Proxy ARP". Distribution of this memo is unlimited.
∂1026 Oct 87 S.E. Kille Addendum to RFC 987
This memo augments the proposed protocol for mapping between RFC-882
mail and X.400 mail. The additional information is primarily about
the mapping between RFC-882 mailboxes and X.400 O/R names especially
regarding componet ordering. Distribution of this memo is
unlimited.
∂1025 Oct 87 Jon Postel TCP AND IP BAKE OFF
This memo puts a bit history of the early work on IP and TCP into
the RFC record. The Bake Offs were testing sessions for the early
implementations, and this memo lists the test suggested for those
sessions. Some of these test may be of interest for new
implementations. Distribution of this memo is unlimited.
∂1024 Oct 87 Partridge, Trewitt HEMS VARIABLE DEFINITIONS
This memo assigns instruction codes, defines object formats and
object semantics for use with the High-Level Monitoring and
Control Language, defined in RFC-1023. A general system has
been described in previous memos (RFC-1021, RFC-1022). This
system is called the High-Level Entity Management System (HEMS).
This memo is provisional and the definitions are subject to
change. Readers should confirm with the authors that they have
the most recent version.
This RFC assumes a working knowledge of the ISO data encoding
standard, ASN.1, and a general understanding of the IP protocol
suite. Distribution of this memo is unlimited.
∂1023 Oct 87 Partridge, Trewitt HEMS MONITORING AND CONTROL LANGUAGE
This RFC specifies the High-Level Entity Management System
(HEMS) Monitoring and Control Language. This language
defines the request and replies used in HEMS. This memo
assumes knowledge of the HEMS system described in RFC-1021,
and of the ISO data encoding standard ASN.1. Distribution
of the memo is unlimited.
∂1022 Oct 87 Partridge, Trewitt THE HIGH-LEVEL ENTITY MANAGEMENT PROTOCOL (HEMP)
This memo presents an application protocol for managing network
entities such as hosts, gateways, and front end machines.
This protocol is a component of the High-Level Entity Management
System (HEMS), described is RFC-1021. This memo also assumes
a knowledge of the ISO data encoding standard, ASN.1.
Distribution of this memo is unlimited
∂1021 Oct 87 Partridge, Trewitt THE HIGH-LEVEL ENTITY MANAGEMENT SYSTEM (HEMS)
The memo provides a general overview of the High-Level Entity
Management System (HEMS). This system is experimental, and
is currently being tested in portions of the Internet.
The RFCs that currently define HEMS include this memo, along
with 1022, 1023, and 1024. Distribution of this memo is
unlimted.
∂1020 Nov 87 Romano, Stahl Internet Numbers
This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous
System Numbers. This RFC obsoletes RFC-997. Distribution of this memo is
unlimited.
∂1019 Sep 87 Dennis Arnon Report of the Workshop on Environments for
Computational Mathematics
This RFC is a report on a discussion of equations and their
representation in documentation and computational mathematics.
This is a request for the discussion of the ideas presented
here. Distribution of this memo is unlimited.
∂1018 Aug 87 Alex McKenzie Some Comments on SQuID
This memo is a discussion of some of the ideas expressed in RFC-1016 on
Source Quench. This memo introduces the distinction of the cause of
congestion in a gateway between the effects of "Funneling" and
"Mismatch". It is offered in the same spirit as RFC-1016; to stimulate
discussion. The opinions offered are personal, not corporate, opinions.
Distribution of this memo is unlimited.
∂1017 Aug 87 Barry Leiner Network Requirements for Scientific Computing
This RFC identifies the requirements on communication networks for
supporting scientific research. It proposes some specific areas for
near term work, as well as some long term goals. This is an "idea"
paper and discussion is strongly encouraged. Distribution of this memo
is unlimited.
∂1016 Jul 87 Prue and Postel Something a Host Could Do with Source Quench:
The Source Quench Intriduced Delay (SQuID)
This memo is intended to explore the issue of what a host could do with
a source quench. The proposal is for each source host IP module to
introduce some delay between datagrams sent to the same destination
host. Normally, the introduced delay is zero. When a source quench is
received, the introduced delay is increased. As time goes by, the
introduced delay is decreased. This is an "crazy idea paper" and
discussion is essential. Distribution of this memo is unlimited.
∂1015 Jul 87 RIACS Implementation Plan for Interagency Research Internet
Networking has become widespread in the scientific community,
and even more so in the computer science community. There are
networks being supported by a number of the Federal agencies
interested in scientific research, and many scientists
throughout the country have access to one or more of these
networks. While many of these networks are interconnected on
an informal basis, there is currently no consistent mechanism to
allow sharing of the networking resources. The RFC proposes an
Intergency Research Internet as the natural outgrowth of the
current Internet. This is an "idea paper" and discussion is
strongly encouraged. Distribution of this memo is unlimited.
∂1014 Jul 87 Sun Microsystems XDR: External Data Representation Standard
XDR is a standard for the description and encoding of data. Is useful
for trasferring data between different computer architectures. XDR fits
into ISO presentation layer, and is roughly analogous in purpose to
X.409, ISO Abstract Syntax Notation. The major difference between these
two is that XDR uses implicit typing, while X.409 uses explicit typing.
This RFC is distributed for information only, it does not establish a
Internet standard. Distribution of this memo is unlimited.
∂1013 Jun 87 Robert Scheifler X WINDOW SYSTEM PROTOCOL, VERSION 11
This RFC is the specification of the X window system protocol.
This document describes the requests and replies that make up the X
protocol. The X window system has been widely reviewed and tested
and the Internet community is encouraged to experiment with it.
This RFC is distributed for information only, it does not establish
a Internet standard. Distribution of this memo is unlimited.
∂1012 Jun 87 Reynolds/Postel Bibliography of Requests for Comments 1:999
This RFC is a reference guide for the Internet community which
provides a bibliographic summary of the Request for Comments numbers
1 through 999 issued between the years 1969-1987. Distribution of
this memo is unlimited.
∂1011 May 87 Reynolds, Postel Official Internet Protocols
This memo is an official status report on the protocols used in
the Internet community. It identifies the documents specifying
the official protocols used in the Internet. Comments indicate
any revisions or changes planned. Distribution of this memo is
unlimited.
∂1010 May 87 Reynolds, Postel Assigned Numbers
This memo is an official status report on the numbers used in
protocols in the Internet community. It documents the currently
assigned values from several series of numbers including link,
socket, port, and protocol, used in network protocol
implementations. Distribution of this memo is unlimited.
∂1009 Jun 87 Braden, Postel Requirements for Internet Gateways
This RFC summarizes the requirements for gateways to be used between
networks supporting the Internet protocols. This document is a formal
statement of the requirements to be met by gateways used in the Internet
system. As such, it is an official specification for the Internet
community. Distribution of this memo is unlimited.
∂1008 Jun 87 Wayne McCoy Implementation Guide for the ISO Transport Protocol
This RFC is being distributed to members of the Internet
community in order to solicit comments on the Implementors
Guide. While this document may not be directly relevant to
the research problems of the Internet, it may be of some
interest to a number of researchers and implementors.
Distribution of this memo is unlimited.
∂1007 Jun 87 Wayne McCoy Military Supplement to the ISO Transport Protocol
This RFC is being distributed to members of the Internet
community in order to solicit comments on the Draft Military
Supplement. While this document may not be directly relevant
to the research problems of the Internet, it may be of some
interest to a number of researchers and implementors.
Distribution of this memo is unlimited.
∂1006 May 87 Rose & Cass ISO Transport Services on Top of the TCP, Version: 3
This memo specifies a standard for the Internet community. Hosts
on the Internet that choose to implement ISO transport services
on top of the TCP are expected to adopt and implement this
standard. TCP port 102 is reserved for hosts which implement
this standard. Distribution of this memo is unlimited.
∂1005 May 87 Khanna & Malis The ARPANET AHIP-E Host Access Protocol
(Enhanced AHIP)
This RFC is a proposed specification for the encoding of Class A
IP addresses for use on ARPANET-style networks such as the Milnet
and Arpanet, and for enhancements to the ARPANET AHIP Host Access
Protocol (AHIP; formerly known as 1822). These enhancements
increase the size of the PSN field, allow ARPANET hosts to use
logical names to address each other, allow for the communication
of type-of-service information from the host to the PSN and
enable the PSN to provide congestion feedback to the host on a
connection basis. Distribution of this memo is unlimited.
∂1004 Apr 87 D. L. Mills A Distributed-Protocol Authentication Scheme
The purpose of this RFC is to focus discussion on authentication
problems in the Internet and possible methods of solution. The
proposed solutions this document are not intended as standards
for the Internet at this time. Rather, it is hoped that a general
consensus will emerge as to the appropriate solution to
authentication problems, leading eventually to the adoption of
standards. This document suggests mediated access-control and
authentication procedures suitable for those cases when an
association is to be set up between users belonging to
different trust environments. Distribution of this memo is
unlimited.
∂1003 Mar 87 Alan Katz Issues in Defining an Equations
Representation Standard
This memo is intended to identify and explore issues in defining a
standard for the exchange of mathematical equations. No attempt is
made at a complete definition and more questions are asked than are
answered. Questions about the user interface are only addressed to
the extent that they affect interchange issues. Comments are
welcome. Distribution of this memo is unlimited.
∂1002 Mar 87 NetBIOS Group Protocol Standard for A NetBOIS Service on a
TCP/UDP Transport: Detailed Specifications
This RFC defines a proposed standard protocol to support
NetBIOS services in a TCP/IP environment. Both local network
and internet operation are supported. Various node types are
defined to accommodate local and internet topologies and to
allow operation with or without the use of IP broadcast.
This RFC gives the detailed specifications of the NetBIOS-over-TCP
packets, protocols, and defined constants and variables. A more
general overview is found in a companion RFC, "Protocol Standard
For a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods".
Distribution of this memo is unlimited.
∂1001 Mar 87 NetBIOS Group Protocol Standard for A NetBOIS Service on a
TCP/UDP Transport: Concepts and Methods
This RFC defines a proposed standard protocol to support NetBIOS
services in a TCP/IP environment. Both local network and internet
operation are supported. Various node types are defined to
accommodate local and internet topologies and to allow operation
with or without the use of IP broadcast.
This RFC describes the NetBIOS-over-TCP protocols in a general
manner, emphasizing the underlying ideas and techniques.
Detailed specifications are found in a companion RFC, "Protocol
Standard For a NetBIOS Service on a TCP/UDP Transport: Detailed
Specifications". Distribution of this memo is unlimited.
∂1000 Aug 87 Reynolds/Postel The Request for Comments Reference Guide
This RFC is a Reference Guide to provide a historical account of the
first 1000 RFCs which were issued between the years 1969-1987.
Distribution of this memo is unlimited.
∂RFC Date Author Title (999:900)
---- ---- ------ -----
∂999 Apr 87 Westine & Postel Requests For Comments Summary
This RFC is a slightly annotated list of the 100 RFCs from
RFC-900 through RFC-999. This is a status report on these
RFCs. Distribution of this memo is unlimited.
∂998 Mar 87 Clark, Lambert & Zhang NETBLT: A Bulk Data Transfer Protocol
This document is a description of, and a specification for, the
NETBLT protocol. It is a revision of the specification published in
RFC-969. NETBLT (NETwork BLock Transfer) is a transport level
protocol intended for the rapid transfer of a large quantity of data
between computers. It provides a transfer that is reliable and flow
controlled, and is designed to provide maximum throughput over a wide
variety of networks. Although NETBLT currently runs on top of the
Internet Protocol (IP), it should be able to operate on top of any
datagram protocol similar in function to IP.
This document is published for discussion and comment, and does not
constitute a standard. The proposal may change and certain parts of
the protocol have not yet been specified; implementation of this
document is therefore not advised. Distribution of this memo is
unlimited.
∂997 Mar 87 Reynolds/Postel Internet Numbers
This memo is an official status report on the network numbers used in
the Internet community. As of 1-Mar-87 the Network Information
Center (NIC) at SRI International has assumed responsibility for
assignment of Network Numbers and Autonomous System Numbers. This
RFC documents the current assignments of these numbers at the time of
this transfer of responsibility. Distribution of this memo is
unlimited.
∂996 Feb 87 D. L. Mills Statistics Server
This RFC specifies a standard for the ARPA Internet community. Hosts
and gateways on the DARPA Internet that choose to implement a remote
statistics monitoring facility may use this protocol to send
statistics data upon request to a monitoring center or debugging
host. Distribution of this memo is unlimited.
∂995 Jan 87 ANSI X3S3.3 End System to Intermediate System Routing Exchange
Protocol for use in conjunction with ISO 8473
This Protocol is one of a set of International Standards produced to
facilitate the interconnection of open systems. The set of standards
covers the services and protocols required to achieve such
interconnection.
This Protocol is positioned with respect to other related standards
by the layers defined in the Reference Model for Open Systems
Interconnection (ISO 7498) and by the structure defined in the
Internal Organization of the Network Layer (DIS 8648). In
particular, it is a protocol of the Network Layer. This Protocol
permits End Systems and Intermediate Systems to exchange
configuration and routing information to facilitate the operation of
the routing and relaying functions of the Network Layer.
Distribution of this memo is unlimited.
∂994 Jan 87 ANSI X3S3.3 Final Text of DIS 8473, Protocol for Providing
the Connectionless Mode Network Service
This Protocol Standard is one of a set of International Standards
produced to facilitate the interconnection of open systems. The set
of standards covers the services and protocols required to achieve
such interconnection.
This Protocol Standard is positioned with respect to other related
standards by the layers defined in the Reference Model for Open
Systems Interconnection (ISO 7498). In particular, it is a protocol
of the Network Layer. This Protocol may be used between
network-entities in end systems or in Network Layer relay systems (or
both). It provides the Connectionless-mode Network Service as
defined in Addendum 1 to the Network Service Definition Covering
Connectionless-mode Transmission (ISO 8348/AD1). Distribution of
this memo is unlimited.
∂993 Dec 86 Clark & Lambert PCMAIL: A Distributed Mail System for Personal
Computers
This document is a discussion of the Pcmail workstation-based
distributed mail system. It is a revision of the design published in
NIC RFC-984. The revision is based on discussion and comment fromm a
variety of sources, as well as further research into the design of
interactive Pcmail clients and the use of client code on machines
other than IBM PCs. As this design may change, implementation of
this document is not advised. Distribution of this memo is
unlimited.
∂991 Nov 86 Reynolds/Postel OFFICIAL ARPA-INTERNET PROTOCOLS
This RFC identifies the documents specifying the official protocols
used in the Internet. Comments indicate any revisions or changes
planned. This memo is an official status report on the numbers used
in protocols in the ARPA-Internet community. Distribution of this
memo is unlimited.
∂990 Nov 86 Reynolds/Postel 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 memo is an official status
report on the numbers used in protocols in the ARPA-Internet
community. Distribution of this memo is unlimited.
∂989 Feb 87 John Linn Privacy Enhancement for Internet Electronics Mail:
Part I: Message Encipherment and Authentication Procedures
This RFC suggests a proposed protocol for the Internet community and
requests discussion and suggestions for improvements. This RFC is
the outgrowth of a series of IAB Privacy Task Force meetings and of
internal working papers distributed for those meetings. This RFC
defines message encipherment and authentication procedures, as the
initial phase of an effort to provide privacy enhancement services
for electronic mail transfer in the Internet. It is intended that the
procedures defined here be compatible with a wide range of key
management approaches, including both conventional (symmetric) and
public-key (asymmetric) approaches for encryption of data encrypting
keys. Use of conventional cryptography for message text encryption
and/or authentication is anticipated.
Privacy enhancement services (confidentiality, authentication, and
message integrity assurance) are offered through the use of end-to-
end cryptography between originator and recipient User Agent
processes, with no special processing requirements imposed on the
Message Transfer System at endpoints or at intermediate relay sites.
This approach allows privacy enhancement facilities to be
incorporated on a site-by-site or user-by-user basis without impact
on other Internet entities. Interoperability among heterogeneous
components and mail transport facilities is supported. Distribution
of this memo is unlimited.
∂988 Jul 86 S.E. Deering Host Extensions for IP Multicasting
This memo specifies the extensions required of a host implementation
of the Internet Protocol (IP) to support internetwork multicasting.
This specification supersedes that given in RFC-966, and constitutes
a proposed protocol standard for IP multicasting in the
ARPA-Internet. The reader is directed to RFC-966 for a discussion of
the motivation and rationale behind the multicasting extension
specified here. Distribution of this memo is unlimited.
∂987 Jun 86 S.E. Kille Mapping between X.400 and RFC-822
The X.400 series protocols have been defined by CCITT to provide an
Interpersonal Messaging Service (IPMS), making use of a store and
forward Message Transfer Service. It is expected that this standard
will be implemented very widely. This document describes a set of
mappings which will enable interworking between systems operating the
X.400 protocols and systems using RFC-822 mail protocol or protocols
derived from RFC-822. This RFC suggests a proposed protocol for the
ARPA-Internet community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
∂986 Jun 86 Ross Callon Guidelines for the Use of Internet-IP Addresses
in the ISO Connectionless-Mode Network Protocol
This RFC suggests a method to allow the existing IP addressing,
including the IP protocol field, to be used for the ISO
Connectionless Network Protocol (CLNP). This is a draft solution to
one of the problems inherent in the use of "ISO-grams" in the DoD
Internet. Related issues will be discussed in subsequent RFCs. This
RFC suggests a proposed protocol for the ARPA-Internet community, and
requests discussion and suggestions for improvements. Distribution
of this memo is unlimited.
∂985 May 86 Network Technical Advisory Group
Requirements for Internet Gateways -- Draft
This RFC summarizes the requirements for gateways to be used on
networks supporting the DARPA Internet protocols. While it applies
specifically to National Science Foundation research programs, the
requirements are stated in a general context and are believed
applicable throughout the Internet community. The purpose of this
document is to present guidance for vendors offering products that
might be used or adapted for use in an Internet application. It
enumerates the protocols required and gives references to RFCs and
other documents describing the current specification. Suggestions
and comments on this document are welcomed and can be sent to Dave
Mills (mills@usc-isid.arpa) or Dave Farber (farber@huey.udel.edu).
Distribution of this memo is unlimited.
∂984 May 86 Clark/L. Lambert PCMAIL: A Distributed Mail System
for Personal Computers
This document is a preliminary discussion of the design of a
personal-computer-based distributed mail system. Pcmail is a
distributed mail system that provides mail service to an arbitrary
number of users, each of which owns one or more personal computers
(PCs). The system is divided into two halves. The first consists of
a single entity called the "repository". The repository is a storage
center for incoming mail. Mail for a Pcmail user can arrive
externally from the Internet or internally from other repository
users. The repository also maintains a stable copy of each user's
mail state. The repository is therefore typically a computer with a
large amount of disk storage. It is published for discussion and
comment, and does not constitute a standard. As the proposal may
change, implementation of this document is not advised. Distribution
of this memo is unlimited.
∂983 Apr 86 Cass and Rose ISO Transport Services on Top of the TCP
This memo describes a proposed protocol standard for the ARPA
Internet community. The CCITT and the ISO have defined various
session, presentation, and application recommendations which have
been adopted by the international community and numerous vendors. To
the largest extent possible, it is desirable to offer these higher
level services directly in the ARPA Internet, without disrupting
existing facilities. This permits users to develop expertise with
ISO and CCITT applications which previously were not available in the
ARPA Internet. The intention is that hosts in the ARPA-Internet that
choose to implement ISO TSAP services on top of the TCP be expected
to adopt and implement this standard. Suggestions for improvement
are encouraged. Distribution of this memo is unlimited.
∂982 Apr 86 ANSI Guidelines for the Specification of the
Structure of the Domain Specific Part (DSP)
of the ISO Standard NSAP Address
This RFC is a draft working document of the ANSI "Guidelines for the
Specification of the Structure of the Domain Specific Part (DSP) of
the ISO Standard NSAP Address". It provides guidance to private
address administration authorities on preferred formats and semantics
for the Domain Specific Part (DSP) of an NSAP address. This RFC
specifies the way in which the DSP may be constructed so as to
facilitate efficient address assignment. This RFC is for
informational purposes only and its distribution is unlimited and
does not specify a standard of the ARPA-Internet.
∂981 Mar 86 D. L. Mills An Experimental Multiple-Path Routing Algorithm
This document introduces wiretap algorithms, a class of experimental,
multiple routing algorithms that compute quasi-optimum routes for
stations sharing a packet-radio broadcast channel. The primary route
(a minimum-distance path), and additional paths ordered by distance,
which serve as alternate routes should the primary route fail, are
computed. This prototype is presented as an example of a class of
routing algorithms and data-base management techniques that may find
wider application in the Internet community. Discussions and
suggestions for improvements are welcomed. Distribution of this memo
is unlimited.
∂980 Mar 86 Jacobsen/Postel Protocol Document Order Information
This RFC indicates how to obtain various protocol documents used in
the DARPA research community. Included is an overview of the new
1985 DDN Protocol Handbook and available sources for obtaining
related documents (such as DOD, ISO, and CCITT). Distribution of
this memo is unlimited.
∂979 Mar 86 Andrew G. Malis PSN End-to-End Functional Specification
This memo is an updated version of BBN Report 5775, "End-to-End
Functional Specification" and describes important changes to the
functionality of the interface between a Host and the PSN, and should
be carefully reviewed by anyone involved in supporting a host on
either the ARPANET or MILNET". The new End-to-End protocol (EE) is
being developed in order to correct a number of deficiencies in the
old EE, to improve its performance and overall throughput, and to
better equip the Packet Switch Node (PSN, also known as the IMP) to
support its current and anticipated host population. Distribution of
this memo is unlimited.
∂978 Mar 86 Reynolds,et al. Voice File Interchange Protocol (VFIP)
The purpose of the Voice File Interchange Protocol (VFIP) is to
permit the interchange of various types of speech files between
different systems in the ARPA-Internet community. Suggestions for
improvement are encouraged. Distribution of this memo is unlimited.
∂977 Feb 86 Brian Kantor & Phil Lapsley Network News Transfer Protocol
NNTP specifies a protocol for the distribution, inquiry, retrieval,
and posting of news articles using a reliable stream-based
transmission of news among the ARPA-Internet community. NNTP is
designed so that news articles are stored in a central database
allowing a subscriber to select only those items he wishes to read.
Indexing, cross-referencing, and expiration of aged messages are also
provided. This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.
Distribution of this memo is unlimited.
∂976 Feb 86 Mark. R. Horton UUCP Mail Interchange Format Standard
This document defines the standard format for the transmission of
mail messages between computers in the UUCP Project. It does not
however, address the format for storage of messages on one machine,
nor the lower level transport mechanisms used to get the date from
one machine to the next. It represents a standard for conformance by
hosts in the UUCP zone. Distribution of this memo is unlimited.
∂975 Feb 86 Dave Mills Autonomous Confederations
This RFC proposes enhancements to the Exterior Gateway Protocol (EGP)
to support a simple, multiple-level routing capability while
preserving the robustness features of the current EGP model. The
enhancements generalize the concept of the core system to include
multiple communities of autonomous systems, called autonomous
confederations. Discussion and suggestions for improvement are
requested. Distribution of this memo is unlimited.
∂974 Jan 86 Craig Partridge Mail Routing and the Domain System
This RFC presents a description of how mail systems on the Internet
are expected to route messages based on information from the domain
system. This involves a discussion of how mailers interpret MX RRs,
which are used for message routing. Distribution of this memo is
unlimited.
∂973 Jan 86 Paul Mockapetris Domain System Changes and Observations
This RFC documents updates to Domain Name System specifications
RFC-882 and RFC-883, suggests some operational guidelines, and
discusses some experiences and problem areas in the present system.
Distribution of this memo is unlimited.
∂972 Jan 86 F. Wancho Password Generator Protocol
This RFC specifies a standard for the ARPA Internet community. The
Password Generator Service (PWDGEN) provides a set of six randomly
generated eight-character "words" with a reasonable level of
pronounceability, using a multi-level algorithm. Hosts on the ARPA
Internet that choose to implement a password generator service are
expected to adopt and implement this standard. Distribution of this
memo is unlimited.
∂971 Jan 86 Annette L. DeSchon A Survey of Data Representation Standards
This RFC is a comparison of several data representation standards
that are currently in use. The standards discussed are the CCITT
X.409 recommendation, the NBS Computer Based Message System (CBMS)
standard, DARPA Multimedia Mail system, the Courier remote procedure
call protocol, and the SUN Remote Procedure Call package. No
proposals in this document are intended as standards for the
ARPA-Internet at this time. Rather, it is hoped that a general
consensus will emerge as to the appropriate approach to a data
representation standard, leading eventually to the adoption of an
ARPA-Internet standard. Distribution of this memo is unlimited.
∂970 Dec 85 John Nagle On Packet Switches With Infinite Storage
The purpose of this RFC is to focus discussion on a particular
problem in the ARPA-Internet and possible methods of solution. Most
prior work on congestion in datagram systems focuses on buffer
management. In this memo the case of a packet switch with infinite
storage is considered. Such a packet switch can never run out of
buffers. It can, however, still become congested. The meaning of
congestion in an infinite-storage system is explored. An unexpected
result is found that shows a datagram network with infinite storage,
first-in-first-out queuing, at least two packet switches, and a
finite packet lifetime will, under overload, drop all packets. By
attacking the problem of congestion for the infinite-storage case,
new solutions applicable to switches with finite storage may be
found. No proposed solutions this document are intended as standards
for the ARPA-Internet at this time. Distribution of this memo is
unlimited.
∂969 Dec 85 Clark, Lambert, Zhang NETBLT: A Bulk Data Transfer Protocol
This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.
This is a preliminary discussion of the Network Block Transfer
(NETBLT) protocol. NETBLT is intended for the rapid transfer of a
large quantity of data between computers. It provides a transfer
that is reliable and flow controlled, and is structured to provide
maximum throughput over a wide variety of networks. This description
is published for discussion and comment, and does not constitute a
standard. As the proposal may change, implementation of this
document is not advised. Distribution of this memo is unlimited.
∂968 Dec 85 Vint Cerf 'Twas the Night Before Start-up'
This memo discusses problems that arise and debugging techniques used
in bringing a new network into operation. Distribution of this memo
is unlimited.
∂967 Dec 85 M. A. Padlipsky All Victims Together
This RFC proposes a new set of RFCs on how the networking code is
integrated with various operating systems. It appears that this
topic has not received enough exposure in the literature. Comments
and suggestions are encouraged. Distribution of this memo is
unlimited.
∂966 Dec 85 Deering/Cheriton Host Groups: A Multicast Extension to the
Internet Protocol
In this paper, we describe a model of multicast service we call host
groups and propose this model as a way to support multicast in the
DARPA Internet environment. We argue that it is feasible to
implement this facility as an extension of the existing "unicast" IP
datagram model and mechanism. Discussion and suggestions for
improvements are requested. Distribution of this memo is unlimited.
∂965 Dec 85 Lorenzo Aguilar A Format for a Graphical Communication Protocol
This RFC describes the requirements for a graphical format on which
to base a graphical on-line communication protocol, and proposes an
Interactive Graphical Communication Format using the GKSM session
metafile. We hope this contribution will encourage the discussion of
multimedia data exchange and the proposal of solutions. Distribution
of this memo is unlimited.
∂964 Nov 85 Sidhu & Blumer Some Problems with the Specification of the
Military Standard Transmission Control Protocol
The purpose of this RFC is to provide helpful information on the
Military Standard Transmission Control Protocol (MIL-STD-1778) so
that one can obtain a reliable implementation of this protocol
standard. This note points out three errors with this specification.
This note also proposes solutions to these problems. Distribution of
this note is unlimited.
∂963 Nov 85 Deepinder P. Sidhu Some Problems with the Specification of the
Military Standard Internet Protocol
The purpose of this RFC is to provide helpful information on the
Military Standard Internet Protocol (MIL-STD-1777) so that one can
obtain a reliable implementation of this protocol. This paper points
out several problems in this specification. This note also proposes
solutions to these problems. Distribution of this note is unlimited.
∂962 Nov 85 M. A. Padlipsky TCP-4 Prime
This memo is in response to Bob Braden's call for a transaction
oriented protocol (RFC-955), and continues the discussion of a
possible transaction oriented transport protocol. This memo does not
propose a standard. Distribution of this memo is unlimited.
∂961 Dec 85 Joyce Reynolds & Jon Postel Official ARPA-Internet Protocols
This memo identifies the documents specifying the official protocols
used in the Internet, and comments on any revisions or changes
planned. This edition of the Official Protocols updates and
obsoletes RFC-944. This memo is an official status report on the
protocols used in the ARPA-Internet community. Distribution of this
memo is unlimited.
∂960 Dec 85 Joyce Reynolds & Jon Postel Assigned Numbers
This memo documents the currently assigned values from several
series of numbers used in network protocol implementations. This
edition of Assigned Numbers updates and obsoletes RFC-943. This
memo is an official status report on the numbers used in protocols
in the ARPA-Internet community. Distribution of this memo is
unlimited.
∂959 Oct 85 J. Postel, and J. K. Reynolds File Transfer Protocol (FTP)
This memo is the official specification of the File Transfer Protocol
(FTP) for the DARPA Internet community. The primary intent is to
clarify and correct the documentation of the FTP specification, not
to change the protocol. The following new optional commands are
included in this edition of the specification: Change to Parent
Directory (CDUP), Structure Mount (SMNT), Store Unique (STOU), Remove
Directory (RMD), Make Directory (MKD), Print Directory (PWD), and
System (SYST). Note that this specification is compatible with the
previous edition. Distribution of this memo is unlimited.
∂958 Oct 85 D. L. Mills Network Time Protocol (NTP)
This document describes the Network Time Protocol (NTP), a protocol
for synchronizing a set of network clocks using a set of distributed
clients and servers. NTP is built on the User Datagram Protocol
(UDP), which provides a connectionless transport mechanism. It is
evolved from the Time Protocol and the ICMP Timestamp message and is
a suitable replacement for both. This RFC suggests a proposed
protocol for the ARPA-Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is
unlimited.
∂957 Oct 85 D. L. Mills Experiments in Network Clock Synchronization
This RFC discusses some experiments in clock synchronization in the
ARPA-Internet community, and requests discussion and suggestions for
improvements. One of the services frequently neglected in computer
network design is a high-quality, time-of-day clock capable of
generating accurate timestamps with small errors compared to one-way
network delays. Such a service would be useful for tracing the
progress of complex transactions, synchronizing cached data bases,
monitoring network performance and isolating problems. In this memo
one such clock service design will be described and its performance
assessed. This design has been incorporated as an integral part of
the network routing and control protocols of the Distributed Computer
Network (DCnet) architecture. Distribution of this memo is
unlimited.
∂956 Sep 85 D. L. Mills Algorithms for Synchronizing Network Clocks
This RFC discussed clock synchronization algorithms for the
ARPA-Internet community, and requests discussion and suggestions for
improvements. The recent interest within the Internet community in
determining accurate time from a set of mutually suspicious network
clocks has been prompted by several occasions in which errors were
found in usually reliable, accurate clock servers after thunderstorms
which disrupted their power supply. To these sources of error should
be added those due to malfunctioning hardware, defective software and
operator mistakes, as well as random errors in the mechanism used to
set and synchronize clocks. This report suggests a stochastic model
and algorithms for computing a good estimator from time-offset
samples measured between clocks connected via network links.
Included in this report are descriptions of certain experiments which
give an indication of the effectiveness of the algorithms.
Distribution of this memo is unlimited.
∂955 Sep 85 Robert Braden Towards a Transport Service for Transaction
Processing Applications
The DoD Internet protocol suite includes two alternative transport
service protocols, TCP and UDP, which provide virtual circuit and
datagram service, respectively. These two protocols represent points
in the space of possible transport service attributes which are quite
"far apart". We want to examine an important class of applications,
those which perform what is often called "transaction processing".
We will see that the communication needs for these applications fall
into the gap "between" TCP and UDP -- neither protocol is very
appropriate.
∂954 Nov 85 Harrenstien, M. Stahl, E. Feinler NAME/WHOIS
This RFC is the official specification of the NICNAME/WHOIS Protocol.
This memo describes the protocol and the service. This edition of
the specification includes minor revisions to RFC-812 which brings it
up-to-date. Distribution of this memo is unlimited.
∂953 Nov 85 Harrenstien, M. Stahl, E. Feinler tname Server
This RFC is the official specification of the Hostname Server
Protocol. This edition of the specification includes minor revisions
to RFC-811 which brings it up-to-date. Distribution of this memo is
unlimited.
∂952 Nov 85 Harrenstien, M. Stahl, E. Feinler Internet Host Table Specification
This RFC is the official specification of the format of the Internet
Host Table. This edition of the specification includes minor
revisions to RFC-810 which brings it up-to-date. Distribution of
this memo is unlimited.
∂951 Sep 85 Bill Croft and John Gilmore Bootstrap protocol (BOOTP)
This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows
a diskless client machine to discover its own IP address, the address
of a server host, and the name of a file to be loaded into memory and
executed. The bootstrap operation can be thought of as consisting of
two phases. This RFC describes the first phase, which could be
labeled 'address determination and bootfile selection'. After this
address and filename information is obtained, control passes to the
second phase of the bootstrap where a file transfer occurs. The file
transfer will typically use the TFTP protocol, since it is intended
that both phases reside in PROM on the client. However BOOTP could
also work with other protocols such as SFTP or FTP.
∂950 Aug 85 J. Mogul & J. Postel Internet Standard Subnetting Procedure
This memo discusses the utility of "subnets" of Internet networks,
which are logically visible sub-sections of a single Internet
network. For administrative or technical reasons, many organizations
have chosen to divide one Internet network into several subnets,
instead of acquiring a set of Internet network numbers. This memo
specifies procedures for the use of subnets. These procedures are
for hosts (e.g., workstations). The procedures used in and between
subnet gateways are not fully described. Important motivation and
background information for a subnetting standard is provided in
RFC-940#[7]. This RFC specifies a protocol for the ARPA-Internet
community. If subnetting is implemented it is strongly recommended
that these procedures be followed. Distribution of this memo is
unlimited.
∂949 Jul 85 Mike Padlipsky FTP Unique-Named Store Command
There are various contexts in which it would be desirable to have an
FTP command that had the effect of the present STOR but rather than
requiring the sender to specify a file name instead caused the
resultant file to have a unique name relative to the current
directory.
∂948 Jun 85 Ira Winston Two Methods for the Transmission of IP Datagrams
Over IEEE 802.3 Networks
This memo describes two methods of encapsulating Internet Protocol
(IP) [1] datagrams on an IEEE 802.3 network [2]. This RFC suggests a
proposed protocol for the ARPA-Internet community, and requests
discussion and suggestions for improvements. Distribution of this
memo is unlimited.
∂947 Jun 85 Ken Lebowitz Multi-Network Broadcasting Within the Internet
This RFC describes the extension of a network's broadcast domain to
include more than one physical network through the use of a broadcast
packet repeater. Distribution of this memo is unlimited.
∂946 Jun 85 R. Nedved Telnet Terminal Location Number Option
Many systems provide a mechanism for finding out where a user is
logged in from usually including information about telephone
extension and office occupants names. The information is useful for
physically locating people and/or calling them on the phone. In 1982
CMU designed and implemented a terminal location database and
modified existing network software to handle a 64-bit number called
the Terminal Location Number (or TTYLOC). It now seems appropriate
to incorporate this mechanism into the TCP-based network protocol
family. The mechanism is not viewed as a replacement for the
Terminal Location Telnet Option (SEND-LOCATION) but as a shorthand
mechansim for communicating terminal location information between
hosts in a localized community. This RFC proposes a new option for
Telnet for the ARPA-Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is
unlimited.
∂945 May 85 Jon Postel A DoD Statement on the NRC Report
In May 1983 the National Research Council (NRC) was asked jointly by
DoD and NBS to study the issues and recommend a course of action.
The final report of the NRC committee was published in February 1985
(see RFC-942). The enclosed letter is from Donald C. Latham (ASDC3I)
to DCA transmitting the NRC report and requesting specific actions
relative to the recommendations of the report.
This RFC reproduces a letter from the Assistant Secretary of Defense
for Command, Control, Communications, and Intelligence (ASDC3I) to
the Director of the Defense Communications Agency (DCA). This letter
is distributed for information only. Distribution of this memo is
unlimited.
∂944 Apr 85 Reynolds/Postel Official ARPA-Internet Protocols
This RFC identifies the documents specifying the official protocols
used in the Internet. Comments indicate any revisions or changes
planned.
∂943 Apr 85 Reynolds/Postel Assigned Network 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 Joyce Reynolds. The assignment of numbers is also handled by
Joyce. If you are developing a protocol or application that will
require the use of a link, socket, port, protocol, network number,
etc., please contact Joyce to receive a number assignment.
∂942 Nat'l Research Council Mar 85 Transport Protocols for Department
of Defense Data Networks
This RFC reproduces the National Research Council report resulting
from a study of the DoD Internet Protocol (IP) and Transmission
Control Protocol (TCP) in comparison with the ISO Internet Protocol
(ISO-IP) and Transport Protocol level 4 (TP-4). This RFC is
distributed for information only. This RFC does not establish any
policy for the DARPA research community or the DDN operational
community. Distribution of this memo is unlimited.
∂941 ISO Apr 84 Addendum to the Network Service Definition
Covering Network Layer Addressing
This Addendum to the Network Service Definition Standard, ISO 8348,
defines the abstract syntax and semantics of the Network Address
(Network Service Access Point Address). The Network Address defined
in this Addendum is the address that appears in the primitives of the
connection-mode Network Service as the calling address, called
address, and responding address parameters, and in the primitives of
the connectionless-mode Network Service as the source address and
destination address parameters.
This document is distributed as an RFC for information only. It does
not specify a standard for the ARPA-Internet. Distribution of this
document is unlimited.
∂940 GADS April 85 Toward an Internet Standard Scheme for Subnetting
Several sites now contain a complex of local links connected to the
Internet via a gateway. The details of the internal connectivity are
of little interest to the rest of the Internet. One way of
organizing these local complexes of links is to use the same strategy
as the Internet uses to organize networks, that is, to declare each
link to be an entity (like a network) and to interconnect the links
with devices that perform routing functions (like gateways). This
general scheme is called subnetting, the individual links are called
subnets, and the connecting devices are called subgateways (or
bridges, or gateways). This RFC discusses standardizing the protocol
used in subnetted environments in the ARPA-Internet. Distribution of
this memo is unlimited. The author of this RFC is the Gateway
Algorithms and Data Structures (GADS) Task Force, chaired by David L.
Mills.
∂939 Nat'l Research Council Mar 85 Executive Summary of the NRC Report on
Transport Protocols for Department of
Defense Data Networks
This RFC reproduces the material from the "front pages" of the
National Research Council report resulting from a study of the DOD
Internet Protocol (IP) and Transmission Control Protocol (TCP) in
comparison with the ISO Internet Protocol (ISO-IP) and Transport
Protocol level 4 (TP-4). The point of this RFC is to make the text
of the Executive Summary widely available in a timely way. The order
of presentation has been altered, and the pagination changed. This
RFC is distributed for information only. This RFC does not establish
any policy for the DARPA research community or the DDN operational
community. Distribution of this memo is unlimited.
∂938 Trudy Miller Feb 85 Internet Reliable Transaction Protocol
Functional and Interface Specification
This RFC is being distributed to members of the DARPA research
community in order to solicit their reactions to the proposals
contained in it. While the issues discussed may not be directly
relevant to the research problems of the DARPA community, they may be
interesting to a number of researchers and implementors. This RFC
suggests a proposed protocol for the ARPA-Internet community, and
requests discussion and suggestions for improvements. Distribution
of this memo is unlimited.
∂937 Butler,Postel, et al. Feb 85 Post Office Protocol - Version 2
This RFC suggests a simple method for workstations to dynamically
access mail from a mailbox server. This RFC specifies a proposed
protocol for the ARPA-Internet community, and requests discussion and
suggestions for improvement. This memo is a revision of RFC%918.
Distribution of this memo is unlimited.
∂936 M. Karels Feb 85 Another Internet Subnet Addressing Scheme
There have been several proposals for schemes to allow the use of a
single Internet network number to refer to a collection of physical
networks under common administration which are reachable from the
rest of the Internet by a common route. Such schemes allow a
simplified view of an otherwise complicated topology from hosts and
gateways outside of this collection. They allow the complexity of
the number and type of these networks, and routing to them, to be
localized. Additions and changes in configuration thus cause no
detectable change, and no interruption of service, due to slow
propagation of routing and other information outside of the local
environment. These schemes also simplify the administration of the
network, as changes do not require allocation of new network numbers
for each new cable installed. This proposal discusses an alternative
scheme, one that has been in use at the University of California,
Berkeley since April 1984. This RFC suggests a proposed protocol for
the ARPA-Internet community, and requests discussion and suggestions
for improvements. Distribution of this memo is unlimited.
∂935 J. Robinson Jan 85 Reliable Link Layer Protocols
This RFC discusses protocols proposed recently in RFCs 914 and 916,
and suggests a proposed protocol that could meet the same needs
addressed in those memos. The stated need is reliable communication
between two programs over a full-duplex, point-to-point communication
link, and in particular the RFCs address the need for such
communication over an asynchronous link at relatively low speeds.
The suggested protocol uses the methods of existing national and
international data link layer standards. This RFC suggests a
proposed protocol for the ARPA-Internet community, and requests
discussion and suggestions for improvements. Distribution of this
memo is unlimited.
∂934 Rose/Stefferud Jan 85 Proposed Standard for Message Encapsulation
This memo concerns itself with message forwarding. Forwarding can be
thought of as encapsulating one or more messages inside another.
Although this is useful for transfer of past correspondence to new
recipients, without a decapsulation process (which this memo terms
"bursting"), the forwarded messages are of little use to the
recipients because they can not be distributed, forwarded,
replied-to, or otherwise processed as separate individual messages.
In order to burst a message it is necessary to know how the component
messages were encapsulated in the draft. At present there is no
unambiguous standard for interest group digests. This RFC proposes a
proposed protocol for the ARPA-Internet community, and requests
discussion and suggestions for improvements. Distribution of this
memo is unlimited.
∂933 Steve Silverman Jan 85 Output Marking Telnet Option
This proposed option would allow a Server-Telnet to send a banner to
a User-Telnet so that this banner would be displayed on the
workstation screen independently of the application software running
in the Server-Telnet. This RFC proposes a new option for Telnet for
the ARPA-Internet community, and requests discussion and suggestions
for improvements. Distribution of this memo is unlimited.
∂932 David D. Clark Jan 85 A Subnetwork Addressing Scheme
This RFC proposes an alternative addressing scheme for subnets which,
in most cases, requires no modification to host software whatsoever.
The drawbacks of this scheme are that the total number of subnets in
any one network are limited, and that modification is required to all
gateways. This RFC suggests a proposed protocol for the
ARPA-Internet community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
∂931 Mike StJohns Jan 85 Authentication Server
This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.
This is the second draft of this proposal (superseding RFC 912) and
incorporates a more formal description of the syntax for the request
and response dialog, as well as a change to specify the type of user
identification returned. Distribution of this memo is unlimited.
∂930 Solomon/Wimmers Jan 85 Telnet Terminal Type Option
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. Distribution of this memo is unlimited. This standard
supersedes RFC 884. The only change is to specify that the
TERMINAL-TYPE IS sub-negotiation should be sent only in response to
the TERMINAL-TYPE SEND sub-negotiation.
∂929 Lilienkamp,Mandell,Padlipsky Dec 84 Proposed Host-Front End Protocol
The Host-Front End Protocol introduced in RFC-928 is described in
detail in this memo. The first order of business is to declare that
THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of
business is to request that any readers of these documents who are
able to do test implementations (a) do so and (b) coordinate their
efforts with the author (617-271-2978 or Padlipsky@USC-ISI.ARPA).
This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.
Distribution of this memo is unlimited.
∂928 Padlipsky Dec 84 Introduction to Proposed DOD Standard H-FP
The broad outline of the Host-Front End Protocol introduced here and
described in RFC 929 is the result of the deliberations of a number
of experienced H-FP designers, who sat as a committee of the DoD
Protocol Standards Technical Panel. It is the intent of the
designers that the protocol be subjected to multiple test
implementations and probable iteration before being agreed upon as
any sort of "standard". Therefore, the first order of business is to
declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second
order of business is to request that any readers of these documents
who are able to do test implementations (a) do so and (b) coordinate
their efforts with the author (617-271-2978 or
Padlipsky@USC-ISI.ARPA.). This RFC suggests a proposed protocol for
the ARPA-Internet community, and requests discussion and suggestions
for improvements. Distribution of this memo is unlimited.
∂927 B. Anderson Dec 84 TACACS User Identification Telnet Option
The following is the description of a TELNET option designed to
facilitate double login avoidance. It is intended primarily for TAC
connections to target hosts on behalf of TAC users, but it can be
used between any two consenting hosts. For example, all hosts at one
site (e.g., BBN) can use this option to avoid double login when
TELNETing to one another.
This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.
Distribution of this memo is unlimited.
∂926 ISO Dec 84 Protocol for Providing the Connectionless-Mode
Network Services
This note is the draft ISO protocol roughly similar to the DOD
Internet Protocol. This document has been prepared by retyping the
text of ISO DIS 8473 of May 1984, which is currently undergoing
voting within ISO as a Draft International Standard (DIS). This
document is distributred as an RFC for information only. It does not
specify a standard for the ARPA-Internet. Distribution of this memo
is unlimited.
∂925 J. Postel Oct 84 Multi-LAN Address Resolution
The problem of treating a set of local area networks (LANs) as one
Internet network has generated some interest and concern. It is
inappropriate to give each LAN within an site a distinct Internet
network number. It is desirable to hide the details of the
interconnections between the LANs within an site from people,
gateways, and hosts outside the site. The question arises on how to
best do this, and even how to do it at all. In RFC-917 Jeffery Mogul
makes a case for the use of "explicit subnets" in a multi-LAN
environment. The explicit subnet scheme is a call to recursively
apply the mechanisms the Internet uses to manage networks to the
problem of managing LANs within one network. In this note I urge
another approach: the use of "transparent subnets" supported by a
multi-LAN extension of the Address Resolution Protocol. This RFC
suggests a proposed protocol for the ARPA-Internet community, and
requests discussion and suggestions for improvements. Distribution
of this memo is unlimited.
∂924 Reynolds/Postel Oct 84 Official ARPA-Internet Protocols
This RFC identifies the documents specifying the official protocols
used in the ARPA-Internet. This edition of Official ARPA-Internet
Protocols obsoletes RFC 901 and earlier editions. This memo is an
official status report on the numbers used in protocols in the
ARPA-Internet community. Distribution of this memo is unlimited.
∂923 Reynolds/Postel Oct 84 Assigned Numbers
This RFC documents the currently assigned values from several series
of numbers used in network protocol implementations. This edition of
Assigned Numbers obsoletes RFC 900 and earlier editions. This memo
is an official status report on the numbers used in protocols in the
ARPA-Internet community. Distribution of this memo is unlimited.
∂922 Jeff Mogul Dec 84 Broadcasting Internet Datagrams in
the Presence of Subnets
We propose simple rules for broadcasting Internet datagrams on local
networks that support broadcast, for addressing broadcasts, and for
how gateways should handle them.
This RFC suggests a proposed protocol for the ARPA-Internet
community, and requests discussion and suggestions for improvements.
Distribution of this memo is unlimited.
∂921 Jon Postel Nov 84 Domain Name System Implementation
Schedule - Revised
This memo is a policy statement on the implementation of the Domain
Style Naming System in the Internet. This memo is an update of
RFC-881, and RFC-897. This is an official policy statement of the
IAB and the DARPA.
∂920 Postel/Reynolds Oct 84 Domain Requirements
This memo states the requirements on establishing a Domain, and
introduces the limited set of top level domains. This memo is a
policy statement on the requirements of establishing a new domain in
the ARPA-Internet and the DARPA research community. This is an
official policy statement of the IAB and the DARPA. Distribution of
this memo is unlimited.
∂919 Jeff Mogul Oct 84 Broadcasting Internet Datagrams
We propose simple rules for broadcasting Internet datagrams on local
networks that support broadcast, for addressing broadcasts, and for
how gateways should handle them.
∂918 Joyce Reynolds Oct 84 Post Office Protocol (POP)
This RFC suggests a simple method for workstations to dynamically
access mail from a mailbox server. This RFC specifies a proposed
protocol for the ARPA-Internet community, and requests discussion and
suggestions for improvement.
∂917 Jeff Mogul Oct 84 Internet Subnets
This memo discusses subnets and proposes procedures for the use of
subnets, including approaches to solving the problems that arise,
particularly that of routing. A subnet of an Internet network is a
logically visible sub-section of a single Internet network. For
administrative or technical reasons, many organizations have chosen
to divide one Internet network into several subnets, instead of
acquiring a set of Internet network numbers. This RFC suggests a
proposed protocol for the ARPA-Internet community, and requests
discussion and suggestions for improvements. Distribution of this
memo is unlimited.
∂916 Greg Finn Oct 84 Reliable Asynchronous Transfer Protocol (RATP)
This paper proposes and specifies a protocol which allows two
programs to reliably communicate over a communication link. It
ensures that the data entering one end of the link if received
arrives at the other end intact and unaltered. The protocol, named
RATP, is designed to operate over a full duplex point-to-point
connection. It contains some features which tailor it to the RS-232
links now in common use.
∂915 Elvy/Nedved Dec 84 Network Mail Path Service
This RFC proposed a new service for the ARPA-Internet community and
requests discussion and suggestions for improvements. Distribution
of this memo is unlimited. The network mail path service fills the
current need of people to determine mailbox addresses for hosts that
are not part of the ARPA-Internet but can be reached by one or more
relay hosts that have Unix to Unix Copy (UUCP) mail, CSNET mail,
MAILNET mail, BITNET mail, etc. Anyone can use the service if they
have TCP/TELENET to one of the hosts with a mail path server.
∂914 Farber/Delp/Conte Sep 84 A Thinwire Protocol
This RFC focuses discussion on the particular problems in the
ARPA-Internet of low speed network interconnection with personal
computers, and possible methods of solution. None of the proposed
solutions in this document are intended as standards for the
ARPA-Internet. Rather, it is hoped that a general consensus will
emerge as to the appropriate solution to the problems, leading
eventually to the adoption of standards. Distribution of this memo
is unlimited.
∂913 M. Lottor Sept 84 Simple File Transfer Protocol
This memo describes a proposed Simple File Transfer Protocol (SFTP).
It fills the need of people wanting a protocol that is more useful
than TFTP but easier to implement (and less powerful) than FTP. SFTP
supports user access control, file transfers, directory listing,
directory changing, file renaming and deleting. Discussion of this
proposal is encouraged, and suggestions for improvements may be sent
to the author. Distribution of this memo is unlimited.
∂912 M. StJohns Sept 84 Authentication Service
This memo describes a proposed authentication protocol for verifying
the identity of a user of a TCP connection. Discussion of this
proposal is encouraged, and suggestions for improvements may be sent
to the author. Distribution of this memo is unlimited.
∂911 P. Kirton Sep 84 EGP Gateway under Berkeley Unix 4.2
This memo describes an implementation of the Exterior Gateway
Protocol (EGP) (in that sense it is a status report). The memo also
discusses some possible extentions and some design issues (in that
sense it is an invitation for further discussion). Distribution of
this memo is unlimited.
∂910 H. Forsdick Aug 84 Multimedia Mail Meeting Notes
This memo is a report on a meeting about the experimental multimedia
mail system (and in a sense a status report on that experiment). The
meeting was held at Bolt Beranek and Newman on 23-24 July 1984 to
discuss recent progress by groups who are building multimedia mail
systems and to discuss a variety of issues related to the further
development of multimedia systems. Representatives were present from
BBN, ISI, SRI and Linkabit. Distribution of this memo is unlimited.
∂909 Welles/Milliken July 84 Loader Debugger Protocol
The Loader Debugger Protocol (LDP) is an application layer protocol
for loading, dumping, and debugging target machines from hosts in a
network environment. This RFC specifies a proposed protocol for the
ARPA-Internet and DARPA research community, and requests discussion
and suggestions for improvemts. Distribution of this memo is
unlimited.
∂908 Velten/Hinden/Sax July 84 Reliable Data Protocol
The Reliable Data Protocol (RDP) is designed to provide a reliable
data transport service for packet-based applications. This RFC
specifies a proposed protocol for the ARPA-Internet and DARPA
research community, and requests discussion and suggestions for
improvemts. Distribution of this memo is unlimited.
∂907 S. Storch July 84 Host Access Protocol Specification
This document specifies the Host Access Protocol (HAP). Although HAP
was originally designed as the network-access level protocol for the
DARPA/DCA sponsored Wideband Packet Satellite Network, it is intended
that it evolve into a standard interface SATNET and TACNET (aka
MATNET) as well as the Wideband Network. HAP is an experimental
protocol, and will undergo further revision as new capabilities are
added and/or different satellite networks are suported.
Implementations of HAP should be performed in coordination with
satellite network development and operations personnel.
∂906 R. Finlayson June 84 Bootstrap Loading Using TFTP
It is often convenient to be able to boootstrap a computer system
from a communications network. This RFC proposes the use of the IP
TFTP protocol for bootstrap loading in this case.
∂905 ISO May 84 ISO Transport Protocol Specification (ISO DP 8073)
This is the current specification of the ISO Transport Protocol.
This document is the text of ISO/TC97/SC16/N1576 as corrected by
ISO/TC97/SC16/N1695. This is the specification currently being voted
on in ISO as a Draft International Standard (DIS). This document is
distributed as an RFC for your information only, it does not specify
a standard for the ARPA-Internet or DARPA research community. Our
thanks to Alex McKenzie of BBN for making this online version
available. Please note the size of this document, the file contains
258,729 characters.
∂904 D. Mills May 84 Exterior Gateway Protocol Formal Specification
This memo is the specification of the Exterior Gateway Protocol.
This memo updates portions of RFC 888 and RFC 827. Anyone working on
an implementation of the EGP should follow this specification. This
RFC specifies an official protocol of the DARPA community for use
between gateways of different autonomous systems in the
ARPA-Internet.
∂903 Finlayson,Mann,Mogul,Theimer June 84 A Reverse Address Resolution Protocol
This RFC suggests a method for workstations to dynamically find their
protocol address (e.g., their Internet Address), when they know only
their hardware address (e.g., their attached physical network
address). This RFC specifies a proposed protocol for the ARPA
Internet community, and requests discussion and suggestions for
improvements.
∂902 Postel/Reynolds July 84 ARPA-Internet Protocol Policy
The purpose of this memo is to explain how protocol standards are
adopted for the ARPA-Internet and the DARPA research community.
There are three important aspects to be discussed: the process, the
authority, and the complex relationship between the DARPA community
and the DDN community. This memo is a policy statement on how
protocols become official standards for the ARPA-Internet and the
DARPA research community. This is an official policy statement of
the ICCB and the DARPA. Distribution of this memo is unlimited.
∂901 J. Reynolds June 84 Official ARPA-Internet Protocols
This RFC identifies the documents specifying the official protocols
used in the ARPA-Internet. Annotations identify any revisions or
changes planned. This memo is an official status report on the
protocols used in the DARPA research community.
∂900 J. Reynolds June 84 Assigned Numbers
This RFC specifies parameter values use in the Internet family of
protocols, such as network numbers, well known ports, protocol types,
and version numbers. This memo is an official status report on the
protocol parameters used in the Internet protocol system.
RFC Author Date Title (899:800)
--- ------ ---- -----
∂899 Postel Apr 84 Requests For Comments Summary
This RFC is a slightly annotated list of the 100 RFCs from RFC 800
through RFC 899. This is a status report on these RFCs.
∂898 Hinden Apr 84 Gateway Special Interest Group Meeting
Notes
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.
∂897 Postel Feb 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 Nagle Jan 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.
∂895 Postel Apr 84 A Standard for the Transmission of
IP Datagrams over Experimental Ethernet
Networks
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.
∂894 Hornig Apr 84 A Standard for the Transmission of
IP Datagrams over Ethernet Networks
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.
∂893 Leffler Apr 84 Trailer Encapsulations
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.
∂892 ISO Dec 83 ISO Transport Protocol Specification
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.
∂891 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 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 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 Seamonson Jan 84 "Stub" Exterior Gateway Protocol
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.
∂887 Accetta Dec 83 Resource Location Protocol
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.
∂886 Rose Dec 83 Proposed Standard for Message Header
Munging
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.
∂885 Postel Dec 83 Telnet End of Record Option
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.
∂884 Solomon Dec 83 Telnet Terminal Type Option
This RFC specifies a standard for the ARPA Internet community. It
specifies a method for exchanging terminal type information in the
Telnet protocol.
∂883 Mockapetris Nov 83 Domain Names - Implementation and
Specification
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.
∂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 protocol and servers used to
implement domain name facilities.
∂881 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 Oct 83 Official Protocols
This RFC identifies the documents specifying the official protocols
used in the ARPA Internet. Annotations identify any revisions or
changes planned. Obsoletes RFC 840.
∂879 Postel Nov 83 The TCP Maximum Segment Size and
Related Topics
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".
∂878 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 Korb Sep 83 A Standard for the Transmission of IP
Datagrams Over Public Data Networks
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.
∂876 Smallberg Sep 83 Survey of SMTP Implementations
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.
∂875 Padlipsky Sep 82 Gateways, Architectures, and Heffalumps
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.
∂874 Padlipsky Sep 82 A Critique of X.25
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.
∂873 Padlipsky Sep 82 The Illusion of Vendor Support
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.
∂872 Padlipsky Sep 82 TCP-ON-A-LAN
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.
∂871 Padlipsky Sep 82 A Perspective on the Arpanet Reference
Model
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.
∂870 Reynolds Oct 83 Assigned Numbers
This RFC documents the list of numbers assigned for networks,
protocols, etc. Obsoletes RFCs 820, 790, 776, 770, 762, 758, 755,
750, 739, 604.
∂869 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 May 83 Time Protocol
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.
∂867 Postel May 83 Daytime Protocol
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.
∂866 Postel May 83 Active Users
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.
∂865 Postel May 83 Quote of the Day Protocol
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.
∂864 Postel May 83 Character Generator Protocol
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.
∂863 Postel May 83 Discard Protocol
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.
∂862 Postel May 83 Echo Protocol
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.
∂861 Postel May 83 Telnet Extended Options - List Option
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.
∂860 Postel May 83 Telnet Timing Mark Option
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.
∂859 Postel May 83 Telnet Status Option
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).
∂858 Postel May 83 Telnet Suppress Go Ahead Option
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.
∂857 Postel May 83 Telnet Echo Option
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.
∂856 Postel May 83 Telnet Binary Transmission
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.
∂855 Postel May 83 Telnet Option Specifications
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.
∂854 Postel May 83 Telnet Protocol Specifications
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.
∂853 Not issued yet.
∂852 Malis Apr 83 The ARPANET Short Blocking Feature
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.
∂851 Malis Apr 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. 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.
∂850 Horton Jun 83 Standard for Interchange of USENET
Messages
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.
∂849 Crispin May 83 Suggestions for Improved Host Table
Distribution
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.
∂848 Smallberg Mar 83 Who provides the "Little" TCP Services?
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.
∂847 Westine Feb 83 Summary of Smallberg Surveys
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).
∂846 Smallberg Feb 83 Who Talks TCP? -- Survey of 22 February
1983
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.
∂845 Smallberg Feb 83 Who Talks TCP? -- Survey of 15 February
1983
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.
∂844 Clements Feb 83 Who Talks ICMP, too? Survey of 18
February 1983
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.
∂843 Smallberg Feb 83 Who Talks TCP? -- Survey of 8 February
1983
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.
∂842 Smallberg Feb 83 Who Talks TCP? -- Survey of 1 February
1983
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.
∂841 FIPS PUB 98 Jan 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.
Obsoletes RFC 806.
∂840 Postel Apr 83 Official Protocols
This RFC has been revised, see RFC 880.
∂839 Smallberg Jan 83 Who Talks TCP?
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.
∂838 Smallberg Jan 83 Who Talks TCP?
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.
∂837 Smallberg Jan 83 Who Talks TCP?
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.
∂836 Smallberg Jan 83 Who Talks TCP?
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.
∂835 Smallberg Dec 82 Who Talks TCP?
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.
∂834 Smallberg Dec 82 Who Talks TCP?
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.
∂833 Smallberg Dec 82 Who Talks TCP?
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.
∂832 Smallberg Dec 82 Who Talks TCP?
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.
∂831 Braden Dec 82 Backup Access to the European Side of
SATNET
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.
∂830 Zaw-Sing Su Oct 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 Cerf Oct 82 Packet Satellite Technology Reference
Sources
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.
∂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.
∂827 Rosen Oct 82 Exterior Gateway Protocol (EGP)
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.
∂826 Plummer Nov 82 An Ethernet Address Resolution Protocol
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.
∂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 MacGregor Aug 82 The Cronus Virtual Local Network
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.
∂823 Hinden Sep 82 The DARPA Internet Gateway
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.
∂822 Crocker Aug 82 Standard for the Format of ARPA
Internet Text Messages
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.
∂821 Postel Aug 82 Simple Mail Transfer Protocol
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.
∂820 Postel Jan 82 Assigned Numbers
This RFC is an old version, see RFC 870.
∂819 Zaw-Sing Su Aug 82 The Domain Naming Convention for
Internet User Applications
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.
∂818 Postel Nov 82 The Remote User Telnet Service
This RFC is the specification of an application protocol. Any host
that implements this application level service must follow this
protocol.
∂817 Clark Jul 82 Modularity and Efficiency in Protocol
Implementation
This RFC will discuss some of the commonly encountered reasons why
protocol implementations seem to run slowly.
∂816 Clark Jul 82 Fault Isolation and Recovery
This RFC describes the portion of fault isolation and recovery which
is the responsibility of the host.
∂815 Clark Jul 82 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.
∂814 Clark Jul 82 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.
∂813 Clark Jul 82 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.
∂812 Harrenstien Mar 82 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.
∂811 Harrenstien Mar 82 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.
∂810 Feinler Mar 82 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.
∂809 Chang Feb 82 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.
∂808 Postel Mar 82 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.
∂807 Postel Feb 82 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.
∂806 NBS Sep 81 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.
∂805 Postel Feb 82 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.
∂804 CCITT Jan 82 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.
∂803 Agarwal Nov 81 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.
∂802 Malis Nov 81 The 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.
∂801 Postel Nov 81 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.
∂800 Postel Nov 82 Requests for Comments Summary
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 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.
RFC NIC number Date Author Title (599:500)
--- --------- --------- ------ ---------------
599 NIC-20854 13 Dec 73 Braden Update on NETRJS
598 NIC-20853 5 Dec 73 NICSTA RF Index - December 5, 1973
597 NIC-20826 12 Dec 73 Neigus Host Status
596 NIC-20812 8 Dec 73 Taft Second Thoughts On TELNET Go-Ahead
595 NIC-20617 12 Dec 73 Hathaway Second Thoughts in Defense of the
TELNET Go-Ahead
594 NIC-20616 10 Dec 73 Burchfiel Speedup of Host-Imp Interface
593 NIC-20615 29 Nov 73 McKenzie TELNET and FTP Implementation
Schedule Change
592 NIC-20391 20 Nov 73 Watson Some Thoughts on System Design to
Facilitate Resource Sharing
591 NIC-20327 29 Nov 73 Walden Addition to the Very Distant Host
Specifications
590 NIC-20326 19 Nov 73 Padlipsky MULTICS Address Change
589 NIC-20268 26 Nov 73 Braden CCN NETRJS Server Message to
Remote User
588 NIC-20217 29 Oct 73 Stokes London Node Is Now Up
587 NIC-20198 13 Nov 73 Postel Announcing New TELNET Options
586 NIC-20096 8 Nov 73 McKenzie Traffic Statistics (October 1973)
585 NIC-20050 6 Nov 73 Crocker ARPANET Users Interest Working
Group Meeting
584 NIC-20049 6 Nov 73 Iseli Charter for ARPANET Users
Interest Working Group
583 Not Issued
582 NIC-19962 5 Nov 73 Clements Comments on RFC 580 - Machine
Readable Protocols
581 NIC-19860 2 Nov 73 Crocker Corrections to RFC 560, 18492,
Remote controlled Transmission
and Echoing Telnet Option
580 NIC-19849 25 Oct 73 Postel Note to Protocol Designers and
Implementers
579 NIC-19655 15 Oct 73 McKenzie Traffic Statistics (September 1973)
578 NIC-19501 8 Oct 73 Bhushan Using MIT-MATHLAB MACSYMA from
MIT-DMS Muddle
577 NIC-19356 18 Oct 73 Crocker Mail Priority
576 NIC-19324 26 Sep 73 Victor Proposal for Modifying Linking
575 Not Issued
574 NIC-19144 26 Sep 73 Krilanovich Announcement of a Mail Facility at UCSB
573 NIC-19083 14 Sep 73 Bhushan Data and File Transfer - Some
Measurement Results
572 Not Issued
571 NIC-18974 15 Nov 73 Braden TENEX FTP Problem
570 NIC-18973 30 Oct 73 Pickens Experimental Input Mapping
Between NVT ASCII and UCSB
Online System
569 NIC-18972 15 Oct 73 Padlipsky NETED: A Common Editor for the
ARPA Network
568 NIC-18971 18 Sep 73 McQuillan Response to RFC 567 -
Cross-Country Network Bandwidth
567 NIC-18970 6 Sep 73 Deutsch Cross-Country Network Bandwidth
566 NIC-18801 4 Sep 73 McKenzie Traffic Statistics (August 1973)
565 NIC-18777 28 Aug 73 Cantor Storing Network Survey Data at
the Datacomputer
564 Not Issued
563 NIC-18775 28 Aug 73 Davidson Comments on the RCTE TELNET
Option
562 NIC-18638 28 Aug 73 McKenzie Modifications to the TELNET
Specification
561 NIC-18516 5 Sep 73 Bhushan Standardizing Network Mail Headers
560 NIC-18492 20 Aug 73 Crocker Remote Controlled Transmission
and Echoing TELNET Option
559 NIC-18482 15 Aug 73 Bhushan Comments on the New TELNET
Protocol and Its Implementation
558 Not Issued
557 NIC-18457 30 Aug 73 Wessler Revelations in Network Host
Measurements
556 NIC-18376 13 Aug 73 McKenzie Traffic Statistics (July 1973)
555 NIC-17993 27 Jul 73 White Responses to Critiques of the
Proposal Mail Protocol
554 Not Issued
553 NIC-17810 14 Jul 73 Irby Draft Design for a Text/Graphics
Protocol
552 NIC-17809 13 Jul 73 Owen Single Access to Standard
Protocols
551 NIC-17797 27 Aug 73 Feinroth (Re: NYU, ANL, and LBL Entering
Net, and FTP Protocol)
550 NIC-17796 24 Aug 73 Deutsch NIC NCP Experiment
549 NIC-17795 Jul 73 Michener Minutes of Network Graphics Group
Meeting, 15-17 July 1973
548 NIC-17794 16 Aug 73 Walden Hosts Using the IMP Going Down
Message
547 NIC-17793 13 Aug 73 Walden Change to the Very Distant Host
Specification
546 NIC-17792 10 Aug 73 Thomas TENEX Load Averages for July 1973
545 NIC-17791 23 Jul 73 Pickens Of What Quality Be the UCSB
Resources Evaluators
544 NIC-17782 13 Jul 73 Meyer Locating ON-Line Documentation at
SRI-ARC
543 NIC-17777 13 Jul 73 Meyer Network Journal Submission and
Delivery
542 NIC-17759 12 Jul 73 Neigus File Transfer Protocol
541 Not Issued
540 Not Issued
539 NIC-17644 7 Jul 73 Crocker Thoughts on the MAIL Protocol
Proposed in RFC 524
538 NIC-17642 5 Jul 73 McKenzie Traffic Statistics (June 1973)
537 NIC-17498 27 Jun 73 Bunch Announcement of NGG Meeting July
16-17
536 Not Issued
535 NIC-17454 25 Jul 73 Thomas Comments on File Access Protocol
534 NIC-17453 17 Jul 73 Walden Lost Message Detection
533 NIC-17452 17 Jul 73 Walden Message-ID Numbers
532 NIC-17451 12 Jul 73 Merryman The UCSD-CC Server-FTP Facility
531 NIC-17450 26 Jun 73 Padlipsky Feast or Famine? A Response to
Two Recent RFC's About Network Information
530 NIC-17375 22 Jun 73 Bhushan A Report on the Survey Project
529 NIC-17165 29 Jun 73 McKenzie A Note on Protocol Synch
Sequences
528 NIC-17164 20 Jun 73 McQuillan Software Checksumming in the Imp
and Network Reliability
527 NIC-17163 25 Jun 73 Merryman ARPAWOCKY
526 NIC-17162 25 Jun 73 Pratt Technical Meeting-Digital Image
Processing Software Systems
525 NIC-17161 1 Jun 73 Parrish MIT-Mathlab Meets UCSB-OLS - An
Example of Resource Sharing
524 NIC-17140 13 Jun 73 White A Proposed Mail Protocol
523 NIC-17048 5 Jun 73 Bhushan SURVEY is in Operation Again
522 NIC-17033 5 Jun 73 McKenzie Traffic Statistics (May 1973)
521 NIC-16855 30 May 73 McKenzie Restricted Use of IMP DDT
520 NIC-16819 25 Jun 73 Day Memo to FTP Group (Proposal for
File Access Protocol)
519 NIC-16818 Jun 73 Pickens Resource Evaluation
518 NIC-16817 19 Jun 73 Vaughan ARPANET Accounts
517 Not Issued
516 NIC-16693 18 May 73 Postel Lost Message Detection
515 NIC-16446 6 Jun 73 Winter Specifications for Datalanguage,
Version 0/9
514 NIC-16445 5 Jun 73 Kantrowitz Network Make-Work
513 NIC-16444 30 May 73 Hathaway Comments on the New TELNET
Specifications
512 NIC-16443 25 May 73 Hathaway More on Lost Message Detection
511 NIC-16442 23 May 73 North Enterprise Phone Service to NIC
From ARPANET Sites
510 NIC-16400 30 May 73 White Request for Network Mailbox
Addresses
509 NIC-16294 7 May 73 McKenzie Traffic Statistics (April 1973)
508 NIC-16159 7 May 73 Pfeifer Real-Time Data Transmission on
the ARPANET
507 NIC-16158 (Not Issued)
506 NIC-16157 26 Jun 73 Padlipsky An FTP Command-Naming Problem
505 NIC-16156 25 Jun 73 Padlipsky Two Solutions to a File Transfer
Access Problem
504 NIC-16155 30 Apr 73 Thomas Distributed Resources Workshop
Announcement
503 NIC-15747 12 Apr 73 Neigus Socket Number List
502 Not Issued
501 NIC-15718 11 May 73 Pogran Un-Muddling "Free File Transfer"
500 NIC-15717 16 Apr 73 Shoshani The Integration of Data Management
Systems on a Computer Network
RFC NIC number Date Author Title (499:400)
--- --------- --------- ------ ---------------
499 NIC-11576 1 Apr 73 Reussow Harvard's Network RJE
498 NIC-15715 17 Apr 73 Braden On MAIL Service to CCN
497 NIC-15651 10 Apr 73 McKenzie Traffic Statistics (March 1973)
496 NIC-15496 5 Apr 73 Auerbach A TNLS Quick Reference Card is
Available
495 NIC-15371 1 May 73 McKenzie TELNET Protocol Specifications
495 NIC-15371 1 May 73 McKenzie TELNET Protocol Specifications
494 NIC-15359 20 Apr 73 Walden Availability of MIX and MIXAL in
the Network
493 NIC-15358 26 Apr 73 Michener Graphics Protocol
492 NIC-15357 18 Apr 73 Meyer Response to RFC 467
491 NIC-15356 12 Apr 73 Padlispsky What is "Free"?
490 NIC-15355 6 Mar 73 Pickens Surrogate RJS for UCLA-CCN
489 NIC-15298 26 Mar 73 Postel Comment on Resynchronization of
Connection Status Proposal
488 NIC-15266 23 Mar 73 Auerbach NLS Classes at Network Sites
487 NIC-15065 6 Apr 73 Bressler Free File Transfer
486 NIC-15064 20 Mar 73 Bressler Data Transfer Revisited
485 NIC-15063 19 Mar 73 Pickens Mix and Mixal at UCSB
484 Not Issued
483 NIC-15061 14 Mar 73 Kudlick Cancellation of the Resource
Notebook Framework Meeting
482 NIC-14966 12 Mar 73 McKenzie Traffic Statistics (February
1973)
481 Not Issued
480 NIC-14949 8 Mar 73 White Host-Dependent FTP Parameters
479 NIC-14948 8 Mar 73 White Use of FTP by the NIC Journal
478 NIC-14947 26 Mar 73 Bressler FTP Server-Server Interaction -
II
477 NIC-14922 23 May 73 Krilanovich Remote Job Service at UCSB
476 NIC-14920 7 Mar 73 McKenzie IMP/TIP Memory Retrofit Schedule
(Rev. 2)
475 NIC-14919 6 Mar 73 Bhushan FTP and Network Mail System
474 NIC-14905 Mar 73 Bunch Announcement of NGWG Meeting,
Call for Papers
473 NIC-14811 28 Feb 73 Walden MIX and MIXAL?
472 NIC-14801 Mar 73 Bunch Illinois' Reply to Maxwell's
Request for Graphics Information (NIC 14925)
471 NIC-14800 13 Mar 73 Thomas Workshop on Multi-Site Executive
Programs
470 NIC-14799 13 Mar 73 Thomas Change in Socket for TIP News
Facility
469 NIC-14798 8 Mar 73 Kudlick Network Mail Meeting Summary
468 NIC-14742 8 Mar 73 Braden FTP Data Compression
467 NIC-14741 20 Feb 73 Burchfiel Proposed Change to Host-Host
Protocol Resynchronization of Connection Status
466 NIC-14740 27 Feb 73 Winett TELNET Logger/Server for Host
LL-67
465 (not issued)
464 NIC-14738 27 Feb 73 Kudlick Resource Notebook Framework
463 NIC-14573 21 Feb 73 Bhushan FTP Comments and Response to RFC
430
462 NIC-14434 22 Feb 73 Iseli Responding to User Needs
461 NIC-14416 14 Feb 73 McKenzie TELNET Protocol Meeting
Announcement
460 NIC-14415 13 Feb 73 Kline NCP Survey
459 NIC-14379 26 Feb 73 Kantrowitz Network Questionnaires
458 NIC-14378 20 Feb 73 Bressler Mail Retrieval via FTP
457 NIC-14377 15 Feb 73 Walden TIPUG (Notes Distribution List)
456 NIC-14376 13 Feb 73 Kudlick Memorandum: (Date Change of Mail
Meeting)
455 NIC-14375 12 Feb 73 McKenzie Traffic Statistics (January 1973)
454 NIC-14333 16 Feb 73 McKenzie File Transfer Protocol - Meeting
Announcement and a New Proposed Document
453 NIC-14317 7 Feb 73 Kudlick Meeting Announcement to Discuss a
Network Mail System
452 NIC-14136 8 Feb 73 Winnett TELNET Command at Host LL
451 NIC-14135 22 Feb 73 Padlispsky Tentative Proposal for a Unified
User Level Protocol
450 NIC-14134 8 Feb 73 Padlipsky MULTICS Sampling Timeout Change
449 NIC-14133 6 Jan 73 Walden The Current Flow-Control Scheme
for IMPSYS (Updates 13774)
448 NIC-14132 27 Feb 73 Braden Print Files in FTP
447 NIC-14104 29 Jan 73 McKenzie IMP/TIP Memory Retrofit Schedule
446 NIC-14068 25 Jan 73 Deutsch Proposal to Consider a Network
Program Resource Notebook
445 NIC-14028 22 Jan 73 McKenzie IMP/TIP Preventive Maintenance
Schedule
444 Not Issued
443 NIC-13899 18 Jan 73 McKenzie Traffic Statistics (December 1972
442 NIC-13774 24 Jan 73 Cerf The Current Flow-Control Scheme
for IMPSYS
441 NIC-13773 19 Jan 73 Bressler Inter-Entity Communication - An
Experiment
440 NIC-13772 29 Jan 73 Walden Scheduled Network Software
Maintenance
439 NIC-13771 21 Jan 73 Cerf PARRY Encounters the DOCTOR
438 NIC-13770 15 Jan 73 Thomas FTP Server-Server Interaction
437 NIC-13701 30 Jun 73 Faeh Data Reconfiguration Service at
UCSB
436 NIC-13700 10 Jan 73 Krilanovich Announcement of RJS at UCSB
435 NIC-13675 5 Jan 73 Cosell TELNET Issues
434 NIC-13658 4 Jan 73 McKenzie IMP/TIP Memory Retrofit Schedule
433 NIC-13491 22 Dec 72 Postel Socket Number List
432 NIC-13490 29 Dec 72 Neigus Network Logical Map
431 NIC-13300 15 Dec 72 Krilanovich Update on SMFS Login and Logout
430 NIC-13299 7 Feb 73 Braden Comments on File Transfer
Protocol
429 NIC-13281 12 Dec 72 Postel Character Generator Process
428 Not Issued
427 Not Issued
426 NIC-13011 26 Jan 73 Thomas Reconnection Protocol
425 NIC-13010 19 Dec 72 Bressler "But My NCP Costs $500 a Day"
424 Not Issued
423 NIC-13008 12 Dec 72 Noble UCLA Campus Computing Network
Liaison Staff for ARPANET
422 NIC-13007 11 Dec 72 McKenzie Traffic Statistics (November
1972)
421 NIC-12897 27 Nov 72 McKenzie A Software Consulting Service for
Network Users
420 NIC-12764 4 Jan 73 Murray CCA ICCC Weather Demo
419 NIC-12763 12 Dec 72 Vezza To: Network Liaisons and Station
Agents
418 NIC-12762 27 Nov 72 Hathaway Server File Transfer Under
TSS/NIC-360 at NASA-AMES
417 NIC-12574 6 Nov 72 Postel Link Usage Violation
416 NIC-12542 7 Nov 72 Norton The ARC System Will Be
Unavailable for Use During Thanksgiving Week
415 NIC-12407 29 Nov 72 Murray TENEX Bandwidth
414 NIC-12406 29 Nov 72 Bhushan File Transfer Protocol (FTP)
Status and Further Comments (Updates 10596 and 11357)
413 NIC-12405 13 Nov 72 McKenzie Traffic Statistics (October 1972)
412 NIC-12404 27 Nov 72 Hicks User FTP Documentation
411 NIC-12403 14 Nov 72 Padlipsky New MULTICS Network Software
Features
410 NIC-12402 10 Nov 72 McQuillan Removal of the NIC-30-Second
Delay When Hosts Come Up
409 NIC-12401 6 Dec 72 White TENEX Interface to USCB's
Simple-Minded File System
408 NIC-12390 25 Oct 72 Owen NETBANK
407 NIC-12112 16 Oct 72 Bressler Remote Job Entry Protocol
406 NIC-12111 10 Oct 72 McQuillan Scheduled IMP Software Releases
405 NIC-12110 10 Oct 72 McKenzie Correction to RFC 404 (12068)
404 NIC-12068 5 Oct 72 McKenzie Host Address Changes Involving
RAND and ISI
403 NIC-11925 10 Jan 73 Hicks Desirability of a Network 1108
Service
402 NIC-11924 26 Oct 72 North ARPA Network Mailing Lists
401 NIC-11923 23 Oct 72 Hansen Conversion of NGP-O Coordinates
to Device Specific Co-ordinates
400 NIC-11922 18 Oct 72 McKenzie Traffic Statistics (Sept 1972)
RFC NIC number Date Author Title (399:300)
--- --------- --------- ------ ---------------
399 NIC-11917 26 Sep 72 Krilanovich SMFS Login and Logout
398 NIC-11911 22 Sep 72 Pickens ICP Sockets
397 Not Issued
396 NIC-11796 13 Nov 73 Bunch Network Graphics Working Group
Meeting - Second Iteration
395 NIC-11587 3 Oct 72 McQuillan Switch Settings on IMPS and TIPS
394 NIC-11586 27 Sep 72 McQuillan Two Proposed Changes to the
IMP-HOST Protocol
393 NIC-11585 3 Oct 72 Winett Comments on TELNET Protocol
Changes
392 NIC-11584 20 Sep 72 Hicks Measurement of Host Costs for
Transmitting Network Data
391 NIC-11583 15 Sep 72 McKenzie Traffic Statistics (August 1972)
(Updates 11120)
390 NIC-11582 12 Sep 72 Braden TSO Scenario
389 NIC-11361 30 Aug 72 Noble UCLA Campus Computing Network
Liaison Staff for ARPA Network (Updates 10264)
388 NIC-11360 23 Aug 72 Cerf NCP Statistics (Updates 9630)
387 NIC-11359 10 Aug 72 Kelley Some Experience in Implementing
Network Graphics Protocol Level O
386 NIC-11358 16 Aug 72 Cosell Letter to Tip Users -- 2
385 NIC-11357 18 Aug 72 Bhushan Comments on the File Transfer
Protocol (Updates RFC 354)
384 NIC-11356 28 Aug 72 North Official Site Idents for
Organization in the ARPA Network (Obsoletes 8295)
383 Not Issued
382 NIC-11122 3 Aug 72 McDaniel Mathematical Software on the ARPA
Network
381 NIC-11151 26 Jul 72 McQuillan Three Aids To Improved Network
Operation
380 Not Issued
379 NIC-11121 11 Aug 72 Braden Using TSO at CCN
378 NIC-11120 10 Aug 72 McKenzie Traffic Statistics (July 1972)
377 NIC-11119 10 Aug 72 Braden Using TSO via ARPA Network
Virtual Terminal
376 NIC-11118 8 Aug 72 Westheimer Network Host Status (Updates
11017)
375 Not Issued
374 NIC-11099 19 Jul 72 McKenzie IMP System Announcement
373 NIC-11058 14 Jul 72 McCarthy Arbitrary Character Sets
372 NIC-11022 12 Jul 72 Watson Notes on a Conversation with Bob
Kahn on the ICCC
371 NIC-11020 12 Jul 72 Kahn Demonstration at International
Computer Communications Conference
370 NIC-11017 31 Jul 72 Westheimer Network Host Status (Updates
11014)
369 NIC-11016 25 Jul 72 Pickens Evaluation of ARPANET Services
January - March, 1972
368 NIC-11015 21 Jul 72 Braden Comments on "Proposed Remote Job
Entry Protocol"
367 NIC-11014 19 Jul 72 Westheimer Network Host Status (Updates
11013)
366 NIC-11013 11 Jul 72 Westheimer Network Host Status (Updates
10604)
365 NIC-10607 11 Jul 72 Walden A Letter to All TIP Users
364 NIC-10606 11 Jul 72 Abrams Serving Remote Users on the
Arpanet
363 NIC-10605 8 Aug 72 NICSTA ARPA Network Mailing Lists
362 NIC-10604 28 Jun 72 Westheimer Network Host Status (Updates
10595)
361 NIC-10603 5 Jul 72 Bressler (Deamon Processes on Host 106)
360 NIC-10602 24 Jun 72 Holland Proposed Remote Job Entry
Protocol
359 NIC-10601 22 Jun 72 Walden The Status of the Release of the
new IMP System (2600)
358 Not Issued
357 NIC-10599 26 Jun 72 Davidson An Echoing Strategy For Satellite
Links
356 NIC-10598 21 Jun 72 Alter ARPA Network Control Center
355 NIC-10597 9 Jun 72 Davidson Response to NWG/RFC 346
354 NIC-10596 8 Jul 72 Bhushan The File Transfer Protocol
353 NIC-10595 12 Jun 72 Westheimer Network Host Status (Updated by
10604; Updates 10423)
352 NIC-10594 5 Jun 72 Crocker TIP Site Information Form
351 NIC-10593 5 Jun 72 Crocker Graphics Information form for the
ARPANET Graphics Resources Notebook
350 NIC-10549 18 May 72 Stoughton User Accounts for UCSB On-Line
System
349 NIC-10428 30 May 72 Postel Proposed Standard Socket Numbers
348 NIC-10427 30 May 72 Postel Discard Process
347 NIC-10426 30 May 72 Postel Echo Process
346 NIC-10425 30 May 72 Postel Satellite Considerations
345 NIC-10424 26 May 72 Kelley Interest in Mixed Integer
Programming (MPSX on NIC-360/91 at CCN)
344 NIC-10423 22 May 72 Westheimer Network Host Status (Updates
10421)
343 NIC-10422 19 May 72 McKenzie IMP System Change Notification
(Obsoletes 9924)
342 NIC-10421 15 May 72 Westheimer Network Host Status (Updates
9925; Updated by 10423)
341 Not Issued
340 NIC-9933 15 May 72 O'Sullivan Proposed TELNET Changes
339 NIC-9932 5 May 72 Thomas MLTNET - a "Multi-Telnet"
Subsystem for TENEX
338 NIC-9931 17 May 72 Braden EBCDIC/ASCII Mapping for Network
RJE
337 Not Issued
336 NIC-9929 5 May 72 Cotton Level O Graphic Input Protocol
335 NIC-9928 1 May 72 Bryan New Interface-IMP/360
334 NIC-9927 1 May 72 McKenzie Network Use on May 8
333 NIC-9926 15 May 72 Bressler A Proposed Experiment with a
Message Switching Protocol
332 NIC-9925 25 Apr 72 Westheimer Network Host Status (Updates
9923; Updated by 10421)
331 NIC-9924 19 Apr 72 McQuillan IMP System Change Notification
(Obsoleted by 10422)
330 NIC-9923 13 Apr 72 Westheimer Network Host Status (Updates
9633; Updated by 9925)
329 NIC-9636 17 May 72 NIC ARPA Network Mailing Lists
(Obsoletes 9075)
328 NIC-9635 29 Apr 72 Postel Suggested Telnet Protocol Changes
327 NIC-9634 27 Apr 72 Bhushan Data and File Transfer Workshop
Notes
326 NIC-9633 3 Apr 72 Westheimer Network Host Status (Updates
9349; Updated by 9923)
325 NIC-9632 6 Apr 72 Hicks Network Remote Job Entry Program
- NETRJS
324 NIC-9631 3 Apr 72 Postel RJE Protocol Meeting
323 NIC-9630 23 Mar 72 Cerf Formation of Network Measurement
Group (NMG)
322 NIC-9609 26 Mar 72 Cerf Well Known Socket Numbers
321 NIC-9608 24 Mar 72 Karp CBI Networking Activity at MITRE
320 NIC-9350 27 Mar 72 Reddy Workshop on Hard Copy Line
Printers
319 NIC-9349 21 Mar 72 Westheimer Network Host Status (Updates
9345)
318 NIC-9348 3 Apr 72 Postel (Obsoletes 6768)
317 NIC-9347 20 Mar 72 Postel Official HOST-HOST Protocol
Modification: Assigned Link Numbers
316 NIC-9346 24 Feb 72 McKay ARPA Network Data Management
Working Group
315 NIC-9345 8 Mar 72 Westheimer Network Host Status (Updates
9257; Updated by 9349)
314 NIC-9344 14 Mar 72 Cotton Network Graphics Working Group
Meeting
313 NIC-9343 6 Mar 72 O'Sullivan Computer Based Instruction
312 NIC-9342 22 Mar 72 McKenzie Proposed Change in IMP-to-Host
Protocol
311 NIC-9341 29 Feb 72 Bryan New Console Attachments to the
USCB Host
310 NIC-9261 3 Apr 72 Bhushan Another Look at Data and File
Transfer Protocols
309 NIC-9260 17 Mar 72 Bhushan Data and File Transfer Workshop
Announcement
308 NIC-9259 13 Mar 72 Seriff ARPANET Host Availability Data
307 NIC-9258 24 Feb 72 Harslem Using Network Remote Job Entry
306 NIC-9257 15 Feb 72 Westheimer Network Host Status (Updates
8486; Updated by 9345)
305 NIC-9078 23 Feb 72 Alter Unknown Host Numbers
304 NIC-9077 17 Feb 72 McKay A Data Management System Proposal
for the ARPA Network
303 NIC-9075 23 Feb 72 ARPA Network Mailing Lists
(Obsoletes 8488)
302 NIC-9074 8 Feb 72 Bryan Exercising the ARPANET
301 NIC-9073 11 Feb 72 Alter BBN IMP No. 5 and NCC Schedule
March 4, 1971
300 NIC-8488 25 Jan 72 North ARPA Network Mailing Lists
(Obsoleted by 9075)
RFC NIC number Date Author Title (299:200)
--- --------- --------- ------ ---------------
299 NIC-8487 11 Feb 72 Hopkin Information Management System
298 NIC-8486 1 Feb 72 Westheimer Network Host Status (Updates
8303)
297 NIC-8485 31 Jan 72 Walden TIP Message Buffers
296 NIC-8484 27 Jan 72 Liddle DS-1 Display System
295 NIC-8355 2 Jan 72 Postel Report of the Protocol Workshop,
12 October 1971
294 NIC-8304 25 Jan 72 Bhushan On the Use of "Set Data Type"
Transaction in File Transfer Protocol
293 NIC-8303 18 Jan 71 Westheimer Network Host Status (Updates
8274; 8273; 7815)
292 NIC-8302 12 Jan 72 Michener Graphics Protocol - Level O Only
291 NIC-8301 14 Jan 72 McKay Data Management Meeting
Announcement
290 NIC-8300 11 Jan 72 Mullery Computer Networks and Data
Sharing: A Bibliography (Updates 7673)
289 NIC-8295 21 Dec 71 Watson What We Hope is an Official List
of Host Names
288 NIC-8274 6 Jan 72 Westheimer Network Host Status (Updates
7815; 8273; Updated by 8303)
287 NIC-8273 22 Dec 71 Westheimer Status of Network Hosts (Updates
7815; Updated by 8303; 8274)
286 NIC-8272 21 Dec 71 Forman Network Library Information
System
285 NIC-8271 15 Dec 71 Huff Network Graphics
284 Not Issued
283 NIC-8165 20 Dec 71 Braden NETRJT -- Remote Job Service
Protocol for TIPS
282 NIC-8164 8 Dec 71 Padlispsky Graphics Meeting Report
281 NIC-8163 8 Dec 71 McKenzie A Suggested Addition to File
Transfer Protocol
280 NIC-8060 17 Nov 71 Watson A Draft of Host Names
279 Not Issued
278 NIC-8056 17 Nov 71 Bhushan Revision of the Mail Box Protocol
(Obsoletes 7612)
277 Not Issued
276 NIC-7936 8 Nov 71 Watson NIC Course
275 Not Issued
274 NIC-7901 1 Nov 71 Forman Establishing A Local Guide for
Network Usage
273 NIC-7837 18 Oct 71 Watson More on Standard Host Names
(Obsoletes 7662)
272 Not Issued
271 NIC-7819 3 Jan 72 Cosell IMP System Change Notifications
270 NIC-7818 1 Jan 72 McKenzie Correction to BBN Report No. 1822
(RFC7958) (Updates 7959)
269 NIC-7817 6 Dec 71 Brodie Some Experience with File
Transfer (Updates 5834; 6794; 7663)
268 NIC-7816 24 Nov 71 Postel Graphics Facilities Information
267 NIC-7815 22 Nov 71 Westheimer Network Host Status (Updates
7814; Updated by 8273; 8274; 8303)
266 NIC-7814 8 Nov 71 Westheimer Network Host Status (Updates
7696; Updated by 7815)
265 NIC-7813 17 Nov 71 Bhushan The File Transfer Protocol
264 NIC-7812 15 Nov 71 Bhushan The Data Transfer Protocol
(Obsoletes 6793)
263 NIC-7811 17 Dec 71 McKenzie "Very Distant" Host Interface
262 Not Issued
261 Not Issued
260 Not Issued
259 Not Issued
258 Not Issued
257 Not Issued
256 NIC-7697 3 Nov 71 Cosell IMPSYS Change Notification
255 NIC-7696 26 Oct 71 Westheimer Status of Network Hosts (Updates
7693; Updated by 7814)
254 NIC-7695 29 Oct 71 Bhushan Scenarios for Using ARPANET
Computers
253 NIC-7694 19 Oct 71 Moorer Second Network Graphics Meeting
Details
252 NIC-7693 8 Oct 71 Westheimer Network Host Status (Updates
7665; Updated by 7696)
251 NIC-7692 13 Oct 71 Stern Weather Data
250 NIC-7691 7 Oct 71 Brodie Some Thoughts of File Transfer
249 NIC-7690 8 Oct 71 Borelli Coordination of Equipment and
Supplies Purchase
248 Not Issued
247 NIC-7688 12 Oct 71 Karp Proffered Set of Standard Host
Names (Obsoletes 7625)
246 NIC-7687 5 Oct 71 Vezza Network Graphics Meeting
245 NIC-7675 5 Oct 71 Falls Reservations for Network Group
Meeting
244 Not Issued
243 NIC-7673 5 Oct 71 Mullery Network and Data Sharing
Bibliography (Updated by 8300)
242 NIC-7672 1 Jul 71 Haibt Data Descriptive Language for
Shared Data
241 NIC-7671 29 Sep 71 McKenzie Connecting Computers to MLC Ports
240 NIC-7665 30 Sep 71 McKenzie Site Status (Updated by 7693;
Obsoletes 7652)
239 NIC-7664 23 Sep 71 Braden Host Mnemonics Proposed in RFC
226 (NIC-7625)
238 NIC-7663 29 Sep 71 Braden Comments ON DTP and FTP Proposals
(Updates 6793; 6794; Updated by 7817)
237 NIC-7662 7 Oct 71 Watson The NIC View of Standard Host
Names (Obsoleted by 7837)
236 NIC-7661 27 Sep 71 Postel Standard Host Names (Obsoletes
7646)
235 NIC-7652 27 Sep 71 Westheimer Site Status (Obsoleted by 7665)
234 NIC-7651 5 Oct 71 Vezza Network Working Group Meeting
Schedule (Updates 7192; 7621)
233 NIC-7650 28 Sep 71 Bhushan Standardization of Host Call
Letters
232 NIC-7649 23 Sept 71 Vezza Postponement of Network Graphics
Meeting
231 NIC-7648 21 Sep 71 Heafner Service Center Standards for
Remote Usage--A User's View
230 NIC-7647 24 Sep 71 Pyke Toward Reliable Operation of
Minicomputer-Based Terminals on a TIP
229 NIC-7646 22 Sep 71 Postel Standard Host Names (Obsoleted by
7661)
228 NIC-7645 22 Sep 71 Walden Clarification (Updates 5413)
227 NIC-7631 17 Sep 71 Heafner Data Transfer Rates (RAND/UCLA)
(Updates 5820)
226 NIC-7625 20 Sep 71 Karp Standardization of Host Mnemonics
(Obsoleted by 7688)
225 NIC-7624 13 Sep 71 Harslem RAND/USCB Network Graphics
Experiment (Updates 5415)
224 NIC-7623 14 Sep 71 McKenzie Comments on Mailbox Protocol
223 NIC-7622 14 Sep 71 Melvin Network Information Center
Schedule for Network Users
222 NIC-7621 13 Sep 71 Metcalfe Subject: System Programmer's
Workshop (Updated by 7651)
221 NIC-7612 27 Aug 71 Watson A Mail Box Protocol, Version-2
(Obsoleted by 8056)
220 Not Issued
219 NIC-7549 3 Sep 71 Winter User's View of the Datacomputer
218 NIC-7548 8 Sep 71 Cosell Changing the IMP Status Reporting
Facility
217 NIC-7547 8 Sep 71 White Specifications Changes for OLS,
RJE/RJOR, and SMFS (Updates 5775; 5834)
216 NIC-7546 8 Sep 71 White TELNET Access to UCSB's On-Line
System
215 NIC-7545 30 Aug 71 McKenzie NCP, ICP, and TELNET: The
Terminal IMP Implementation
214 NIC-7195 21 Aug 71 Harslem Network Checkpoint (Obsoletes
7138; 7149)
213 NIC-7194 20 Aug 71 Cosell IMP System Change Notification
212 NIC-7192 23 Aug 71 Committee NWG Meeting on Network Usage
(Updates 7178; Updated by 7651)
211 NIC-7191 18 Aug 71 North ARPA Network Mailing Lists
(Updated by 8488; Obsoletes 6785)
210 NIC-7189 16 Aug 71 Conrad Improvement of Flow Control
209 NIC-7187 13 Aug 71 Cosell Host/Imp Interface Documentation
208 NIC-7181 9 Aug 71 McKenzie Address Tables
207 NIC-7178 9 Aug 71 Vezza A September Network Working Group
Meeting (Updated by 7192)
206 NIC-7176 9 Aug 71 White A User Telnet - Description of an
Initial Implementation
205 NIC-7172 6 Aug 71 Braden NETCRT - A Character Display
Protocol
204 NIC-7196 5 Aug 71 Postel Sockets in Use
203 NIC-7168 10 AUg 71 Kalin Achieving Reliable Communication
202 NIC-7155 26 Jul 71 Wolfe Possible Deadlock in ICP
201 Not Issued
200 NIC-7152 1 Aug 71 North RFC List by Number (Obsoleted by
7724)
RFC NIC number Date Author Title (199:100)
--- --------- --------- ------ ---------------
199 NIC-7151 15 Jul 71 Williams Suggestions for a Network
Data-Tablet Graphics Protocol
198 NIC-7149 20 Jul 71 Heafner Site Certification - Lincoln Labs
NIC-360/67 (Obsoleted by 7195)
197 NIC-7142 14 Jul 71 Shoshani Initial Connection
Protocol-Reviewed
196 NIC-7141 20 Jul 71 Watson A Mail Box Protocol (Obsoleted by
7612)
195 NIC-7140 16 Jul 71 Mealy Data Computers--Data Descriptions
and Access Language
194 NIC-7139 Jul 71 Cerf The Data Reconfiguration Service -
Compiler/Interpreter Implementation Notes
193 NIC-7138 14 Jul 71 Harslem Network Checkout (Obsoleted by
7195)
192 NIC-7137 12 Jul 71 Watson Some Factors Which a Network
Graphics Protocol Must Consider
191 NIC-7136 13 Jul 71 Irby Graphics Implementation and
Conceptualization at ARC
190 NIC-7135 13 Jul 71 Deutsch DEC PDP-10 -- IMLAC Communications
System
189 NIC-7133 15 Jul 71 Braden Interim NETRJS Specifications
(Obsoletes 5668)
188 NIC-7132 28 Jul 71 Karp Data Management Meeting
Announcement
187 NIC-7131 Jul 71 McKay A Network/440 Protocol Concept
186 NIC-7130 12 Jul 71 Michener A Network Graphics Loader
185 NIC-7129 7 Jul 71 North NIC Distribution of Manuals and
Handbooks
184 NIC-7128 6 Jul 71 Kelley Proposed Graphic Display Modes
183 NIC-7127 21 Jul 71 Winett The EBCDIC Codes and Their Mapping
to ASCII
182 NIC-7126 25 Jun 71 North Compilation of List of Relevant
Site Reports
181 NIC-7124 27 Jun 71 McConnell Modifications to RFC 177 (Updates
7102)
180 NIC-7123 25 Jun 71 McKenzie File System Questionaire
179 NIC-7119 22 Jun 71 McKenzie Link Number Assignments (Updates
5806)
178 NIC-7118 27 Jun 71 Cotton Network Graphic Attention Handling
177 NIC-7102 15 Jun 71 McConnell A Device Independent Graphical
Display Description
176 NIC-7100 14 Jun 71 Bhushan Comments on Byte Size for
Connections
175 NIC-7074 11 Jun 71 Harslem Comments on "Socket Conventions
Reconsidered"
174 NIC-6799 8 Jun 71 Postel UCLA-Computer Science Graphics
Overview
173 NIC-6795 4 Jun 71 Karp Network Data Management Committee
Meeting Announcement
172 NIC-6794 23 Jun 71 Bhushan The File Tranfer Protocol
(Obsoleted by 7813)
171 NIC-6793 23 Jun 71 hushan The Data Transfer Protocol
(Obsoleted by 7812)
170 NIC-6790 1 Jun 71 NIC RFC List by Number (Updates 6771;
Updated by 7152)
169 NIC-6789 27 May 71 Crocker Computer Networks
168 NIC-6785 26 May 71 North ARPA Network Mailing Lists
(Obsoleted by 7191)
167 NIC-6784 24 May 71 Bhushan Socket Conventions Reconsidered
166 NIC-6780 25 May 71 Anderson Data Reconfiguration Service -- An
Implementation Specification
165 NIC-6779 25 May 71 Postel A Proffered Official Initial
Connection Protocol (Obsoletes 5837; 6728; 6739)
164 NIC-6778 25 May 71 Heafner Minutes of Network Working Group
Meeting, 5/16 through 5/19/71
163 NIC-6775 19 May 71 Cerf Data Transfer Protocols
162 NIC-6774 22 May 71 Kampe NETBUGGER3
161 NIC-6772 19 May 71 Shoshani A Solution to the Race Condition
in the ICP
160 NIC-6771 18 May 71 NIC RFC Brief List (Updated by 6790;
7152; Updates 6716)
159 Not Issued
158 NIC-6768 19 May 71 O'Sullivan Telnet Protocol -- A Proposed
Document
157 NIC-6762 12 May 71 Cerf Invitation to the Second Symposium
on Problems in the Optimization of Data Communications Systems
156 NIC-6761 26 Apr 71 Bouknight Status of the Illinois Site
(Response to RFC 116)
155 NIC-6760 May 71 North ARPA Network Mailing Lists
(Obsoleted by 6785)
154 NIC-6759 12 May 71 Crocker Exposition Style (Obsoletes 6708;
Updates 5806)
153 NIC-6758 15 May 71 Melvin SRI-ARC-NIC Status
152 NIC-6756 10 May 71 Wilber SRI Artificial Intelligence Status
Report
151 NIC-6755 10 May 71 Shoshani Comments on a Proffered Official
ICP (RFCS 123, 127)
150 NIC-6754 5 May 71 Kalin The Use of IPG Facilities - A
Working Paper
149 NIC-6752 10 May 71 Crocker The Best Laid Plans (Updates 6725)
148 NIC-6751 7 May 71 Bhushan Comments on RFC 123
147 NIC-6750 7 May 71 Winett The Definition of a Socket
(Updates 5845)
146 NIC-6742 12 May 71 Karp Views On Issues Relevant to Data
Sharing on Computer Networks
145 NIC-6739 4 May 71 Postel Initial Connection Protocol
Control Commands (Obsoleted by 6779)
144 NIC-6729 30 Apr 71 Shoshani Data Sharing on Computer Networks
143 NIC-6728 3 May 71 Naylor Regarding Proffered Official ICP
(Obsoleted by 6779)
142 NIC-6727 3 May 71 Kline Time-Out Mechanism in the
Host-Host Protocol
141 NIC-6726 29 Apr 71 Harslem Comments on RFC 114 (A File
Transfer Protocol)
140 NIC-6725 4 May 71 Crocker Agenda for the May NWG Meeting
(Updated by 6725)
139 NIC-6717 7 May 71 O'Sullivan Discussion of TELNET Protocol
(Updates 6717)
138 NIC-6715 28 Apr 71 Anderson Status Report on Proposed Data
Reconfiguration Service
137 NIC-6714 30 Apr 71 O'Sullivan Telnet Protocol -- A Proposed
Document (Obsoletes 6783)
137 NIC-6783 8 May 71 O'Sullivan Telnet Protocol -- A Proposed
Document (Obsoleted by 6714)
136 NIC-6713 29 Apr 71 Kahn Host Accounting and Administrative
Procedures
135 NIC-6712 29 Apr 71 Hathaway Response to NWG/RFC 110 (Updates
5809)
134 NIC-6711 29 Apr 71 Vezza Network Graphics Meeting
133 NIC-6710 27 Apr 71 Sundberg File Transfer and Recovery
132 NIC-6708 8 Apr 71 White Typographical Error in RFC 107
(Obsoleted by 6759)
131 NIC-5849 22 Apr 71 Harslem Response to RFC 116 (May NWG
Meeting)
130 NIC-5848 22 Apr 71 Heafner Response to RFC 111 (Pressure from
the Chairman)
129 NIC-5845 22 Apr 71 Harslem A Request for Comments on Socket
Name Structure (Updated by 6750)
128 NIC-5844 21 Apr 71 Postel Bytes
127 NIC-5843 20 Apr 71 Postel Comments on RFC 123 (Obsoleted by
6739)
126 NIC-5842 18 Apr 71 McConnell Graphics Facilities at Ames
Research Center
125 NIC-5841 18 Apr 71 McConnell Response to RFC 86, Proposal for
Network Standard Format for a Graphics Data Stream
124 NIC-5840 19 Apr 71 Melvin Typographical Error in RFC 107
(Updates 5806)
123 NIC-5837 20 Apr 71 Crocker A Proffered Official ICP
(Obsoleted by 6779)
122 NIC-5834 26 Apr 71 White Network Specifications for UCSB's
Simple-Minded File System
121 NIC-5833 21 Apr 71 Krilanovich Network On-Line Operators
120 NIC-5832 21 Apr 71 Krilanovich Network PL1 Subprograms
119 NIC-5831 21 Apr 71 Krilanovich Network Fortran Subprograms
118 NIC-5830 16 Apr 71 Watson Recommendations for Facility
Documentation
117 NIC-5826 7 Apr 71 Wong Some Comments on the Official
Protocol
116 NIC-5825 12 Apr 71 Crocker Structure of the May NWG Meeting
(Updates 5758)
115 NIC-5822 16 Apr 71 Watson Some Network Information Center
Policies on Handling Documents
114 NIC-5823 16 Apr 71 Bhushan A File Transfer Protocol (Updated
by 6794; 6793)
113 NIC-5820 5 Apr 71 Harslem Network Activity Report,
UCSB--RAND (Updated by 7631)
112 NIC-5816 1 Apr 71 O'Sullivan User/Server Site Protocol; Network
Host Questionnaire Responses
111 NIC-5815 31 Mar 71 Crocker Pressure from the Chairman
(Updates 5806)
110 NIC-5809 25 Mar 71 Winett Conventions for Using an IBM 2741
Terminal as a User Console for Access to Network Server Hosts
109 NIC-5808 24 Mar 71 Winett Level III Server Protocol for the
Lincoln Laboratory NIC-360/67 Host
108 NIC-5807 25 Mar 71 Watson Attendance List at the Urbana NWG
Meeting, February 17-19, 1971 (Updates 5762)
107 NIC-5806 23 Mar 71 Bressler Output of the Host-Host Protocol
Glitch Cleaning Committee (Obsoleted by 7147)
106 NIC-5776 3 Mar 71 O'Sullivan User/Server Site Protocol Network
Host Questionnaire
105 NIC-5775 22 Mar 71 White Network Specifications for Remote
Job Entry and Remote Job Output Retrieval at UCSB
104 NIC-5768 25 Feb 71 Postel Link 191
103 NIC-5764 24 Feb 71 Kalin Implementation of Interrupt Keys
102 NIC-5763 23 Feb 71 Crocker Output of the Host/Host Protocol
Glitch Cleaning Committee (Obsoleted by 5806)
101 NIC-5762 23 Feb 71 Watson Notes on the Network Working Group
Meeting (Urbana, Illinois, February 17, 1971
100 NIC-5761 26 Feb 71 Karp Categorization and Guide to
NWG/RFCS
RFC NIC number Date Author Title (099:000)
--- --------- --------- ------ ---------------
099 NIC-5758 22 Feb 71 Karp Network Meeting (Updated by 5825)
098 NIC-5744 11 Feb 71 Meyer Logger Protocol Proposal (Updated
by 5837)
097 NIC-5740 15 Feb 71 Melvin A First Cut at a Proposed Telnet
Protocol
096 NIC-5739 12 Feb 71 Watson An Interactive Network Experiment
to Study Modes of Access to the Network Information Center
095 NIC-5731 4 Feb 71 Crocker Distribution of NWG/RFC's through
The NIC (Obsoleted by 6785)
094 NIC-5725 3 Feb 71 Harslem Some Thoughts on Network Graphics
093 NIC-5721 27 Jan 71 McKenzie Initial Connection Protocol
092 Not Issued
091 NIC-5708 27 Dec 70 Mealy A Proposed USER-USER Protocol
090 NIC-5707 25 Jan 71 Braden CCN as a Network Service Center
089 NIC-5697 19 Jan 71 Metcalfe Some Historic Moments in
Networking
088 NIC-5668 13 Jan 71 Braden NETRJS--A Third Level Protocol for
Remote Job Entry (Obsoleted by 7133)
087 NIC-5632 12 Jan 71 Vezza Topic for Discussion at the next
Network Working Group Meeting
086 NIC-5631 5 Jan 71 Crocker Proposal For a Network Standard
Format For a Data Stream to Control Graphics Display
085 NIC-5624 28 Dec 70 Crocker Network Working Group Meeting
084 NIC-5620 23 Dec 70 North List of NWG/RFC's 1-80
083 NIC-5621 18 Dec 70 Anderson Language-Machine for Data
Reconfiguration
082 NIC-5619 9 Dec 70 Meyer Network Meeting Notes
081 NIC-5609 3 Dec 70 Bouknight Request for Reference Information
080 NIC-5608 1 Dec 70 Harslem Protocols and Data Formats
(Obsoleted by 5837)
079 NIC-5601 16 Nov 70 Meyer Logger Protocol Error
078 NIC-5199 Nov 70 Harslem NCP Status Report: UCSB/RAND
077 NIC-5604 20 Nov 70 Postel Network Meeting Report
076 undated Grossman Syntax and Semantics for the
Terminal User Control Language for the Proposed PDP-11 ARPA Network
Terminal System
075 NIC-5418 14 Oct 70 Crocker Network Meeting
074 NIC-5417 16 Oct 70 White Specifications for Network Use of
The UCSB On-Line System
073 NIC-5416 25 Sep 70 Crocker Response to NWG/RFC 67
072 NIC-5415 28 Sep 70 Bressler Proposed Moratorium on Changes to
Network Protocol (Updated by 7624)
071 NIC-5414 25 Sep 70 Schipper Reallocation in Case of Input
Error
070 NIC-5413 15 Oct 70 Crocker A Note on Padding (Updated by
7645)
069 NIC-5412 22 Sep 70 Bhushan Distribution List Change for MIT
(Updates 4753)
068 NIC-5411 31 Aug 70 Elie Comments on Memory Allocation
Control Commands (CEASE, ALL, GVB, RET) and RFNM
067 NIC-5410 undated Crowther Proposed Change to Host/IMP Spec
to Eliminate Marking
066 NIC-5409 26 Aug 70 Crocker NIC-3rd Level Ideas and Other
Noise (Obsoleted by 5837)
065 NIC-4965 29 Aug 70 Walden Comments on Host-Host Protocol
Document No. 1 (by S. Crocker - 8/3/70)
064 NIC-4964 undated Elie Getting Rid of Marking
063 NIC-4963 31 Jul 70 Cerf Related Network Meeting Report
062 NIC-4962 3 Aug 70 Walden A Note on Interprocess
Communication in a Resource Sharing Computer Network (Updates 4961)
061 NIC-4961 17 Jul 70 Walden A Note on Interprocess
Communication in a Resource Sharing Computer Network
060 NIC-4762 13 Jul 70 Kalin A Simplified NCP Protocol
059 NIC-4761 27 Jun 70 Meyer Flow Control - Fixed Versus Demand
Allocation
058 NIC-4760 26 Jun 70 Skinner Logical Message Synchronization
057 NIC-4759 19 Jun 70 Kraley Thoughts and Reflections on
NWG/RFC 54
056 NIC-4758 Jun 70 Belove Third Level Protocol, Logger
Protocol
055 NIC-4757 19 Jun 70 Newkirk A Prototypical Implementation of
the NCP
054 NIC-4756 18 Jun 70 Crocker An Official Protocol Proffering
053 NIC-4755 9 Jun 70 Crocker An Official Protocol Mechanism
052 NIC-4753 1 Jul 70 Postel Updated Distribution List (Updated
by 5412)
051 NIC-4752 4 May 70 Elie Proposal for a Network Interchange
Language
050 NIC-4751 30 Apr 70 Harslem Comments on the Meyer Proposal
049 NIC-4728 25 Apr 70 Meyer Conversations with Steve Crocker
(UCLA)
048 NIC-4750 21 Apr 70 Postel A Possible Protocol Plateau
047 NIC-4749 20 Apr 70 Postel BBN's Comments on NWG/RFC 33
046 NIC-4748 17 Apr 70 Meyer ARPA Network Protocol Notes
045 NIC-4747 14 Apr 70 Postel NEW Protocol is Coming
044 NIC-4746 10 Apr 70 Shoshani Comments on NWG/RFC 33 and 36
043 NIC-4745 8 Apr 70 Nemeth Proposed Meeting
042 NIC-4744 31 Mar 70 Ancona Message Data Types
041 NIC-4743 30 Mar 70 Melvin IMP-IMP Teletype Communication
040 NIC-4742 27 Mar 70 Harslem More Comments on the Forthcoming
Protocol
039 NIC-4741 25 Mar 70 Harslem Comments on Protocol Re: NWG/RFC
NIC-36 (Updates 4738)
038 NIC-4740 20 Mar 70 Wolfe Comments on Network Protocol from
NWG/RFC NIC-36
037 NIC-4739 20 Mar 70 Crocker Network Meeting Epilogue, etc.
036 NIC-4738 16 Mar 70 Crocker Protocol Notes (Updates 4735;
Updated by 4741)
035 NIC-4737 3 Mar 70 Crocker Network Meeting
034 NIC-4736 26 Feb 70 English Some Brief Preliminary Notes on
the ARC Clock
033 NIC-4735 12 Feb 70 Crocker New HOST-HOST Protocol (Updates
4718; Updated by 4738)
032 NIC-4734 31 Jan 69 Vedder Connecting M.I.T. Computers to the
ARPA Computer-To-Computer Communication Network
031 NIC-4733 Feb 68 Bobrow Binary Message Forms in Computer
Networks
030 NIC-4732 4 Feb 70 Crocker Documentation Conventions (Updates
4696; 4719; 4726; 4729)
029 NIC-4731 19 Jan 70 Kahn Note in Response to Bill English's
Request for Comments
028 NIC-4730 13 Jan 70 English Time Standards
027 NIC-4729 9 Dec 69 Crocker Documentation Conventions (Updates
4696; 4719; 4726; Updated by 4732)
026 Not Issued
025 NIC-4727 30 Oct 69 Crocker No High Link Numbers
024 NIC-4726 21 Nov 69 Crocker Documentation Conventions (Updates
4696; 4719; Updated by 4729; 4732)
023 NIC-4725 16 Oct 69 Gregg Transmission of Multiple Control
Messages
022 NIC-4724 17 Oct 69 Cerf HOST-HOST Control Message Formats
(Updates 4718)
021 NIC-4723 17 Oct 69 Cerf Report of Network Meeting
020 NIC-4722 16 Oct 69 Cerf ASCII Format for Network
Interchange
019 NIC-4721 7 Oct 69 Kreznar Two Protocol Suggestions to Reduce
Congestion at Swap-Bound Nodes
018 NIC-4720 Sep 69 Cerf Use of Links 1 and 2
017 NIC-4699 27 Aug 69 Kreznar Some Questions Re: HOST-IMP
Protocol
016 NIC-4719 27 Aug 69 Crocker M.I.T. (Address) (Updated by 4726;
4729; 4732)
015 NIC-4754 25 Sep 69 Carr Network Subsystem for Time-Sharing
Hosts
014 Not Issued
013 NIC-4698 20 Aug 69 Cerf Referring to NWG/RFC 11
012 NIC-4697 26 Aug 69 Wingfield Imp-Host Interface Flow Diagrams
011 NIC-4718 1 Aug 69 Deloche Implementation of the HOST-HOST
Software Procedures in Gordo
010 NIC-4696 29 Jul 69 Crocker Documentation Conventions
(Obsoletes 4689; Updated by 4726; 4729; 4732)
009 NIC-4695 1 May 69 Deloche Host Software
008 NIC-4694 5 May 69 Deloche ARPA Network Functional
Specifications
007 NIC-4693 May 69 Deloche Host-Imp Interface
006 NIC-4692 10 Apr 69 Crocker Conversation with Bob Kahn
005 NIC-4691 2 Jun 69 Rulifson DEL
004 NIC-4690 24 Mar 69 Shapiro Network Timetable
003 NIC-4689 9 Apr 69 Crocker Documentation Conventions
(Obsoleted by 4696)
002 NIC-4688 9 Apr 69 Duvall Host Software
001 NIC-4687 7 Apr 69 Crocker Host Software