Network programming in C#, Network Programming in VB.NET, Network Programming in .NET
Available now!
Buy at Amazon US or
Buy at Amazon UK


» Windows API reference
» Webcam streaming in VB.NET
» Remoting with firewalls
» RSA from first principles
» Key & MouseLogger in .NET
» Networking Resource Kit for .NET
» Migrating VB6 Winsock to VB.NET
» Migrating C++ sockets to C#
» RFC Reference guide
» COM Reference guide
» WMI Reference guide
» SQL stored procedures
» TCP & UDP port reference
» NET Framework reference
» Ethernet Type codes
» MAC address assignments
» DLL entry point reference
» Boost SQL performance
» Free SMS UK
» Free SMS Ireland
» Free SMS South Africa
» Internet Explorer

Contact us

Request for comments (RFC) reference, RFC500 to RFC1000

The RFC documents are the definitive specifications for every major internet protocol. They are sourced direct from the IETF, and have not been modified or altered in any way. Therefore, you may use this site to determine if your client or server software adheres to internationally recognised specifications. If you are looking to implement any of these protocols in .NET, either C# or VB.NET, you may find the book Network Programming in .NET (Buy at Amazon UK) (Buy at Amazon US) of invaluable assistance.

RFC999 Requests For Comments summary notes: 900-999

RFC998 NETBLT: A bulk data transfer protocol

RFC997 Internet numbers

RFC996 Statistics server

RFC995 End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473

RFC994 Final text of DIS 8473

RFC993 PCMAIL: A distributed mail system for personal computers

RFC992 On communication support for fault tolerant process groups

RFC991 Official ARPA-Internet protocols

RFC990 Assigned numbers

RFC989 Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures

RFC988 Host extensions for IP multicasting

RFC987 Mapping between X

RFC986 Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol

RFC985 Requirements for Internet gateways - draft

RFC984 PCMAIL: A distributed mail system for personal computers

RFC983 ISO transport arrives on top of the TCP

RFC982 Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address

RFC981 Experimental multiple-path routing algorithm

RFC980 Protocol document order information

RFC979 PSN End-to-End functional specification

RFC978 Voice File Interchange Protocol (VFIP)

RFC977 Network News Transfer Protocol

RFC976 UUCP mail interchange format standard

RFC975 Autonomous confederations

RFC974 Mail routing and the domain system

RFC973 Domain system changes and observations

RFC972 Password Generator Protocol

RFC971 Survey of data representation standards

RFC970 On packet switches with infinite storage

RFC969 NETBLT: A bulk data transfer protocol

RFC968 Twas the night before start-up

RFC967 All victims together

RFC966 Host groups: A multicast extension to the Internet Protocol

RFC965 Format for a graphical communication protocol

RFC964 Some problems with the specification of the Military Standard Transmission Control Protocol

RFC963 Some problems with the specification of the Military Standard Internet Protocol

RFC962 TCP-4 prime

RFC961 Official ARPA-Internet protocols

RFC960 Assigned numbers

RFC959 File Transfer Protocol

RFC958 Network Time Protocol (NTP)

RFC957 Experiments in network clock synchronization

RFC956 Algorithms for synchronizing network clocks

RFC955 Towards a transport service for transaction processing applications


RFC953 Hostname Server

RFC952 DoD Internet host table specification

RFC951 Bootstrap Protocol

RFC950 Internet Standard Subnetting Procedure

RFC949 FTP unique-named store command

RFC948 Two methods for the transmission of IP datagrams over IEEE 802

RFC947 Multi-network broadcasting within the Internet

RFC946 Telnet terminal location number option

RFC945 DoD statement on the NRC report

RFC944 Official ARPA-Internet protocols

RFC943 Assigned numbers

RFC942 Transport protocols for Department of Defense data networks

RFC941 Addendum to the network service definition covering network layer addressing

RFC940 Toward an Internet standard scheme for subnetting

RFC939 Executive summary of the NRC report on transport protocols for Department of Defense data networks

RFC938 Internet Reliable Transaction Protocol functional and interface specification

RFC937 Post Office Protocol: Version 2

RFC936 Another Internet subnet addressing scheme

RFC935 Reliable link layer protocols

RFC934 Proposed standard for message encapsulation

RFC933 Output marking Telnet option

RFC932 Subnetwork addressing scheme

RFC931 Authentication server

RFC930 Telnet terminal type option

RFC929 Proposed Host-Front End Protocol

RFC928 Introduction to proposed DoD standard H-FP

RFC927 TACACS user identification Telnet option

RFC926 Protocol for providing the connectionless mode network services

RFC925 Multi-LAN address resolution

RFC924 Official ARPA-Internet protocols for connecting personal computers to the Internet

RFC923 Assigned numbers

RFC922 Broadcasting Internet datagrams in the presence of subnets

RFC921 Domain name system implementation schedule - revised

RFC920 Domain requirements

RFC919 Broadcasting Internet Datagrams

RFC918 Post Office Protocol

RFC917 Internet subnets

RFC916 Reliable Asynchronous Transfer Protocol (RATP)

RFC915 Network mail path service

RFC914 Thinwire protocol for connecting personal computers to the Internet

RFC913 Simple File Transfer Protocol

RFC912 Authentication service

RFC911 EGP Gateway under Berkeley UNIX 4

RFC910 Multimedia mail meeting notes

RFC909 Loader Debugger Protocol

RFC908 Reliable Data Protocol

RFC907 Host Access Protocol specification

RFC906 Bootstrap loading using TFTP

RFC905 ISO Transport Protocol specification ISO DP 8073

RFC904 Exterior Gateway Protocol formal specification

RFC903 Reverse Address Resolution Protocol

RFC902 ARPA Internet Protocol policy

RFC901 Official ARPA-Internet protocols

RFC900 Assigned Numbers

RFC899 Request For Comments summary notes: 800-899

RFC898 Gateway special interest group meeting notes

RFC897 Domain name system implementation schedule

RFC896 Congestion control in IP/TCP internetworks

RFC895 Standard for the transmission of IP datagrams over experimental Ethernet networks

RFC894 Standard for the transmission of IP datagrams over Ethernet networks

RFC893 Trailer encapsulations

RFC892 ISO Transport Protocol specification

RFC891 DCN local-network protocols

RFC890 Exterior Gateway Protocol implementation schedule

RFC889 Internet delay experiments

RFC888 "STUB" Exterior Gateway Protocol

RFC887 Resource Location Protocol

RFC886 Proposed standard for message header munging

RFC885 Telnet end of record option

RFC884 Telnet terminal type option

RFC883 Domain names: Implementation specification

RFC882 Domain names: Concepts and facilities

RFC881 Domain names plan and schedule

RFC880 Official protocols

RFC879 TCP maximum segment size and related topics

RFC878 ARPANET 1822L Host Access Protocol

RFC877 Standard for the transmission of IP datagrams over public data networks

RFC876 Survey of SMTP implementations

RFC875 Gateways

RFC874 Critique of X

RFC873 Illusion of vendor support

RFC872 TCP-on-a-LAN

RFC871 Perspective on the ARPANET reference model

RFC870 Assigned numbers

RFC869 Host Monitoring Protocol

RFC868 Time Protocol

RFC867 Daytime Protocol

RFC866 Active users

RFC865 Quote of the Day Protocol

RFC864 Character Generator Protocol

RFC863 Discard Protocol

RFC862 Echo Protocol

RFC861 Telnet Extended Options: List Option

RFC860 Telnet Timing Mark Option

RFC859 Telnet Status Option

RFC858 Telnet Suppress Go Ahead Option

RFC857 Telnet Echo Option

RFC856 Telnet Binary Transmission

RFC855 Telnet Option Specifications

RFC854 Telnet Protocol Specification

RFC853 Not Issued

RFC852 ARPANET short blocking feature

RFC851 ARPANET 1822L Host Access Protocol

RFC850 Standard for interchange of USENET messages

