ARPANET Protocols: Difference between revisions
NCommander (talk | contribs) (→NETCRT) |
NCommander (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
This section covers protocols that were at one used or tested on ARPANET. This list is not considered to be comprehensive, but should cover any protocol predating RFC 791 or 1981, which defined IP. These protocols, by and later cover | This section covers protocols that were at one used or tested on ARPANET. This list is not considered to be comprehensive, but should cover any protocol predating RFC 791 or 1981, which defined IP. These protocols, by and later cover | ||
=== | === Protocols Listed in RFC 349 === | ||
[https://datatracker.ietf.org/doc/html/rfc359 RFC 349] contains the earlist listen of "well known services" as of 1972, and assigns static socket numbers. NCP was a half-duplex protocol, so each application was assigned in pairs of two (so telnet would use sockets 1 and 2). | |||
{| class="wikitable" | |||
|+ ARPANET Well Known Sockets | |||
|- | |||
! Socket !! Assignment | |||
|- | |||
| 1 || Telnet | |||
|- | |||
| 3 || File Transfer | |||
|- | |||
| 5 || Remote Job Entry | |||
|- | |||
| 7 || Echo | |||
|- | |||
| 9 || Discard | |||
|- | |||
|} | |||
==== TELNET ==== | ==== TELNET ==== | ||
Originally defined in [https://www.rfc-editor.org/rfc/ | Originally defined in [https://datatracker.ietf.org/doc/html/rfc15 RFC 15]. User experience is documented in [https://www.rfc-editor.org/rfc/rfc206.txt RFC 206] | ||
==== FTP ==== | ==== FTP ==== | ||
Originally defined in [https://datatracker.ietf.org/doc/html/rfc114 RFC 114]. | |||
==== NETRJS ==== | |||
Remote Job Submission [https://datatracker.ietf.org/doc/html/rfc325 RFC 325] | |||
==== Echo Protocol ==== | |||
Provides a loopback service to determine if a given host is available or not. Considered obsolete on modern systems, originally documented as [https://www.rfc-editor.org/rfc/rfc347 RFC 347]. | |||
==== Discard Protocol ==== | |||
Discards all incoming data; intended to use for diagnostic and testing. Documented as [https://www.rfc-editor.org/rfc/rfc348 RFC 348] | |||
=== Protocols with known implementations === | |||
These protocols are known to have at least some sort of implementation as documented by later documentations, or exist in some form in archived source code or similar. | |||
==== Login ==== | ==== Login ==== | ||
==== NETCRT ==== | ==== NETCRT ==== | ||
[https://www.rfc-editor.org/rfc/ | NETWORK CHARACTER DISPLAY PROTOCOL. [https://datatracker.ietf.org/doc/html/rfc205 RFC 205]. Implementation notes discussed on [https://www.rfc-editor.org/rfc/rfc387.txt RFC 387] | ||
=== NAME/FINGER === | |||
[https://datatracker.ietf.org/doc/html/rfc742 RFC742] | |||
=== Simple Minded File System ==== | |||
[https://datatracker.ietf.org/doc/html/rfc112 RFC112] | |||
=== Mail Protocols === | === Mail Protocols === | ||
| Line 29: | Line 65: | ||
==== Host-IMP Protocol (1822) ==== | ==== Host-IMP Protocol (1822) ==== | ||
Documented in [https://www.rfc-editor.org/rfc/rfc7 RFC 7], the Host-IMP protocol is the set of commands that a given computer would use to talk to ARPANET directly. It's comparable to the AT commands used in Hayes modems. | Documented in [https://www.rfc-editor.org/rfc/rfc7 RFC 7], the Host-IMP protocol is the set of commands that a given computer would use to talk to ARPANET directly. It's comparable to the AT commands used in Hayes modems. | ||
=== Other === | === Other === | ||
==== Network Voice Protocol ==== | ==== Network Voice Protocol ==== | ||
==== Network Graphics Protocol ==== | |||
Originally discussed in[https://www.rfc-editor.org/rfc/rfc94.txt RFC94], and more formally defined in [https://www.rfc-editor.org/rfc/rfc186.txt RFC186], its unclear if the Network Graphics Protocol was ever used beyond basic testing. [https://www.rfc-editor.org/rfc/rfc387.txt RFC387] discusses real world problems in deploying graphics over the network, and a need to design for the least common denominator. | |||
== CSNET/NSFNET Era (1981-1989) == | == CSNET/NSFNET Era (1981-1989) == | ||
This era largely covers the growth and development of | |||
=== Berkeley r-commands === | |||
R utilties represent commands popularized by BSD, and common in most TCP/IP implements of the era == | |||
=== rexec === | |||
=== | |||
== The World Wide Web (1990-2000) == | == The World Wide Web (1990-2000) == | ||
Revision as of 11:51, 4 October 2022
This page keeps track of ARPANET protocols, classified by status, and RFC and year.
Used on ARPANET (1969-1981)
This section covers protocols that were at one used or tested on ARPANET. This list is not considered to be comprehensive, but should cover any protocol predating RFC 791 or 1981, which defined IP. These protocols, by and later cover
Protocols Listed in RFC 349
RFC 349 contains the earlist listen of "well known services" as of 1972, and assigns static socket numbers. NCP was a half-duplex protocol, so each application was assigned in pairs of two (so telnet would use sockets 1 and 2).
| Socket | Assignment |
|---|---|
| 1 | Telnet |
| 3 | File Transfer |
| 5 | Remote Job Entry |
| 7 | Echo |
| 9 | Discard |
TELNET
Originally defined in RFC 15. User experience is documented in RFC 206
FTP
Originally defined in RFC 114.
NETRJS
Remote Job Submission RFC 325
Echo Protocol
Provides a loopback service to determine if a given host is available or not. Considered obsolete on modern systems, originally documented as RFC 347.
Discard Protocol
Discards all incoming data; intended to use for diagnostic and testing. Documented as RFC 348
Protocols with known implementations
These protocols are known to have at least some sort of implementation as documented by later documentations, or exist in some form in archived source code or similar.
Login
NETCRT
NETWORK CHARACTER DISPLAY PROTOCOL. RFC 205. Implementation notes discussed on RFC 387
NAME/FINGER
Simple Minded File System =
Mail Protocols
Due to an influx of different systems and needs, a large number of email systems were to exchange mail between systems. How much these were used is a matter of some debate.
SENDMSG
Mailbox
Network Utilities
Network utilities represents testing protocols, or infrastructure ones
Host-IMP Protocol (1822)
Documented in RFC 7, the Host-IMP protocol is the set of commands that a given computer would use to talk to ARPANET directly. It's comparable to the AT commands used in Hayes modems.
Other
Network Voice Protocol
Network Graphics Protocol
Originally discussed inRFC94, and more formally defined in RFC186, its unclear if the Network Graphics Protocol was ever used beyond basic testing. RFC387 discusses real world problems in deploying graphics over the network, and a need to design for the least common denominator.
CSNET/NSFNET Era (1981-1989)
This era largely covers the growth and development of
Berkeley r-commands
R utilties represent commands popularized by BSD, and common in most TCP/IP implements of the era ==