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, RFC1 to RFC500

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.

RFC500 Integration of data management systems on a computer network

RFC499 Harvard's network RJE

RFC498 On mail service to CCN

RFC497 Traffic statistics (March 1973)

RFC496 TNLS quick reference card is available

RFC495 Telnet Protocol specifications

RFC494 Availability of MIX and MIXAL in the Network

RFC493 Graphics Protocol

RFC492 Response to RFC 467

RFC491 What is "Free"?

RFC490 Surrogate RJS for UCLA-CCN

RFC489 Comment on resynchronization of connection status proposal

RFC488 NLS classes at network sites

RFC487 Free file transfer

RFC486 Data transfer revisited


RFC484 Not Issued

RFC483 Cancellation of the resource notebook framework meeting

RFC482 Traffic statistics (February 1973)

RFC481 Not Issued

RFC480 Host-dependent FTP parameters

RFC479 Use of FTP by the NIC Journal

RFC478 FTP server-server interaction - II

RFC477 Remote Job Service at UCSB

RFC476 IMP/TIP memory retrofit schedule (rev 2)

RFC475 FTP and network mail system

RFC474 Announcement of NGWG meeting: Call for papers


RFC472 Illinois' reply to Maxwell's request for graphics information (NIC 14925)

RFC471 Workshop on multi-site executive programs

RFC470 Change in socket for TIP news facility

RFC469 Network mail meeting summary

RFC468 FTP data compression

RFC467 Proposed change to Host-Host Protocol: Resynchronization of connection status

RFC466 Telnet logger/server for host LL-67

RFC465 Not Issued

RFC464 Resource notebook framework

RFC463 FTP comments and response to RFC 430

RFC462 Responding to user needs

RFC461 Telnet Protocol meeting announcement

RFC460 NCP survey

RFC459 Network questionnaires

RFC458 Mail retrieval via FTP


RFC456 Memorandum: Date change of mail meeting

RFC455 Traffic statistics (January 1973)

RFC454 File Transfer Protocol - meeting announcement and a new proposed document

RFC453 Meeting announcement to discuss a network mail system

RFC452 TELENET Command at Host LL

RFC451 Tentative proposal for a Unified User Level Protocol

RFC450 MULTICS sampling timeout change

RFC449 Current flow-control scheme for IMPSYS

RFC448 Print files in FTP

RFC447 IMP/TIP memory retrofit schedule

RFC446 Proposal to consider a network program resource notebook

RFC445 IMP/TIP preventive maintenance schedule

RFC444 Not Issued

RFC443 Traffic statistics (December 1972)

RFC442 Current flow-control scheme for IMPSYS

RFC441 Inter-Entity Communication - an experiment

RFC440 Scheduled network software maintenance

RFC439 PARRY encounters the DOCTOR

RFC438 FTP server-server interaction

RFC437 Data Reconfiguration Service at UCSB

RFC436 Announcement of RJS at UCSB

RFC435 Telnet issues

RFC434 IMP/TIP memory retrofit schedule

RFC433 Socket number list

RFC432 Network logical map

RFC431 Update on SMFS Login and Logout

RFC430 Comments on File Transfer Protocol

RFC429 Character Generator Process

RFC428 Not Issued

RFC427 Not Issued

RFC426 Reconnection Protocol

RFC425 "But my NCP costs $500 a day"

RFC424 Not Issued

RFC423 UCLA Campus Computing Network Liaison Staff for ARPANET

RFC422 Traffic statistics (November 1972)

RFC421 Software Consulting Service for Network Users

RFC420 CCA ICCC weather demo

RFC419 To: Network liaisons and station agents

RFC418 Server file transfer under TSS/360 at NASA Ames

RFC417 Link usage violation

RFC416 ARC System Will Be Unavailable for Use During Thanksgiving Week

RFC415 Tenex bandwidth

RFC414 File Transfer Protocol (FTP) status and further comments

RFC413 Traffic statistics (October 1972)

RFC412 User FTP Documentation

RFC411 New MULTICS Network Software Features

RFC410 Removal of the 30-Second Delay When Hosts Come Up

RFC409 Tenex interface to UCSB's Simple-Minded File System


RFC407 Remote Job Entry Protocol

RFC406 Scheduled IMP Software Releases

RFC405 Correction to RFC 404

RFC404 Host Address Changes Involving Rand and ISI

RFC403 Desirability of a network 1108 service

RFC402 ARPA Network Mailing Lists

