Discusses some unusual interface issues for the Plato terminal.
Susceptibility of ARPANET to security violations.
Questions about the ARPANET topology described in RFC 597.
Modifies official host-host protocol. Replaces RFC 377.
Resolving differences in hostname-address mappings; see also RFCs 627, 625, 623 and 608.
An old version; see RFC 624; see also RFCs 614, 542 and 640.
Response to RFC 606; see also RFCs 627, 625 and 623.
See also RFCs 621 and 620.
Preliminary results of the language design; a model for data languagea semantics; future considerations.
Expansion of Host-Going-Down and addition of Dead-Host-Status Message.
See also RFCs 624, 542 and 640.
Danger of imposing more fixed socket number requirements; see also RFCs 542, 503 and 451.
Distribution of NCP and IMP message types by actual measurement.
Actual measurements of round-trip times.
In conjunction with moving NIC users to OFFICE-1; see also RFCs 621 and 609.
See also RFCs 620 and 609.
Modification of previous policy.
See also RFCs 627, 625, 608 and 606.
Design changes and slight modifications. Replaces RFC 607; see also RFCs 614, 542 and 640.
See also RFCs 606, 608, 623 and 627.
See also RFCs 606, 608, 623 and 625.
Describes FTP reply-code usage in TENEX mail processing.
An old version; see RFC 638.
Theoretical and practical motivation for redesign. Multipacket messages; host retransmission; duplicate detection; sequencing; acknowledgement.
Obtaining/maintaining connections; recovery from lost connections; connection-state changes.
Corrects RFC 633.
Updates RFC 542.
To be used in an implementation of a PDP-11 network bootstrap device and a cross-network debugger.
Providing a mechanism for specifying all attributes of a collection of bits; see also RFC 615.
Approaches to Front-End protocol processing using available hardware and software.
Options defined in RFCs 651-658.
Decoupling of message number sequences of hosts; host-host access control; message number window; messages outside normal mechanism; see also BBN 1822.
An old version; see RFC 694.
Experimenting with host output buffers to improve throughput.
Proposed extension of host-host protocol; see also RFCs 534, 516, 512, 492 and 467.
Discusses and proposes a common command language.
Approved scheme to connect host ports to the network.
An earlier poll of Telnet server implementation status. Updates RFC 702; see also RFCs 703 and 679.
Experience with implementation in RSEXEC context.
Applicability of TIP/TENEX protocols beyond TIP accounting.
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.
The first detailed specification of TCP; see RFC 793.
For transmission of documents across different environments.
An earlier poll of Telnet server implementation status. Updates RFCs 701, 702 and 669; see also RFC 703.
Extends message field definition beyond RFC 561 attempts to establish syntactic and semantic standards for ARPANET; see also RFCs 733 and 822.
Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP, Hardware/Software requirements, reliability, availability.
Defines an extension to FTP for page-mode transfers between TENEX systems; also discusses file transfer reliability.
Issues in designing distributed computing systems. Shortcomings of RFC 674; see also RFCs 542 and 354.
The contribution of ARPANET communication to response time.
Discusses difference between early and later versions of FTP; see also RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354.
Addressing hosts on more than 63 IMPs, and other backwards compatible expansions; see also RFCs 690 and 692.
Describes the internal states of an NCP connection in the TENEX implementation.
Comments on suggestions in RFC 687; see also RFCs 692 and 696.
Slight revision of RFC 686, on the subject of print files; see also RFCs 640, 630, 542, 454, 448, 414, 385 and 354.
A proposed solution to the problem of combined length of IMP and Host leaders; see also RFCs 696, 690 and 687.
References to documents and contacts concerning the various protocols used in the ARPANET, as well as recent developments; updates RFC 661.
Corrects ambiguity concerning the ERR command; changes NIC 8246 and NIC 7104.
Observations on current international standards recommendations from IFIP working group 6.1; see also RFCs 692, 690 687.
Discusses FTP login access to "files only" directories.
Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs.