RFC 701
August, 1974, survey of New-Protocol Telnet servers
RFC 701: August, 1974 Survey of New-Protocol Telnet Servers β¨
- Author: D. W. Dodds π§
- Date: August 1974 (submitted 20 August 1974) π
- Category or status: not stated in the document π€·ββοΈ
- Obsoletes: nothing listed π
- Updates: nothing listed π
Introduction π
okay bestie, this is the first of what are planned to be monthly reports on the status of the new-protocol TELNET implementations on the server hosts on the ARPA Network πΈ this one only has data on server TELNETs at the various sites. ngl, you'd hope that any site with a working new-protocol server TELNET would also have a new-protocol user TELNET too π we can totally assume that for TENEX sites running TENEX 1.32. but no further claims are made for the server data in this report, so don't come for me π
I'm sorry to report that, at this late date (a month after the release of TENEX 1.32 π), less than one-third of the server sites have any new-protocol server operating, according to my surveys*. and only half of those are using the logger socket conventions correctly, as I understand them π at the end of this report is a complete tabulation compiled from my surveys. here's the summary:
TOTAL SERVER HOSTS 32 100%
STATUS UNKNOWN (1) 3 9%
NO NEW-PROT SERVER 19 59%
TOTAL NEW-PROT IMPLEM. 10 31%
NEW-PROT ON SOCKET 27,
OLD ON SOCKET 1 (2) 5 16%
NEW-PROT ON 1 AND 27 (3) 4 13%
NEW-PROT ON 1 ONLY (3) 1 3%
Notes πΈ
* all the data in this report was gathered via a surveying program run at various times, plus a few manual checks to fill out the data. what's reported here is the way the various servers work as seen by the new-protocol user TELNET at BBNA, as of 15 Aug. 1974. there may be discrepancies between these results and those from surveys made at other sites, so keep that in mind β¨
(1) numerous attempts to connect to these sites all failed due to the sites' being down to the network π©
(2) these are the sites whose operation is 100% correct according to all protocols and conventions, as I understand them π
(3) we realize that some of the servers that appear here as new-protocol servers on socket 1 are actually servers which attempt to communicate with both old- and new-protocol user TELNETs, according to what control sequences are received π¦
Server Status Tabulation for All Server Sites π¦
HOST HOST SOCKET SOCKET NEW-PROT. OPTIONS
NO. NAME 1 27 IMPLEMENTATED (IF ANY)
1 UCLA-NMC ? ?
101 UCLA-CCN OLD X
201 UCLA-CCBC OLD X
2 SRI-ARC OLD X
102 SRI-AI OLD X
3 UCSB-MOD75 OLD X
4 UTAH-10 OLD X
105 BBN-TENEX OLD NEW I1,3,6; 03
205 BBN-TENEXB OLD NEW I1,3,6; 03
305 BBN-TENEXA OLD NEW I1,3,6; 03
106 MIT-DMS NEW NEW I1,3; 03
206 MIT-AI OLD X
306 MIT-ML OLD X
10 SDC-LAB ? ?
11 HARV-10 NEW X I1,3; 03
12 LL-67 OLD X
112 LL-TX-2 OLD X
13 SU-AI NEW* NEW* I1,3
15 CASE-10 OLD X
16 CMU-10B NEW NEW I1,3; 03
116 CMU-10A NEW NEW I1,3; 03
17 I4-TENEX OLD X
117 I4-TENEXA ? ?
20 AMES-67 OLD OLD(1)
126 USC-ISI OLD X
27 USC-44 OLD X
32 SDAC OLD X
37 CCA-TENEX OLD X
40 PARC-MAXC OLD NEW I1,3,6; 03
43 UCSD-CC OLD NEW IO(1),3; 00,3
53 OFFICE-1 OLD X
54 MIT-MULTICS NEW NEW NONE
Key π§
KEY:
X NO SEVER AT THIS SOCKET
? STATUS UNKNOWN
I# OPTION # IMPLEMENTED INCOMING TO USER
(SERVER SAYS "WILL #")
O# OPTION # IMPLEMENTED OUTGOING FROM USER
(SERVER SAYS "DO #")
(# IS OPTION NUMBER IN NEW PROTOCOL. ALL OPTIONS
IMPLEMENTED BY ANYONE ARE:
0 TRANSMIT-BINARY
1 ECHO
3 SUPRESS-GO-AHEAD
6 TIMING MARK )
Note π
* there appears to be a minor bug in SU-AI's server: it seems to send an improper response to a request for option O. that's the tea β
Submitted 20 August 1974 by D. W. Dodds π«Ά you're literally the best, RFC 701 era π
π¦ where this page comes from
- ietf: rfc701 1974-08
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms