In October 2008 I gave myself a new long term challenge – to read all the IETF (Internet Engineering Task Force) RFC (Request For Comments) – in order – starting from number 1. The IETF RFC are one of the most important collections of documents involved in the building blocks of building the Internet we know today. RFC currently number over 5,500 so reading them all could take some time – as I read them I will list them here with a short (hopefully) interesting observation. Recently added, at the end of this article, is a glossary of regular used acronyms and terms used in this article.

Contents

• Introduction
• Background
• Update Status
• Protocol RFC Chain
• RFC Year By Year
• Glossary
• Further Reading

Background

Most people would agree that it is hard to grasp the size and scope of the Internet we all know and love. It has developed and expanded at such a rate one can only imagine where it will be in five years time, let alone ten years or more. This is one of the main reasons why the Internet Engineering Task Force – otherwise known as the IETF for short – came into being.

The IETF began life back in January 1986, and its main purpose was (and still is) to develop standards on the Internet. It also then promotes these standards as widely as possible, so the internet hopefully develops in a way that is uniform and understandable to all. The IETF is a purely voluntary organisation, and whilst well known companies are frequently a part of the process, any individual is welcome to join. A good example would be a network designer, whose job it is to create efficient and well thought out computer networks. Such a person could contribute greatly to the work of the IETF, as this is one area they are interested in providing uniform standards for.

Part of the work undertaken by the IETF is represented by the RFC system. This is otherwise referred to as the ‘Request For Comments’ system or RFC for short. Each RFC focuses on a specific method or idea for how an aspect of the Internet should work, or alternatively for perhaps refining some current method. A common mistake many people make when looking at RFCs is the assumption each one points to a specific way things should be done. However, the RFC is a discussion forum where ideas are expressed and concepts analysed until everyone, more or less, agrees. This still does not lead directly to a new standard.

One of the roles the IETF takes is the act of checking through these RFCs. They then decide which of them should become accepted widespread standards on the Internet. Furthermore, once an RFC has been published it remains as such. Sometimes it may happen that an error or omission has been spotted in an RFC, but in this case the original would still exist. A brand new RFC would be made which would override the original one.

The role of the Internet Engineering Task Force is ongoing and in depth. It meets three times during the year and everyone is welcome to go along and find out more about what the organisation does. But perhaps suitably for an organisation such as the IETF, it is mainly based online.

Update Status

This section shows the current progress of reading through the RFC, the latest RFC is taken from the RFC Editor page. The RFC Editor page shows the latest 12 RFC.

LATEST PROGRESS: 14% of the way through! (which means I’ve got through 723 of the 5549 RFC).

• Update 12th October 2009
  
  Phew, I have reached RFC1000 “The Request For Comments Reference Guide” by Jon Postel in 1987.

  The latest RFC is RFC5689 which puts me at 17.5%.

• Update 12th September 2009
  
  It has been slow going again but I did get up to RFC803 and into 1981. The latest RFC is RFC5653 which puts me at 14%.
• Update 10th August 2009
  
  It has been slow going again but I did get up to RFC803 and into 1981. The latest RFC is RFC5653 which puts me at 14%.
• Update 15th June 2009
  
  Up to RFC 749 – a little slower than some as there have been some large RFC to work through.
• Update 25th May 2009
  
  Up to RFC723 and into 1977 already. This gets me 13% of the way through the RFC.
• Update 4th May 2009
  
  Up to RFC554. Reached a huge milestone (for me at least). I am now 10% of the way through all the RFC. My next milestone has to be 25% which, given the current latest RFC, would lead me to RFC1385 (A fast ride to November 1992 with Wang talking about EIP: The Extended Internet Protocol A Framework for Maintaining Backward Compatibility).
• Update 19th April 2009
  
  Up to RFC400. Make good progress over the last few weeks and many of the ideas are starting to make sense to me. The last officially released RFC is 5540 celebrating 40 Years of RFCs
• Update 2nd April 2009
  
  Up to RFC292. The latest officially released RFC is 5514.
• Update 7th March 2009
  
  Up to RFC225. The latest officially released RFC is 5487.
• Update 7th February 2009
  
  Up to RFC181. The latest officially released RFC is 5452.
• Update 22nd December 2008
  
  Up to RFC163. The officially released RFC is still 5407 which is a bit of a relief which means we just broke through to being 3% complete.
• Update 16th December 2008
  
  A little slow only up to RFC135 but some interesting observations including the lack of certain modern commonly accepted characters on terminals and outlines of working environments. Interesting to see the discussions on RFC starting to pick up as intended. As of today (16th December 2008) the latest RFC issued is 5407 – so I am currently 2.5% of the way through.
• Update 9th December 2008
  
  Up to RFC125, the evenings are getting later and the mornings earlier as I work through these documents. Managed 40 documents over the last 9 days which is just over four per day. Admittedly three days were spent on RFC114 talking about FTP otherwise this figure may have been closer to five. Trying to get my head around concepts that were commonplace fourty years ago give me brain ache but I’m staying in there for the moment. As of today (9th Dec 2008) the latest RFC issued is 5401 – so I am currently 2.3% of the way through.
• Update 1st December 2008
  
  I’ve reached 1971 with 85 RFC in the can. 1970 was a little slow going with a lot of reading including the largest RFC  so far – 18 pages may not seem a lot but when you have to cross-refer and lookup a lot of the technical information just to get to grips with it – it can become quite time consuming. The documentation conventions are major factors in the RFC system and although broken in a few areas they really help consolidate and bind the documents. There are 204 RFC to read in 1971 so it looks like in 1971 the RFC thing is really starting to take off.
• Update 1st November 2008
  
  So far I am up to June 1970 with 55 RFC under my belt and a couple of real eye openers too. Before I started reading these I thought I wouldn’t find anything particularly interesting until I got into the hundreds. Who would have thought I would be talking about Telnet, Java, and XML already. In RFC54 we have a first official protocol draft for host to host communications over a network.

PROTOCOL RFC CHAIN

I am aiming to maintain this section to link related RFC as currently in the RFC there is no reference as to which RFC are related to each other.

Telnet RFC 318

File Transfer RFC 354 & RFC 385

Remote Job Entry RFC 407

Echo RFC 347

Discard RFC 348

Character Generator RFC 429

Speech Data Base SUR 37

Datacomputer [Murray @ CCA]

NCP Measurment RFC 388

Survey Data [Kampe @ NMC]

LINK [Bressler @ BBN]

FTP

RFCs covering the File Transfer Protocol.

• RFC114
• RFC141
• RFC172
• RFC238
• RFC250
• RFC265
• RFC269
• RFC281
• RFC542
• RFC506

DTP

RFCs covering the Data Transfer Protocol.

• RFC171
• RFC238
• RFC250
• RFC264

DEL

RFCs covering the DEL program

• RFC5

Mail Box Protocol

• RFC221
• RFC278

RFCs covering the Mail Box Protocol

NCP

• RFC117

REMOTE JOB SERVICE (RJS) Protocol and NETRJT

RFCs covering the RJS protocol

• RFC281
• RFC283

TELNET

RFCs covering the Telnet protocol

• RFC15
• RFC106
• RFC111
• RFC137
• RFC139
• RFC158

Host-To-Host

• RFC1
• RFC2
• RFC142

Administrative RFC

I am including this as it helps to describe the evolution of the RFC system itself

• RFC3
• RFC155
• RFC160

RFC Year By Year

From 1969 onwards the RFC system was operated, each of the years RFC are broken down below – as I get through them.

• 1987 (RFC996 onwards)
• 1986 (RFC971 to RFC995)
• 1985 (RFC930 to RFC970)
• 1984 (RFC888 to RFC929)
• 1983 (RFC836 to RFC887)
• 1982 (RFC800 to RFC835)
• 1981 (RFC775 to RFC799)
• 1980 (RFC759 to RFC774)
• 1979 (RFC752 to RFC758)
• 1978 (RFC744 to RFC751)
• 1977 (RFC723 to RFC743)
• 1976 (RFC707 to RFC722)
• 1975 (RFC703 to RFC706)
• 1974 (RFC607 to RFC702)
• 1973 (RFC434 to RFC606)
• 1972 (RFC290 to RFC433)
• 1971 (RFC86 to RFC289)
• 1970 (RFC28 to RFC85)
• 1969 (RFC1 to RFC27)

1987 (RFC996 onwards)

RFC1000 [Aug 1987] “THE REQUEST FOR COMMENTS REFERENCE GUIDE” p(149).

Postel and Reynolds give us a huge reference guide for the RFC system – it summarises all the RFC issued so far. I love Crockers introduction “The DDN community now includes hundreds of nodes and thousands of users, but once it was all a gleam in Larry Roberts’ eye. While much of the development proceeded according to a grand plan, the design of the protocols and the creation of the RFCs was largely accidental.”

RFC999 [Aug 1987] “Requests For Comments Summary Notes: 900-999” p(22)

Postel and Westine produce a summary of RFC900 to RFC999.

RFC998 [Mar 1987] “NETBLT: A Bulk Data Transfer Protocol” p(21)

A description of the NETBLT protocol which is a transport level protocol for fast transfer of huge amounts of data between computer devices.

RFC997 [Mar 1987] “INTERNET NUMBERS” p(42)

An update of the network number in use by the Internet community including an explanation of the 32-bit, 4 octet, addressing system that we are familiar with today.

RFC996 [Feb 1987] "Statistics Server” p(3)

D.L. Mills Suggests a standard to remote statistics monitoring.

1986 (RFC971 to RFC995)

RFC995 [Apr 1986] “ISO/TC 97/SC 6 | | TELECOMMUNICATIONS AND INFORMATION | | EXCHANGE BETWEEN SYSTEMS” p(41)

RFC994 [Mar 1986] “ISO/TC 97/SC 6 | | TELECOMMUNICATIONS AND INFORMATION | | EXCHANGE BETWEEN SYSTEMS” p(52)

RFC993 [Dec 1986] “PCMAIL: A Distributed Mail System for Personal Computers” p(28)

RFC992 [Nov 1986] “On Communication Support for Fault Tolerant Process Groups” p(18)

RFC991 [Nov 1986] “OFFICIAL ARPA-INTERNET PROTOCOLS” p(46)

RFC990 [Nov 1986] “ASSIGNED NUMBERS” p(75)

RFC989 [Feb 1987] “Privacy Enhancement for Internet Electronic Mail: Part I: Message Encipherment and Authentication Procedures” p(23)

RFC988 [Jul 1986] “Host Extensions for IP Multicasting” p(20)

RFC987 [Jun 1986] “Mapping between X.400 and RFC 822” p(69)

RFC986 [Jun 1986] “Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol” p(7)

RFC985 [May 1986] “Requirements for Internet Gateways – Draft” p(23)

RFC984 [May 1986] “PCMAIL: A Distributed Mail System for Personal Computers” p(31)

RFC983 [Apr 1986] “ISO Transport Services on Top of the TCP” p(27)

RFC982 [Apr 1986] “Guidelines for the Specification of the Structure of the Domain Specific Part (DSP) of the ISO Standard NSAP Address” p(11)

RFC981 [Mar 1986] “An Experimental Multiple-Path Routing Algorithm” p(22)

RFC980 [Mar 1986] “Protocol Document Order Information” p(12)

RFC979 [Mar 1986] “PSN END-TO-END FUNCTIONAL SPECIFICATION” p(15)

RFC978 [Feb 1986] “VOICE FILE INTERCHANGE PROTOCOL (VFIP)” p(5)

RFC977 [Feb 1986] “A Proposed Standard for the Stream-Based Transmission of News” p(27)

RFC976 [Feb 1986] “UUCP Mail Interchange Format Standard” p(12)

RFC975 [Feb 1986] “Autonomous Confederations” p(10)

RFC974 [Jan 1986] “MAIL ROUTING AND THE DOMAIN SYSTEM” p(7)

RFC973 [Jan 1986] “Domain System Changes and Observations” p(10)

RFC972 [Jan 1986] “Password Generator Protocol” p(2)

RFC971 [Jan 1986] “A SURVEY OF DATA REPRESENTATION STANDARDS” p(9)

1985 (RFC930 to RFC970)

1984 (RFC888 to RFC929)

1983 (RFC836 to RFC887)

1982 (RFC800 to RFC835)

RFC804 [na] “CCITT Draft Recommendation T.4” p(11).

RFC803 [2 Nov 1981] “Dacom 450/500 Facsimile Data Transcoding” p(14).

RFC802 [Nov 1981] “RFC 802: The ARPANET 1822L Host Access Protocol” p(43).

RFC801 [Nov 1981] “NCP/TCP TRANSITION PLAN” p(1).

RFC800 [Nov 1982] “Requests For Comments Summary Notes: 700-799” p(10).

1981 (RFC775 to RFC 799)

RFC799 [Sep 1981] “Internet Name Domains” p(6).

RFC798 [Sep 1981] “DECODING FACSIMILE DATA FROM THE RAPICOM 450” p(17].

RFC797 [Sep 1981] “FORMAT FOR BITMAP FILES” p(2).

RFC796 [Sep 1981] “ADDRESS MAPPINGS” p(7).

RFC795 [Sep 1981] “SERVICE MAPPINGS” p(4).

RFC794 [Sep 1981] “PRE-EMPTION” p(2).

RFC793 [Sep 1981] “TRANSMISSION CONTROL PROTOCOL DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION” p(85).

RFC792 [Sep 1981] “INTERNET CONTROL MESSAGE PROTOCOL DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION” p(21).

RFC791 [Sep 1981] “INTERNET PROTOCOL DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION” p(45).

RFC790 [Sep 1981] “ASSIGNED NUMBERS” p(15).

RFC789 [na] “Vulnerabilities of Network Control Protocols: An Example” p(15).

RFC788 [Nov 1981] “SIMPLE MAIL TRANSFER PROTOCOL” p(62).

RFC787 [Jul 1981] “Connectionless Data Transmission Survey/Tutorial” p(41).

RFC786 [Jul 1981] “MAIL TRANSFER PROTOCOL: ISI TOPS20 MTP-NIMAIL INTERFACE” p(2).

RFC785 [Jul 1981] “MAIL TRANSFER PROTOCOL: ISI TOPS20 FILE DEFINITIONS” p(3).

RFC784 [Jul 1981] “MAIL TRANSFER PROTOCOL: ISI TOPS20 IMPLEMENTATION” p(3).

RFC783 [Jun 1981] “THE TFTP PROTOCOL (REVISION 2)” p(18).

RFC782 [na] “A Virtual Terminal Management Model” p(20).

RFC781 [May 1981] “A SPECIFICATION OF THE INTERNET PROTOCOL (IP) TIMESTAMP OPTION” p(2).

RFC780 [May 1981] “MAIL TRANSFER PROTOCOL” p(43).

A huge leap in date for this document to four years later than expected. Jon Postel and Suzanna Sluizer submit a proposal for MTP (Mail Transfer Protocol) – a precursor to the SMTP we know today.

RFC779 [Apr 1981] “Telnet send-location option” p(2).

RFC778 [Apr 1981] “DCNET Internet Clock Service” p(5).

RFC777 [Apr 1981] “Internet Control Message Protocol” p(13).

One of the founding protocols for what would become the TCP/IP protocol – in particular the IP Protocol. The first ICMP code 0 is often used to PING (or Echo-Response) a host.

RFC776 [Jan 1981] “ASSIGNED NUMBERS” p(13).

RFC775 [na] “DIRECTORY ORIENTED FTP COMMANDS” p(6).

1980 (RFC759 to RFC774)

RFC774 [Oct 1980] “Internet Protocol Handbook” p(3)

RFC773 [Oct 1980] “COMMENTS ON NCP/TCP MAIL SERVICE TRANSITION STRATEGY” p(11).

RFC772 [Sep 1980] “MAIL TRANSFER PROTOCOL” p(31).

RFC771 [Sep 1980] “MAIL TRANSITION PLAN” p(9).

RFC770 [Sep 1980] “ASSIGNED NUMBERS” p(15).

RFC769 [26 Sep 1980] “Rapicom 450 Facsimile File Format” p(2).

RFC768 [28 Aug 1980] “User Datagram Protocol” p(3).

RFC767 [Aug 1980] “A STRUCTURED FORMAT FOR TRANSMISSION OF MULTI-MEDIA DOCUMENTS” p(34).

RFC766 [Jul 1980] “Internet Protocol Handbook” p(2).

RFC765 [Jun 1980] “FILE TRANSFER PROTOCOL” p(70).

RFC764 [Jun 1980] “TELNET PROTOCOL SPECIFICATION” p(15).

RFC763 [7 May 1980] “ROLE MAILBOXES” p(1)

A note from Marshall Abrams talking about early distribution groups, or “MAIL address synonyms” as he refers to it.

RFC762 [Jan 1980] “ASSIGNED NUMBERS” p(13)

Jon Postel outlines the current network protocol assigned numbers such as TELENET on 14, ARPANET on 10, and DIALNET on 22.

RFC761 [Jan 1980] “DOD STANDARD TRANSMISSION CONTROL PROTOCOL” p(84)

What a whopper!" A description of the DoD TCP (Transmission Control Protocol). With RFC760 we now have TCP and IP together.

RFC760 [Jan 1980]  “DOD STANDARD INTERNET PROTOCOL” p(42).

“The Internet Protocol is designed for use in interconnected systems of packet-switched computer communication networks.”

RFC759 [Aug 1980] “INTERNET MESSAGE PROTOCOL” p(71).

Jon Postel outlines IMP.

1979 (From RFC752 to RFC758)

RFC758 [Aug 1979] “ASSIGNED NUMBERS” p(12).

RFC757 [10 Sep 1979] “A Suggested Solution to the Naming, Addressing, and Delivery Problem for ARPAnet Message Systems” p(10)

RFC756 [Jul 1979] “The NIC Name Server–A Datagram Based Information Utility” p(10).

RFC755 [May 1979] “ASSIGNED NUMBERS” p(12).

RFC754 [Apr 1979] “Out-of-Net Host Addresses for Mail” p(10)

RFC753 [Mar 1979] “INTERNET MESSAGE PROTOCOL” p(56)

RFC752 [2 Jan 1979] “A Universal Host Table” p(11).

1978 (RFC744 to RFC751)

RFC751 [10 Dec 1978] “SURVEY OF FTP MAIL AND MLFL” p(5)

RFC750 [26 Sep 1978] “ASSIGNED NUMBERS” p(12)

RFC749 [18 Sep 1978] “Telnet SUPDUP-OUTPUT Option” p(4)

RFC748 [1 Apr 1978] “TELNET RANDOMLY-LOSE Option” p(2)

RFC747 [21 Mar 1978] “Recent Extensions to the SUPDUP Protocol” p(1)

RFC746 [17 Mar 1978] “The SUPDUP Graphics Extension” p(15)

RFC745 [30 Mar 1978] “JANUS Interface Specifications (Symmetrical, 1822-like Interface)” p(10)

RFC744 [8 Jan 1978] “MARS – A Message Archiving & Retrieval Service” p(6)

1977 (RFC723 to RFC743)

RFC743 [30 Dec 1977] “FTP extension: XRSQ/XRCP” p(8)

RFC742 [30 Dec 1977] “NAME/FINGER” p(7)

RFC741 [22 Nov 1977] “SPECIFICATIONS FOR THE NETWORK VOICE PROTOCOL (NVP)” p(30)

RFC740 [22 Nov 1977] “NETRJS PROTOCOL” p(19)

RFC739 [11 Nov 1977] “ASSIGNED NUMBERS” p(11)

RFC738 [31 Oct 1977] “Time Server” p(1)

RFC737 [31 Oct 1977] “FTP Extension: XSEN” p(1)

RFC736 [31 Oct 1977] “TELNET SUPDUP Option” p(2)

RFC735 [3 Nov 1977] “Revised TELNET Byte Macro Option” p(5)

RFC734 [7 Oct 1977] “SUPDUP Protocol” p(14)

RFC733 [21 Nov 1977] “STANDARD FOR THE FORMAT OF ARPA NETWORK TEXT MESSAGES(1)” p(38)

RFC732 [12 Sep 1977] “Telnet Data Entry Terminal Option” p(30)

RFC731 [27 Jun 1977] “Telnet Data Entry Terminal Option” p(28)

RFC730 [20 May 1977] “Extensible Field Addressing” p(5).

RFC729 [13 May 1977] “TELNET Byte Macro Option” p(4).

Dave Crocker, from Rand-ISD, suggests the addition of byte macro for the Telnet protocol. The Byte Macro will allow for blocks much smaller than five or ten bytes – for example in the cases of a block separator. This could reduce the amount of traffic sent over the line.

RFC728 [Apr 1977] “A Minor Pitfall in the Telnet Protocol” p(1).

John Day highlights a situation, with the sync sequence, which could lead to unexpected behaviour from the Telnet connection.

RFC727 [26 Apr 1977] “Telnet Logout Option” p(3).

RFC726 [8 May 1977] “Remote Controlled Transmission & Echoing Telnet Option” p(16).

RFC725 [25 Apr 1977] “An RJE Protocol for a Resource Sharing Network” p(26).

RFC724 [12 May 1977] “Proposed Official Standard for the Format of ARPA Network Messages” p(33).

RFC723 was never issued.

1976 (RFC707 to RFC722)

In 1976 it looks like RFC publishing is picking up again, albeit slowly.

RFC722 [Sep 1976] “the interaction of two programs which support some network service” p(14).

RFC721 [1 Sep 1976] “Out-of-Band Control Signals in a Host-to-Host Protocol” p(7).

RFC720 [Aug 1976] “Address Specification Syntax for Network Mail” p(4).

RFC719 [Jul 1976] “Discussion on RCTE” p(2).

RFC718 [Jun 1976] “Comments on RCTE from the TENEX Implementation Experience” p(2).

RFC717 [1 Jul 1976] “Assigned Network Numbers” p(2).

RFC716 [24 May 1976] “Interim Revision to Appendix F of BBN Report 1822” p(2).

RFC715 [na] “na” p(na).

RFC715 was never issued.

RFC714 [na] “na” p(na).

RFC714 does not exist.

RFC713 [Apr 1976] “a mechanism developed for use by message servers communicating over an eight-bit byte-oriented network connection to move data structures and associated data-typing information” p(22).

RFC712 [na] “na” p(na).

RFC712 does not exist.

RFC711 [na] “na” p(na).

RFC711 was never issued.

RFC710 [na] “na” p(na).

RFC710 was never issued.

RFC709 [na] “na” p(na).

RFC709 was never issued.

RFC708 [5 Jan 1976] “Elements of a Distributed Programming System” p(30).

RFC707 [14 Jan 1976] “A High-Level Framework for Network-Based Resource Sharing” p(28).

1975 (RFC703 to RFC706)

A very short year for RFC work with only four RFC being published.

RFC706 [Nov 1975] “On the Junk Mail Problem” p(1).

First RFC to specifically talk about the problem of junk electronic mail.

RFC705 [2 Sep 1975] “FRONT – END PROTOCOL B6700 VERSION” p(38).

RFC704 [Sep 1975] “IMP/Host and Host/IMP Protocol Change” p(3).

RFC703 [11 Jul 1975] “July, 1975, Survey of New-Protocol TELNET Servers” p(3).

1974 (RFC607 to RFC702)

Heading into 1973 talking more about data management and data sharing.

RFC702 [25 Sep 1974] “SEPTEMBER, 1974, SURVEY OF NEW-PROTOCOL TELNET SERVERS” p(3).

RFC701 [Aug 1974] “AUGUST, 1974, SURVEY OF NEW-PROTOCOL TELNET SERVERS” p(2).

RFC700 [Aug 1974] “A Protocol Experiment” p(7).

RFC699 [Nov 1982] “Requests For Comments Summary Notes: 600-699” p(9).

Curious why this RFC is dated 1982 – but it does serve as a useful cross check for existing RFC up to 699.

RFC698 [Jul 1975] “TELNET EXTENDED ASCII OPTION” p(4).

RFC697 [14 Jul 1975] “CWD Command of FTP” p(2).

RFC696 [na] “na” p(na).

RFC696 does not exist.

RFC695 [5 Jul 1975] “Official Change in Host-Host Protocol” p(1).

RFC694 [na] “na” p(na).

RFC694 does not exist.

RFC693 [na] “na” p(na).

RFC693 was never issued.

RFC692 [20 Jun 1975] “COMMENTS ON IMP/HOST PROTOCOL CHANGES, (RFCS 687 AND 690)” p(2).

RFC691 [28 May 1975] “One More Try on the FTP” p(13).

RFC690 [6 Jun 1975] “Comments on the proposed Host/IMP Protocol Change” p(3).

RFC689 [May 1975] “TENEX NCP Finite State Machine for connections TENEX Memo Number 155” p(6).

RFC688 [4 Jun 1975] “Tentative Schedule for the New TELNET Implementation for the TIP” p(1).

RFC687 [Jun 1975] “IMP/Host and Host/IMP Protocol Change” p(3).

RFC686 [10 May 1975] “Leaving Well Enough Alone” p(9).

RFC685 [16 Apr 1975] “Response Time in Cross-network Debugging” p(4).

RFC684 [15 Apr 1975] “A Commentary on Procedure Calling as a Network Protocol” p(8).

RFC683 [3 Apr 1975] “FTPSRV – TENEX FTP EXTENSIONS FOR PAGED FILES” p(2).

RFC682 [na] “na” p(na).

RFC682 was never issued.

RFC681 [14 May 1975] “NETWORK UNIX” p(6).

RFC680 [30 Apr 1975] “Message Transmission Protocol” p(6).

RFC679 [na] “na” p(na).

RFC679 does not exist.

RFC678 [19 Dec 1974] “Standard File Formats” p(8).

RFC677 [27 Jan 1975] “The Maintenance of Duplicate Databases” p(10).

RFC676 [na] “na” p(na).

RFC676 was never issued.

RFC675 [Dec 1974] “SPECIFICATION OF INTERNET TRANSMISSION CONTROL PROGRAM” p(70).

RFC674 [11 Dec 1974] “Procedure Call Protocol Documents Version 2” p(4).

RFC673 [na] “na” p(na).

RFC673 was never issued.

RFC672 [Dec 1974] “A Multi-Site Data Collection Facility” p(10)

RFC671 Not Available

RFC670 Never Issued

RFC669 [4 Dec 1974] “November, 1974, Survey of New-Protocol TELNET Servers” p(3)

RFC668 Never Issued

RFC667 [Dec 1974] “Host Ports” p(2)

RFC666 [26 Nov 1974] “Specification of the Unified User-Level Protocol” p(19)

RFC665 Never Issued

RFC664 Never Issued

RFC663 [29 Nov 1974] “A LOST MESSAGE DETECTION AND RECOVERY PROTOCOL” p(19)

RFC662 [Nov 1974] “PERFORMANCE IMPROVEMENT IN ARPANET FILE TRANSFERS FROM MULTICS” p(3)

RFC661 Not Available

RFC660 [Oct 1974] “SOME CHANGES TO THE IMP AND THE IMP/HOST INTERFACE” p(2)

RFC659 [18 Oct 1974] “Announcing Addtional Telnet Options” p(1)

RFC658 [25 Oct 1974] “TELNET OUTPUT LINEFEED DISPOSITION” p(4)

RFC657 [25 Oct 1974] “TELNET OUTPUT VERTICAL TAB DISPOSITION OPTION” p(3)

