Who talks ICMP, too? - Survey of 18 February 1983
A survey of Telnet connections from a Class C site to listed Internet hosts.
Clements, R., "Who talks ICMP, too? - Survey of 18 February 1983", RFC 844, DOI 10.17487/RFC0844, February 1983, <https://www.rfc-editor.org/info/rfc844>.
@misc{rfc844,
series = {Request for Comments},
number = 844,
howpublished = {RFC 844},
publisher = {RFC Editor},
doi = {10.17487/RFC0844},
url = {https://www.rfc-editor.org/info/rfc844},
author = {R. Clements},
title = {{Who talks ICMP, too? - Survey of 18 February 1983}},
pagetotal = 5,
year = 1983,
month = feb,
} RFC text
Network Working Group R. Clements Request for Comments: 844 February 1983 Who Talks ICMP, too? Survey of 18 February 1983 A survey was undertaken to determine how many hosts are able to respond to TELNET connections from a user at a class C site. This requires, in addition to IP and TCP, participation in gateway routing via ICMP and handling of class C addresses. The list of hosts was taken from RFC843, extracting only those hosts which are listed there as accepting TELNET connections. The tests were run on 18-Feb-83 from 3 PM to 6:30 PM EST from a terminal concentrator located at 192.1.2.22, at BBN. This net (192.1.2.xxx) is connected to the internet through a routing gateway, and this terminal concentrator speaks ICMP including redirection and reporting to the user. The connection attempts were done manually by typing the dotted form addresses, so only three passes were made through the table of hosts. Therefore a few may have been missed due to being down at these times. Summary information: Type # OK out of % OK ---- ---- ------ ---- On net 10 77 121 63.6% other class A 20 34 58.8% non-class A 30 32 93.8% Total 127 187 67.9% Results in host table order: Name Address Result ---- ------- ------ ll 10.0.0.10 no response compion-vms 10.0.0.12 no response ames-tss 10.0.0.16 refused mitre 10.0.0.17 OK radc-multics 10.0.0.18 OK nbs-vms 10.0.0.19 no response usc-eclb 10.0.0.23 OK nadc 10.0.0.24 OK seismo 10.0.0.25 OK usc-isid 10.0.0.27 OK brl 10.0.0.29 no response nosc-cc 10.0.0.3 OK cca-unix 10.0.0.31 OK parc-maxc 10.0.0.32 OK purdue 10.0.0.37 OK utah-cs 10.0.0.4 host unreachable wpafb 10.0.0.47 no response afwl 10.0.0.48 no response bbn-tenexb 10.0.0.49 OK bbnf 10.0.0.5 OK ada-vax 10.0.0.52 no response afsc-ad 10.0.0.53 no response cit-20 10.0.0.54 OK sumex-aim 10.0.0.56 OK nyu 10.0.0.58 no response mit-multics 10.0.0.6 OK utexas-11 10.0.0.62 OK usgs1-multics 10.0.0.68 OK usgs2-multics 10.0.0.69 OK usgs3-multics 10.0.0.70 OK sri-nic 10.0.0.73 OK ucb-arpa 10.0.0.78 no response nrl 10.0.0.8 no response hi-multics 10.0.0.80 OK dtnsrdc 10.0.0.81 OK bbnt 10.0.0.82 OK nswc-dl 10.0.0.84 OK sandia 10.0.0.87 OK nlm-mcs 10.0.0.88 OK lanl-unix 10.0.0.90 OK washington 10.0.0.91 OK ucla-ccn 10.1.0.1 OK ll-vlsi 10.1.0.10 OK compion 10.1.0.12 no response gunter-adam 10.1.0.13 OK cmu-cs-a 10.1.0.14 OK nbs-sdc 10.1.0.19 no response sri-kl 10.1.0.2 OK lll-mfe 10.1.0.21 OK usc-isi 10.1.0.22 OK usc-eclc 10.1.0.23 OK apg-1 10.1.0.29 OK cca-vms 10.1.0.31 refused lbl-csam 10.1.0.34 no response wpafb-afwal 10.1.0.47 no response bbng 10.1.0.5 OK usc-isie 10.1.0.52 OK cit-vax 10.1.0.54 no response anl-mcs 10.1.0.55 no response mit-dms 10.1.0.6 OK utexas-20 10.1.0.62 OK martin-b 10.1.0.64 OK rand-relay 10.1.0.7 OK bbn-unix 10.1.0.72 OK mit-devmultics 10.1.0.77 host unreachable dec-marlboro 10.1.0.79 OK nrl-aic 10.1.0.8 OK nalcon 10.1.0.81 no response bbn-vax 10.1.0.82 OK nswc-g 10.1.0.84 no response office-10 10.1.0.93 no response csnet-sh 10.1.0.94 OK srijoyce 10.1.4.51 no response ucla-security 10.2.0.1 OK sri-csl 10.2.0.2 OK isi-vaxa 10.2.0.27 OK office-3 10.2.0.43 no response sri-unix 10.2.0.51 no response usc-isif 10.2.0.52 OK afsc-dev 10.2.0.53 no response aids-unix 10.2.0.56 host unreachable rutgers 10.2.0.58 OK mit-ai 10.2.0.6 OK aerospace 10.2.0.65 OK sri-ai 10.2.0.73 OK ucb-vax 10.2.0.78 no response nswc-wo 10.2.0.8 no response ucla-ats 10.3.0.1 OK su-score 10.3.0.11 OK cmu-cs-c 10.3.0.14 OK radc-tops20 10.3.0.18 OK sri-tsc 10.3.0.2 no response edn-unix 10.3.0.20 OK usc-ecl 10.3.0.23 OK brl-bmd 10.3.0.29 no response nprdc 10.3.0.3 OK kestrel 10.3.0.32 no response utah-20 10.3.0.4 OK office-7 10.3.0.43 no response mit-mc 10.3.0.44 OK okc-unix 10.3.0.46 host unreachable bbn-tenexc 10.3.0.49 OK bbna 10.3.0.5 OK sri-prmh 10.3.2.51 no response usc-isib 10.3.0.52 OK jpl-vax 10.3.0.54 no response mit-ml 10.3.0.6 OK rand-unix 10.3.0.7 OK sri-iu 10.3.0.73 no response mcclellan 10.3.0.78 no response nsrdcoa 10.3.0.81 no response bbns 10.3.0.82 host unreachable nwc-387b 10.3.0.85 OK uw-vlsi 10.3.0.91 OK s1-c 10.3.0.95 OK ll-en 10.4.0.10 no response dca-ems 10.4.0.20 OK bbn-clxx 10.4.0.49 OK bbn-rsm 10.4.0.82 no response bbn-noc2 10.6.0.82 OK nrl-css 10.7.0.8 OK ucl-cs 11.3.1.42 OK ucl-ucl2 11.3.2.42 OK cmu-cs-ius 128.2.254.128 OK cmu-cs-vlsi 128.2.254.129 OK cmu-cs-zog 128.2.254.131 OK cmu-cs-g 128.2.254.132 OK cmu-cs-cad 128.2.254.133 OK cmu-ri-fas 128.2.254.138 OK cmu-cs-spice 128.2.254.139 OK cmu-cs-gandalf 128.2.254.140 OK cmu-ri-isl 128.2.254.143 OK cmu-cs-speech 128.2.254.145 OK cmu-cs-unh 128.2.254.150 no response cmu-ri-arm 128.2.254.151 OK cmu-ri-isl2 128.2.254.152 OK cmu-cs-pt 128.2.254.155 OK dcn1 128.4.0.1 OK dcn2 128.4.0.2 OK dcn3 128.4.0.3 OK dcn5 128.4.0.5 OK dcn6 128.4.0.6 OK ford1 128.5.0.1 OK ford3 128.5.0.3 OK ford4 128.5.0.4 OK ford-lab 128.5.0.8 OK ford-ecc 128.5.0.11 OK ford-ers 128.5.0.13 OK ford-eed 128.5.0.14 OK ford-wdl1 128.5.32.1 no response ford-wdl6 128.5.32.6 OK umd1 128.8.0.1 OK umd3 128.8.0.3 OK umd5 128.8.0.5 OK mit-csr 18.10.0.8 no response mit-ajax 18.10.0.64 no response mit-cls 18.10.0.76 no response csnet-sh 192.5.2.3 OK edn-host1 21.1.0.1 host unreachable bbncca 3.0.0.2 OK bbnccf 3.0.0.4 OK bbnx 3.0.0.8 OK csnet-cic 3.0.0.14 OK bbn-noc 3.1.0.14 OK bbnccb 3.1.0.2 OK bbn-admin 3.1.0.6 OK bbnz 3.1.0.7 OK bbnccc 3.2.0.2 OK bbnp 3.2.0.4 OK bbn-inoc 3.2.0.6 OK bbnq 3.2.0.7 OK bbny 3.2.0.8 OK bbnccd 3.3.0.2 OK bbncci 3.3.0.4 OK bbnw 3.3.0.6 OK bbn-cd 3.3.0.9 OK ucbarpa 46.0.0.4 no response ucbcad 46.0.0.5 no response ucbernie 46.0.0.6 no response ucbmonet 46.0.0.7 no response ucbesvax 46.0.0.9 no response ucbvax 46.0.0.10 no response ucbkim 46.0.0.11 no response ucbcalder 46.0.0.12 no response ucbmatisse 46.0.0.14 no response ucbingres 46.0.0.19 no response ndre1 48.3.1.41 OK -- end --
ISO Plain Language
On this page
§1What the Survey Tested
The survey asked how many hosts could respond to Telnet connections from a Class C site. Success required more than Telnet: the test also depended on IP, TCP, ICMP gateway routing, and correct handling of Class C addresses.
The test computer was a terminal concentrator at 192.1.2.22 at BBN, connected to the Internet through a routing gateway that supported ICMP.
The survey tested whether hosts could accept a Telnet connection from a Class C network. That checked several Internet functions working together.
§2Test Method
The author took hosts listed as accepting Telnet in RFC 843 and manually tried their dotted-form addresses on 18 February 1983 between 3 PM and 6:30 PM EST.
Only three passes were made through the host list. The report cautions that a host might have been missed because it was down during those attempts.
The tests were typed manually and repeated three times through the list. A host that was down at those times might not have been counted as reachable.
§3Reported Results
Of 187 hosts tested, 127 accepted the connection, for a reported success rate of 67.9%. The table groups outcomes by network type: 77 of 121 on network 10 accepted, 20 of 34 on other Class A networks accepted, and 30 of 32 on non-Class A networks accepted.
The detailed table records each host's address and result as OK, refused, no response, or host unreachable.
Most tested hosts accepted the connection, but results varied by network group. The report lists each attempt's outcome as well as the totals.