The RFC Archive
 The RFC Archive   RFC 701   « Jump to any RFC number directly 
 RFC Home
Full RFC Index
Recent RFCs
RFC Standards
Best Current Practice
RFC Errata
1 April RFC



IETF RFC 701

August, 1974, survey of New-Protocol Telnet servers

Last modified on Thursday, October 15th, 1992

Permanent link to RFC 701
Search GitHub Wiki for RFC 701
Show other RFCs mentioning RFC 701

					AUGUST, 1974

	AUGUST, 1974, SURVEY OF NEW-PROTOCOL TELNET SERVERS

THIS IS THE FIRST OF WHAT ARE PLANNED TO BE MONTHLY REPORTS ON
THE STATUS OF THE NEW-PROTOCOL TELNET IMPLEMENTAIONS ON THE SERVER
HOSTS ON THE ARPA NETWORK.  INCLUDED IN THIS REPORT ARE DATA ONLY
ON SERVER TELNETS AT THE VARIOUS SITES.  ONE WOULD HOPE THAT ANY
SITE WITH AN OPERATIONAL NEW-PROTOCOL SERVER TELNET WOULD ALSO BOAST
A NEW-PROTOCOL USER TELNET; WE CAN CERTAINLY ASSUME THIS FOR TENEX
SITES AT WHICH TENEX 1.32 IS OPERATING.  HOWEVER, NO FURTHER CLAIMS
ARE MADE FOR THE SERVER DATA CONTAINED IN THIS REPORT.

I AM 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 CORRECTLY THE LOGGER SOCKET CONVENTIONS, AS I
UNDERSTAND THEM.  AT THE END OF THIS REPORT IS A COMPLETE TABULATION
COMPILED FROM MY SURVEYS;  THE FOLLOWING IS A 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 DATA IN THIS REPORT WERE GATHERED VIA A SURVEYING PROGRAM
   RUN AT VARIOUS TIMES, PLUS A FEW MANUAL CHECKS TO FILL OUT THE
   DATA.  WHAT IS 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.

(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.



TABULATION OF SERVER STATUS 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: 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. SUBMITTED 20 AUGUST 1974 BY D. W. DODDS August, 1974, survey of New-Protocol Telnet servers RFC TOTAL SIZE: 3549 bytes PUBLICATION DATE: Thursday, October 15th, 1992 LEGAL RIGHTS: The IETF Trust (see BCP 78)


RFC-ARCHIVE.ORG

© RFC 701: The IETF Trust, Thursday, October 15th, 1992
© the RFC Archive, 2024, RFC-Archive.org
Maintainer: J. Tunnissen

Privacy Statement