RFC656 [25 Oct 1974] “TELNET OUTPUT VERTICAL TABSTOPS OPTION” p(2)

RFC655 [25 Oct 1974] “TELNET OUTPUT FORMFEED DISPOSITION OPTION” p(2)

RFC654 [25 Oct 1974] “TELNET OUTPUT HORIZONTAL TAB DISPOSITION OPTION” p(2)

RFC653 [25 Oct 1974] “TELNET OUTPUT HORIZONTAL TABSTOPS OPTION” p(2)

RFC652 [25 Oct 1974] “Telnet Output Carriage-Return Disposition Option” p(3)

RFC651 [25 Oct 1974] “Revised Telnet Status Option” p(2)

RFC650 Never Issued

RFC649 Never Issued

RFC648 Never Issued

RFC647 Not Available

RFC646 Never Issued

RFC645 Not Available

RFC644 [Jul 1974] “On the Problem of Signature Authentication for Network Mail” p(4)

RFC643 [Jul 1974] “Network Debugging Protocol” p(8)

RFC642 [5 Jul 1974] “Ready Line Philosophy and Implementation” (4)

RFC641 Never Issued

RFC640 [19 Jun 1975] “Revised FTP Reply Codes” p(26)

RFC639 Never Issued

RFC638 [25 Apr 1974] “IMP/TIP Preventive Maintenance Schedule” p(4)

RFC637 [23 Apr 1974] “CHANGE OF NETWORK ADDRESS FOR SU-DSL” p(1)

RFC636 [23 Oct 1974] “TIP/TENEX Reliability Improvements” p(6)

RFC635 [May 1974] “An Assessment of ARPANET Protocols” p(20)

RFC634 [10 Apr 1974] “Change in Network Address for Haskins Lab” p(1)

RFC633 [18 Mar 1974] “IMP/TIP Preventive Maintenance Schedule” p(4)

RFC632 [20 May 1974] “Throughput Degradations for Single Packet Messages” p(6)

RFC631 [17 Apr 1974] “International Meeting on Mini-Computers and Data Communication” p(2)

RFC630 [10 Apr 1974] “FTP Error Code Usage for More Reliable Mail Service” p(3)

RFC629 [27 Mar 1974] “SCENARIO FOR USING THE NETWORK JOURNAL” p(3)

RFC628 [27 Mar 1974] “Status of RFC Numbers and a Note on Pre-assigned Journal Numbers” p(1)

RFC627 [25 Mar 1974] “ASCII TEXT FILE OF HOSTNAMES” p(1)

RFC626 [Mar 1974] “On a Possible Lockup Condition in the IMP Subnet Due to Message Sequencing" p(6)

RFC625 [7 Mar 1974] “ON LINE HOSTNAMES SERVICE” p(1)

RFC624 [Feb 1974] “Comments on the File Transfer Protocol” p(3)

RFC623 [22 Feb 1974] “Comments on On-Line Host Name Service” p(2)

RFC622 [13 Mar 1974] “Scheduling IMP/TIP Down Time” p(3)

RFC621 [6 Mar 1974] “NIC USER DIRECTORIES AT SRI-ARC” p(1)

RFC620 [Mar 1974] “Request for Monitor Host Table Updates” p(1)

RFC619 [7 Mar 1974] “Mean Round-Trip Times in the ARPANET” p(14)

RFC618 [Feb 1974] “A Few Observations on NCP Statistics” p(4)

RFC617 [Feb 1974] “A Note on Socket Number Assignment 2” p(4)

RFC616 [11 Feb 1974] “LATEST NETWORK MAPS” p(1)

RFC615 [Mar 1974] “Proposed Network Standard Data Pathname Syntax” p(5)

RFC614 [Jan 1974] “Response to RFC 607, "Comments on the File Transfer Protocol”" p(4)

RFC613 [Jan 1974] “Network Connectivity: A Response to RFC 603” p()

RFC612 [16 Jan 1974] “Traffic Statistics (December 1973)” p(6).

RFC611 [14 Feb 1974] “TWO CHANGES T0 THE IMP/HOST PROTOCOL TO IMPROVE USER/NETWORK COMMUNICATIONS*” p(4).

RFC610 [15 Dec 1973] “Further Datalanguage Design Concepts” p(88).

RFC609 [10 Jan 1974] “Statement of Upcoming Move of NIC/NLS Services” p(1).

RFC608 [10 Jan 1974] “HOST NAMES ON-LINE” p(4).

RFC607 [Jan 1974] “Comments on the File Transfer Protocol” p(3).

1973 (RFC434 to RFC606)

RFC606 [Dec 1973] “Host Names On-line” p(3).

RFC605 [na] “na” p(na).

RFC605 was never issued.

RFC604 [26 Dec 1973] “Assigned Link Numbers” p(2).

RFC603 [31 Dec 1973] “Response to RFC # 597: Host Status” p(1).

RFC602 [Dec 1973] “"The Stockings Were Hung by the Chimney with Care"” p(1).

Bob Metcalfe highlight, with an interesting title, three security issues facing the computer network.

RFC601 [14 Dec 1973] “Traffic Statistics (November 1973)” p(5).

RFC600 [na] “na” p(na).

RFC600 is not available.

RFC599 [13 Dec 1973] “UPDATE ON NETRJS” p(9).

RFC598 [na] “na” p(na).

RFC598 is not available.

RFC597 [12 Dec 1973] “Host Status” p(6).

RFC596 [8 Dec 1973] “Second Thoughts on Telnet Go-Ahead” p(5).

RFC595 [12 Dec 1973] “Some Thoughts in Defense of the TELNET Go-Ahead” p(5).

RFC594 [na] “na” p(na).

RFC594 is not available.

RFC593 [na] “Telnet and FTP Implementation Schedule Change” p(1).

RFC592 [na] “na” p(na).

RFC592 is not available.

RFC591 [29 Nov 1973] “Addition to the Very Distant Host Specification” p(1).

RFC590 [19 Nov 1973] “Multics Address Change” p(1).

RFC589 [26 Nov 1973] “CCN NETRJS SERVER MESSAGES TO REMOTE USER” p(5).

RFC588 [na] “na” p(na).

RFC588 is not available.

RFC587 [Nov 1973] “Announcing New Telnet Options” p(1).

RFC586 [na] “na” p(na).

RFC586 is not available.

RFC585 [6 Nov 1973] “Arpanet Users Interest Working Group Meeting” p(9).

RFC584 [6 Nov 1973] “Charter for Arpanet Users Interest Working Group” p(2).

RFC583 [na] “na” p(na).

RFC583 was never issued.

RFC582 [5 Nov 1973] “Comments on RFC 580 – Machine Readable Protocols” p(1).

RFC581 [na] “na” p(na).

RFC581 was never issued.

RFC580 [25 Oct 1973] “note to protocol designers and implementers” p(1).

RFC579 [na] “na” p(na).

RFC579 was never issued.

RFC578 [na] “na” p(na).

RFC578 was never issued.

RFC577 [na] “na” p(na).

RFC577 was never issued.

RFC576 [na] “na” p(na).

RFC576 was never issued.

RFC575 [na] “na” p(na).

RFC575 was never issued.

RFC574 [26 Sep 1973] “Announcement of a Mail Facility at UCSB” p(1).

RFC573 [14 Sep 1973] “DATA AND FILE TRANSFER – SOME MEASUREMENT RESULTS” p(8).

RFC572 [na] “na” p(na).

RFC572 was never issued.

RFC571 [15 Nov 1973] “TENEX FTP PROBLEM” p(1).

RFC570 [na] “na” p(na).

RFC570 is not available.

RFC569 [15 Oct 1973] “NETED: A Common Editor for the ARPA Network” p(7).

RFC568 [18 Sep 1973] “Response to RFC 567 — Cross-Country Network Bandwidth” p(2).

RFC567 [6 Sep 1973] “CROSS-COUNTRY NETWORK BANDWIDTH” p(1).

RFC566 [4 Sep 1973] “Traffic Statistics (August 1973)” p(4).

RFC565 [28 Aug 1973] “Storing Network Survey Data at the Datacomputer” p(5).

RFC564 [na] “na” p(na).

RFC564 was never issued.

RFC563 [28 Aug 1973] “Comments on the RCTE TELNET Option” p(5).

RFC562 [28 Aug 1973] “Modifications to the TELNET Specification” p(2).

RFC561 [5 Sep 1973] “Standardizing Network Mail Headers” p(3).

RFC560 [20 Aug 1973] “Remote Controlled Transmission & Echoing TELNET Option” p(12).

RFC559 [15 Aug 1973] “Comments on the new TELNET Protocol and its Implementation” p(5).

RFC558 [na] “na” p(na).

RFC558 was never issued.

RFC557 [30 Aug 1973] "REVELATIONS IN NETWORK HOST MEASUREMENTS” p(2).

RFC556 [13 Aug 1973] “Traffic Statistics (July 1973)” p(4).

RFC555 [27 Jul 1973] “Response to Critiques of the Proposed Mail Protocol” p(11).

RFC554 [na] “na” p(na)

RFC554 was never issued.

RFC553 [14 Jul 1973] “Draft design for a text/graphics protocol” p(19).

RFC552 [13 Jul 1973] “Single access to Standard Protocols” p(1).

RFC551 [na] “na” p(na).

RFC551 does not exist.

RFC550 [24 Aug 1973] “NIC NCP EXPERIMENT” p(2).

RFC549 [15 Jul 1973] “MINUTES OF NETWORK GRAPHICS GROUP MEETING” p(12).

RFC548 [16 Aug 1973] “Hosts Using the IMP Going Down Message” p(1).

RFC547 [13 Aug 1973] “Change to the Very Distant Host Specification” p(3).

RFC546 [10 Aug 1973] “TENEX Load Averages for July 1973” p(4).

RFC545 [23 Jul 1973] “OF WHAT QUALITY BE THE UCSB RESOURCE EVALUATORS? A Response to "Feast of Famine"” p(2).

RFC544 [13 Jul 1973] “Locating On-Line Documentation at SRI-ARC” p(1).

RFC543 [31 Jul 1973] “Network Journal Submission and Delivery” p(8).

RFC542 [12 Aug 1973] “File Transfer Protocol for the ARPA Network” p(39).

RFC541 [na] “na” p(na).

RFC541 was never issued.

RFC540 [na] “na” p(na).

RFC540 was never issued.

RFC539 [9 Jul 1973] “Thoughts on the Mail Protocol Proposed in RFC 524” p(3).

RFC538 [5 Jul 1973] “Traffic Statistics (June 1973)” p(4).

RFC537 [27 Jun 1973] “Announcement of NGG meeting-JULY 16-17” p(2).

RFC536 [na] “na” p(na).

RFC536 was never issued.

RFC535 [na] “na” p(na).

RFC535 does not exist.

RFC534 [17 Jul 1973] “Lost Message Detection” p(2).

RFC533 [17 Jul 1973] “MESSAGE-ID NUMBERS” p(1).

RFC532 [12 Jul 1973] “The UCSD-CC Server-FTP Facility” p(4).

RFC531 [26 Jun 1973] “Feast or famine? A Response to Two Recent RFC’s About Network Information” p(2).

RFC530 [na] “na” p(na).

RFC530 does not exist.

RFC529 [29 Jun 1973] “A Note on Protocol Synch Sequences” p(4).

RFC528 [20 Jun 1973] “SOFTWARE CHECKSUMMING IN THE IMP AND NETWORK RELIABILITY” p(9).

RFC527 [22 Jun 1973] “ARPAWOCKY” p(1).

Interesting little poem about the work of the Arpanet.

RFC526 [25 Jun 1973] “Technical Meeting Digital Image Processing Software Systems” p(3).

RFC525 [1 Jun 1973] “MIT-MATHLAB MEETS UCSB-OLS: An Example of Resource Sharing” p(9).

RFC524 [13 Jun 1973] “A Proposed Mail Protocol” p(40).

RFC523 [5 Jun 1973] “SURVEY is in Operation Again” p(2).

RFC522 [na] “na” p(na).

RFC522 does not exist.

RFC521 [30 May 1973] “Restricted Use of IMP DDT” p(2).

RFC520 [25 Jun 1973] “A Proposed File Access Protocol Specification” p(8).

RFC519 [Jun 1973] “Resource Evaluation” p(4).

RFC518 [19 Jun 1973] “ARPANET ACCOUNTS” p(9).

RFC517 [na] “na” p(na).

RFC517 was never issued.

RFC516 [18 May 1973] “LOST MESSAGE DETECTION” p(2).

RFC515 [6 Jun 1973] “Specifications for Datalanguage, Version 0/9” p(31).

RFC514 [5 Jun 1973] “NETWORK MAKE-WORK” p(4).

RFC513 [30 May 1973] “COMMENTS ON THE NEW TELNET SPECIFICATIONS” p(3).

RFC512 [25 May 1973] “MORE ON LOST MESSAGE DETECTION” p(2).

RFC511 [23 May 1973] “Enterprise Phone Service to NIC From ARPANET Sites” p(3).

RFC510 [30 May 1973] “Request for Network Mailbox Addresses” p(2).

RFC509 [7 May 1973] “Traffic Statistics (April 1973)” p(4).

RFC508 [7 May 1973] “REAL-TIME DATA TRANSMISSION ON THE ARPANET” p(10).

RFC507 [na] “na” p(na).

RFC507 was never issued.

RFC506 [26 Jun 1973] “An FTP Command-Naming Problem” p(1).

RFC505 [25 Jun 1973] “Two Solutions to a File Transfer Access Problem” p(3).

RFC504 [30 Apr 1973] “Workshop Announcement” p(5).

RFC503 [13 Apr 1973] “Socket Number List” p(8).

Socket Assignments

• 1 Telnet
• 3 File Transfer
• 5 Remote Job Entry
• 7 Echo
• 9 Discard
• 11 Systat or who-is-on function
• 13 Date-Time function
• 15 Netstat or who-is-up function
• 19 Character Generator [e.g. TTYTST]
• 65 Speech Data Base @ 11-tx-2 (74)
• 67
• 69 CPYNET
• 71 NETRJS [EBCDIC]
• 73 NETRJS [ASCII]
• 75 NETRJS [TTY]
• 241 NCP Measurement
• 243 Survey Measurement
• 245 LINK
• 247 RSEXEC
• 249 RSEXEC
• 251 RSEXEC

RFC502 [na] “na” p(na).

RFC502 was never issued.

RFC501 [11 May 1973] “Un-Muddling "Free File Transfer"” p(5).

RFC500 [na] “na” p(na).

RFC500 does not exist.

RFC499 [1 Apr 1973] “HARVARD’S NETWORK RJE” p(6).

RFC498 [17 Apr 1973] “ON MAIL SERVICE TO CCN” p(3).

RFC497 [10 Apr 1973] “Traffic Statistics (March 1973)” p(4).

RFC496 [5 Apr 1973] “A TNLS QUICK REFERENCE CARD IS AVAILABLE” p(1).

RFC495 [1 May 1973] “TELNET Protocol Specification” p(2).

RFC494 [20 Apr 1973] “Availability of MIX and MIXAL in the Network” p(1).

RFC493 [26 Apr 1973] “GRAPHICS PROTOCOL” p(28).

RFC492 [18 Apr 1973] “RESPONSE TO RFC 467” p(7).

RFC491 [12 Apr 1973] “What Is Free” p(2).

RFC490 [6 Mar 1973] “SURROGATE RJS FOR UCLA-CCN” p(6).

RFC489 [26 Mar 1973] “Comment on Resynchronization of Connection Status Proposal” p(1).

RFC488 [23 Mar 1973] “NLS Classes at Network Sites” p(2).

RFC487 [6 Apr 1973] “Free File Transfer” p(2).

RFC486 [20 Mar 1973] “Data Transfer Revisited” p(2).

RFC485 [19 Mar 1973] “MIX and MIXAL at UCSB” p(1).

RFC484 [na] “na” p(na).

RFC484 was never issued.

RFC483 [14 Mar 1973] “Meeting Cancellation” p(1).

RFC482 [12 Mar 1973] “Traffic Statistics (February 1973)” p(4).

RFC481 [na] “na” p(na).

RFC481 was never issued.

RFC480 [8 Mar 1973] “Host-Dependent FTP Parameters” p(1).

RFC479 [8 Mar 1973] “Use of FTP by the NIC Journal” p(5).

RFC478 [26 Mar 1973] “FTP Server-Server Interaction-II” p(2).

RFC477 [23 May 1973] “Remote Job Service at UCSB” p(19).

RFC476 [7 Mar 1973] “IMP/TIP Memory Retrofit Schedule (Revision 2)” p(2).

RFC475 [na] “na” p(na).

RFC475 does not exist.

RFC474 [1973] “Announcement of forthcoming meeting of the Network Graphics Working Group and call for RFC’s” p(1).

RFC473 [28 Feb 1973] “IX and MIXAL?” p(1).

RFC472 [Mar 1973] “Illinois’ reply to Maxwell’s Request for Graphics Information, NIC Document 14925.” p(2).

RFC471 [13 Mar 1973] “Announcement Of A (Tentative) Workshop On Multi Site Executive Programs” p(2).

RFC470 [13 Mar 1973] “Change in Socket for TIP News Facility” p(1).

RFC469 [8 Mar 1973] “Network Mail Meeting Summary” p(10).

RFC468 [8 Mar 1973] “FTP DATA COMPRESSION” p(7).

RFC467 [20 Feb 1973] “Proposed Change To Host-Host Protocol Resynchronization Of Connection Status” p(7).

RFC466 [27 Feb 1973] “TELNET LOGGER/SERVER For Host LL-67” p(9).

RFC465 [na] “na” p(na).

RFC465 was never issued.

RFC464 [27 Feb 1973] “Resource Notebook Framework” p(2).

RFC463 [21 Feb 1973] “FTP Comments and Response to RFC 430” p(3).

RFC462 [22 Feb 1973] “Responding to User Needs” p(2).

RFC461 [14 Feb 1973] “TELNET Protocol Meeting Announcement” p(1).

RFC460 [13 Feb 1973] “NCP Survey” p(7).

RFC459 [26 Feb 1973] “Network Questionnaires” p(1).

RFC458 [20 Feb 1973] “Mail Retrieval via FTP” p(2).

RFC457 [15 Feb 1973] “TIPUG” p(1).

RFC456 [13 Feb 1973] “Meeting Announcement to Discuss a Network Mail System (Revised)” p(1).

RFC455 [16 Feb 1973] “Traffic Statistics (January 1973)” p(3).

RFC454 [16 Feb 1973] “FILE TRANSFER PROTOCOL” p(35).

RFC453 [7 Feb 1973] “Meeting Announcement to Discuss a Network Mail System” p(3).

RFC452 [8 Feb 1973] “TELNET Command at Host LL” p(14).

RFC451 [22 Feb 1973] “Tentative Proposal for a Unified User Level Protocol” p(3).

RFC450 [8 Feb 1973] “MULTICS SAMPLING TIMEOUT CHANGE” p(1).

RFC449 [6 Jan 1973] “The Current Flow-control Scheme for IMPSYS.” p(1).

RFC448 [27 Feb 1973] “PRINT FILES IN FTP” p(3).

RFC447 [29 Jan 1973] “IMP/TIP Memory Retrofit Schedule (Revision 1)” p(2).

RFC446 [25 Jan 1973] “Proposal to consider a Network Program Resource Notebook” p(2).

RFC445 [22 Jan 1973] “IMP/TIP Preventive Maintenance Schedule” p(2).

RFC444 [na] “na” p(na).

RFC444 was never issued.

RFC443 [18 Jan 1973] “Traffic Statistics (December 1972)” p(3).

RFC442 [24 Jan 1973] “The Current Flow-Control Scheme for IMPSYS” p(7).

RFC441 [19 Jan 1973] “Inter-Entity Communication – An Experiment” p(7).

RFC440 [Jan 1973] “Scheduled Network Software Maintenance” p(1).

RFC439 [21 Jan 1973] “PARRY Encounters the DOCTOR” p(7).

A bit of humour from Vint Cerf: PARRY was running at SAIL and DOCTOR at BBN Tenex, both being accessed from UCLA/SEX.

RFC438 [15 Jan 1973] “FTP Server-Server Interaction” p(3).

RFC437 [30 Jun 1973] “DATA RECONFIGURATION SERVICE AT UCSB” p(10).

RFC436 [10 Jan 1973] “Announcement of RJS at UCSB” p(1).

RFC435 [5 Jan 1973] “TELNET Issues” p(10).

RFC434 [4 Jan 1973] “IMP/TIP MEMORY RETROFIT SCHEDULE” p(2).

1972 (RFC290 to RFC433)

Off into 1972 talking about data management and data sharing.

RFC433 [22 Dec 1972] “Socket Number List” p(5).

An updates socket number list from RFC349

RFC432 [Dec 1972] “Network Logical Map” p(1).

RFC431 [15 Dec 1972] “Update on SMFS Login and Logout” p(3).

RFC430 [7 Feb 1973] “COMMENTS ON FILE TRANSFER PROTOCOL” p(8).

RFC429 [12 Dec 1972] “Character Generator Process” p(1).

RFC428 [na] “na” p(na).

RFC428 was never issued.

RFC427 [na] “na” p(na).

RFC427 was never issued.

RFC426 [23 Jan 1973] “Reconnection Protocol” p(12).

RFC425 [Dec 1972] “"But my NCP costs $500 a day…"” p(1).

Addressing the increasing appearance of “Network Noise”.

RFC424 [na] “na” p(na).

RFC424 was never issued.

RFC423 [12 Dec 1972] “UCLA CAMPUS COMPUTING NETWORK LIAISON STAFF FOR ARPA NETWORK” p(2).

RFC422 [11 Dec 1972] “Traffic Statistics (November 1972)” p(4).

RFC421 [27 Nov 1972] “A SOFTWARE CONSULTING SERVICE FOR NETWORK USERS” p(1).

RFC420 [4 Jan 1973] “CCA ICCC WEATHER DEMO” p(8).

RFC419 [12 Dec 1972] “MIT-DMS on Vacation” p(1).

RFC418 [na] “” p(na).

RFC418 is not available.

RFC417 [6 Nov 1972] “LINK USAGE VIOLATION” p(1).

RFC416 [7 Nov 1972] “THE ARC SYSTEM WILL BE UNAVAILABLE FOR USE DURING THANKSGIVING WEEK” p(2).

RFC415 [29 Nov 1972] “TENEX BANDWIDTH” p(2).

RFC414 [29 Nov 1972] “FILE TRANSFER PROTOCOL (FTP) STATUS AND FURTHER COMMENTS” p(5).

RFC413 [13 Nov 1972] “TRAFFIC STATISTICS (October 1972)” p(10).

RFC412 [27 Nov 1972] “User FTP Documentation” p(10).

RFC411 [14 Nov 1972] “NEW MULTICS NETWORK SOFTWARE FEATURES” p(2).

RFC410 [10 Nov 1972] “Removal of the 30-Second Delay When Hosts Come Up” p(2).

RFC409 [8 Dec 1972] “TENEX Interface To UCSB’s Simple-Minded File System” p(8).

RFC408 [25 Oct 1972] “NETBANK” p(1).

RFC407 [16 Oct 1972] “REMOTE JOB ENTRY PROTOCOL” p(20).

RFC406 [10 Oct 1972] “Scheduled IMP Software Releases” p(2).

RFC405 [10 Oct 1972] “Correction to RFC 404” p(1).

RFC404 [5 Oct 1972] “Host Address Changes Involving RAND and ISI” p(1).

RFC403 [na] “” p(na).

RFC403 is not available.

RFC402 [26 Oct 1972] “ARPA NETWORK MAILING LISTS” p(16).

RFC401 [23 Oct 1972] “Conversion of NGP-0 Coordinates to Device Specific Coordinates” p(2).

RFC400 [18 Oct 1972] “TRAFFIC STATISTICS (September 1972)” p(3).

RFC399 [26 Sept 1972] “SMFS Login and Logout” p(2).

RFC398 [22 Sep 1972] “UCSB Online Graphics” p(2).

RFC397 [ 1972] “” p().

RFC397 is unavailable.

RFC396 [ 1972] “Network Graphics Working Group Meeting – Second Iteration” p(1).

RFC395 [3 Oct 1972] “SWITCH SETTINGS ON IMPS AND TIPS” p(1).

RFC394 [27 Sep 1972] “TWO PROPOSED CHANGES TO THE IMP-HOST PROTOCOL” p(3).

RFC393 [3 Oct 1972] “Comments on TELNET Protocol Changes” p(4).

RFC392 [20 Sep 1972] “Measurement of Host Costs for Transmitting Network Data” p(6).

RFC391 [15 Sep 1972] “TRAFFIC STATISTICS (August 1972)” p(3).

RFC390 [12 Sep 1972] “TSO SCENARIO BATCH COMPILATION AND FOREGROUND EXECUTION” p(4).

RFC389 [30 Aug 1972] “UCLA CAMPUS COMPUTING NETWORK LIAISON STAFF FOR ARPA NETWORK” p(2).

RFC388 [23 Aug 1972] “NCP Statistics” p(5).

RFC387 [10 Aug 1972] “SOME EXPERIENCES IN IMPLEMENTING NETWORK GRAPHICS PROTOCOL LEVEL 0” p(5).

RFC386 [16 Aug 1972] “LETTER TO TIP USERS — 2” p(5).

RFC385 [18 Aug 1972] “COMMENTS ON THE FILE TRANSFER PROTOCOL (RFC 354)” p(6).

RFC384 [28 Aug 1972] “OFFICIAL SITE IDENTS FOR ORGANIZATIONS IN THE ARPA NETWORK” p(4).

RFC383 [na 1972] “na” p(na).

RFC383 was never issued.

RFC382 [3 Aug 1972] “MATHEMATICAL SOFTWARE ON THE ARPA NETWORK” p(1).

RFC381 [26 Jul 1972] “Three Aids To Improved Network Operation” p(4).

RFC380 [na 1972] “na” p(na).

RFC380 was never issued.

RFC379 [11 Aug 1972] “USING TSO AT CCN” p(5).

RFC378 [10 Aug 1972] “Traffic Statistics (July 1972)” p(3).

RFC377 [10 Aug 1972] “USING TSO VIA ARPA NETWORK VIRTUAL TERMINAL” p(4).

RFC376 [8 Aug 1972] “NETWORK HOST STATUS” p(5).

Another host status report.

RFC375 [na 1972] “na” p(na).

RFC375 was never issued.

RFC374 [19 Jul 1972] “There are two significant developments in the operation of the network which should be of interest to all sites:” p(2).

RFC373 [14 Jul 1972] “ARBITRARY CHARACTER SETS” p(4).

RFC372 [12 Jul 1972] “NOTES ON A CONVERSATION WITH BOB KAHN ON THE ICCC” p(4).

RFC371 [12 Jul 1972] “DEMONSTRATION AT INTERNATIONAL COMPUTER COMMUNICATIONS CONFERENCE” p(2).

RFC370 [31 Jul 1972] “NETWORK HOST STATUS” p(5).

Another host status report.

RFC369 [25 Jul 1972] “EVALUATION OF ARPANET SERVICES” p(11).

RFC368 [21 Jul 1972] “COMMENTS ON "PROPOSED REMOTE JOB ENTRY PROTOCOL”” p(2).

