RFC Abstracts

RFC0671
Experience with implementation in RSEXEC context.
RFC0669
An earlier poll of Telnet server implementation status. Updates RFC 702; see also RFCs 703 and 679.
RFC0667
Approved scheme to connect host ports to the network.
RFC0666
Discusses and proposes a common command language.
RFC0663
Proposed extension of host-host protocol; see also RFCs 534, 516, 512, 492 and 467.
RFC0662
Experimenting with host output buffers to improve throughput.
RFC0661
An old version; see RFC 694.
RFC0660
Decoupling of message number sequences of hosts; host-host access control; message number window; messages outside normal mechanism; see also BBN 1822.
RFC0659
Options defined in RFCs 651-658.
RFC0647
Approaches to Front-End protocol processing using available hardware and software.
RFC0645
Providing a mechanism for specifying all attributes of a collection of bits; see also RFC 615.
RFC0643
To be used in an implementation of a PDP-11 network bootstrap device and a cross-network debugger.
RFC0640
Updates RFC 542.
RFC0638
Corrects RFC 633.
RFC0636
Obtaining/maintaining connections; recovery from lost connections; connection-state changes.
RFC0635
Theoretical and practical motivation for redesign. Multipacket messages; host retransmission; duplicate detection; sequencing; acknowledgement.
RFC0633
An old version; see RFC 638.
RFC0630
Describes FTP reply-code usage in TENEX mail processing.
RFC0627
See also RFCs 606, 608, 623 and 625.
RFC0625
See also RFCs 606, 608, 623 and 627.
RFC0624
Design changes and slight modifications. Replaces RFC 607; see also RFCs 614, 542 and 640.
RFC0623
See also RFCs 627, 625, 608 and 606.
RFC0622
Modification of previous policy.
RFC0621
See also RFCs 620 and 609.
RFC0620
In conjunction with moving NIC users to OFFICE-1; see also RFCs 621 and 609.
RFC0619
Actual measurements of round-trip times.
RFC0618
Distribution of NCP and IMP message types by actual measurement.
RFC0617
Danger of imposing more fixed socket number requirements; see also RFCs 542, 503 and 451.
RFC0614
See also RFCs 624, 542 and 640.
RFC0611
Expansion of Host-Going-Down and addition of Dead-Host-Status Message.
RFC0610
Preliminary results of the language design; a model for data languagea semantics; future considerations.
RFC0609
See also RFCs 621 and 620.
RFC0608
Response to RFC 606; see also RFCs 627, 625 and 623.
RFC0607
An old version; see RFC 624; see also RFCs 614, 542 and 640.
RFC0606
Resolving differences in hostname-address mappings; see also RFCs 627, 625, 623 and 608.
RFC0604
Modifies official host-host protocol. Replaces RFC 377.
RFC0603
Questions about the ARPANET topology described in RFC 597.
RFC0602
Susceptibility of ARPANET to security violations.
RFC0600
Discusses some unusual interface issues for the Plato terminal.