Requests for Comments 🌐

9847 pages Β· page 4 of 50

1–999 (continued)

  • RFC 660Some changes to the IMP and the IMP/Host interface✨
  • RFC 661Protocol information✨
  • RFC 662Performance improvement in ARPANET file transfers from Multics✨
  • RFC 663Lost message detection and recovery protocol✨
  • RFC 666Specification of the Unified User-Level Protocol✨
  • RFC 667Host Ports✨
  • RFC 669November, 1974, survey of New-Protocol Telnet servers✨
  • RFC 671Note on Reconnection Protocol✨
  • RFC 672Multi-site data collection facility✨
  • RFC 674Procedure call documents: Version 2✨
  • RFC 675Specification of Internet Transmission Control Program✨
  • RFC 677Maintenance of duplicate databases✨
  • RFC 678Standard file formats✨
  • RFC 679February, 1975, survey of New-Protocol Telnet servers✨
  • RFC 680Message Transmission Protocol✨
  • RFC 681Network UNIX✨
  • RFC 683FTPSRV - Tenex extension for paged files✨
  • RFC 684Commentary on procedure calling as a network protocol✨
  • RFC 685Response time in cross network debugging✨
  • RFC 686Leaving well enough alone✨
  • RFC 687IMP/Host and Host/IMP Protocol changes✨
  • RFC 688Tentative schedule for the new Telnet implementation for the TIP✨
  • RFC 689Tenex NCP finite state machine for connections✨
  • RFC 690Comments on the proposed Host/IMP Protocol changes✨
  • RFC 691One more try on the FTP✨
  • RFC 692Comments on IMP/Host Protocol changes (RFCs 687 and 690)✨
  • RFC 694Protocol information✨
  • RFC 695Official change in Host-Host Protocol✨
  • RFC 696Comments on the IMP/Host and Host/IMP Protocol changes✨
  • RFC 697CWD command of FTP✨
  • RFC 698Telnet extended ASCII option✨
  • RFC 699Request For Comments summary notes: 600-699✨
  • RFC 700Protocol experiment✨
  • RFC 701August, 1974, survey of New-Protocol Telnet servers✨
  • RFC 702September, 1974, survey of New-Protocol Telnet servers✨
  • RFC 703July, 1975, survey of New-Protocol Telnet Servers✨
  • RFC 704IMP/Host and Host/IMP Protocol change✨
  • RFC 705Front-end Protocol B6700 version✨
  • RFC 706On the junk mail problem✨
  • RFC 707High-level framework for network-based resource sharing✨
  • RFC 708Elements of a Distributed Programming System✨
  • RFC 712Distributed Capability Computing System (DCCS)✨
  • RFC 713MSDTP-Message Services Data Transmission Protocol✨
  • RFC 714Host-Host Protocol for an ARPANET-Type Network✨
  • RFC 716Interim Revision to Appendix F of BBN 1822✨
  • RFC 717Assigned Network Numbers✨
  • RFC 718Comments on RCTE from the Tenex Implementation Experience✨
  • RFC 719Discussion on RCTE✨
  • RFC 720Address Specification Syntax for Network Mail✨
  • RFC 721Out-of-Band Control Signals in a Host-to-Host Protocol✨
  • RFC 722Thoughts on Interactions in Distributed Services✨
  • RFC 724Proposed official standard for the format of ARPA Network messages✨
  • RFC 725RJE protocol for a resource sharing network✨
  • RFC 726Remote Controlled Transmission and Echoing Telnet option✨
  • RFC 727Telnet logout option✨
  • RFC 728Minor pitfall in the Telnet Protocol✨
  • RFC 729Telnet byte macro option✨
  • RFC 730Extensible field addressing✨
  • RFC 731Telnet Data Entry Terminal option✨
  • RFC 732Telnet Data Entry Terminal option✨
  • RFC 733Standard for the format of ARPA network text messages✨
  • RFC 734SUPDUP Protocol✨
  • RFC 735Revised Telnet byte macro option✨
  • RFC 736Telnet SUPDUP option✨
  • RFC 737FTP extension: XSEN✨
  • RFC 738Time server✨
  • RFC 739Assigned numbers✨
  • RFC 740NETRJS Protocol✨
  • RFC 741Specifications for the Network Voice Protocol (NVP)✨
  • RFC 742NAME/FINGER Protocol✨
  • RFC 743FTP extension: XRSQ/XRCP✨
  • RFC 744MARS - a Message Archiving and Retrieval Service✨
  • RFC 745JANUS interface specifications✨
  • RFC 746SUPDUP graphics extension✨
  • RFC 747Recent extensions to the SUPDUP Protocol✨
  • RFC 748Telnet randomly-lose option✨
  • RFC 749Telnet SUPDUP-Output option✨
  • RFC 750Assigned numbers✨
  • RFC 751Survey of FTP mail and MLFL✨
  • RFC 752Universal host table✨
  • RFC 753Internet Message Protocol✨
  • RFC 754Out-of-net host addresses for mail✨
  • RFC 755Assigned numbers✨
  • RFC 756NIC name server - a datagram-based information utility✨
  • RFC 757Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems✨
  • RFC 758Assigned numbers✨
  • RFC 759Internet Message Protocol✨
  • RFC 760DoD standard Internet Protocol✨
  • RFC 761DoD standard Transmission Control Protocol✨
  • RFC 762Assigned numbers✨
  • RFC 763Role mailboxes✨
  • RFC 764Telnet Protocol specification✨
  • RFC 765File Transfer Protocol specification✨
  • RFC 766Internet Protocol Handbook: Table of contents✨
  • RFC 767Structured format for transmission of multi-media documents✨
  • RFC 768User Datagram Protocol✨
  • RFC 769Rapicom 450 facsimile file format✨
  • RFC 770Assigned numbers✨
  • RFC 771Mail transition plan✨
  • RFC 772Mail Transfer Protocol✨
  • RFC 773Comments on NCP/TCP mail service transition strategy✨
  • RFC 774Internet Protocol Handbook: Table of contents✨
  • RFC 775Directory oriented FTP commands✨
  • RFC 776Assigned numbers✨
  • RFC 777Internet Control Message Protocol✨
  • RFC 778DCNET Internet Clock Service✨
  • RFC 779Telnet send-location option✨
  • RFC 780Mail Transfer Protocol✨
  • RFC 781Specification of the Internet Protocol (IP) timestamp option✨
  • RFC 782Virtual Terminal management model✨
  • RFC 783TFTP Protocol (revision 2)✨
  • RFC 784Mail Transfer Protocol: ISI TOPS20 implementation✨
  • RFC 785Mail Transfer Protocol: ISI TOPS20 file definitions✨
  • RFC 786Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface✨
  • RFC 787Connectionless data transmission survey/tutorial✨
  • RFC 788Simple Mail Transfer Protocol✨
  • RFC 789Vulnerabilities of network control protocols: An example✨
  • RFC 790Assigned numbers✨
  • RFC 791Internet Protocol✨
  • RFC 792Internet Control Message Protocol✨
  • RFC 793Transmission Control Protocol✨
  • RFC 794Pre-emption✨
  • RFC 795Service mappings✨
  • RFC 796Address mappings✨
  • RFC 797Format for Bitmap files✨
  • RFC 798Decoding facsimile data from the Rapicom 450✨
  • RFC 799Internet name domains✨
  • RFC 800Request For Comments summary notes: 700-799✨
  • RFC 801NCP/TCP transition plan✨
  • RFC 802ARPANET 1822L Host Access Protocol✨
  • RFC 803Dacom 450/500 facsimile data transcoding✨
  • RFC 804CCITT draft recommendation T.4✨
  • RFC 805Computer mail meeting notes✨
  • RFC 806Proposed Federal Information Processing Standard: Specification for message format for computer based message systems✨
  • RFC 807Multimedia mail meeting notes✨
  • RFC 808Summary of computer mail services meeting held at BBN on 10 January 1979✨
  • RFC 809UCL facsimile system✨
  • RFC 810DoD Internet host table specification✨
  • RFC 811Hostnames Server✨
  • RFC 812NICNAME/WHOIS✨
  • RFC 813Window and Acknowledgement Strategy in TCP✨
  • RFC 814Name, addresses, ports, and routes✨
  • RFC 815IP datagram reassembly algorithms✨
  • RFC 816Fault isolation and recovery✨
  • RFC 817Modularity and efficiency in protocol implementation✨
  • RFC 818Remote User Telnet service✨
  • RFC 819The Domain Naming Convention for Internet User Applications✨
  • RFC 820Assigned numbers✨
  • RFC 821Simple Mail Transfer Protocol✨
  • RFC 822STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES✨
  • RFC 823DARPA Internet gateway✨
  • RFC 824CRONUS Virtual Local Network✨
  • RFC 825Request for comments on Requests For Comments✨
  • RFC 826An Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware✨
  • RFC 827Exterior Gateway Protocol (EGP)✨
  • RFC 828Data communications: IFIP's international "network" of experts✨
  • RFC 829Packet satellite technology reference sources✨
  • RFC 830Distributed system for Internet name service✨
  • RFC 831Backup access to the European side of SATNET✨
  • RFC 832Who talks TCP?✨
  • RFC 833Who talks TCP?✨
  • RFC 834Who talks TCP?✨
  • RFC 835Who talks TCP?✨
  • RFC 836Who talks TCP?✨
  • RFC 837Who talks TCP?✨
  • RFC 838Who talks TCP?✨
  • RFC 839Who talks TCP?✨
  • RFC 840Official protocols✨
  • RFC 841Specification for message format for Computer Based Message Systems✨
  • RFC 842Who talks TCP? - survey of 1 February 83✨
  • RFC 843Who talks TCP? - survey of 8 February 83✨
  • RFC 844Who talks ICMP, too? - Survey of 18 February 1983✨
  • RFC 845Who talks TCP? - survey of 15 February 1983✨
  • RFC 846Who talks TCP? - survey of 22 February 1983✨
  • RFC 847Summary of Smallberg surveys✨
  • RFC 848Who provides the "little" TCP services?✨
  • RFC 849Suggestions for improved host table distribution✨
  • RFC 850Standard for interchange of USENET messages✨
  • RFC 851ARPANET 1822L Host Access Protocol✨
  • RFC 852ARPANET short blocking feature✨
  • RFC 854Telnet Protocol Specification✨
  • RFC 855Telnet Option Specifications✨
  • RFC 856Telnet Binary Transmission✨
  • RFC 857Telnet Echo Option✨
  • RFC 858Telnet Suppress Go Ahead Option✨
  • RFC 859Telnet Status Option✨
  • RFC 860Telnet Timing Mark Option✨
  • RFC 861Telnet Extended Options: List Option✨
  • RFC 862Echo Protocol✨
  • RFC 863Discard Protocol✨
  • RFC 864Character Generator Protocol✨
  • RFC 865Quote of the Day Protocol✨
  • RFC 866Active users✨
  • RFC 867Daytime Protocol✨
  • RFC 868Time Protocol✨
  • RFC 869Host Monitoring Protocol✨
  • RFC 870Assigned numbers✨
  • RFC 871Perspective on the ARPANET reference model✨
  • RFC 872TCP-on-a-LAN✨
  • RFC 873Illusion of vendor support✨