RFC367 [19 Jul 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC366 [11 Jul 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC365 [11 Jul 1972] “A LETTER TO ALL TIP USERS” p(5).

RFC364 [11 Jul 1972] “Serving Remote Users on the ARPANET” p(6).

RFC363 [8 Aug 1972] “ARPA NETWORK MAILING LISTS” p(13).

RFC362 [28 Jun 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC361 [5 Jul 1972] “In response to RFCs 347 and 348, ECHO and DISCARD, MIT-DMCG (Host 106) now has deamon processes that will respond to RFCs on sockets 7 and 9.” p(1).

RFC360 [na 1972] “na” p(na).

RFC360 does not exist.

RFC359 [22 Jun 1972] “HE STATUS OF THE RELEASE OF THE NEW IMP SYSTEM (2600)” p(1).

RFC358 [na 1972] “na” p(na).

RFC358 was never issued.

RFC357 [26 Jun 1972] “An Echoing Strategy For Satellite Links” p(13).

RFC356 [21 Jun 1972] “ARPA NETWORK CONTROL CENTER” p(1).

RFC355 [9 Jun 1972] “RESPONSE TO NWG/RFC 346” p(3).

RFC354 [8 Jul 1972] “THE FILE TRANSFER PROTOCOL” p(25).

RFC353 [12 Jun 1972] “NETWORK HOST STATUS” p(5).

Another host status report.

RFC352 [5 Jun 1972] “TIP SITE INFORMATION FORM” p(3).

RFC351 [5 Jun 1972] “(Graphics)Information form for the ARPANET Graphics Resources Notebook:” p(2).

RFC350 [18 May 1972] “”User Accounts for UCSB On-line System p(3).

RFC349 [30 May 1972] “Proposed Standard Socket Numbers” p(1).

The first list of proposed socket numbers emerge:

Sockets Assignment

• 0-63 Network wide standard functions
  • 1 Telnet
  • 3 File Transfer
  • 5 Remote Job Entry
  • 7 Echo
  • 9 Discard
• 64-127 Host specific functions
• 128-239 Reserved for future use
• 240-255 Any experimental function

RFC348 [30 May 1972] “Discard Process” p(1).

RFC347 [30 May 1972] “Echo Process” p(1).

RFC346 [30 May 1972] “Satellite Considerations” p(1).

RFC345 [26 May 1972] “INTEREST IN MIXED INTEGER PROGRAMMING (MPSX ON 360/91 AT CCN)” p(1).

RFC344 [22 May 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC343 [19 May 1972] “IMP System Change Notification” p(2).

RFC342 [15 May 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC341 [na 1972] “na” p(na).

RFC341 was never issued.

RFC340 [15 May 1972] “PROPOSED TELNET CHANGES” p(2).

RFC339 [5 May 1972] “MLTNET – A "MULTI-TELNET" SUBSYSTEM FOR TENEX” p(4).

RFC338 [17 May 1972] “EBCDIC/ASCII MAPPING FOR NETWORK RJE” p(6).

RFC337 [na 1972] “na” p(na).

RFC337 was never issued.

RFC336 [5 May 1972] “Level 0 Graphic Input Protocol” p(2).

RFC335 [1 May 1972] “NEW INTERFACE-IMP/360” p(1).

Roland F. Bryan, of UCSB Research Lab, highlights a number interface for the 360-75 and asks everyone to report any issue with it.

RFC334 [1 May 1972] “Network Use on MAY 8” p(1).

RFC333 [15 May 1972] “A PROPOSED EXPERIMENT WITH A MESSAGE SWITCHING PROTOCOL” p(26).

RFC332 [25 Apr 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC331 [19 Apr 1972] “IMP System Change Notification” p(1).

RFC330 [13 Apr 1972] “NETWORK HOST STATUS” p(3).

Another host status report.

RFC329 [17 May 1972] “ARPA NETWORK MAILING LISTS” p(13).

RFC328 [29 Apr 1972] “Suggested Telnet Protocol Changes” p(2).

RFC327 [27 Apr 1972] “DATA AND FILE TRANSFER WORKSHOP NOTES” p(5).

RFC326 [3 Apr 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC325 [6 Apr 1972] “Network Remote Job Entry Program – NETRJS” p(9).

RFC324 [3 Apr 1972] “RJE Protocol Meeting” p(1).

RFC323 [23 Mar 1972] “Formation of Network Measurement Group (NMG)” p(9).

RFC322 [26 Mar 1972] “Well Known Socket Numbers” p(1).

Vint Cerf and Jon Postel call for a single list of all well known socket numbers in use. They start with Socket 1 which is the Network Logger.

RFC321 [24 Mar 1972] “CBI Networking Activity at MITRE” p(14).

RFC320 [27 Mar 1972] “Workshop on Hard Copy Line Graphics” p(3).

RFC319 [21 Mar 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC318 [3 Apr 1972] “Telnet Protocol” p(16).

RFC317 [20 Mar 1972] “Official Host-Host Protocol Modification: Assigned Link Numbers” p(1).

RFC316 [24 Feb 1972] “ARPA Network Data Management Working Group” p(7).

RFC315 [8 Mar 1972] “NETWORK HOST STATUS” p(4).

RFC314 [14 Mar 1972] “Network Graphics Working Group Meeting” p(1).

RFC313 [Mar 1972] “COMPUTER BASED INSTRUCTION” p(8).

RFC312 [22 Mar 1972] “Proposed Change in IMP-to-Host Protocol” p(2).

RFC311 [29 Feb 1972] “NEW CONSOLE ATTACHMENTS TO THE UCSB HOST” p(2).

RFC310 [3 Apr 1972] “Another Look At Data And File Transfer Protocols” p(7).

RFC309 [17 Mar 1972] “DATA AND FILE TRANSFER WORKSHOP ANNOUNCEMENT” p(6).

RFC308 [13 Mar 1972] “ARPANET HOST AVAILABILITY DATA” p(4).

RFC307 [24 Feb 1972] “USING NETWORK REMOTE JOB ENTRY” p(6).

RFC306 [15 Feb 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC305 [23 Feb 1972] “UNKNOWN HOST NUMBERS” p(1).

RFC304 [ 1972] “” p().

This does not exist.

RFC303 [3 March 1972] “ARPA Network Mailing Lists” p(11).

RFC302 [8 Feb 1972] “EXERCISING THE ARPANET” p(3).

RFC301 [11 Feb 1972] “BBN IMP (#5) AND NCC SCHEDULE MARCH 4, 1971” p(1).

The BBN IMP is to be relocated and will go offline for a short period of time.

RFC300 [25 Jan 1972] “ARPA NETWORK MAILING LISTS” p(9).

Directory showing who is distributed what report.

RFC299 [11 Feb 1972] “Information Management System” p(1).

Dorothy Hopkin, of University of Illinois, introduces a new development and calls for interested parties.

RFC298 [1 Feb 1972] “NETWORK HOST STATUS” p(4).

Another host status report.

RFC297 [31 Jan 1972] “TIP Message Buffers” p(2).

Dave Walden, of BBN, Attempts to address complains about the size of message buffers.

RFC296 [na] “” p(na).

This RFC does not exist.

RFC295 [2 Jan 1972] “Report of the Protocol Workshop 12 October, 1971” p(4).

Jon Postel outlines some key recent decisions regarding IMP-Host Protocol, Host-to-Host protocol, Initial Connection Protocol, and Telnet Protocol.

RFC294 [25 Jan 1972] “The Use of ‘Set Data Type’ Transaction in File Transfer Protocol” p(2).

Abhay Bhushan, of MIT, clarifies a further point from RFC265.

RFC293 [18 Jan 1972] “NETWORK HOST STATUS” p(3).

Another host status update by Ellen Westheimer.

RFC292 [12 Jan 1972] “GRAPHICS PROTOCOL – LEVEL 0 ONLY” p(10).

Thoughts and opinions from the second meeting of the Network Graphics Group. This RFC covers a proposed Network Standard Graphics Protocol and covers the proposed commands for review.

RFC291 [14 Jan 1972] “Data Management Meeting Announcement” p(2).

McKay, of IBM, outlines an upcoming MITRE hosted meeting to discuss the subject of data management.

RFC290 [11 Jan 1972] “COMPUTER NETWORKS AND DATE SHARING: A BIBLIOGRAPHY” p(15).

Mullery, of the Thomas J. Watson Research Center, brings together a bibliography of articles covering the subject of data structures and sharing.

1971 (RFC86 to RFC289)

Heading in to 1971, looking to the future (from a historic point of view that is). We have further talk of Telnet and we start to talk about FTP.

RFC289 [21 Dec 1971] “What We Hope Is An Official List of Host Names” p(3).

Watson, of SRI-ARC, proposes a format list of official host names.

RFC288 [6 Jan 1972] “NETWORK HOST STATUS” p(4).

Westheimer, of BBN, gives a status network update of hosts.

RFC287 [22 Dec 1971] “Status of Network Hosts” p(5).

Westheimer, of BBN, gives a status network update of hosts.

RFC286 [21 Dec 1971] “Network Library Information System” p(1).

Forman, of MITRE, talks about the Learning Resource Center (LRC) being designed by Georgetown University.

RFC285 [15 Dec 1971] “Network Graphics” p(7).

Huff, or CWRU, brings together various thinking about network graphics.

RFC284 [] “” p().

RFC284 was never issued.

RFC283 [20 Dec 1971] “NETRJT — Remote Job Service Protocol for TIPS” p(9).

Finding a way for TIP users to make use of the job entry protocol.

RFC282 [8 Dec 1971] “Graphics Meeting Report” p(8).

Report on the recently held graphics meeting covering the various experiments carried out by each institute.

RFC281 [8 Dec 1971] “A suggested Addition to File Transfer Protocol” p(8).

McKenzie, of BBN,  talking about a network Remote Job Service (RJS) protocol and recommending a restart procedure to the FTP protocol

RFC280 [17 Nov 1971] “A Draft Set of Host Names” p(3).

Watson, from SRI-ARC, puts together a draft list of standard host names, based largely on requests from sites.

RFC279 [] “” p().

RFC279 was never issued.

RFC278 [17 Nov 1971] “REVISION OF THE MAIL BOX PROTOCOL” p(4).

A group project talking about changes of the protocol described in RFC221. In particular setting the standard path name as:

"MAIL" <separator> ("PRINTER"/<ident>)

RFC277 [] “” p().

RFC277 was never issued.

RFC276 [8 Nov 1971] “NIC Course” p(1).

Richard Watson, of SRI-ARC, invites people to attend a course on the use SRI Online System (NLS).

RFC275 [] “” p().

RFC275 was never issued.

RFC274 [1 Nov 1971] “ESTABLISHING A LOCAL GUIDE FOR NETWORK USAGE” p(5).

Forman, from MITRE, talks about establishing a guide for network usage ideally tailored to the needs of MITRE users.

RFC273 [18 Oct 1971] “MORE ON STANDARD HOST NAMES” p(3).

The host naming standard heats up with Richard Watson, from SRI, suggesting the host name convention remain in the Network Information Center.

RFC272 [] “” p().

RFC272 was never issued.

RFC271 [3 Jan 1971] “IMP System Change Notification” p(2).

Cosell, of BBN, highlights the planned upgrade of the IMP system, to version 2514.

RFC270 [1 Jan 1971] “CORRECTION TO BBN REPORT NO. 1822” p(1).

McKenzie, makes a correction to RFC271. Even though it post dates this RFC.

RFC269 [6 Dec 1971] “Some Experience with File Transfer” p(3).

Brodie, of UCLA-NMC, highlights experiences of using the proposed FTP protocol.

RFC268 [24 Nov 1971] “Graphics Facilities Information” p(1).

Postel suggests the inclusion of the graphics facilities in the Resources Notebook, and calls for submissions.

RFC267 [22 Nov 1971] “Untitled” p(4).

Westheimer, from BBN, with the regular network status report.

RFC266 [8 Nov 1971] “NETWORK HOST STATUS” p(2).

Westheimer, from BBN, with the regular network status report.

RFC265 [17 Nov 1971] “THE FILE TRANSFER PROTOCOL” p(12).

A revision of previous RFC172 clarifying some changes to the protocol.

RFC264 [15 Nov 1971] “THE DATA TRANSFER PROTOCOL” p(9).

A revision of previous RFC171 clarifying some changes to the protocol.

RFC263 [17 Dec 1971] “VERY DISTANT HOST INTERFACE” p(2).

McKenzie, of BBN, identifies criteria for dealing with hosts especially far away ones.

RFC262 [] “” p().

RFC262 was never issued. I wonder how many there are?

RFC261 [] “” p().

RFC261 was never issued. What is going on here?

RFC260 [] “” p().

RFC260 was never issued. Unusual.

RFC259 [] “” p().

RFC259 was never issued. Three in a row is a bit odd.

RFC258 [] “” p().

RFC258 was never issued. Two in a row.

RFC257 [] “” p().

RFC257 was never issued.

RFC256 [3 Nov 1971] “IMPSYS Change Notification” p(1).

Cosell, of BBN, outlines the upcoming installation of the new version of the IMP system, this will be version 2513. Two major changes are involved, firstly the transmission delay, upon initial connection, has been increased to 40-60 seconds from 30-60 seconds. Secondly, the NCC can now run tests directly on the IMP.

RFC255 [26 Oct 1971] “Untitled” p(2).

Another status update of the hosts on the network.

RFC254 [] “” p().

RFC254 is missing.

RFC253 [19 Oct 1971] “Second Network Graphics Meeting Details” p(1).

Moorer, from Stanford Al Laboratory, outlines the upcoming meeting at Stanford.

RFC252 [8 Oct 1971] “Untitled” p(3).

Another status update of the hosts on the network.

RFC251 [13 Oct 1971] “WEATHER DATA” p(2).

Stern, from Computer Corporate of America, describes the working group set up to design and coordinate a database for the USAF Environmental Technical Applications Centre (ETAC) providing weather data for the ARPA Network.

RFC250 [7 Oct 1971] “Some Thoughts on File Transfer” p(1).

Brodie talks about the frustrations of transferring large files over Telnet and offers some thoughts on the FTP and DTP protocols in RFC171 and RFC172.

RFC249 [8 Oct 1971] “Coordination of Equipment and Supplies Purchase” p(2).

Borelli, of University of Illinois, explains an agreement between Borelli and Crocker to look into coordinating purchases of equipment and supplies for use on the new network.

RFC248 [] “” p().

RFC248 was never issued.

RFC247 [12 Oct 1971] “Proferred Set of Standard Host Names” p(4).

Peggy Karp rejoins the debate and suggests a set of ules for forming host names. Host names should be eight characters, in the form <site> hyphen <machine>.

RFC246 [5 Oct 1971] “Network Graphics Meeting” p(1).

Confirming the November Networks Graphics Meeting in November 1971.

RFC245 [5 Oct 1971] “Reservations for Network Working Group Meeting” p(1).

Administrative RFC confirming hotel reservations for the upcoming meeting.

RFC244 [] “” p().

RFC244 was never issued.

RFC243 [5 Oct 1971] “NETWORK AND DATA SHARING BIBLIOGRAPHY” p(7).

RFC242 [19 Jul 1971] “DATA DESCRIPTIVE LANGUAGE FOR SHARED DATA” p(10).

Haibt and Mullery suggest a standardised way of representing data transmitted over the network.

RFC241 [29 Sep 1971] “CONNECTING COMPUTERS TO MLC PORTS” p(2).

McKenzie, of BBN, clarifies the situation about requests to connect to the Terminal IMP using serial connections.

RFC240 [30 Sep 1971] “SITE STATUS” p(4).

McKenzie, of BBN, effectively reissues RFC235, and apologies for any problems it may have caused. Oops. This RFC gives a fuller list of the equipment installed at each particular location.

RFC239 [23 Sep 1971] “HOST MNEMONICS PROPOSED IN RFC #226” p(1).

Braden, from UCLA, picks up on RFC226 by Peggy Karp and adds some of his own recommendations – he also mentions there are 40 known hosts at this time (Peggy Karp had identified 20).

RFC238 [29 Sep 1971] “COMMENTS ON DTP AND FTP PROPOSALS” p(2).

Braden, from UCLA, makes some comments about these two proposals. In particular he identifies, in the proposed FTP protocol, end-of-file should be indicated not simply by closing the connection but by using an indicator prior to closing – this will help separate error conditions from normal conditions.

RFC237 [5 Oct 1971] “The Nic’s View of Standard Host Names” p(1).

Richard Watson, representing NIC, joins the standard host names discussion with some additional recommendations, ideally using 8 characters and indicating site and host names. He also indicates that once the system is agreed it should fall under the responsibility of the NIC.

RFC236 [27 Sep 1971] “STANDARD HOST NAMES” p(2).

Postel throws his oar back in about the standard host names, interestingly he says “It has been brought to my attention that programmers are lazy and don’t like to deal with character strings longer than one computer word or containing characters other than the capital letters A-Z or the digits 0-9”. He also indicates a four character list of names – did he not read RFC233?

RFC235 [27 Sep 1971] “SITE STATUS” p(5).

A new plan by Westheimer, of BBN, to periodically (indicated two be fortnightly) report the status of the network hosts. Some interesting information about the computers in use at sites is given:

• Rand use a PDP-10
• Lincoln use a TX2
• Stanford use a PDP-10
• Case use a PDP-10
• Carnegie use a PDP-10
• Paoli use a B6500

RFC234 [5 Oct 1971] “Network Working Group Meeting Schedule” p(1).

Vezza outlines the schedule for the Network Group Meeting – was this not postponed in RFC232?

RFC233 [28 Sep 1971] “” p(2).

Agreeing with Peggy Karp in RFC226 about the benefit of standard host names, Bhushnan and Metcalfe suggest a four character mechanism for standard host names – allowing upper and lower case letters to be used interchangeably, these have a one to one resolution to the eight character names in RFC229.

RFC232 [23 Sep 1971] “Untitled” p(1).

Postponing the Network Working Group meeting planned for October 1971.

RFC231 [21 Sep 1971] “SERVICE CENTER STANDARDS FOR REMOTE USAGE–A USER’S VIEW” p(4).

Heafner and Harfner, from RAND, talk about the importance of standards in the service centre.

RFC230 [24 Sep 1971] “TOWARD RELIABLE OPERATION OF MINICOMPUTER-BASED TERMINALS ON A TIP” p(3).

Pyke discussions the effectiveness of communications between a TIP and terminals.

RFC229 [22 Sep 1971] “STANDARD HOST NAMES” p(3).

An attempt by Jon Postel to standardise the host names, but this time based on eight characters, for example UCLA-NMC, MIT-MLTX

RFC228 [22 Sep 1971] “CLARIFICATION” p(1).

A slight clarification to a statement made in RFC #70

RFC227 [17 Sep 1971] “DATA TRANSFER RATES (RAND/UCLA)” p(2).

Heafner and Harslem give some example data transmission rates for sending to/and from UCLA (from RAND). They range from 8KB/s to 16KB/sec.

RFC226 [20 Sep 1971] “STANDARDIZATION OF HOST MNEUMONICS” p(1).

Peggy Karp offers a suggestion to standardise host names, using six characters maximum, for telnet implementations, for example UCLA, HARV, and MITRE

RFC225 [13 Sep 1971] “RAND/UCSB NETWORK GRAPHICS EXPERIMENT” p(5).

The results of the graphics experiment, apparently a film was made showing the use of the OLS from Rand – it would be great to track that down and watch it from a new perspective.

RFC224 [14 Sep 1971] “Comments on Mailbox Protocol” p(2).

Notes on why the Terminal IMP may be unable to implement the new mailbox protocol, primarily due to lack of storage and lack of capacity for processing programs.

RFC223 [14 Sep 1971] “NETWORK INFORMATION CENTER SCHEDULE FOR NETWORK USERS” p(4).

RFC222 [12 Sep 1971] “na” p(2).

RFC221 [25 Aug 1971] “A Mail Box Protocol, Version-2” p(5).

RFC220 [na] “na” p(na).

RFC220 was never issued

RFC219 [3 Sep 1971] “User’s View of the Datacomputer” p(7).

RFC218 [8 Sep 1971] “na” p(1).

RFC217 [8 Sep 1971] “Specification Changes for OLS, RJE/RJOR, and SMFS” p(2).

RFC216 [na] “na” p(na).

RFC is missing

RFC215 [30 Aug 1971] “NCP, ICP, and TELNET: The Terminal IMP Implementation” p(7).

RFC214 [21 Aug 1971] “NETWORK CHECKOUT” p(2).

RFC213 [20 Aug 1971] “IMP System Change Notification” p(1).

RFC212 [23 Aug 1971] “NWG Meeting On Network Usage” p(2).

RFC211 [na] “na” p(na).

RFC is missing

RFC210 [16 Aug 1971] “Improvement of Flow Control” p(2).

RFC209 [13 Aug 1971] “HOST/IMP Interface Documentation” p(1).

RFC208 [9 Aug 1971] “ADDRESS TABLES” p(3).

RFC207 [9 Aug 1971] “A SEPTEMBER NETWORK WORKING GROUP MEETING” p(2).

RFC206 [9 Aug 1971] “A User TELNET Description of an Initial Implementation” p(14).

RFC205 [6 Aug 1971] “NETCRT – A CHARACTER DISPLAY PROTOCOL” p(13).

RFC204 [5 Aug 1971] “Sockets in use” p(1).

RFC203 [10 Aug 1971] “Achieving Reliable Communication” p(4).

RFC202 [26 Jul 1971] “Possible Deadlock Situation” p(2).

RFC201 [na] – RFC was never issued

RFC200 [1 Aug 1971] “RFC List by Number” p(7).

RFC199 [] “Suggestions for Network Data Tablet” p(na).

This RFC is missing

RFC198 [20 Jul 1971] “SITE CERTIFICATION – LINCOLN LABS 360/67” p(1).

RFC197 [14 Jul 1971] “INITIAL CONNECTION PROTOCOL–REVIEWED” p(5).

RFC196 [20 Jul 1971] “A MAIL BOX PROTOCOL” p(4).

RFC195 [16 Jul 1971] “Data Computers — Data Descriptions and Access Language” p(4).

RFC194 [na] “THE DATA RECONFIGURATION SERVICE — COMPILER/INTERPRETER IMPLEMENTATION NOTES” p(18).

RFC193 [14 Jul 1971] “NETWORK CHECKOUT” p(2).

RFC192 [12 Jul 1971] “Some Factors which a Network Graphics Protocol must Consider” p(19).

RFC191 [13 Jul 1971] “GRAPHICS IMPLEMENTATION AND CONCEPTUALIZATION AT ARC” p(4).

RFC190 [13 Jul 1971] “DEC PDP-10 — IMLAC COMMUNICATION SYSTEM” p(16).

RFC189 [15 Jul 1971] “INTERIM NETRJS SPECIFICATIONS” p(19).

RFC188 [28 Jan 1971] “Data Management Meeting Announcement” p(2).

RFC187 [na] “A NETWORK/440 PROTOCOL CONCEPT” p(11).

RFC186 [12 Jul 1971] “A Network Graphics Loader” p(17).

RFC185 [7 Jul 1971] “NIC DISTRIBUTION OF MANUALS AND HANDBOOKS” p(1).

RFC184 [6 Jul 1971] “Proposed Graphic Display Modes” p(7).

RFC183 [na] – RFC does not exist or is missing

RFC182 [25 Jun 1971] “COMPILATION OF LIST OF RELEVANT SITE REPORTS” p(1).

RFC181 [27 Jun 1971] "MODIFICATIONS TO RFC #177" p(3).

RFC180 [25 Jun 1971] "File System Questionnaire" p(4).

RFC179 [22 Jun 1971] "LINK NUMBER ASSIGNMENTS" p(1).

RFC178 [27 Jun 1971] "NETWORK GRAPHIC ATTENTION HANDLING" p(11).

RFC177 [15 Jun 1971] "A DEVICE INDEPENDENT GRAPHICAL DISPLAY DESCRIPTION" p(9).

RFC176 [14 Jun 1971] "Comments on Byte Size for Connections" p(5).

RFC175 [11 Jun 1971] "Comments on "Socket Conventions Reconsidered"" p(1).

RFC174 [8 Jun 1971] "UCLA-Computer Science Graphics Overview" p(3).

RFC173 [4 Jun 1971] "Network Data Management Committee Meeting Announcement" p(2).

RFC172 [23 Jun 1971] "THE FILE TRANSFER PROTOCOL" p(12).

More on the future FTP protocol.

RFC171 [23 Jun 1971] "THE DATA TRANSFER PROTOCOL" p(9).

RFC170 [1 Jun 1971] "RFC List by Number" p(6).

List of all the RFC issues to date.

RFC169 [27 May 1971] "IEEE Computer Society Workshop West Coast Committee" p(4).

RFC168 [26 May 1971] "Arpa Network Mailing Lists" p(7).

RFC167 [24 May 1971] "Socket Conventions Reconsidered" p(4).

RFC166 [25 May 1971] "DATA RECONFIGURATION SERVICE — AN IMPLEMENTATION SPECIFICATION" p(20).

RFC165 [25 May 1971] "A Proferred Official Initial Connection Protocol" p(na)

RFC is missing or unavailable.

RFC164 [na May 1971] "MINUTES OF NETWORK WORKING GROUP MEETING 5/16 through 5/19/71" p(32).

Review of minutes so far.

RFC163 [19 May 1971] "DATA TRANSFER PROTOCOLS" p(3).

Vint Cert summaries the discussions at the recent meeting to talk about data protocols.

RFC162 [22 May 1971] "NETBUGGER3" p(2).

Outlining a second and third level program debugging tool.

RFC161 [19 May 1971] "A SOLUTION TO THE RACE CONDITION IN THE ICP" p(1).

The race condition identified in RFC143 is discussed with an outline solution suggested.

RFC160 [18 May 1971] "RFC Brief List" p(4).

Cross reference list of RFC to NIC reference numbers to date.

RFC159 was never issued – I wonder what happened to it?

RFC158 [19 May 1971] "TELNET Protcol [(11).

Further requests to comment onf the forthcoming official TELNET protocol.

RFC157 [12 May 1971] "Invitation to the Second Symposium on Problems in the Optimization of Data Communication Systems" p(2).

Call for papers for upcoming Symposium.

RFC156 [26 Apr 1971] "Status of the Illinois Site (Response to RFC 0116)" p(1).

Illinois now has the IMP software up and running on a PDP-11.

RFC155 [na May 1971] "LIST TO RECEIVE RFC’S" p(na)

Updating the circulation list for RFC.

RFC154 [12 May 1971] "Exposition Style" p(1).

Crocker clarifies how he describes formula.

RFC153 [15 May 1971] "SRI ARC-NIC Status" p(4).

Update status of migrating the PDP-10 from BBN to Tenex.

RFC152 [10 May 1971] "SRI ARTIFICIAL INTELLIGENCE STATUS REPORT" p(1).

The AI group at Stanford highlight how they are planning to join the network.

RFC151 [10 May 1971] "COMMENTS ON A PROFERRED OFFICIAL ICP (RFCs 123, 127)" p(2).

Further commments on the previously recommended ICP protocol.

RFC150 [5 May 1971] "THE USE OF IPC FACILITIES" p(11).

I hope the first sentence disclaimer has timed out by now.

RFC149 [10 May 1971] "The Best Laid Plans . . ." p(1).

Changing the agenda due to non attendance.

RFC148 [7 May 1971] "Comments on RFC #123" p(1).

Bhushan highlights the PDP-10 transmits data using either 36-bits or 8-bits and not in a fixed 32-bit size as described in RFC123. 72 bits is suggested as a recommendation.

RFC147 [7 May 1971] "The Definition of a Socket" p(3).

Winett describes a socket as being a 32 bit number with even numbered sockets identifying receiving sockets and odd numbered sockets sending sockets.

RFC146 [12 May 1971] "Views on Issues Relevant to Data Sharing on Computer Networks" p(6).

Feedback on RFC140.

RFC145 [4 May 1971] "Initial Connection Protocol Control Commands" p(2).

Building on RFC123.

RFC144 [30 Apr 1971] "Data Sharing on Computer Networks" p(6).

Proposing a discussion at the upcoming meeting talking about data sharing.

RFC143 [3 May 1971] "Regarding Proferred Official ICP" p(4).

Discovery of a race condition.

RFC142 [3 May 1971] "Time-out Mechanism in the Host-Host Protocol" p(2).

Recommending a time out mechanism based on observation of connections with the host-to-host protocol.

RFC141 [29 Apr 1971] "COMMENTS ON RFC 141 (A FILE TRANSFER PROTOCOL)" p(2).

Feedback on the previously released FTP Protocol recommendation.

RFC140 [4 May 1971] "AGENDA FOR THE MAY NWG MEETING" p(4).

Setting the guidelines for the upcoming network group meeting.

RFC139 [7 May 1971] "Discussion of TELNET Protocol" p(11).

Further TELNET dicussion building on from RFC137.

RFC13 [28 Apr 1971] "STATUS REPORT ON PROPOSED DATA RECONFIGURATION SERVICE" p(23).

Experiment on Network Data reformatting techniques.

RFC137 [30 Apr 1971] "TELNET Protocol" p(11).

Discussions for TELNET drawing to a close prior to official protocol specification, discussions expected in Atlantic City.

RFC136 [29 Apr 1971] "Host Accounting and Administrative Procedures" p(4).

Establishing discussion for a host accounting mechanisms on the ARPA network.

RFC135 [29 Apr 1971] "Response to NWG/RFC #110 (Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts)" p(3).

Suggesting replacement convention for those outlines in RFC110 as some terminals do not have all the characters described in RFC110.

RFC134 [29 Apr 1971] "Network Graphics Meeting" p(2).

Outlining the structure of the upcoming MAC meeting.

RFC133 [27 Apr 1971] "FILE TRANSFER AND ERROR RECOVERY" p(4).

Combining and evaluating thinking from RFC114 and RFC60.

RFC132 [28 Apr 1971] "TYPOGRAPHICAL ERROR IN RFC 107" p(1).

Correcting a typographical error from RFC107 – 128 should read 127.

RFC131 [na Apr 1971] "Response to RFC #116 (May NWG Meeting)" p(3).

Updating the status of the implementation on the IBM 360.

RFC130 [22 Apr 1971] "RESPONSE TO RFC #111 (PRESSURE FROM THE CHAIRMAN)" p(1).

From Heafner – new Chairman? Clarifying the RFC111 understanding.

RFC129 [22 Apr 1971] "A REQUEST FOR COMMENTS ON SOCKET NAME STRUCTURE" p(6).

Discussing Socket naming conventions.

RFC128 [21 Apr 1971] "BYTES" p(2).

Further clarification of the use of the Byte size parameter for the NCP protocol – again from Postel.

RFC127 [20 Apr 1971] "Comments on RFC 123" p(2).

Postel outlines understand of the NCP connectio protocol.

RFC126 [na Apr 1971] "Ames Graphics Facilities at Ames Research Center" p(1).

Describing the Ames graphic environment for the IBM 360 machine.

RFC125 [18 Apr 1971] "Response to RFC #86, Proposal for Network Standard Format for a graphics

data stream." p(4).

J. McConnell updates RFC86 – identifying areas for special handling such as the back space and line feed characters.

RFC124 [19 Apr 1971] "Typographical Error in RFC 107" p(1)

J. Melvin corrects a typographical error in RFC107 (RTS should read STR).

RFC123 [20 Apr 1971] "A Proferred Official ICP" p(3).

Steve Crocker identifies a mechanism for initiating connection between a pair of devices – this can be utilised for other mechanisms for example Telnet.

RFC122 [26 Apr 1971] "NETWORK SPECIFICATIONS FOR UCSB’s SIMPLE-MINDED FILE SYSTEM" p(21).

Implementing a simple file storage system for network users using the NCP protocol.

RFC121 [21 Apr 1971] "NETWORK ON-LINE OPERATORS" p(13).

Similar in style to RFC120 but talking about how On-Line System users can utilise the NCP protocol for accessing the network.

RFC120 [21 Apr 1971] "NETWORK PL1 SUBPROGRAMS" p(16).

Making the network, using the NCP protocol, available in PL1 sub-programs by providing a higher level interface to the protocol.

RFC119 [na 1971] "na" p(na)

Not available or missing.

RFC118 [16 Apr 1971] "RECOMMENDATIONS FOR FACILITY DOCUMENTATION" p(2)

Richard Watson talks about how best to identify particular types of document, e.g. Programmer Documents and User Documents.

RFC117 [7 Apr 1971] "Some Comments on the Official Protocol" p(5).

Further analysis on the NCP protocol, in particular handling errors.

RFC116 [12 Apr 1971] "STRUCTURE OF THE MAY NWG MTG." p(1).

Steve Crocker reformulates update meetings to ensure progress reports are included.

RFC115 [16 Apr 1971] "SOME NETWORK INFORMATION CENTER POLICIES ON HANDLING DOCUMENTS" p(8).

Describing how the Network Information Centre handles documents – in particular RFC documents.

RFC114 [16 Apr 1971] "A FILE TRANSFER PROTOCOL" p(17).

In addition to Telnet we now have another of the most established protocols in use today, described by A. Bhushan. The FTP protocol was born out of this RFC and later revised through dozens of further RFC.

RFC113 [5 Apr 1971] "NETWORK ACTIVITY REPORT:  UCSB <- -> RAND" p(2).

Activity report from RFC105 asserting that the systems from that RFC have been implemented and validated by RAND.

RFC112 [na 1971] "na" p(na)

Not available or missing.

RFC111 [31 Mar 1971] "Pressure from the Chairman" p(2).

Steve Crocker puts his foot down and tells the team to get their act together (he uses nicer words) to finish the work on the protocols for NCP and Telnet.

RFC110 [na 1971] "na" p(na)

Not available or missing.

RFC109 [na 1971] "na" p(na)

Not available or missing.

RFC108 [25 Mar 1971] "Addendum to NWG Meeting Notes, NIC (5762)" p(2).

Lists the attendees from the February 1971 meeting.

RFC107 [23 Mar 1971] "Output of the Host-Host Protocol Glitch Cleaning Committee" p(12).

A further update from RFC102 – in fact this RFC supercedes RFC102.

RFC106 [3 Mar 1971] "USER/SERVER SITE PROTOCOL NETWORK HOST QUESTIONNAIRE" p(5).

Wow, a questionnaire collecting information about a planned Telnet protocol (Is your terminal "line at a time" or "character at a time"?).

RFC105 [na Mar 1971] "Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB" p(9).

Interesting that our commonly understood meaning of a byte needs to be restated here as 8 bits (mind you it numbers them 0-7 left to right whereas these days it would right to left).

RFC104 [25 Feb 1971] "Link 191" p(1).

Correcting the assumption that a previously agreed link number 223 would be reserved for measurements and specifies it is actually link 191 – though it doesn’t particularly explain why 223 cannot be used.

RFC103 [24 Feb 1971] "Implementation of Interrupt Keys " p(4).

Talks about the break key in relation to time-sharing protocols and how the NCP does not fully implement the mechanism. It is interesting to see that particular protocols have no formal identification at the start of RFC. It would have been useful to see some linking keyword in the header of an RFC.

RFC102 [22,23 Feb 1971] "OUTPUT OF THE HOST/HOST PROTOCOL GLITCH CLEANING COMMITTEE" p(4).

A summary of what needs to be actioned on the host-to-host protocol. A recommendation to make communications full-duplex was rejected.

RFC101 [23 Feb 1971] "NOTES ON THE NETWORK WORKING GROUP MEETING" p(14).

Talks about a number of subjects. Interesting suggestion that old RFC should be reviewed to identify which ones are obsolete.

RFC100 [26 Feb 1971] "Categorization and Guide to NWG/RFCs" p(37)

A review of all RFC so far and an attempt to categorise them leading to a more structured system going forward.

RFC99 [22 Feb 1971] "Nework Meeting" p(1)

Arranging the next Network Group Meeting  for May 16, 1971.

RFC98 [Feb 11 1971] "Logger Protocol Proposal" p(10).

Edwin Meyer asks how best to proceed with the host-to-host protocol.

RFC97 [na 1971] "Logger Protocol" p(na)

Not available or missing.

RFC96 [12 Feb 1971] "An Interactive Network Experiment to Study Modes of Access the Network Information Center" p(5).

Laying down how the test experiment will work in RFC97

RFC95 [4 Feb 1971] "Distribution of NWG/RFCs Through the NIC" p(5).

Mentions Jean North is the current RFC number issuer.

RFC94 [3 Feb 1971] "Some Thoughts on Network Graphics" p(6).

Comments and reactions on RFC86, highlighted differences in terminal equipment (e.g. receiving higher resolution images on lower resolution terminals).

RFC93 [na Jan 1971] "Initial Connection Protocol" p(1).

Clearing up an ambiguity from RFC66 (and later RFC80)

RFC92 [na 1971] Never issued

I wonder what happened to it?

RFC91 [27 Dec 1970] "A PROPOSED USER-USER PROTOCOL" p(12).

George H. Mealy talks about finding ways of accommodating differences in systems at a higher level than the communication system (e.g. representation of integers is cited as an example).

RFC90 [25 Jan 1971] "CCN AS A NETWORK SERVICE CENTER" p(6)

CCN soon to join the ARPA network and describes its systems. In particular, note "CN operates an IBM 360/91KK, i.e., a Model 91 CPU with a 4 million byte fast memory."

RFC89 [19 Jan 1971] "SOME HISTORIC MOMENTS IN NETWORKING" p(7).

Notes on connecting several systems using a partial protocol and observing the resulting behaviour.

RFC88 [13 Jan 1971] "NETRJS – A THIRD LEVEL PROTOCOL FOR REMOTE JOB ENTRY" p(9).

NETRJS described as Network Remote Job Service. Talks about OS/360. Defining a ‘block’ of data to be a string of bytes.

RFC87 [12 Jan 1971] "Topic for discussion at the next Network Working Group meeting p(3).

Planning the next project meeting for Project Mac.

RFC86 [05 Jan 1971] "Proposal for a Network Standard Format for a Data Stream to Control Graphics Display" p(6).

Looks like Steve Crocker talks about ways of handling graphic display feedback.

1970 (RFC28 to RFC85)

Here we go into 1970 – the year that brought me into the world. So far, 1970 focused on the development and implementation of a new Host-To-Host protocol outlined in RFC33 and RFC54.

RFC85 [Dec/1970] "NETWORK WORKING GROUP MEETING." p(1).

Setting the standard for Network Working Group meetings to be held every three months.

RFC84 [Dec/1970] "LIST OF NWG/RFC’s 1-80" p(8).

List showing the first 80 RFC documents. I notice they are all cross referenced with a NIC numbers (e.g. RFC 1 = NIC 4687) – something to investigate.

RFC83 [Dec/1970] "LANGUAGE-MACHINE FOR DATA RECONFIGURATION" p(13).

Building on the protocol manager described in RFC80.

RFC82 [Dec/1970] "Network Meeting Notes" p(18).

More notes further to those in RFC77 – from the same set of meetings.

RFC81 [Dec/1970 "Request for Reference Information" p(1)

Center for Advanced Computation requests information  on communications theory.

RFC80 [01 Dec 1970] "PROTOCOLS AND DATA FORMATS" p(9).

More comments and analysis from RFC66, in particular talking about RAND approach and two particular issues – a variation of protocol and a restatement of an understanding.

RFC79 [16 Nov 1970] "Logger Protocol Error" p(1).

Alert sent out regarding an error found on RFC66.

RFC78 [na 1970] "NCP Status Report:  UCSB/RAND" p(1).

Brief note describing test result from an implementation of the first protocol.

RFC77 [20 Nov 1970] "Network Meeting Report" p(9).

Notes from the November 16, 1970 Network Meeting (27 Attendees).

RFC76 [28 Oct 1970] "Connection-By-Name: User-Oriented Protocol" p(15).

Suggestion and outline of a new protocol. Mentions the Illiac IV Supercomputer. Implementing a layer on top of the network services that takes care of the details, allowing users to use a "telephone book" style directory.

RFC75 [14 Oct 1970] "Network Meeting" p(1) – Network Working Group arrangements. p(1)

Arranging a network meeting for November 16, 1970.

RFC74 [16 Oct 1970] "Specification for Network Use of the UCSB On-Line Systems"

Not available or missing

RFC73 [25 Sep 1970] "Response to NWM/RFC #67" p(1).

Crocker supports RFC72 in delaying changes discussed in RFC67.

RFC72 [28 Sep 1970] "PROPOSED MORATORIUM ON CHANGES TO NETWORK PROTOCOL" p(3).

Picking up on RFC67 suggesting a delay be introduced for any new revisions of agreed implementations.

RFC71 [25 Sep 1970] "Reallocation in Case of Input Error" p(1). Tjaart Schipper describes how UCLA will handle flow control for the new protocol.

RFC70 [15 Oct 1970] "A Note on Padding" p(9).

Discussions on bit padding.

RFC69 [22 Sep 1970] "Distribution List Change for M.I.T." p(1).

A. Bhushan requests to be removed from distribution list and replaced with Albert Vezza.

RFC68 [31 Aug 1970] "Comments on memory allocation control commands CEASE, ALL, GVB, RET) and RFNM" p(2).

Clarifying the Request For Next Message process in relation to sending an ACK signal.

RFC67 [na 1970] "Proposed Change to Host/IMP Spec to Eliminate Marking" p(1).

Crowther suggests the agreement to implement RFC64.

RFC66 [26 Aug 1970] "3rd Level Ideas and other Noises" p(3).

Highlighting a minor issue with the IMP software running on a PDP-10.

RFC65 [29 Aug 1970] "Comments on Host-Host Protocol Document No. 1 (S. Crocker – 8/3/70)" p(2).

Further commends on Host-To-Host protocol.

RFC64 [na 1970] "Getting Rid of Marking" p(4).

Suggested improvement for the IMP-HOST interface to avoid the need for marking.

RFC63 [31 Jul 1970] "Belated Network Meeting Report" p(2).

Review of meeting a Lincoln Labs primarily talking about Lincoln Labs Interaction Language and RFC42.

RFC62 [03 Aug 1970] " A System for Interprocess Communication in a Resource Sharing Computer Network" p(20).

Supercedes RFC61 as Walden tries to take a high level consideration of the process of network sharing.

RFC61 [17 Jul 1970] "A Note on Interprocess Communication in a Resource Sharing Computer Network" p(18).

Describes a resource sharing computer network talking about ad-hoc paired computers (think Bluetooth),  and a network wide system using time sharing. We are starting to see discussion about using tiers/layers in protocol communication. The longest RFC to date and Walden actually references other documents to support his argument.

RFC60 [13 Jul 1970] "A Simplified NCP Protocol" p(8).

R. Kalin starts this RFC with the note "This memo defines an Experimental Protocol for the Internet community" and attempts to propose an alternative protocol to the one described in RFC54.

RFC59 [27 Jun 1970] "MIT Project MAC" p(7).

The first RFC I have read which seems to break all agreed documentation conventions. Notes on RFC54.

RFC58 [26 Jun 1970] "Logical Message Synchronization" p(2)

The idea of synchronising messages is discussed by T. P. Skinner in particular how to deal with logical messages transmitted over physical connections. An early discussion about Transport Protocols perhaps?

RFC57 [19 Jun 1970] "Thoughts and Reflections on NWG/RFC #54" p(5)

Suggestions for improvements and future enhancements to the protocol discussed in RFC54.

RFC56 [19 Jun 1970] "Third Level Protocol, Logger Protocol, General Description" p(6)

Describes four programs to communicate host to host: a send-logger, a receive-logger, sender, receiver. The RFC proposes a protocol to queue multiple requests.

RFC55 [19 Jun 1970] "A Prototypical Implementation of the NCP" p(23)

The first attempt at turning the protocol into a prototype – the implementation was eventually abandoned as "the code was becoming unreadable".

RFC54 [18 Jun 1970] "An Official Protocol Proffering" p(9)

In particular June 18, 1970 – the first draft of a host-to-host protocol for transmission of content over the network.

RFC53 [09 Jun 1970] "An Official Protocol Mechanism" p(1)

Outlines the process for creating the host-to-host protocol – in particular the first version of the protocol should be available this month.

RFC52 [01 Jul 1970] "Updated Distribution List" p(1)

The distribution list grows again – to 18 this time.

RFC51 [4 May 1970] "Proposal for a Network Interchange Language"

Not available or missing

RFC50 [30 Apr 1970] "Comments on the Meyer Proposal" p(2)

Another team touches based with their comments on the proposal.

RFC49 [25 Apr 1970] "Conversations with Steve Crocker (UCLA)" p(5)

Primarily discussing the rejection of the dynamic reconnection, by Edwin W. Meyer, Jr.

RFC48 [21 Apr 1970] "A Possible Protocol Plateau" p(18)

Attempting to formalise the protocol and consider the suggestions and modifications.

RFC47 [20 Apr 1970] "BBN’s Comments on NWG/RFC #33" p(4)

Bill Crowther identifies two substantial erros in RFC33 proposal in particular the previous assumption that buffering was caused by the IMP whereas it was actually caused by the phone line hardware.

RFC46 [17 Apr 1970] "ARPA Network Protocol Notes" p(17)

More descriptive and precise version of RFC36 explaining how to implement the various control commans. Interestinly, the ERR command suggested in RFC40 has been included. First RFC by Edwin W. Meyer, Jr.

RFC45 [14 Apr 1970] "New Protocol is Coming" p(1)

Announcing April 28 as the date for the cleaned up protocol ready for implementation.

RFC44 [10 Apr 1970] "Comments on NWG/RFC 33 and 36" p(3)

Refinement suggestions for protocol specified in RFC36 in particular the suggestion to use 8-bit NCC (Network Common Code) instead of the rejected ASCII-8 code.

RFC43 [08 Apr 1970] "Proposed Meeting" p(1)

A. G. Nemeth in their first RFC calling for a meeting to discuss LIL (Local Interaction Language) and TSP (Terminal Support Processor).

RFC42 [31 Mar 1970] "Message Data Types" p(3)

Suggesting the reservation of the first 8 bits of a message to be a message type indicator without specifying the actua[ message types - best read in relation to RFC31.

RFC41 [30 Mar 1970] "IMP/IMP Teletype Communication" p(1)

Suggestion to tag all all IMP to IMP messages with the date and time of the message. First RFC by John Melvin.

RFC40 [27 Mar 1970] "More Comments on the Forthcoming Protocol" p(3)

Elaborating the suggested debugging codes from RFC39.

RFC39 [25 Mar 1970] "COMMENTS ON PROTOCOL RE: NWG/RFC #36" p(3)

Suggesting the addition of debugging codes for the proposed protocl. First RFC by E. Harslem and J. Heafner.

RFC38 [20 Mar 1970] "Comments on Network Protocol from NWG/RFC #36" p(1)

Raising concerns over the lack of multiplexing support in the proposed protocol. First RFC by Stephen M. Wolfe.

RFC37 [20 Mar 1970] "Network Meeting Epilogue, etc.". p(5)

Clarification of results of meeting called for in RFC35. Interestingly this RFC was published when I came into the world.

RFC36 [16 Mar 1970] "Protocol Notes" p(8)

Notes on the protocol from RFC33.

RFC35 [03 Mar 1970] "Network Meeting" p(1)

Call for a meeting to discuss RFC33.

RFC34 [26 Feb 1970] "SOME BRIEF PRELIMINARY NOTES ON THE ARC CLOCK" p(1).

Talking about the differences between the absolute and relative time readings in the clock.

RFC33 [12 Feb 1970] "New HOST-HOST Protocol" p(19)

Revising RFC11 (RFC22). There is a comment made in this RFC "The Advanced Research Projects Agency (ARPA) Computer Network … is one of the most ambitious computer networks attempted to date." – If only they knew what it would eventually lead to…

RFC32 [31 Jan 1969] "SOME THOUGHTS ON SRI’S PROPOSED REAL TIME CLOCK" p(1).

Commenting on RFC28 and RFC29 in particular for measuring message delays. First RFC by Jerry Cole.

RFC31 [na Feb 1968] "MESSAGE FORMS IN COMPUTER NETWORKS" p(7)

Presumably a back-dated RFC and the first RFC by Daniel Bobrow and William R. Sutherland. Discussing ways of describing standard ways of organising content of binary messages after the header has been removed. Reading this article fourty years on it could be describing an early form of XML.

RFC30 [04 Feb 1970] "DOCUMENTATION CONVENTIONS" p(2)

Revision of RFC27.

RFC29 [19 Jan 1970] "Untitled" p(1)

Robert Kahn replied to RFC28 suggesting a millisecond clock should be sufficient. First RFC by Robert (Bob) Kahn whilst at BBN (Bolt Beranek and Newman).

RFC28 [13 Jan 1970] "TIME STANDARDS" p(1)

Implementing a real time clock on the system and calling for discussion on time standards. First RFC by Bill English (he developed the mouse ball!)

1969 (RFC1 to RFC27)

In 1969 a number of particularly interesting RFC emerge including:

• RFC1 (RFC is invented)
• RFC5 (DEL appears to be an early inspiration for Sun Java)
• RFC15 (Later to be adopted into Telnet standard)
• RFC20 (Adopting use 7-bit ASCII)

RFC27 [06 Dec 1969] "Documentation Conventions" p(2)

Revises RFC24 – The distribution list grows again.

RFC26 [na 1969] Never issued

I wonder what happened to it?

RFC25 [30 Oct 1969] "NO HIGH LINK NUMBERS" p(1)

Although 8 bits (and therefore 256 combinations) of links numbers are defined the suggestion is made to use only the first 6 bits (0-63) and perhaps even only 5 (0-31).

RFC24 [21 Nov 1969] "DOCUMENTATION CONVENTIONS" p(1)

It says it revised RFC16 and RFC10 but according the actual RFC it should be RFC10 and RFC3 – unless RFC16 is missing a few pages.

RFC23 [16 Oct 1969] "TRANSMISSION OF MULTIPLE CONTROL MESSAGES" p(1).

Block sending control messages. First RFC by G. Gregg.

RFC22 [17 Oct 1969] "Host-Host Control Message Formats" p(2).

The republished version of the missing RFC11 but adds an exception to RFC20 that allows 8-bit codes for Host-to Host control messages.

RFC21 [17 Oct 1969] "Network Group Meeting notes" p(1)

RFC20 [10 Oct 1969] "ASCII format for Network Interchange" p(9)

Seems to follow on from RFC6 but asserts the desire to use 7-bit ASCII in an 8 bit byte.

RFC19 [07 Oct 1969] "Two Protocol Suggestions to Reduce Congestion at Swap-Bound Nodes" p(2)

Dealing with network efficiency. Mentions the use of the IBM 360/50 at SDC.

RFC18 [na Sep 1969] "(use of links 1 and 2)" p(1)

Establishing the order of link usage to easily distinguish HOST-HOST and IMP-IMP links.

RFC17 [27 Aug 1969] "Some Questions Re: HOST-IMP Protocol" p(4).

Concerns of the automatic deletion of links and other issues around the HOST – IMP protocol. First RFC by J. Kreznar and R. Kahn (17a). Includes an additional RFC in the form of RFC 17(a).

RFC16 [27 Aug 1969] "M.I.T." p(1)

M.I.T added to the distribution list.

RFC15 [25 Sep 1969] "Network Subsystem for Time Sharing Hosts" p(5)

Uses the term "telnet" and is one of the first to be eventually adopted as an IETF standard "Telnet", a command line interface for communicating with network devices. First RFC by C. Stephen Carr. Describes the servers as being PDP-10 – the first server machines I used at college were PDP-11.

RFC14 [na na 1970] Never issued p(na)

I wonder what happened to it?

RFC13 [20 Aug 1969] "Untitled" p(1)

Marking End-Of-File with a zero length message be used First RFC by Vint Cerf.

RFC12 [26 Aug 1969] "IMP-HOST interface diagrams" p(6)

Some very nice ASCII interpretations of the flow between the IMP and the HOST. First RFC by M. Wingfield.

RFC11 [01 Aug 1979] "Implementation of the HOST-HOST Software Procedures in GORDO" p(na)

Not available or missing – see RFC22 above.

RFC10 [29 Jul 1969] "Documentation Conventions" p(2)

Very similar to RFC3 but distribution list increased and Steve Crocker now issuing RFC numbers.

RFC9 [01 May 1969] "HOST Software" p(na)

Not available or missing.

RFC8 [05 May 1969] "ARPA Network Functional Specifications" p(na)

Not available or missing.

RFC7 [05 May 1969] "Host-Imp Interface" p(7)

Discussing the design of the software interface between host devices and the packet switching Interface Message Processors (IMP). First RFC by G. Deloche.

RFC6 [10 Apr 1969] "Conversation with Bob Kahn" p(1)

Aiming to standardise on 8-bit character codes (9-bit character codes!).

RFC5 [02 Jun 1969] "DEL" p(na)

Outlines the initial syntax for Decode-Encode Language. Identifies the initial ARPA networking group met October 25, 1968. First RFC by Jeff Rulifson. Apparently, DEL was the precursor to the Sun Java language.

RFC4 [24 Mar 1969] "Network Timetable" p(6)

To do list for creation of the network. Adds "Category: Informational" to the documentation convention. This is the first RFC by Elmer B. Shapiro.

RFC3 [09 Apr 1969] "Documentation Conventions" p(1)

Explains how RFC documents work, timely rather than polished and a minimum of one sentence. Bill Duvall to issue RFC numbers.

RFC2 [09 Apr 1969]  "Host Software" p(10)

Refines the actions of links between hosts and clarifies error checking. This is the first RFC by Bill Duvall of SRI.

RFC1 [07 Apr 1969] "Host Software" p(11)

Talks about host to host communications , their links and error checking. This is the first RFC by Steve Crocker of UCLA (University of California, Los Angeles).

Glossary

• ARPA Advanced Research Projects Agency (Decommissioned in 1990 to form the DARPA)
• BBN Bolt Beranek and Newman Inc.
• DEL Decode-Encode Language
• FTP File Transfer Protocol
• IETF Internet Engineering Task Force
• IMP Interface Messaging Processor – think of it as a router
• LRC Learning Resource Centre
• MITRE
• NIC Network Information Center
• NWG Network Working Group
• RFC Request for Comments
• SAIL Stanford Artificial Intelligence Laboratory
• SMFS Simple Minded File System
• SRI Stanford Research Institute
• TENNEX T
• TIP

Further Reading

You can learn more about RFC in this post What is RFC ? 

Visit the IETF at their home page http://www.ietf.org/

This article is from Jason Slater Technology Blog.