


default search action
Request for Comments (RFC) 600-699
1973
600Arthur Berggreen:
Interfacing an Illinois plasma terminal to the ARPANET. 1-3
601Alex M. McKenzie:
Traffic statistics (November 1973). 1-5
602Robert M. Metcalfe:
"The stockings were hung by the chimney with care". 1
603Jerry D. Burchfiel:
Response to RFC 597: Host status. 1
604Jon Postel:
Assigned link numbers. 1-2
606L. Peter Deutsch:
Host names on-line. 1-3
1974
607Mark Krilanovich, George Gregg:
Comments on the File Transfer Protocol. 1-3
608Michael D. Kudlick:
Host names on-line. 1-4
609Bill Ferguson:
Statement of upcoming move of NIC/NLS service. 1-2
1973
610Richard Winter, Jeffrey Hill, Warren Greiff:
Further datalanguage design concepts. 1-88
1974
611David C. Walden:
Two changes to the IMP/Host Protocol to improve user/network communications. 1-4
612Alex M. McKenzie:
Traffic statistics (December 1973). 1-6
613Alex M. McKenzie:
Network connectivity: A response to RFC 603. 1
614Kenneth T. Pogran, Nancy Neigus:
Response to RFC 607: "Comments on the File Transfer Protocol". 1-3
615Dave Crocker:
Proposed Network Standard Data Pathname syntax. 1-4
1973
616Dave Walden:
Latest Network Maps. 1
1974
617Edward A. Taft:
Note on socket number assignment. 1-3
618Edward A. Taft:
Few observations on NCP statistics. 1-3
619William E. Naylor, Holger Opderbeck:
Mean round-trip times in the ARPANET. 1-14
620Bill Ferguson:
Request for monitor host table updates. 1
621Michael D. Kudlick:
NIC user directories at SRI ARC. 1
622Alex M. McKenzie:
Scheduling IMP/TIP down time. 1-3
623Mark Krilanovich:
Comments on on-line host name service. 1-2
624Mark Krilanovich, George Gregg, Wayne Hathaway, James E. White:
Comments on the File Transfer Protocol. 1-3
625Michael D. Kudlick, Elizabeth J. Feinler:
On-line hostnames service. 1
626Leonard Kleinrock, Holger Opderbeck:
On a possible lockup condition in IMP subnet due to message sequencing. 1-5
627Michael D. Kudlick, Elizabeth J. Feinler:
ASCII text file of hostnames. 1
628Marcia L. Keeney:
Status of RFC numbers and a note on pre-assigned journal numbers. 1
629Jeanne B. North:
Scenario for using the Network Journal. 1-3
630Julie Sussman:
FTP error code usage for more reliable mail service. 1-3
631André A. S. Danthine:
International meeting on minicomputers and data communication: Call for papers. 1-2
632Holger Opderbeck:
Throughput degradations for single packet messages. 1-6
633Alex M. McKenzie:
IMP/TIP preventive maintenance schedule. 1-4
634Alex M. McKenzie:
Change in network address for Haskins Lab. 1
635Vint Cerf:
Assessment of ARPANET protocols. 1
636Jerry D. Burchfiel, Bernie Cosell, Raymond S. Tomlinson, David C. Walden:
TIP/Tenex reliability improvements. 1-8
637Alex M. McKenzie:
Change of network address for SU-DSL. 1
638Alex M. McKenzie:
IMP/TIP preventive maintenance schedule. 1-4
640Jon Postel:
Revised FTP reply codes. 1-17
642Jerry D. Burchfiel:
Ready line philosophy and implementation. 1-4
643Eric Mader:
Network Debugging Protocol. 1-7
644Robert Thomas:
On the problem of signature authentication for network mail. 1-3
645Dave Crocker:
Network Standard Data Specification syntax. 1-9
647Michael A. Padlipsky:
Proposed protocol for connecting host computers to ARPA-like networks via front end processors. 1-20
651Dave Crocker:
Revised Telnet status option. 1-2
652Dave Crocker:
Telnet output carriage-return disposition option. 1-4
653Dave Crocker:
Telnet output horizontal tabstops option. 1
654Dave Crocker:
Telnet output horizontal tab disposition option. 1
655Dave Crocker:
Telnet output formfeed disposition option. 1
656Dave Crocker:
Telnet output vertical tabstops option. 1
657Dave Crocker:
Telnet output vertical tab disposition option. 1
658Dave Crocker:
Telnet output linefeed disposition. 1-2
659Jon Postel:
Announcing additional Telnet options. 1
660David C. Walden:
Some changes to the IMP and the IMP/Host interface. 1
661Jon Postel:
Protocol information. 1-21
662Raj Kanodia:
Performance improvement in ARPANET file transfers from Multics. 1-2
663Raj Kanodia:
Lost message detection and recovery protocol. 1-22
666Michael A. Padlipsky:
Specification of the Unified User-Level Protocol. 1-19
667Steve G. Chipman:
Host Ports. 1-2
669D. W. Dodds:
November, 1974, survey of New-Protocol Telnet servers. 1-3
671Richard E. Schantz:
Note on Reconnection Protocol. 1-9
672Richard E. Schantz:
Multi-site data collection facility. 1-9
674Jon Postel, James E. White:
Procedure call documents: Version 2. 1-6
675Vint Cerf, Yogen K. Dalal, Carl A. Sunshine:
Specification of Internet Transmission Control Program. 1-70
1975
677Paul R. Johnson, Robert Thomas:
Maintenance of duplicate databases. 1-10
1974
678Jon Postel:
Standard file formats. 1-9
1975
679D. W. Dodds:
February, 1975, survey of New-Protocol Telnet servers. 1-3
680Theodore H. Myer, D. Austin Henderson:
Message Transmission Protocol. 1-6
681Steve Holmgren:
Network UNIX. 1-8
683Robert C. Clements:
FTPSRV - Tenex extension for paged files. 1-3
684Richard E. Schantz:
Commentary on procedure calling as a network protocol. 1-9
685Michael Beeler:
Response time in cross network debugging. 1-3
686Brian Harvey:
Leaving well enough alone. 1-9
687David C. Walden:
IMP/Host and Host/IMP Protocol changes. 1-2
688David C. Walden:
Tentative schedule for the new Telnet implementation for the TIP. 1
689Robert C. Clements:
Tenex NCP finite state machine for connections. 1-5
690Jon Postel:
Comments on the proposed Host/IMP Protocol changes. 1-3
691Brian Harvey:
One more try on the FTP. 1-14
692Stephen M. Wolfe:
Comments on IMP/Host Protocol changes (RFCs 687 and 690). 1-2
694Jon Postel:
Protocol information. 1-36
695Mark Krilanovich:
Official change in Host-Host Protocol. 1-3
696Vinton G. Cerf:
Comments on the IMP/Host and Host/IMP Protocol changes. 1-2
697J. Lieb:
CWD command of FTP. 1-2
698T. Mock:
Telnet extended ASCII option. 1-3
1982
699Jon Postel, Jim Vernon:
Request For Comments summary notes: 600-699. 1-9

manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.


Google
Google Scholar
Semantic Scholar
Internet Archive Scholar
CiteSeerX
ORCID