RFC849 Suggestions for improved host table distribution

RFC848 Who provides the "little" TCP services?

RFC847 Summary of Smallberg surveys

RFC846 Who talks TCP? - survey of 22 February 1983

RFC845 Who talks TCP? - survey of 15 February 1983

RFC844 Who talks ICMP

RFC843 Who talks TCP? - survey of 8 February 83

RFC842 Who talks TCP? - survey of 1 February 83

RFC841 Specification for message format for Computer Based Message Systems

RFC840 Official protocols

RFC839 Who talks TCP?

RFC838 Who talks TCP?

RFC837 Who talks TCP?

RFC836 Who talks TCP?

RFC835 Who talks TCP?

RFC834 Who talks TCP?

RFC833 Who talks TCP?

RFC832 Who talks TCP?

RFC831 Backup access to the European side of SATNET

RFC830 Distributed system for Internet name service

RFC829 Packet satellite technology reference sources

RFC828 Data communications: IFIP's international "network" of experts

RFC827 Exterior Gateway Protocol (EGP)

RFC826 Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48

RFC825 Request for comments on Requests For Comments

RFC824 CRONUS Virtual Local Network

RFC823 DARPA Internet gateway

RFC822 Standard for the format of ARPA Internet text messages

RFC821 Simple Mail Transfer Protocol

RFC820 Assigned numbers

RFC819 Domain naming convention for Internet user applications

RFC818 Remote User Telnet service

RFC817 Modularity and efficiency in protocol implementation

RFC816 Fault isolation and recovery

RFC815 IP datagram reassembly algorithms

RFC814 Name

RFC813 Window and Acknowledgement Strategy in TCP


RFC811 Hostnames Server

RFC810 DoD Internet host table specification

RFC809 UCL facsimile system

RFC808 Summary of computer mail services meeting held at BBN on 10 January 1979

RFC807 Multimedia mail meeting notes

RFC806 Proposed Federal Information Processing Standard: Specification for message format for computer based message systems

RFC805 Computer mail meeting notes

RFC804 CCITT draft recommendation T

RFC803 Dacom 450/500 facsimile data transcoding

RFC802 ARPANET 1822L Host Access Protocol

RFC801 NCP/TCP transition plan

RFC800 Request For Comments summary notes: 700-799

RFC799 Internet name domains

RFC798 Decoding facsimile data from the Rapicom 450

RFC797 Format for Bitmap files

RFC796 Address mappings

RFC795 Service mappings

RFC794 Pre-emption

RFC793 Transmission Control Protocol

RFC792 Internet Control Message Protocol

RFC791 Internet Protocol

RFC790 Assigned numbers

RFC789 Vulnerabilities of network control protocols: An example

RFC788 Simple Mail Transfer Protocol

RFC787 Connectionless data transmission survey/tutorial

RFC786 Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface

RFC785 Mail Transfer Protocol: ISI TOPS20 file definitions

RFC784 Mail Transfer Protocol: ISI TOPS20 implementation

RFC783 TFTP Protocol (revision 2)

RFC782 Virtual Terminal management model

RFC781 Specification of the Internet Protocol (IP) timestamp option

RFC780 Mail Transfer Protocol

RFC779 Telnet send-location option

RFC778 DCNET Internet Clock Service

RFC777 Internet Control Message Protocol

RFC776 Assigned numbers

RFC775 Directory oriented FTP commands

RFC774 Internet Protocol Handbook: Table of contents

RFC773 Comments on NCP/TCP mail service transition strategy

RFC772 Mail Transfer Protocol

RFC771 Mail transition plan

RFC770 Assigned numbers

RFC769 Rapicom 450 facsimile file format

RFC768 User Datagram Protocol

RFC767 Structured format for transmission of multi-media documents

RFC766 Internet Protocol Handbook: Table of contents

RFC765 File Transfer Protocol specification

RFC764 Telnet Protocol specification

RFC763 Role mailboxes

RFC762 Assigned numbers

RFC761 DoD standard Transmission Control Protocol