RFC401 Conversion of NGP-0 Coordinates to Device Specific Coordinates

RFC400 Traffic Statistics (September 1972)

RFC399 SMFS Login and Logout

RFC398 ICP Sockets

RFC397 Not Issued

RFC396 Network Graphics Working Group Meeting - Second Iteration

RFC395 Switch Settings on IMPs and TIPs

RFC394 Two Proposed Changes to the IMP-Host Protocol

RFC393 Comments on Telnet Protocol Changes

RFC392 Measurement of host costs for transmitting network data

RFC391 Traffic statistics (August 1972)

RFC390 TSO Scenario

RFC389 UCLA Campus Computing Network Liaison Staff for ARPA Network

RFC388 NCP statistics

RFC387 Some experiences in implementing Network Graphics Protocol Level 0

RFC386 Letter to TIP users-2

RFC385 Comments on the File Transfer Protocol

RFC384 Official site idents for organizations in the ARPA Network

RFC383 Not Issued

RFC382 Mathematical Software on the ARPA Network

RFC381 Three aids to improved network operation

RFC380 Not Issued

RFC379 Using TSO at CCN

RFC378 Traffic statistics (July 1972)

RFC377 Using TSO via ARPA Network Virtual Terminal

RFC376 Network Host Status

RFC375 Not Issued

RFC374 IMP System Announcement

RFC373 Arbitrary Character Sets

RFC372 Notes on a Conversation with Bob Kahn on the ICCC

RFC371 Demonstration at International Computer Communications Conference

RFC370 Network Host Status

RFC369 Evaluation of ARPANET services January-March

RFC368 Comments on "Proposed Remote Job Entry Protocol"

RFC367 Network host status

RFC366 Network Host Status

RFC365 Letter to All TIP Users

RFC364 Serving remote users on the ARPANET

RFC363 ARPA Network mailing lists

RFC362 Network Host Status

RFC361 Deamon Processes on Host 106

RFC360 Proposed Remote Job Entry Protocol

RFC359 Status of the Release of the New IMP System (2600)

RFC358 Not Issued

RFC357 Echoing strategy for satellite links

RFC356 ARPA Network Control Center

RFC355 Response to NWG/RFC 346

RFC354 File Transfer Protocol

RFC353 Network host status

RFC352 TIP Site Information Form

RFC351 Graphics information form for the ARPANET graphics resources notebook

RFC350 User Accounts for UCSB On-Line System

RFC349 Proposed Standard Socket Numbers

RFC348 Discard Process

RFC347 Echo process

RFC346 Satellite Considerations

RFC345 Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN)

RFC344 Network Host Status

RFC343 IMP System change notification

RFC342 Network Host Status

RFC341 Not Issued

RFC340 Proposed Telnet Changes

RFC339 MLTNET: A "Multi Telnet" Subsystem for Tenex

RFC338 EBCDIC/ASCII Mapping for Network RJE

RFC337 Not Issued

RFC336 Level 0 Graphic Input Protocol

RFC335 New Interface - IMP/360

RFC334 Network Use on May 8

RFC333 Proposed experiment with a Message Switching Protocol

RFC332 Network Host Status

RFC331 IMP System Change Notification

RFC330 Network Host Status

RFC329 ARPA Network Mailing Lists

RFC328 Suggested Telnet Protocol Changes

RFC327 Data and File Transfer workshop notes

RFC326 Network Host Status

RFC325 Network Remote Job Entry program - NETRJS

RFC324 RJE Protocol meeting

RFC323 Formation of Network Measurement Group (NMG)

RFC322 Well known socket numbers

RFC321 CBI Networking Activity at MITRE

RFC320 Workshop on Hard Copy Line Printers

RFC319 Network Host Status

RFC318 Telnet Protocols

RFC317 Official Host-Host Protocol Modification: Assigned Link Numbers

RFC316 ARPA Network Data Management Working Group

RFC315 Network Host Status

RFC314 Network Graphics Working Group Meeting

RFC313 Computer based instruction

RFC312 Proposed Change in IMP-to-Host Protocol

RFC311 New Console Attachments to the USCB Host

RFC310 Another Look at Data and File Transfer Protocols

RFC309 Data and File Transfer Workshop Announcement

RFC308 ARPANET host availability data

RFC307 Using network Remote Job Entry

RFC306 Network host status

RFC305 Unknown Host Numbers

RFC304 Data management system proposal for the ARPA network

RFC303 ARPA Network mailing lists

RFC302 Exercising The ARPANET

RFC301 BBN IMP (#5) and NCC Schedule March 4

RFC300 ARPA Network mailing lists

RFC299 Information Management System

RFC298 Network host status

RFC297 TIP Message Buffers

RFC296 DS-1 display system

RFC295 Report of the Protocol Workshop

RFC294 The Use of "Set Data Type" Transaction in File Transfer Protocol

RFC293 Network Host Status

RFC292 Graphics Protocol: Level 0 only

RFC291 Data Management Meeting Announcement

RFC290 Computer networks and data sharing: A bibliography

RFC289 What we hope is an official list of host names

RFC288 Network host status

RFC287 Status of Network Hosts

RFC286 Network Library Information System

RFC285 Network graphics

RFC284 Not Issued

RFC283 NETRJT: Remote Job Service Protocol for TIPS

RFC282 Graphics meeting report

RFC281 Suggested addition to File Transfer Protocol

RFC280 A Draft of Host Names

RFC279 Not Issued

RFC278 Revision of the Mail Box Protocol

RFC277 Not Issued

RFC276 NIC course

RFC275 Not Issued

RFC274 Establishing a local guide for network usage

RFC273 More on standard host names

RFC272 Not Issued

RFC271 IMP System change notifications

RFC270 Correction to BBN Report No

RFC269 Some Experience with File Transfer

RFC268 Graphics facilities information

RFC267 Network Host Status

RFC266 Network host status

RFC265 The File Transfer Protocol

RFC264 The Data Transfer Protocol

RFC263 "Very Distant" Host interface

RFC262 Not Issued

RFC261 Not Issued

RFC260 Not Issued

RFC259 Not Issued

RFC258 Not Issued

RFC257 Not Issued

RFC256 IMPSYS change notification

RFC255 Status of network hosts

RFC254 Scenarios for using ARPANET computers

RFC253 Second Network Graphics meeting details

RFC252 Network host status

RFC251 Weather data

RFC250 Some thoughts on file transfer

RFC249 Coordination of equipment and supplies purchase

RFC248 Not Issued

RFC247 Proffered set of standard host names

RFC246 Network Graphics meeting

RFC245 Reservations for Network Group meeting

RFC244 Not Issued

RFC243 Network and data sharing bibliography

RFC242 Data Descriptive Language for Shared Data

RFC241 Connecting computers to MLC ports

RFC240 Site Status

RFC239 Host mnemonics proposed in RFC 226 (NIC 7625)

RFC238 Comments on DTP and FTP proposals

RFC237 NIC view of standard host names

RFC236 Standard host names

RFC235 Site status

RFC234 Network Working Group meeting schedule

RFC233 Standardization of host call letters

RFC232 Postponement of network graphics meeting

RFC231 Service center standards for remote usage: A user's view

RFC230 Toward reliable operation of minicomputer-based terminals on a TIP

RFC229 Standard host names

RFC228 Clarification

RFC227 Data transfer rates (Rand/UCLA)

RFC226 Standardization of host mnemonics

RFC225 Rand/UCSB network graphics experiment

RFC224 Comments on Mailbox Protocol

RFC223 Network Information Center schedule for network users

RFC222 Subject: System programmer's workshop

RFC221 Mail Box Protocol: Version 2

RFC220 Not Issued

RFC219 User's view of the datacomputer

RFC218 Changing the IMP status reporting facility

RFC217 Specifications changes for OLS

RFC216 Telnet access to UCSB's On-Line System


RFC214 Network checkpoint

RFC213 IMP System change notification

RFC212 NWG meeting on network usage

RFC211 ARPA Network mailing lists

RFC210 Improvement of Flow Control

RFC209 Host/IMP interface documentation

RFC208 Address tables

RFC207 September Network Working Group meeting

RFC206 User Telnet - description of an initial implementation

RFC205 NETCRT - a character display protocol

RFC204 Sockets in use

RFC203 Achieving reliable communication

RFC202 Possible Deadlock in ICP

RFC201 Not Issued

RFC200 RFC list by number

RFC199 Suggestions for a network data-tablet graphics protocol

RFC198 Site Certification - Lincoln Labs 360/67

RFC197 Initial Connection Protocol - Reviewed

RFC196 Mail Box Protocol

RFC195 Data computers-data descriptions and access language

RFC194 The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes


RFC192 Some factors which a Network Graphics Protocol must consider

RFC191 Graphics implementation and conceptualization at Augmentation Research Center

RFC190 DEC PDP-10-IMLAC communications system

RFC189 Interim NETRJS specifications

RFC188 Data management meeting announcement

RFC187 Network/440 Protocol Concept

RFC186 Network graphics loader

RFC185 NIC distribution of manuals and handbooks

RFC184 Proposed graphic display modes

RFC183 EBCDIC codes and their mapping to ASCII

RFC182 Compilation of list of relevant site reports

RFC181 Modifications to RFC 177

RFC180 File system questionnaire

RFC179 Link Number Assignments

RFC178 Network graphic attention handling

RFC177 Device independent graphical display description

RFC176 Comments on "Byte size for connections"

RFC175 Comments on "Socket Conventions Reconsidered"

RFC174 UCLA - Computer Science Graphics Overview

RFC173 Network Data Management Committee Meeting Announcement

RFC172 The File Transfer Protocol

RFC171 The Data Transfer Protocol

RFC170 RFC List by Number

RFC169 Computer networks

RFC168 ARPA Network mailing lists

RFC167 Socket conventions reconsidered

RFC166 Data Reconfiguration Service: An implementation specification

RFC165 Proffered official Initial Connection Protocol

RFC164 Minutes of Network Working Group meeting

RFC163 Data transfer protocols


RFC161 Solution to the race condition in the ICP

RFC160 RFC brief list

RFC159 Not Issued

RFC158 Telnet Protocol: A Proposed Document

RFC157 Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems

RFC156 Status of the Illinois site: Response to RFC 116

RFC155 ARPA Network mailing lists

RFC154 Exposition Style

RFC153 SRI ARC-NIC status

RFC152 SRI Artificial Intelligence status report

RFC151 Comments on a proffered official ICP: RFCs 123

RFC150 Use of IPC Facilities: A Working Paper

RFC149 Best Laid Plans

RFC148 Comments on RFC 123

RFC147 Definition of a socket

RFC146 Views on issues relevant to data sharing on computer networks

RFC145 Initial Connection Protocol Control Commands

RFC144 Data sharing on computer networks

RFC143 Regarding proffered official ICP

RFC142 Time-Out Mechanism in the Host-Host Protocol

RFC141 Comments on RFC 114: A File Transfer Protocol

RFC140 Agenda for the May NWG meeting

RFC139 Discussion of Telnet Protocol

RFC138 Status report on proposed Data Reconfiguration Service

RFC137 Telnet Protocol - a proposed document

RFC136 Host accounting and administrative procedures

RFC135 Response to NWG/RFC 110

RFC134 Network Graphics meeting

RFC133 File Transfer and Error Recovery

RFC132 Typographical Error in RFC 107

RFC131 Response to RFC 116: May NWG meeting

RFC130 Response to RFC 111: Pressure from the chairman

RFC129 Request for comments on socket name structure

RFC128 Bytes

RFC127 Comments on RFC 123

RFC126 Graphics Facilities at Ames Research Center

RFC125 Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream

RFC124 Typographical error in RFC 107

RFC123 Proffered Official ICP

RFC122 Network specifications for UCSB's Simple-Minded File System

RFC121 Network on-line operators

RFC120 Network PL1 subprograms

RFC119 Network Fortran subprograms

RFC118 Recommendations for facility documentation

RFC117 Some comments on the official protocol

RFC116 Structure of the May NWG Meeting

RFC115 Some Network Information Center policies on handling documents

RFC114 File Transfer Protocol

RFC113 Network activity report: UCSB Rand

RFC112 User/Server Site Protocol: Network host questionnaire responses

RFC111 Pressure from the Chairman

RFC110 Conventions for using an IBM 2741 terminal as a user console for access to network server hosts

RFC109 Level III Server Protocol for the Lincoln Laboratory NIC 360/67 Host

RFC108 Attendance list at the Urbana NWG meeting

RFC107 Output of the Host-Host Protocol Glitch Cleaning Committee

RFC106 User/Server Site Protocol Network Host Questionnaire

RFC105 Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB

RFC104 Link 191

RFC103 Implementation of Interrupt Keys

RFC102 Output of the Host-Host Protocol glitch cleaning committee

RFC101 Notes on the Network Working Group meeting

RFC100 Categorization and guide to NWG/RFCs

RFC99 Network Meeting

RFC98 Logger Protocol Proposal

RFC97 First Cut at a Proposed Telnet Protocol

RFC96 An Interactive Network Experiment to Study Modes of Access the Network Information Center

RFC95 Distribution of NWG/RFC's through the NIC

RFC94 Some thoughts on Network Graphics

RFC93 Initial Connection Protocol

RFC92 Not Issued

RFC91 Proposed User-User Protocol

RFC90 CCN as a Network Service Center

RFC89 Some historic moments in networking

RFC88 NETRJS: A third level protocol for Remote Job Entry

RFC87 Topic for Discussion at the Next Network Working Group Meeting

RFC86 Proposal for a Network Standard Format for a Data Stream to Control Graphics Display

RFC85 Network Working Group meeting

RFC84 List of NWG/RFC's 1-80

RFC83 Language-machine for data reconfiguration

RFC82 Network Meeting Notes

RFC81 Request for Reference Information

RFC80 Protocols and Data Formats

RFC79 Logger Protocol error

RFC78 NCP Status Report: UCSB/Rand

RFC77 Network meeting report

RFC76 Connection by name: User oriented protocol

RFC75 Network Meeting

RFC74 Specifications for network use of the UCSB On-Line System

RFC73 Response to NWG/RFC 67

RFC72 Proposed Moratorium on Changes to Network Protocol

RFC71 Reallocation in Case of Input Error

RFC70 Note on Padding

RFC69 Distribution List Change for MIT

RFC68 Comments on Memory Allocation Control Commands: CEASE

RFC67 Proposed Change to Host/IMP Spec to Eliminate Marking

RFC66 NIC - third level ideas and other noise

RFC65 Comments on Host/Host Protocol document #1

RFC64 Getting rid of marking

RFC63 Belated Network Meeting Report

RFC62 Systems for Interprocess Communication in a Resource Sharing Computer Network

RFC61 Note on Interprocess Communication in a Resource Sharing Computer Network

RFC60 Simplified NCP Protocol

RFC59 Flow Control - Fixed Versus Demand Allocation

RFC58 Logical Message Synchronization

RFC57 Thoughts and Reflections on NWG/RFC 54

RFC56 Third Level Protocol: Logger Protocol

RFC55 Prototypical implementation of the NCP

RFC54 Official Protocol Proffering

RFC53 Official protocol mechanism

RFC52 Updated distribution list

RFC51 Proposal for a Network Interchange Language

RFC50 Comments on the Meyer Proposal

RFC49 Conversations with S

RFC48 Possible protocol plateau

RFC47 BBN's Comments on NWG/RFC #33

RFC46 ARPA Network protocol notes

RFC45 New Protocol is Coming

RFC44 Comments on NWG/RFC 33 and 36

RFC43 Proposed Meeting

RFC42 Message Data Types

RFC41 IMP-IMP Teletype Communication

RFC40 More Comments on the Forthcoming Protocol

RFC39 Comments on Protocol Re: NWG/RFC #36

RFC38 Comments on Network Protocol from NWG/RFC #36

RFC37 Network Meeting Epilogue

RFC36 Protocol Notes

RFC35 Network Meeting

RFC34 Some Brief Preliminary Notes on the Augmentation Research Center Clock

RFC33 New Host-Host Protocol

RFC32 Some Thoughts on SRI's Proposed Real Time Clock

RFC31 Binary Message Forms in Computer

RFC30 Documentation Conventions

RFC29 Response to RFC 28

RFC28 Time Standards

RFC27 Documentation Conventions

RFC26 Not Issued

RFC25 No High Link Numbers

RFC24 Documentation Conventions

RFC23 Transmission of Multiple Control Messages

RFC22 Host-host control message formats

RFC21 Network meeting

RFC20 ASCII format for network interchange

RFC19 Two protocol suggestions to reduce congestion at swap bound nodes

RFC18 IMP-IMP and HOST-HOST Control Links

RFC17 Some questions re: Host-IMP Protocol


RFC15 Network subsystem for time sharing hosts

RFC14 Not Issued

RFC13 Zero Text Length EOF Message

RFC12 IMP-Host interface flow diagrams

RFC11 Implementation of the Host-Host software procedures in GORDO

RFC10 Documentation conventions

RFC9 Host software

RFC8 Functional specifications for the ARPA Network

RFC7 Host-IMP interface

RFC6 Conversation with Bob Kahn

RFC5 Decode Encode Language (DEL)

RFC4 Network timetable

RFC3 Documentation conventions

RFC2 Host software

RFC1 Host Software

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.