References from rfc661

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document Title Status Type Downref
RFC 138 Status report on proposed Data Reconfiguration Service
References Referenced by
Unknown Possible Reference
RFC 18 IMP-IMP and HOST-HOST Control Links
References Referenced by
Unknown Possible Reference
RFC 202 Possible Deadlock in ICP
References Referenced by
Unknown Possible Reference
RFC 318 Telnet Protocols
References Referenced by
Unknown Possible Reference
RFC 407 Remote Job Entry Protocol
References Referenced by
Historic Possible Reference
RFC 436 Announcement of RJS at UCSB
References Referenced by
Unknown Possible Reference
RFC 437 Data Reconfiguration Service at UCSB
References Referenced by
Unknown Possible Reference
RFC 454 File Transfer Protocol - meeting announcement and a new proposed document
References Referenced by
Unknown Possible Reference
RFC 520 Memo to FTP group: Proposal for File Access Protocol
References Referenced by
Unknown Possible Reference
RFC 524 Proposed Mail Protocol
References Referenced by
Unknown Possible Reference
RFC 539 Thoughts on the mail protocol proposed in RFC 524
References Referenced by
Unknown Possible Reference
RFC 542 File Transfer Protocol
References Referenced by
Unknown Possible Reference
RFC 555 Responses to critiques of the proposed mail protocol
References Referenced by
Unknown Possible Reference
RFC 561 Standardizing Network Mail Headers
References Referenced by
Unknown Possible Reference
RFC 569 NETED: A Common Editor for the ARPA Network
References Referenced by
Historic Possible Reference
RFC 599 Update on NETRJS
References Referenced by
Unknown Possible Reference
RFC 604 Assigned link numbers
References Referenced by
Unknown Possible Reference
RFC 630 FTP error code usage for more reliable mail service
References Referenced by
Unknown Possible Reference
RFC 636 TIP/Tenex reliability improvements
References Referenced by
Unknown Possible Reference
RFC 640 Revised FTP reply codes
References Referenced by
Unknown Possible Reference
RFC 642 Ready line philosophy and implementation
References Referenced by
Unknown Possible Reference
RFC 643 Network Debugging Protocol
References Referenced by
Unknown Possible Reference
RFC 644 On the problem of signature authentication for network mail
References Referenced by
Unknown Possible Reference
RFC 645 Network Standard Data Specification syntax
References Referenced by
Unknown Possible Reference
RFC 647 Proposed protocol for connecting host computers to ARPA-like networks via front end processors
References Referenced by
Unknown Possible Reference
RFC 651 Revised Telnet status option
References Referenced by
Unknown Possible Reference
RFC 652 Telnet output carriage-return disposition option
References Referenced by
Historic Possible Reference
RFC 653 Telnet output horizontal tabstops option
References Referenced by
Historic Possible Reference
RFC 654 Telnet output horizontal tab disposition option
References Referenced by
Historic Possible Reference
RFC 655 Telnet output formfeed disposition option
References Referenced by
Historic Possible Reference
RFC 656 Telnet output vertical tabstops option
References Referenced by
Historic Possible Reference
RFC 657 Telnet output vertical tab disposition option
References Referenced by
Historic Possible Reference
RFC 658 Telnet output linefeed disposition
References Referenced by
Historic Possible Reference
RFC 660 Some changes to the IMP and the IMP/Host interface
References Referenced by
Unknown Possible Reference
RFC 700 Protocol experiment
References Referenced by
Informational Possible Reference
RFC 702 September, 1974, survey of New-Protocol Telnet servers
References Referenced by
Unknown Possible Reference