RFC760 DoD standard Internet Protocol

RFC759 Internet Message Protocol

RFC758 Assigned numbers

RFC757 Suggested solution to the naming

RFC756 NIC name server - a datagram-based information utility

RFC755 Assigned numbers

RFC754 Out-of-net host addresses for mail

RFC753 Internet Message Protocol

RFC752 Universal host table

RFC751 Survey of FTP mail and MLFL

RFC750 Assigned numbers

RFC749 Telnet SUPDUP-Output option

RFC748 Telnet randomly-lose option

RFC747 Recent extensions to the SUPDUP Protocol

RFC746 SUPDUP graphics extension

RFC745 JANUS interface specifications

RFC744 MARS - a Message Archiving and Retrieval Service

RFC743 FTP extension: XRSQ/XRCP


RFC741 Specifications for the Network Voice Protocol (NVP)

RFC740 NETRJS Protocol

RFC739 Assigned numbers

RFC738 Time server

RFC737 FTP extension: XSEN

RFC736 Telnet SUPDUP option

RFC735 Revised Telnet byte macro option

RFC734 SUPDUP Protocol

RFC733 Standard for the format of ARPA network text messages

RFC732 Telnet Data Entry Terminal option

RFC731 Telnet Data Entry Terminal option

RFC730 Extensible field addressing

RFC729 Telnet byte macro option

RFC728 Minor pitfall in the Telnet Protocol

RFC727 Telnet logout option

RFC726 Remote Controlled Transmission and Echoing Telnet option

RFC725 RJE protocol for a resource sharing network

RFC724 Proposed official standard for the format of ARPA Network messages

RFC723 Not Issued

RFC722 Thoughts on Interactions in Distributed Services

RFC721 Out-of-Band Control Signals in a Host-to-Host Protocol

RFC720 Address Specification Syntax for Network Mail

RFC719 Discussion on RCTE

RFC718 Comments on RCTE from the Tenex Implementation Experience

RFC717 Assigned Network Numbers

RFC716 Interim Revision to Appendix F of BBN 1822

RFC715 Not Issued

RFC714 Host-Host Protocol for an ARPANET-Type Network

RFC713 MSDTP-Message Services Data Transmission Protocol

RFC712 Distributed Capability Computing System (DCCS)

RFC711 Not Issued

RFC710 Not Issued

RFC709 Not Issued

RFC708 Elements of a Distributed Programming System

RFC707 High-level framework for network-based resource sharing

RFC706 On the junk mail problem

RFC705 Front-end Protocol B6700 version

RFC704 IMP/Host and Host/IMP Protocol change

RFC703 July

RFC702 September

RFC701 August

RFC700 Protocol experiment

RFC699 Request For Comments summary notes: 600-699

RFC698 Telnet extended ASCII option

RFC697 CWD command of FTP

RFC696 Comments on the IMP/Host and Host/IMP Protocol changes

RFC695 Official change in Host-Host Protocol

RFC694 Protocol information

RFC693 Not Issued

RFC692 Comments on IMP/Host Protocol changes (RFCs 687 and 690)

RFC691 One more try on the FTP

RFC690 Comments on the proposed Host/IMP Protocol changes

RFC689 Tenex NCP finite state machine for connections

RFC688 Tentative schedule for the new Telnet implementation for the TIP

RFC687 IMP/Host and Host/IMP Protocol changes

RFC686 Leaving well enough alone

RFC685 Response time in cross network debugging

RFC684 Commentary on procedure calling as a network protocol

RFC683 FTPSRV - Tenex extension for paged files

RFC682 Not Issued

RFC681 Network UNIX

RFC680 Message Transmission Protocol

RFC679 February

RFC678 Standard file formats

RFC677 Maintenance of duplicate databases

RFC676 Not Issued

RFC675 Specification of Internet Transmission Control Program

RFC674 Procedure call documents: Version 2

RFC673 Not Issued

RFC672 Multi-site data collection facility

RFC671 Note on Reconnection Protocol

RFC670 Not Issued

RFC669 November

RFC668 Not Issued

RFC667 BBN host ports

RFC666 Specification of the Unified User-Level Protocol

RFC665 Not Issued

RFC664 Not Issued

RFC663 Lost message detection and recovery protocol

RFC662 Performance improvement in ARPANET file transfers from Multics

RFC661 Protocol information

RFC660 Some changes to the IMP and the IMP/Host interface

RFC659 Announcing additional Telnet options

RFC658 Telnet output linefeed disposition

RFC657 Telnet output vertical tab disposition option

RFC656 Telnet output vertical tabstops option

RFC655 Telnet output formfeed disposition option

RFC654 Telnet output horizontal tab disposition option

RFC653 Telnet output horizontal tabstops option

RFC652 Telnet output carriage-return disposition option

RFC651 Revised Telnet status option

RFC650 Not Issued

RFC649 Not Issued

RFC648 Not Issued

RFC647 Proposed protocol for connecting host computers to ARPA-like networks via front end processors

RFC646 Not Issued

RFC645 Network Standard Data Specification syntax

RFC644 On the problem of signature authentication for network mail

RFC643 Network Debugging Protocol

RFC642 Ready line philosophy and implementation

RFC641 Not Issued

RFC640 Revised FTP reply codes

RFC639 Not Issued

RFC638 IMP/TIP preventive maintenance schedule

RFC637 Change of network address for SU-DSL

RFC636 TIP/Tenex reliability improvements

RFC635 Assessment of ARPANET protocols

RFC634 Change in network address for Haskins Lab

RFC633 IMP/TIP preventive maintenance schedule

RFC632 Throughput degradations for single packet messages

RFC631 International meeting on minicomputers and data communication: Call for papers

RFC630 FTP error code usage for more reliable mail service

RFC629 Scenario for using the Network Journal

RFC628 Status of RFC numbers and a note on pre-assigned journal numbers

RFC627 ASCII text file of hostnames

RFC626 On a possible lockup condition in IMP subnet due to message sequencing

RFC625 On-line hostnames service

RFC624 Comments on the File Transfer Protocol

RFC623 Comments on on-line host name service

RFC622 Scheduling IMP/TIP down time

RFC621 NIC user directories at SRI ARC

RFC620 Request for monitor host table updates

RFC619 Mean round-trip times in the ARPANET

RFC618 Few observations on NCP statistics

RFC617 Note on socket number assignment

RFC616 Latest network maps

RFC615 Proposed Network Standard Data Pathname syntax

RFC614 Response to RFC 607: "Comments on the File Transfer Protocol"

RFC613 Network connectivity: A response to RFC 603

RFC612 Traffic statistics (December 1973)

RFC611 Two changes to the IMP/Host Protocol to improve user/network communications

RFC610 Further datalanguage design concepts

RFC609 Statement of upcoming move of NIC/NLS service

RFC608 Host names on-line

RFC607 Comments on the File Transfer Protocol

RFC606 Host names on-line

RFC605 Not Issued

RFC604 Assigned link numbers

RFC603 Response to RFC 597: Host status

RFC602 "The stockings were hung by the chimney with care"

RFC601 Traffic statistics (November 1973)

RFC600 Interfacing an Illinois plasma terminal to the ARPANET

RFC599 Update on NETRJS

RFC598 RFC index - December 5

RFC597 Host status

RFC596 Second thoughts on Telnet Go-Ahead

RFC595 Second thoughts in defense of the Telnet Go-Ahead

RFC594 Speedup of Host-IMP interface

RFC593 Telnet and FTP implementation schedule change

RFC592 Some thoughts on system design to facilitate resource sharing

RFC591 Addition to the Very Distant Host specifications

RFC590 MULTICS address change

RFC589 CCN NETRJS server messages to remote user

RFC588 London node is now up

RFC587 Announcing new Telnet options

RFC586 Traffic statistics (October 1973)

RFC585 ARPANET users interest working group meeting

RFC584 Charter for ARPANET Users Interest Working Group

RFC583 Not Issued

RFC582 Comments on RFC 580: Machine readable protocols

RFC581 Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option

RFC580 Note to Protocol Designers and Implementers

RFC579 Traffic statistics (September 1973)

RFC578 Using MIT-Mathlab MACSYMA from MIT-DMS Muddle

RFC577 Mail priority

RFC576 Proposal for modifying linking

RFC575 Not Issued

RFC574 Announcement of a mail facility at UCSB

RFC573 Data and file transfer: Some measurement results

RFC572 Not Issued

RFC571 Tenex FTP problem

RFC570 Experimental input mapping between NVT ASCII and UCSB On Line System

RFC569 NETED: A Common Editor for the ARPA Network

RFC568 Response to RFC 567 - cross country network bandwidth

RFC567 Cross Country Network Bandwidth

RFC566 Traffic statistics (August 1973)

RFC565 Storing network survey data at the datacomputer

RFC564 Not Issued

RFC563 Comments on the RCTE Telnet option

RFC562 Modifications to the Telnet specification

RFC561 Standardizing Network Mail Headers

RFC560 Remote Controlled Transmission and Echoing Telnet option

RFC559 Comments on The New Telnet Protocol and its Implementation

RFC558 Not Issued

RFC557 Revelations in network host measurements

RFC556 Traffic statistics (July 1973)

RFC555 Responses to critiques of the proposed mail protocol

RFC554 Not Issued

RFC553 Draft design for a text/graphics protocol

RFC552 Single access to standard protocols


RFC550 NIC NCP experiment

RFC549 Minutes of Network Graphics Group meeting

RFC548 Hosts using the IMP Going Down message

RFC547 Change to the Very Distant Host specification

RFC546 Tenex load averages for July 1973

RFC545 Of what quality be the UCSB resources evaluators?

RFC544 Locating on-line documentation at SRI-ARC

RFC543 Network journal submission and delivery

RFC542 File Transfer Protocol

RFC541 Not Issued

RFC540 Not Issued

RFC539 Thoughts on the mail protocol proposed in RFC 524

RFC538 Traffic statistics (June 1973)

RFC537 Announcement of NGG meeting July 16-17

RFC536 Not Issued

RFC535 Comments on File Access Protocol

RFC534 Lost message detection

RFC533 Message-ID numbers

RFC532 UCSD-CC Server-FTP facility

RFC531 Feast or famine? A response to two recent RFC's about network information

RFC530 Report on the Survey project

RFC529 Note on protocol synch sequences

RFC528 Software checksumming in the IMP and network reliability


RFC526 Technical meeting: Digital image processing software systems

RFC525 MIT-MATHLAB meets UCSB-OLS -an example of resource sharing

RFC524 Proposed Mail Protocol

RFC523 SURVEY is in operation again

RFC522 Traffic statistics (May 1973)

RFC521 Restricted use of IMP DDT

RFC520 Memo to FTP group: Proposal for File Access Protocol

RFC519 Resource evaluation

RFC518 ARPANET accounts

RFC517 Not Issued

RFC516 Lost message detection

RFC515 Specifications for datalanguage: Version 0/9

RFC514 Network make-work

RFC513 Comments on the new Telnet specifications

RFC512 More on lost message detection

RFC511 Enterprise phone service to NIC from ARPANET sites

RFC510 Request for network mailbox addresses

RFC509 Traffic statistics (April 1973)

RFC508 Real-time data transmission on the ARPANET

RFC507 Not Issued

RFC506 FTP command naming problem

RFC505 Two solutions to a file transfer access problem

RFC504 Distributed resources workshop announcement

RFC503 Socket number list

RFC502 Not Issued

RFC501 Un-muddling "free file transfer"

Archived RFC documents

RFC3500 to RFC3768
RFC3000 to RFC3500
RFC2500 to RFC3000
RFC2000 to RFC2500
RFC1500 to RFC2000
RFC1000 to RFC1500
RFC500 to RFC1000
RFC1 to RFC500


Copyright 2019 Infinite Loop Ltd.