| 1 |
<pre>Network Working Group G. Kessler |
| 2 |
Request for Comments: 1739 S. Shepard |
| 3 |
Category: Informational Hill Associates, Inc. |
| 4 |
December 1994 |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">A Primer On Internet and TCP/IP Tools</span> |
| 8 |
|
| 9 |
Status of this Memo |
| 10 |
|
| 11 |
This memo provides information for the Internet community. This memo |
| 12 |
does not specify an Internet standard of any kind. Distribution of |
| 13 |
this memo is unlimited. |
| 14 |
|
| 15 |
Table of Contents |
| 16 |
|
| 17 |
<a href="#section-1">1</a>. Introduction .................................................. <a href="#page-2">2</a> |
| 18 |
2. A Beginner's Guide to TCP/IP-based Utilities and Applications . 2 |
| 19 |
<a href="#section-2.1">2.1</a>. NSLOOKUP .................................................... <a href="#page-3">3</a> |
| 20 |
<a href="#section-2.2">2.2</a>. PING ........................................................ <a href="#page-5">5</a> |
| 21 |
<a href="#section-2.3">2.3</a>. FINGER ...................................................... <a href="#page-6">6</a> |
| 22 |
<a href="#section-2.4">2.4</a>. TRACEROUTE .................................................. <a href="#page-7">7</a> |
| 23 |
<a href="#section-2.5">2.5</a>. FTP ......................................................... <a href="#page-10">10</a> |
| 24 |
<a href="#section-2.6">2.6</a>. TELNET ...................................................... <a href="#page-14">14</a> |
| 25 |
<a href="#section-2.7">2.7</a>. User Database Lookup Tools .................................. <a href="#page-17">17</a> |
| 26 |
<a href="#section-2.7.1">2.7.1</a>. WHOIS/NICNAME ............................................. <a href="#page-17">17</a> |
| 27 |
<a href="#section-2.7.2">2.7.2</a>. KNOWBOT ................................................... <a href="#page-20">20</a> |
| 28 |
<a href="#section-2.7.3">2.7.3</a>. NETFIND ................................................... <a href="#page-21">21</a> |
| 29 |
<a href="#section-2.8">2.8</a>. Information Servers ......................................... <a href="#page-24">24</a> |
| 30 |
<a href="#section-2.8.1">2.8.1</a>. ARCHIE .................................................... <a href="#page-24">24</a> |
| 31 |
<a href="#section-2.8.2">2.8.2</a>. GOPHER .................................................... <a href="#page-27">27</a> |
| 32 |
<a href="#section-2.8.3">2.8.3</a>. Other Information Servers ................................. <a href="#page-30">30</a> |
| 33 |
<a href="#section-2.9">2.9</a>. Uniform Resource Locator Format ............................. <a href="#page-31">31</a> |
| 34 |
<a href="#section-3">3</a>. Distribution Lists and Mailing Lists .......................... <a href="#page-32">32</a> |
| 35 |
<a href="#section-3.1">3.1</a>. Internet Discussion Lists ................................... <a href="#page-33">33</a> |
| 36 |
<a href="#section-3.2">3.2</a>. Usenet ...................................................... <a href="#page-33">33</a> |
| 37 |
<a href="#section-3.3">3.3</a>. BITNET/EARN ................................................. <a href="#page-35">35</a> |
| 38 |
<a href="#section-4">4</a>. Internet Documentation ........................................ <a href="#page-36">36</a> |
| 39 |
<a href="#section-4.1">4.1</a>. Request for Comments (RFCs) ................................. <a href="#page-36">36</a> |
| 40 |
<a href="#section-4.2">4.2</a>. Internet Standards .......................................... <a href="#page-38">38</a> |
| 41 |
<a href="#section-4.3">4.3</a>. For Your Information Documents .............................. <a href="#page-39">39</a> |
| 42 |
<a href="#section-4.4">4.4</a>. RARE Technical Reports ...................................... <a href="#page-40">40</a> |
| 43 |
<a href="#section-5">5</a>. Perusing the Internet ......................................... <a href="#page-40">40</a> |
| 44 |
<a href="#section-6">6</a>. Acronyms and Abbreviations .................................... <a href="#page-42">42</a> |
| 45 |
<a href="#section-7">7</a>. Security Considerations ....................................... <a href="#page-43">43</a> |
| 46 |
<a href="#section-8">8</a>. Acknowledgements .............................................. <a href="#page-43">43</a> |
| 47 |
<a href="#section-9">9</a>. References .................................................... <a href="#page-43">43</a> |
| 48 |
<a href="#section-10">10</a>. Authors' Addresses ........................................... <a href="#page-46">46</a> |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Kessler & Shepard [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
This memo is an introductory guide to some of the TCP/IP and Internet |
| 60 |
tools and utilities that allow users to access the wide variety of |
| 61 |
information on the network, from determining if a particular host is |
| 62 |
up to viewing a multimedia thesis on foreign policy. It also |
| 63 |
describes discussion lists accessible from the Internet, ways to |
| 64 |
obtain Internet documents, and resources that help users weave their |
| 65 |
way through the Internet. This memo may be used as a tutorial for |
| 66 |
individual self-learning, a step-by-step laboratory manual for a |
| 67 |
course, or as the basis for a site's users manual. It is intended as |
| 68 |
a basic guide only and will refer to other sources for more detailed |
| 69 |
information. |
| 70 |
|
| 71 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. A Beginner's Guide to TCP/IP-based Utilities and Applications</span> |
| 72 |
|
| 73 |
This section provides descriptions and detailed examples of several |
| 74 |
TCP/IP utilities and applications, including actual sessions using |
| 75 |
these utilities (with some extraneous information removed). Each |
| 76 |
section below describes a single TCP/IP-based tool, it's application, |
| 77 |
and, in some cases, how it works. The text description is followed |
| 78 |
by an actual sample session. |
| 79 |
|
| 80 |
The sample dialogues shown below were made using the Multinet TCP/IP |
| 81 |
software for VAX/VMS or DOS versions of FTP Software's PC/TCP. While |
| 82 |
the examples below can be used as a guide to using and learning about |
| 83 |
the capabilities of these tools, the reader should understand that |
| 84 |
not all of these utilities may be found at all TCP/IP hosts nor in |
| 85 |
all commercial software packages. Furthermore, the user interface |
| 86 |
for different packages will be different and the actual command line |
| 87 |
may appear differently than shown here; this will be particularly |
| 88 |
true for graphical user interfaces running over Windows, X-Windows, |
| 89 |
OS/2, or Macintosh systems. The Internet has many exciting things to |
| 90 |
offer but standardized interfaces to the protocols is not yet one of |
| 91 |
them! This guide will not provide any detail or motivation about the |
| 92 |
Internet Protocol Suite; more information about the TCP/IP protocols |
| 93 |
and related issues may be found in <a href="./rfc1180">RFC 1180</a> [<a href="#ref-18" title=""TCP/IP Tutorial"">18</a>], Comer [<a href="#ref-22" title=""Internetworking with TCP/IP, Vol. I: Principles, Protocols, and Architecture"">22</a>], Feit |
| 94 |
[<a href="#ref-23" title=""TCP/IP"">23</a>], and Kessler [<a href="#ref-30" title=""An Overview of TCP/IP Protocols and the Internet"">30</a>]. |
| 95 |
|
| 96 |
In the commands shown in the descriptions below, any item appearing |
| 97 |
in square brackets ([]) is optional and the vertical-bar (|) means |
| 98 |
"or"; parameters appearing with no brackets or within curly brackets |
| 99 |
({}) are mandatory. In the sample dialogues, most user input is in |
| 100 |
capital letters (only where allowed) and lines containing user input |
| 101 |
are designated with a "**" in the far-left margin. |
| 102 |
|
| 103 |
AUTHOR'S NOTE: The sample dialogues are easier to read in the |
| 104 |
secondary, Postscript version of this RFC. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Kessler & Shepard [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. NSLOOKUP</span> |
| 114 |
|
| 115 |
NSLOOKUP is the name server lookup program that comes with many |
| 116 |
TCP/IP software packages. A user can use NSLOOKUP to examine entries |
| 117 |
in the Domain Name System (DNS) database that pertain to a particular |
| 118 |
host or domain; one common use is to determine a host system's IP |
| 119 |
address from its name or the host's name from its IP address. The |
| 120 |
general form of the command to make a single query is: |
| 121 |
|
| 122 |
NSLOOKUP [IP_address | host_name] |
| 123 |
|
| 124 |
If the program is started without any parameters, the user will be |
| 125 |
prompted for input; the user can enter either an IP address or host |
| 126 |
name at that time, and the program will respond with the name and |
| 127 |
address of the default name sever, the name server actually used to |
| 128 |
resolve each request, and the IP address and host name that was |
| 129 |
queried. "Exit" is used to quit the NSLOOKUP application. |
| 130 |
|
| 131 |
Three simple queries are shown in the example below: |
| 132 |
|
| 133 |
1. Requests the address of the host named "emily.uvm.edu", a system at |
| 134 |
the University of Vermont (UVM). As it turns out, this is not the |
| 135 |
true name of the host, but a shortened version of the name that is |
| 136 |
accepted as an alias by the network. The full name of the host and |
| 137 |
the IP address are listed by NSLOOKUP. |
| 138 |
|
| 139 |
2. Requests the address of host "emily.emba.uvm.edu", which is the |
| 140 |
same host as in the first query. Note that NSLOOKUP provides a |
| 141 |
"non-authoritative" answer. Since NSLOOKUP just queried this same |
| 142 |
address, the information is still in its cache memory. Rather than |
| 143 |
send additional messages to the name server, the answer is one that |
| 144 |
it remembers from before; the server didn't look up the information |
| 145 |
again, however, so it is not guaranteed to still be accurate |
| 146 |
(because the information might have changed within the last few |
| 147 |
milliseconds!). |
| 148 |
|
| 149 |
3. Requests the name of the host with the given IP address. The |
| 150 |
result points to the Internet gateway to Australia, |
| 151 |
"munnari.oz.au". |
| 152 |
|
| 153 |
One additional query is shown in the dialogue below. NSLOOKUP |
| 154 |
examines information that is stored by the DNS. The default NSLOOKUP |
| 155 |
queries examine basic address records (called "A records") to |
| 156 |
reconcile the host name and IP address, although other information is |
| 157 |
also available. In the final query below, for example, the user |
| 158 |
wants to know where electronic mail addressed to the "uvm.edu" domain |
| 159 |
actually gets delivered, since "uvm.edu" is not the name of an actual |
| 160 |
host. This is accomplished by changing the query type to look for |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Kessler & Shepard [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 167 |
|
| 168 |
|
| 169 |
mail exchange (MX) records by issuing a "set type" command (which |
| 170 |
must be in lower case). The query shows that mail addressed to |
| 171 |
"uvm.edu" is handled though a mail server called "moose.uvm.edu". The |
| 172 |
DNS is beyond the scope of this introduction, although more |
| 173 |
information about the concepts and structure of the DNS can be found |
| 174 |
in STD 13/RFC 1034 [<a href="#ref-12" title=""Domain Names - Concepts and Facilities"">12</a>] and <a href="./rfc1591">RFC 1591</a> [<a href="#ref-13" title=""Domain Name System Structure and Delegation"">13</a>]. The "help" command can be |
| 175 |
issued at the program prompt for information about NSLOOKUP's more |
| 176 |
advanced commands. |
| 177 |
|
| 178 |
TECHNICAL NOTE: There are other tools that might be available on your |
| 179 |
system or with your software for examining the DNS. Alternatives to |
| 180 |
NSLOOKUP include HOST and DIG. |
| 181 |
|
| 182 |
================================================================== |
| 183 |
** SMCVAX$ NSLOOKUP |
| 184 |
|
| 185 |
Default Server: LOCALHOST |
| 186 |
Address: 127.0.0.1 |
| 187 |
|
| 188 |
** > EMILY.UVM.EDU |
| 189 |
Server: LOCALHOST |
| 190 |
Address: 127.0.0.1 |
| 191 |
|
| 192 |
Name: emily.emba.uvm.edu |
| 193 |
Address: 132.198.1.7 |
| 194 |
Aliases: emily.uvm.edu |
| 195 |
|
| 196 |
** > EMILY.EMBA.UVM.EDU |
| 197 |
Server: LOCALHOST |
| 198 |
Address: 127.0.0.1 |
| 199 |
|
| 200 |
Non-authoritative answer: |
| 201 |
Name: emily.emba.uvm.edu |
| 202 |
Address: 132.198.1.7 |
| 203 |
|
| 204 |
** > 128.250.1.21 |
| 205 |
Server: LOCALHOST |
| 206 |
Address: 127.0.0.1 |
| 207 |
|
| 208 |
Name: munnari.OZ.AU |
| 209 |
Address: 128.250.1.21 |
| 210 |
|
| 211 |
** > set type=MX |
| 212 |
** > UVM.EDU |
| 213 |
Server: LOCALHOST |
| 214 |
Address: 127.0.0.1 |
| 215 |
|
| 216 |
uvm.edu preference = 10, mail exchanger = moose.uvm.edu |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Kessler & Shepard [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 223 |
|
| 224 |
|
| 225 |
moose.uvm.edu internet address = 132.198.101.60 |
| 226 |
|
| 227 |
** > EXIT |
| 228 |
|
| 229 |
SMCVAX$ |
| 230 |
================================================================== |
| 231 |
|
| 232 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. PING</span> |
| 233 |
|
| 234 |
Ping is one of the most widely available tools bundled with TCP/IP |
| 235 |
software packages. Ping uses a series of Internet Control Message |
| 236 |
Protocol (ICMP) Echo messages to determine if a remote host is active |
| 237 |
or inactive, and to determine the round-trip delay in communicating |
| 238 |
with it. The Ping command, referred to as the Packet Internetwork |
| 239 |
Groper in some references, has the following general format: |
| 240 |
|
| 241 |
PING [-s] {IP_address | host_name} [size] [quantity] |
| 242 |
|
| 243 |
In the first test below, we ping the host "thumper.bellcore.com" to |
| 244 |
determine whether it is up and running. This simple use of the |
| 245 |
command contains no optional parameters. |
| 246 |
|
| 247 |
In the second test, the "-s" parameter tells the system to send an |
| 248 |
ICMP Echo message every second. The optional "size" parameter |
| 249 |
specifies that each message should be 64 bytes in length (which is |
| 250 |
the default size); the optional "quantity" parameter indicates that |
| 251 |
this test will only send 12 messages (the default is to run the test |
| 252 |
continuously until interrupted). The results of the second test |
| 253 |
displays the round-trip delay of each Echo message that is returned |
| 254 |
to the sending host; at the end of the test, summary statistics are |
| 255 |
displayed. |
| 256 |
|
| 257 |
================================================================== |
| 258 |
** SMCVAX$ PING THUMPER.BELLCORE.COM |
| 259 |
thumper.bellcore.com is alive |
| 260 |
|
| 261 |
** SMCVAX$ PING -S THUMPER.BELLCORE.COM 64 12 |
| 262 |
PING THUMPER.BELLCORE.COM (128.96.41.1): 56 data bytes |
| 263 |
64 bytes from 128.96.41.1: icmp_seq=0 time=150 ms |
| 264 |
64 bytes from 128.96.41.1: icmp_seq=1 time=110 ms |
| 265 |
64 bytes from 128.96.41.1: icmp_seq=2 time=130 ms |
| 266 |
64 bytes from 128.96.41.1: icmp_seq=3 time=130 ms |
| 267 |
64 bytes from 128.96.41.1: icmp_seq=4 time=320 ms |
| 268 |
64 bytes from 128.96.41.1: icmp_seq=5 time=110 ms |
| 269 |
64 bytes from 128.96.41.1: icmp_seq=6 time=440 ms |
| 270 |
64 bytes from 128.96.41.1: icmp_seq=7 time=90 ms |
| 271 |
64 bytes from 128.96.41.1: icmp_seq=9 time=100 ms |
| 272 |
64 bytes from 128.96.41.1: icmp_seq=10 time=110 ms |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Kessler & Shepard [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 279 |
|
| 280 |
|
| 281 |
----THUMPER.BELLCORE.COM PING Statistics---- |
| 282 |
12 packets transmitted, 10 packets received, 16% packet loss |
| 283 |
round-trip (ms) min/avg/max = 90/169/440 |
| 284 |
|
| 285 |
SMCVAX$ |
| 286 |
================================================================== |
| 287 |
|
| 288 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. FINGER</span> |
| 289 |
|
| 290 |
The Finger program may be used to find out who is logged in on |
| 291 |
another system or to find out detailed information about a specific |
| 292 |
user. This command has also introduced a brand new verb; "fingering" |
| 293 |
someone on the Internet is not necessarily a rude thing to do! The |
| 294 |
Finger User Information Protocol is described in <a href="./rfc1288">RFC 1288</a> [<a href="#ref-20" title=""The Finger User Information Protocol"">20</a>]. The |
| 295 |
most general format of the Finger command is: |
| 296 |
|
| 297 |
FINGER [username]@host_name |
| 298 |
|
| 299 |
The first example below shows the result of fingering an individual |
| 300 |
user at a remote system. The first line of the response shows the |
| 301 |
username, the user's real name, their process identifier, |
| 302 |
application, and terminal port number. Additional information may be |
| 303 |
supplied at the option of the user in "plan" and/or "project" files |
| 304 |
that they supply; these files are often named PLAN.TXT or |
| 305 |
PROJECT.TXT, respectively, and reside in a user's root directory (or |
| 306 |
somewhere in an appropriate search path). |
| 307 |
|
| 308 |
The second example shows the result of fingering a remote system. |
| 309 |
This lists all of the processes currently running at the fingered |
| 310 |
system or other information, depending upon how the remote system's |
| 311 |
administrator set up the system to respond to the Finger command. |
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Kessler & Shepard [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 335 |
|
| 336 |
|
| 337 |
================================================================== |
| 338 |
** C:\> FINGER [email protected] |
| 339 |
[smcvax.smcvt.edu] |
| 340 |
KUMQUAT Gary Kessler 20A02991 MAIL TXA3 |
| 341 |
Last login Fri 15-Jul-1994 2:59 PM-EDT |
| 342 |
|
| 343 |
Plan: |
| 344 |
|
| 345 |
----------------------------------------------------------------- |
| 346 |
Gary C. Kessler |
| 347 |
Adjunct Faculty Member, Graduate College |
| 348 |
|
| 349 |
Senior Member of Technical Staff |
| 350 |
Hill Associates +1 802-655-8633 or 655-0940 (office) |
| 351 |
17 Roosevelt Highway +1 802-655-7974 (fax) |
| 352 |
Colchester, VT 05446 +1 802-879-5242 (home) |
| 353 |
INTERNET: [email protected] or [email protected] |
| 354 |
----------------------------------------------------------------- |
| 355 |
|
| 356 |
** C:\> FINGER @SMCVAX.SMCVT.EDU |
| 357 |
[smcvax.smcvt.edu] |
| 358 |
Friday, July 15, 1994 4:00PM-EDT Up 21 03:41:31 |
| 359 |
7+0 Jobs on SMCVAX Load ave 0.24 0.31 0.25 |
| 360 |
|
| 361 |
User Personal Name Subsys |
| 362 |
DENIS Denis Stratford MAIL |
| 363 |
GOODWIN Dave Goodwin RTPAD |
| 364 |
JAT John Trono EDT |
| 365 |
KUMQUAT Gary Kessler MAIL |
| 366 |
INFO SMC Info Service TELNET |
| 367 |
SYSTEM System Manager *DCL* |
| 368 |
SMITH Jim Smith LYNX |
| 369 |
|
| 370 |
C:\> |
| 371 |
================================================================ |
| 372 |
|
| 373 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. TRACEROUTE</span> |
| 374 |
|
| 375 |
Traceroute is another common TCP/IP tool, this one allowing users to |
| 376 |
learn about the route that packets take from their local host to a |
| 377 |
remote host. Although used often by network and system managers as a |
| 378 |
simple, yet powerful, debugging aid, traceroute can be used by end |
| 379 |
users to learn something about the structure of the Internet. |
| 380 |
|
| 381 |
The Traceroute command has the following general format (where "#" |
| 382 |
represents a positive integer value associated with the qualifier): |
| 383 |
|
| 384 |
TRACEROUTE [-m #] [-q #] [-w #] [-p #] {IP_address | host_name} |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Kessler & Shepard [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 391 |
|
| 392 |
|
| 393 |
where -m is the maximum allowable TTL value, measured as the |
| 394 |
number of hops allowed before the program terminates |
| 395 |
(default = 30) |
| 396 |
-q is the number of UDP packets that will be sent with each |
| 397 |
time-to-live setting (default = 3) |
| 398 |
-w is the amount of time, in seconds, to wait for an answer |
| 399 |
from a particular router before giving up (default = 5) |
| 400 |
-p is the invalid port address at the remote host (default = |
| 401 |
33434) |
| 402 |
|
| 403 |
The Traceroute example below shows the route between a host at St. |
| 404 |
Michael's College in Colchester, Vermont (smcvax.smcvt.edu) and a |
| 405 |
host at Bellcore in Red Bank, New Jersey (thumper.bellcore.com). The |
| 406 |
output has some interesting points: |
| 407 |
|
| 408 |
1. NEARnet, the New England Academic and Research Network, is a |
| 409 |
regional network serving the northeastern U.S. The packets' route |
| 410 |
runs from St. Mike's NEARnet gateway (smc-gw) to the University of |
| 411 |
Vermont (uvm-gw), etc. Note that some intermediate systems (see |
| 412 |
lines 4 and 16) do not have names associated with them. |
| 413 |
|
| 414 |
2. From NEARnet (lines 1-6), the packets travel on the National |
| 415 |
Science Foundation Network (NSFNET) T3 backbone (lines 7-11). The |
| 416 |
NSFNET backbone nodes are identified as "ans.net" since the NSFNET |
| 417 |
is operated by Advanced Networks and Services, Inc. (ANS). The |
| 418 |
packets travel within ANS' network on their core nodal switching |
| 419 |
subsystems ("cnss") until ready to jump off the backbone; line 11 |
| 420 |
indicates an ANS exterior nodal switching subsystem ("enss"). The |
| 421 |
datagrams are then carried on the JvNCnet (lines 12-16), a regional |
| 422 |
network in New Jersey (note the use of SMDS!). Finally, the |
| 423 |
datagrams are placed on Bellcore's internal network (lines 17 and |
| 424 |
18) for final delivery. |
| 425 |
|
| 426 |
3. Note that not all of the datagrams take the same route. In |
| 427 |
particular, only two of the datagrams go through the ANS gateway |
| 428 |
referred to at line 10. Note also line 17; here, the first two |
| 429 |
datagrams go through one router at Bellcore, while the third |
| 430 |
datagram goes through a companion router. |
| 431 |
|
| 432 |
TECHNICAL NOTE: Traceroute works by sending a sequence of User |
| 433 |
Datagram Protocol (UDP) datagrams to an invalid port address at the |
| 434 |
remote host. Using the default settings, three datagrams are sent, |
| 435 |
each with a Time-To-Live (TTL) field value set to one. The TTL value |
| 436 |
of 1 causes the datagram to "timeout" as soon as it hits the first |
| 437 |
router in the path; this router will then respond with an ICMP Time |
| 438 |
Exceeded Message (TEM) indicating that the datagram has expired. |
| 439 |
Another three UDP messages are now sent, each with the TTL value set |
| 440 |
to 2, which causes the second router to return ICMP TEMs. This |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Kessler & Shepard [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 447 |
|
| 448 |
|
| 449 |
process continues until the packets actually reach the other |
| 450 |
destination. Since these datagrams are trying to access an invalid |
| 451 |
port at the destination host, ICMP Destination Unreachable Messages |
| 452 |
are returned indicating an unreachable port; this event signals the |
| 453 |
Traceroute program that it is finished! The Traceroute program |
| 454 |
displays the round-trip delay associated with each of the attempts. |
| 455 |
|
| 456 |
As an interesting aside, Traceroute did not begin life as a general- |
| 457 |
purpose utility, but as a quick-and-dirty debugging aid used to find |
| 458 |
a routing problem. The code (complete with comments!) is available |
| 459 |
by anonymous FTP in the file "traceroute.tar.Z" from the host |
| 460 |
"ftp.ee.lbl.gov". (See <a href="#section-2.5">Section 2.5</a> for a discussion of anonymous |
| 461 |
FTP.) |
| 462 |
|
| 463 |
================================================================== |
| 464 |
** SMCVAX$ TRACEROUTE THUMPER.BELLCORE.COM |
| 465 |
traceroute to THUMPER.BELLCORE.COM (128.96.41.1), 30 hops max, 38 |
| 466 |
byte packets |
| 467 |
1 smc-gw.near.net (192.80.64.5) 50 ms 20 ms 10 ms |
| 468 |
2 uvm-gw.near.net (131.192.152.1) 160 ms 50 ms 30 ms |
| 469 |
3 harvard-gw.near.net (131.192.65.1) 470 ms 60 ms 60 ms |
| 470 |
4 131.192.32.3 (131.192.32.3) 50 ms 50 ms 40 ms |
| 471 |
5 mit2-gw.near.net (131.192.7.1) 50 ms 40 ms 40 ms |
| 472 |
6 enss.near.net (192.54.222.6) 60 ms 90 ms 40 ms |
| 473 |
7 t3-2.Hartford-cnss49.t3.ans.net (140.222.49.3) 70 ms 100 ms 60 ms |
| 474 |
8 t3-3.Hartford-cnss48.t3.ans.net (140.222.48.4) 70 ms 40 ms 40 ms |
| 475 |
9 t3-2.New-York-cnss32.t3.ans.net (140.222.32.3) 50 ms 60 ms 70 ms |
| 476 |
10 * t3-0.New-York-cnss33.t3.ans.net (140.222.33.1) 340 ms 110 ms |
| 477 |
11 t3-0.enss137.t3.ans.net (140.222.137.1) 90 ms 420 ms 190 ms |
| 478 |
12 zaphod-gateway.jvnc.net (192.12.211.65) 70 ms 50 ms 70 ms |
| 479 |
13 airport1-gateway.jvnc.net (130.94.6.250) 390 ms 110 ms 60 ms |
| 480 |
14 airport4-gateway.jvnc.net (130.94.7.4) 70 ms 50 ms 60 ms |
| 481 |
15 coreSMDS-gateway.jvnc.net (130.94.7.106) 80 ms 130 ms 100 ms |
| 482 |
16 128.96.58.2 (128.96.58.2) 80 ms 70 ms 100 ms |
| 483 |
17 lab214b-cisco.cc.bellcore.com (128.96.34.40) 120 ms 120 ms |
| 484 |
lab214-cisco.cc.bellcore.com (128.96.34.101) 130 ms |
| 485 |
18 thumper.bellcore.com (128.96.41.1) 130 ms 430 ms 80 ms |
| 486 |
|
| 487 |
SMCVAX$ |
| 488 |
================================================================== |
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Kessler & Shepard [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. FTP</span> |
| 506 |
|
| 507 |
The File Transfer Protocol (FTP) [<a href="#ref-16" title=""File Transfer Protocol (FTP)">16</a>] is one of the most useful and |
| 508 |
powerful TCP/IP utilities for the general user. FTP allows users to |
| 509 |
upload and download files between local and remote hosts. Anonymous |
| 510 |
FTP, in particular, is commonly available at file archive sites to |
| 511 |
allow users to access files without having to pre-establish an |
| 512 |
account at the remote host. The general form of the FTP command is: |
| 513 |
|
| 514 |
FTP [IP_address | host_name] |
| 515 |
|
| 516 |
As shown, FTP can be initiated in several ways. In the example shown |
| 517 |
below, an FTP control connection is initiated to a host by supplying |
| 518 |
a host name with the FTP command; optionally, the host's IP address |
| 519 |
in dotted decimal form could be used. If neither host name nor IP |
| 520 |
address are supplied in the command line, a connection to a host can |
| 521 |
be initiated by typing "OPEN host_name" or "OPEN IP_address" once the |
| 522 |
FTP application has been started. |
| 523 |
|
| 524 |
The remote host will now ask for a username and password. If a |
| 525 |
legitimate, registered user of this host supplies a valid username |
| 526 |
and password, then the user will have access to any files and |
| 527 |
directories to which this username has privilege. For anonymous FTP |
| 528 |
access, the username "anonymous" is used and the password (not shown |
| 529 |
in actual use) is "guest" (although an increasing number of systems |
| 530 |
ask that anonymous FTP users supply their Internet address as the |
| 531 |
password). |
| 532 |
|
| 533 |
The first command issued in the example below is "help ?", used to |
| 534 |
obtain a list of available FTP commands and help topics. Although |
| 535 |
not always shown, nearly all TCP/IP applications have a help command. |
| 536 |
|
| 537 |
An example of the help for FTP's "type" command is shown in the |
| 538 |
sample dialogue. This command is very important one, by the way; if |
| 539 |
transferring a binary or executable file, be sure to set the type to |
| 540 |
"image" (or "binary" on some systems). |
| 541 |
|
| 542 |
The "dir" command provides a directory listing of the files in the |
| 543 |
current directory at the remote host; the UNIX "ls" command may also |
| 544 |
usually be used. Note that an FTP data transfer connection is |
| 545 |
established for the transfer of the directory information to the |
| 546 |
local host. The output from the "dir" command will show a file |
| 547 |
listing that is consistent with the native operating system of the |
| 548 |
remote host. Although the TCP/IP suite is often associated with |
| 549 |
UNIX, it can (and does) run with nearly all common operating systems. |
| 550 |
|
| 551 |
The directory information shown in the sample dialogue happens to be |
| 552 |
in UNIX format and includes the following information: |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Kessler & Shepard [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 559 |
|
| 560 |
|
| 561 |
o File attributes. The first character identifies this as a |
| 562 |
directory (d), link (l), or individual file (-). The next nine |
| 563 |
characters list the access permissions for three groups, namely, |
| 564 |
the owner, the owner's group, and all other users. Three access |
| 565 |
privileges may be assigned to each file for each of these groups: |
| 566 |
read (r), write (w), execute (x), and/or search (s). |
| 567 |
|
| 568 |
o File owner and owner's group. |
| 569 |
|
| 570 |
o File size, in bytes. |
| 571 |
|
| 572 |
o Date of last modification. If the date is followed by a timestamp, |
| 573 |
then the date is from the current year. |
| 574 |
|
| 575 |
o File name. |
| 576 |
|
| 577 |
After the directory information has been transferred, FTP closes the |
| 578 |
data transfer connection. |
| 579 |
|
| 580 |
The command "cd" is used to change to another directory, in this case |
| 581 |
the "Gov" directory (note that file and directory names may be case- |
| 582 |
sensitive). As in DOS, "cd .." will change to the parent of the |
| 583 |
current directory. The "CWD command successful" is the only |
| 584 |
indication that the user's "cd" command was correctly executed; the |
| 585 |
"show-directory" (may be truncated to fewer characters, as shown) |
| 586 |
command, if available, may be used to see which directory you are in. |
| 587 |
|
| 588 |
Another "dir" command is used to find all files ending with the |
| 589 |
characters ".act"; note the use of the "*" wildcard character. We |
| 590 |
can now copy (download) the file of choice (The Fair Credit Reporting |
| 591 |
Act, 1992) by using the "get" (or "receive") command, which has the |
| 592 |
following general format: |
| 593 |
|
| 594 |
GET remote_file_name local_file_name |
| 595 |
|
| 596 |
FTP opens another data transfer connection for this file transfer |
| 597 |
purpose; note that the effective data transfer rate is 39.98 kbps. |
| 598 |
|
| 599 |
FTP's "put" (or "send") command allows uploading from the local host |
| 600 |
to the remote. "Put" is often not available when using anonymous |
| 601 |
FTP. |
| 602 |
|
| 603 |
Finally, we terminate the FTP connection by using the "close" |
| 604 |
command. The user can initiate another FTP connection using the |
| 605 |
"open" command or can leave FTP by issuing a "quit" command. "Quit" |
| 606 |
can also be used to close a connection and terminate a session. |
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Kessler & Shepard [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 615 |
|
| 616 |
|
| 617 |
TECHNICAL NOTE: It is important to note that different FTP packages |
| 618 |
have different commands available and even those with similar names |
| 619 |
may act differently. In the example shown here (using MultiNet for |
| 620 |
VMS), the "show" command will display the current directory; in |
| 621 |
another package (e.g., FTP Software's PC/TCP), "show" will display a |
| 622 |
file from the remote host at the local host. Some packages have |
| 623 |
nothing equivalent to either of these commands! |
| 624 |
|
| 625 |
================================================================== |
| 626 |
** SMCVAX$ FTP FTP.SPIES.COM |
| 627 |
SMCVAX.SMCVT.EDU MultiNet FTP user process 3.2(106) |
| 628 |
Connection opened (Assuming 8-bit connections) |
| 629 |
** Username: ANONYMOUS |
| 630 |
** Password: GUEST |
| 631 |
|
| 632 |
** WIRETAP.SPIES.COM> HELP ? |
| 633 |
Commands may be one of the following: |
| 634 |
ACCOUNT AGET |
| 635 |
APPEND APUT |
| 636 |
ASCII ATTACH |
| 637 |
BELL BINARY |
| 638 |
BYE BYTE |
| 639 |
CD CDUP |
| 640 |
CLOSE CONFIRM |
| 641 |
CPATH CREATE-DIRECTORY |
| 642 |
CWD DELETE |
| 643 |
DIRECTORY DISCONNECT |
| 644 |
EXIT EXIT-ON-ERROR |
| 645 |
GET HASH |
| 646 |
HELP LCD |
| 647 |
LDIR LOCAL-CD |
| 648 |
LOCAL-DIRECTORY LOCAL-PWD |
| 649 |
LOGIN LPWD |
| 650 |
LS MDELETE |
| 651 |
MGET MKDIR |
| 652 |
MODE MPUT |
| 653 |
MULTIPLE PASSWORD |
| 654 |
PORT PROMPT-FOR-MISSING-ARGUMENTS |
| 655 |
PROMPT-ON-CONNECT PUSH |
| 656 |
PUT PWD |
| 657 |
QUIT QUOTE |
| 658 |
RECEIVE REMOTE-HELP |
| 659 |
REMOVE-DIRECTORY RENAME |
| 660 |
RETAIN RM |
| 661 |
RMDIR SEND |
| 662 |
SHOW-DIRECTORY SITE |
| 663 |
SPAWN STATISTICS |
| 664 |
STATUS STREAM |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Kessler & Shepard [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 671 |
|
| 672 |
|
| 673 |
STRUCTURE TAKE |
| 674 |
TENEX TYPE |
| 675 |
USER VERBOSE |
| 676 |
VERSION |
| 677 |
|
| 678 |
** WIRETAP.SPIES.COM> HELP TYPE |
| 679 |
The TYPE command changes the FTP transfer type. The possible |
| 680 |
arguments to the TYPE command are ASCII, IMAGE, BACKUP, and |
| 681 |
LOGICAL-BYTE ASCII type is used for transferring ASCII text files. |
| 682 |
IMAGE type is used for transferring binary files. BACKUP type is |
| 683 |
used for transferring VAX/VMS backup savesets with 2048 byte block |
| 684 |
size. |
| 685 |
|
| 686 |
** WIRETAP.SPIES.COM> DIR |
| 687 |
<Opening ASCII mode data connection for /bin/ls. |
| 688 |
total 25 |
| 689 |
drwxr-xr-x 2 9013 daemon 512 Jul 1 1993 .cap |
| 690 |
drwxr-xr-x 4 9013 daemon 512 Jul 1 1993 About |
| 691 |
-rw-r--r-- 1 9013 daemon 791 Apr 6 1993 About_Gopher |
| 692 |
drwxr-xr-x 3 9013 daemon 512 Jul 12 1993 Books |
| 693 |
drwxr-xr-x 13 9013 daemon 512 Jul 1 1993 Clinton |
| 694 |
lrwxrwxrwx 1 root daemon 12 Feb 26 07:02 Economic_Plan |
| 695 |
-> Gov/Economic |
| 696 |
drwxr-xr-x 4 9013 daemon 512 Jul 1 1993 Etext |
| 697 |
lrwxrwxrwx 1 root daemon 13 Feb 26 07:01 GAO_Reports -> |
| 698 |
Gov/GAO-Trans |
| 699 |
drwxr-xr-x 29 9013 daemon 1024 Feb 3 00:15 Gov |
| 700 |
drwxr-xr-x 16 9013 daemon 512 Jul 1 1993 Library |
| 701 |
lrwxrwxrwx 1 root daemon 9 Feb 26 06:56 NAFTA -> |
| 702 |
Gov/NAFTA |
| 703 |
drwxr-xr-x 2 9013 daemon 512 Jul 1 1993 Other |
| 704 |
drwxr-xr-x 3 9013 daemon 3072 Apr 7 20:59 alt.etext |
| 705 |
drwxr-xr-x 8 root 42 512 Jul 1 1993 ba.internet |
| 706 |
dr-xr-xr-x 2 bin wheel 512 Jul 1 1993 bin |
| 707 |
drwxr-xr-x 2 root daemon 512 Feb 15 06:14 dev |
| 708 |
drwxr-xr-x 3 root wheel 512 Jul 1 1993 etc |
| 709 |
drwxr-xr-x 11 9038 daemon 512 Dec 17 05:37 game_archive |
| 710 |
drwx-wx-wx 3 root daemon 1024 Apr 18 02:09 incoming |
| 711 |
drwxr-xr-x 3 root ftp 512 Oct 29 02:35 pub |
| 712 |
drwxr-xr-x 2 root daemon 512 Jul 1 1992 tmp |
| 713 |
drwxr-xr-x 3 root daemon 512 Jul 1 1993 usr |
| 714 |
drwxr-xr-x 3 9013 42 1024 Jul 1 1993 waffle |
| 715 |
<Transfer complete. |
| 716 |
1490 bytes transferred at 4966 bps. |
| 717 |
Run time = 10. ms, Elapsed time = 2400. ms. |
| 718 |
|
| 719 |
** WIRETAP.SPIES.COM> CD Gov |
| 720 |
<CWD command successful. |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Kessler & Shepard [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 727 |
|
| 728 |
|
| 729 |
** WIRETAP.SPIES.COM> SHOW |
| 730 |
<"/Gov" is current directory. |
| 731 |
|
| 732 |
** WIRETAP.SPIES.COM> DIR *.act |
| 733 |
<Opening ASCII mode data connection for /bin/ls. |
| 734 |
-rw-r--r-- 1 9013 42 32695 Dec 10 21:37 brady.act |
| 735 |
-r--r--r-- 1 9013 42 168649 Mar 26 1993 disable.act |
| 736 |
-r--r--r-- 1 9013 42 62602 Mar 30 1993 ecpa.act |
| 737 |
-r--r--r-- 1 9013 42 29519 Mar 30 1993 faircredit.act |
| 738 |
-r--r--r-- 1 9013 42 57206 Mar 30 1993 privacy.act |
| 739 |
-r--r--r-- 1 9013 42 16261 Mar 26 1993 warpower.act |
| 740 |
<Transfer complete. |
| 741 |
401 bytes transferred at 7638 bps. |
| 742 |
Run time = 0. ms, Elapsed time = 420. ms. |
| 743 |
|
| 744 |
** WIRETAP.SPIES.COM> GET faircredit.act FAIRCRDT.TXT |
| 745 |
<Opening ASCII mode data connection for faircredit.act (29519 |
| 746 |
bytes). |
| 747 |
<Transfer complete. |
| 748 |
30132 bytes transferred at 39976 bps. |
| 749 |
Run time = 40. ms, Elapsed time = 6030. ms. |
| 750 |
|
| 751 |
** WIRETAP.SPIES.COM> QUIT |
| 752 |
<Goodbye. |
| 753 |
SMCVAX$ |
| 754 |
================================================================ |
| 755 |
|
| 756 |
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. TELNET</span> |
| 757 |
|
| 758 |
TELNET [<a href="#ref-17" title=""TELNET Protocol Specification"">17</a>] is TCP/IP's virtual terminal protocol. Using TELNET, a |
| 759 |
user connected to one host can login to another host, appearing like |
| 760 |
a directly-attached terminal at the remote system; this is TCP/IP's |
| 761 |
definition of a "virtual terminal." The general form of the TELNET |
| 762 |
command is: |
| 763 |
|
| 764 |
TELNET [IP_address | host_name] [port] |
| 765 |
|
| 766 |
As shown, a TELNET connection is initiated when the user enters the |
| 767 |
"TELNET" command and supplies either a "host_name" or "IP_address"; |
| 768 |
if neither are given, TELNET will ask for one once the application |
| 769 |
begins. |
| 770 |
|
| 771 |
In the example below, a user logged onto a PC on a LAN will use |
| 772 |
TELNET to attach to the remote host "smcvax.smcvt.edu". Once logged |
| 773 |
in via TELNET, the user can do anything on the remote host that they |
| 774 |
could do if they were on a directly-connected terminal or had dialed- |
| 775 |
up by modem. The commands that are used are those available on the |
| 776 |
remote system to which the user is attached. In the sample dialogue |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Kessler & Shepard [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 783 |
|
| 784 |
|
| 785 |
below, the user attached to SMCVAX will use basic VAX/VMS commands: |
| 786 |
|
| 787 |
o The "dir" command lists the files having a "COM" file extension. |
| 788 |
o The "mail" command enters the MAIL system (there are no messages). |
| 789 |
o "Pinging" the home host shows that it is alive! |
| 790 |
|
| 791 |
When finished, "logout" logs the user off the remote host; TELNET |
| 792 |
automatically closes the connection to the remote host and returns |
| 793 |
control to the local system. |
| 794 |
|
| 795 |
It is important to note that TELNET is a very powerful tool, one that |
| 796 |
may provide users with access to many Internet utilities and services |
| 797 |
that might not be otherwise available. Many of these features are |
| 798 |
accessed by specifying a port number with the TELNET command, in |
| 799 |
addition to a host's address, and knowledge of port numbers provides |
| 800 |
another mechanism for users to access information with Telnet. |
| 801 |
|
| 802 |
This guide discusses several TCP/IP and Internet utilities that |
| 803 |
require local client software, such as Finger, Whois, Archie, and |
| 804 |
Gopher. But what if your software does not include a needed client? |
| 805 |
In some cases, Telnet may be used to access a remote client and |
| 806 |
provide the same functionality. |
| 807 |
|
| 808 |
This is done by specifying a port number with the TELNET command. |
| 809 |
Just as TCP/IP hosts have a unique IP address, applications on the |
| 810 |
host are associated with an address, called a "port". Finger, for |
| 811 |
example, is associated with the well-known port number 79. In the |
| 812 |
absence of a Finger client, TELNETing to port 79 at a remote host may |
| 813 |
provide the same information. You can "finger" another host with |
| 814 |
TELNET by using a command like: |
| 815 |
|
| 816 |
TELNET host_name 79 |
| 817 |
|
| 818 |
Other well-known TCP/IP port numbers include 20 (FTP data transfer), |
| 819 |
21 (FTP control), 25 (SMTP), 43 (whois), 70 (Gopher), and 185 |
| 820 |
(KNOWBOT). |
| 821 |
|
| 822 |
Some services are available on the Internet using TELNET and special |
| 823 |
port numbers. A geographical information database, for example, may |
| 824 |
be accessed by TELNETing to port 3000 at host |
| 825 |
"martini.eecs.umich.edu"; current weather information is available at |
| 826 |
port 3000 at hosts "downwind.sprl.umich.edu" and |
| 827 |
"wind.atmos.uah.edu". |
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Kessler & Shepard [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 839 |
|
| 840 |
|
| 841 |
================================================================== |
| 842 |
** C:\> TELNET SMCVAX.SMCVT.EDU |
| 843 |
FTP Software PC/TCP tn 2.31 01/07/94 12:38 |
| 844 |
Copyright (c) 1986-1993 by FTP Software, Inc. All rights reserved |
| 845 |
|
| 846 |
- Connected to St. Michael's College - |
| 847 |
|
| 848 |
** Username: KUMQUAT |
| 849 |
** Password: |
| 850 |
|
| 851 |
St. Michael's College VAX/VMS System. |
| 852 |
Node SMCVAX. |
| 853 |
|
| 854 |
Last interactive login on Thursday, 9-JUN-1994 11:55 |
| 855 |
Last non-interactive login on Thursday, 9-JUN-1994 08:20 |
| 856 |
|
| 857 |
Good Afternoon User KUMQUAT. Logged in on 12-JUN-1994 at 3:27 PM. |
| 858 |
|
| 859 |
User [GUEST,KUMQUAT] has 4292 blocks used, 5708 available, |
| 860 |
of 10000 authorized and permitted overdraft of 100 blocks on $1$DIA2 |
| 861 |
|
| 862 |
** SMCVAX$ DIR *.COM |
| 863 |
Directory $1$DIA2:[GUEST.KUMQUAT] |
| 864 |
|
| 865 |
BACKUP.COM;24 24 16-JUL-1990 16:22:46.68 (RWED,RWED,RE,) |
| 866 |
DELTREE.COM;17 3 16-JUL-1990 16:22:47.58 (RWED,RWED,RE,) |
| 867 |
EXPANDZ.COM;7 2 22-FEB-1993 10:00:04.35 (RWED,RWED,RE,) |
| 868 |
FTSLOGBLD.COM;3 1 16-JUL-1990 16:22:48.57 (RWED,RWED,RE,) |
| 869 |
FTSRRR.COM;2 1 16-JUL-1990 16:22:48.73 (RWED,RWED,RE,) |
| 870 |
LOGIN.COM;116 5 1-DEC-1993 09:33:21.61 (RWED,RWED,RE,) |
| 871 |
SNOOPY.COM;6 1 16-JUL-1990 16:22:52.06 (RWED,RWED,RE,) |
| 872 |
SYLOGIN.COM;83 8 16-JUL-1990 16:22:52.88 (RWED,RWED,RE,RE) |
| 873 |
SYSHUTDWN.COM;1 0 16-JUL-1990 16:22:53.04 (RWED,RWED,RE,) |
| 874 |
SYSTARTUP.COM;88 15 16-JUL-1990 16:22:53.21 (RWED,RWED,RE,) |
| 875 |
WATCH_MAIL.COM;1 173 10-MAY-1994 09:59:52.65 (RWED,RWED,RE,) |
| 876 |
|
| 877 |
Total of 11 files, 233 blocks. |
| 878 |
|
| 879 |
** SMCVAX$ MAIL |
| 880 |
** MAIL> EXIT |
| 881 |
|
| 882 |
** SMCVAX$ PING HILL.COM /N=5 |
| 883 |
PING HILL.COM (199.182.20.4): 56 data bytes |
| 884 |
64 bytes from 199.182.20.4: icmp_seq=0 time=290 ms |
| 885 |
64 bytes from 199.182.20.4: icmp_seq=1 time=260 ms |
| 886 |
64 bytes from 199.182.20.4: icmp_seq=2 time=260 ms |
| 887 |
64 bytes from 199.182.20.4: icmp_seq=3 time=260 ms |
| 888 |
64 bytes from 199.182.20.4: icmp_seq=4 time=260 ms |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Kessler & Shepard [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 895 |
|
| 896 |
|
| 897 |
----HILL.COM PING Statistics---- |
| 898 |
5 packets transmitted, 5 packets received, 0% packet loss |
| 899 |
round-trip (ms) min/avg/max = 260/266/290 |
| 900 |
|
| 901 |
** SMCVAX$ LOGOUT |
| 902 |
KUMQUAT logged out at 12-JUN-1994 15:37:04.29 |
| 903 |
|
| 904 |
Connection #0 closed |
| 905 |
|
| 906 |
C:\> |
| 907 |
================================================================== |
| 908 |
|
| 909 |
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. User Database Lookup Tools</span> |
| 910 |
|
| 911 |
<span class="h4"><a class="selflink" id="section-2.7.1" href="#section-2.7.1">2.7.1</a>. WHOIS/NICNAME</span> |
| 912 |
|
| 913 |
WHOIS and NICNAME are TCP/IP applications that search databases to |
| 914 |
find the name of network and system administrators, RFC authors, |
| 915 |
system and network points-of-contact, and other individuals who are |
| 916 |
registered in appropriate databases. The original NICNAME/WHOIS |
| 917 |
protocol is described in <a href="./rfc954">RFC 954</a> [<a href="#ref-4" title=""NICNAME/WHOIS"">4</a>]. |
| 918 |
|
| 919 |
WHOIS may be accessed by TELNETing to an appropriate WHOIS server and |
| 920 |
logging in as "WHOIS" (no password is required); the most common |
| 921 |
Internet name server is located at the Internet Network Information |
| 922 |
Center (InterNIC) at "rs.internic.net". This specific database, in |
| 923 |
particular, only contains INTERNET domains, IP network numbers, and |
| 924 |
points of contact; policies governing the InterNIC database are |
| 925 |
described in <a href="./rfc1400">RFC 1400</a> [<a href="#ref-19" title=""Transition and Modernization of the Internet Registration Service"">19</a>]. The MILNET database resides at |
| 926 |
"nic.ddn.mil" and PSI's White Pages pilot service is located at |
| 927 |
"psi.com". |
| 928 |
|
| 929 |
Many software packages contain a WHOIS/NICNAME client that |
| 930 |
automatically establishes the TELNET connection to a default name |
| 931 |
server database, although users can usually specify any name server |
| 932 |
database that they want. |
| 933 |
|
| 934 |
The accompanying dialogues shows several types of WHOIS/NICNAME |
| 935 |
information queries. In the session below, we request information |
| 936 |
about an individual (Denis Stratford) by using WHOIS locally, a |
| 937 |
specific domain (hill.com) by using NICNAME locally, and a high-level |
| 938 |
domain (edu) using TELNET to a WHOIS server. |
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Kessler & Shepard [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 951 |
|
| 952 |
|
| 953 |
================================================================== |
| 954 |
** SMCVAX$ WHOIS STRATFORD, DENIS |
| 955 |
Stratford, Denis (DS378) denis@@SMCVAX.SMCVT.EDU |
| 956 |
St. Michael's College |
| 957 |
Jemery Hall, Room 274 |
| 958 |
Winooski Park |
| 959 |
Colchester, VT 05439 |
| 960 |
(802) 654-2384 |
| 961 |
|
| 962 |
Record last updated on 02-Nov-92. |
| 963 |
SMCVAX$ |
| 964 |
|
| 965 |
** C:\> NICNAME HILL.COM |
| 966 |
Hill Associates (HILL-DOM) |
| 967 |
17 Roosevelt Highway |
| 968 |
Colchester, VT 05446 |
| 969 |
|
| 970 |
Domain Name: HILL.COM |
| 971 |
|
| 972 |
Administrative Contact: |
| 973 |
Kessler, Gary C. (GK34) [email protected] |
| 974 |
(802) 655-8633 |
| 975 |
Technical Contact, Zone Contact: |
| 976 |
Monaghan, Carol A. (CAM4) [email protected] |
| 977 |
(802) 655-8630 |
| 978 |
|
| 979 |
Record last updated on 15-Jun-94. |
| 980 |
|
| 981 |
Domain servers in listed order: |
| 982 |
|
| 983 |
NETCOMSV.NETCOM.COM 192.100.81.101 |
| 984 |
NS.NETCOM.COM 192.100.81.105 |
| 985 |
** C:\> TELNET RS.INTERNIC.NET |
| 986 |
Connected to RS.INTERNIC.NET, a SUN 670 running SUNOS-4.1.3 |
| 987 |
|
| 988 |
****************************************************************** |
| 989 |
* -- InterNIC Registration Services Center -- |
| 990 |
****************************************************************** |
| 991 |
|
| 992 |
Cmdinter Ver 1.3 Mon Mar 21 13:42:27 1994 EST |
| 993 |
** [dec-vt220] InterNIC> WHOIS |
| 994 |
Connected to the rs Database |
| 995 |
InterNIC WHOIS Version: 1.0 Mon, 21 Mar 94 13:42:32 |
| 996 |
|
| 997 |
** Whois: DOMAIN EDU |
| 998 |
Education top-level domain (EDU-DOM) |
| 999 |
Network Solutions, Inc. |
| 1000 |
505 Huntmar park Dr. |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Kessler & Shepard [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
Herndon, VA 22070 |
| 1010 |
|
| 1011 |
Domain Name: EDU |
| 1012 |
|
| 1013 |
Administrative Contact, Technical Contact, Zone Contact: |
| 1014 |
Network Solutions, Inc. (HOSTMASTER) [email protected] |
| 1015 |
(703) 742-4777 (FAX) (703) 742-4811 |
| 1016 |
|
| 1017 |
Record last updated on 16-May-94. |
| 1018 |
|
| 1019 |
Domain servers in listed order: |
| 1020 |
|
| 1021 |
NS.INTERNIC.NET 198.41.0.4 |
| 1022 |
AOS.ARL.ARMY.MIL 128.63.4.82, 192.5.25.82 |
| 1023 |
NS1.ISI.EDU 128.9.0.107 |
| 1024 |
C.NYSER.NET 192.33.4.12 |
| 1025 |
TERP.UMD.EDU 128.8.10.90 |
| 1026 |
NS.NASA.GOV 128.102.16.10, 192.52.195.10 |
| 1027 |
NIC.NORDU.NET 192.36.148.17 |
| 1028 |
NS.NIC.DDN.MIL 192.112.36.4 |
| 1029 |
|
| 1030 |
Would you like to see the known domains under this top-level domain? |
| 1031 |
** Y |
| 1032 |
|
| 1033 |
There are 1504 known sub-domains: |
| 1034 |
|
| 1035 |
0.EDU Reserved Domain |
| 1036 |
1.EDU Reserved Domain |
| 1037 |
2.EDU Reserved Domain |
| 1038 |
22CF.EDU 22nd Century Foundation |
| 1039 |
3.EDU Reserved Domain |
| 1040 |
** There are 1499 more matches. Show them? N |
| 1041 |
|
| 1042 |
** Whois: EXIT |
| 1043 |
|
| 1044 |
** [dec-vt220] InterNIC> QUIT |
| 1045 |
|
| 1046 |
Connection #0 closed |
| 1047 |
C:\> |
| 1048 |
================================================================== |
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Kessler & Shepard [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<span class="h4"><a class="selflink" id="section-2.7.2" href="#section-2.7.2">2.7.2</a>. KNOWBOT</span> |
| 1066 |
|
| 1067 |
KNOWBOT is an automated username database search tool that is related |
| 1068 |
to WHOIS. The Knowbot Information Service (KIS) provides a simple |
| 1069 |
WHOIS-like interface that allows users to query several Internet user |
| 1070 |
databases (White Pages services) all at one time. A single KIS query |
| 1071 |
will automatically search the InterNIC, MILNET, MCImail, and PSI |
| 1072 |
White Pages Pilot Project; other databases may also be included. |
| 1073 |
|
| 1074 |
KNOWBOT may be accessed by TELNETing to port 185 at host |
| 1075 |
"info.cnri.reston.va.us" or "sol.bucknell.edu". The "help" command |
| 1076 |
will supply sufficient information to get started. The sample |
| 1077 |
dialogue below shows use of the "query" command to locate a user |
| 1078 |
named "Gary Kessler"; this command automatically starts a search |
| 1079 |
through the default set of Internet databases. |
| 1080 |
|
| 1081 |
================================================================== |
| 1082 |
** C:\> TELNET INFO.CNRI.RESTON.VA.US 185 |
| 1083 |
|
| 1084 |
Knowbot Information Service |
| 1085 |
KIS Client (V2.0). Copyright CNRI 1990. All Rights Reserved. |
| 1086 |
|
| 1087 |
Please enter your email address in our guest book... |
| 1088 |
** (Your email address?) > [email protected] |
| 1089 |
|
| 1090 |
** > QUERY KESSLER, GARY |
| 1091 |
|
| 1092 |
Trying whois at ds.internic.net... |
| 1093 |
The ds.internic.net whois server is being queried: |
| 1094 |
No match for "KESSLER and GARY" |
| 1095 |
|
| 1096 |
The rs.internic.net whois server is being queried: |
| 1097 |
|
| 1098 |
Kessler, Gary C. (GK34) [email protected] |
| 1099 |
Hill Associates |
| 1100 |
17 Roosevelt Highway |
| 1101 |
Colchester, VT 05446 |
| 1102 |
(802) 655-8633 |
| 1103 |
|
| 1104 |
The nic.ddn.mil whois server is being queried: |
| 1105 |
|
| 1106 |
Kessler, Gary P. (GK15) [email protected] |
| 1107 |
NAVAL AIR WARFARE CENTER-AD PAX |
| 1108 |
Simulation & Control Technology Dept |
| 1109 |
SATD |
| 1110 |
Patuxent River, MD 20670 |
| 1111 |
301-826-3192 (DSN) 326-3192 (FAX) 301-826-4555 |
| 1112 |
MILNET TAC user (Issued: 11-jul-1994) |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Kessler & Shepard [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
TAC authorizing host: TECNET1.JCTE.JCS.MIL (NATC-3COM) |
| 1122 |
|
| 1123 |
Trying mcimail at cnri.reston.va.us... |
| 1124 |
Trying ripe at whois.ripe.net... |
| 1125 |
Trying whois at whois.lac.net... |
| 1126 |
No match found for .KESSLER,GARY |
| 1127 |
|
| 1128 |
** > QUIT |
| 1129 |
KIS exiting |
| 1130 |
Connection #0 closed |
| 1131 |
C:\> |
| 1132 |
================================================================== |
| 1133 |
|
| 1134 |
<span class="h4"><a class="selflink" id="section-2.7.3" href="#section-2.7.3">2.7.3</a>. NETFIND</span> |
| 1135 |
|
| 1136 |
NETFIND is another tool that may be used to locate people on the |
| 1137 |
network. NETFIND's advantage is that it searches for users by |
| 1138 |
utilizing extant tools such as Finger and SMTP, thus providing the |
| 1139 |
potential to find any user on any host without relying on databases. |
| 1140 |
For NETFIND to be successful, however, the system manager of existing |
| 1141 |
systems must set up Finger and SMTP to respond correctly to NETFIND's |
| 1142 |
queries. NETFIND is still relatively new and use will grow over |
| 1143 |
time. |
| 1144 |
|
| 1145 |
NETFIND is a menu-driven, text-based system. Users need to TELNET to |
| 1146 |
an available NETFIND server. Once connected, login as "netfind" |
| 1147 |
(must be lower-case; no password required) and follow the menu |
| 1148 |
prompts. The sample dialogue below shows the search for "Tom |
| 1149 |
Maufer", who is known to work at Goddard Space Flight Center ("gsfc") |
| 1150 |
at NASA ("nasa.gov"). |
| 1151 |
|
| 1152 |
The primary NETFIND server is located at the University of Colorado |
| 1153 |
in Boulder (bruno.cs.colorado.edu); alternate servers include: |
| 1154 |
|
| 1155 |
archie.au (AARNet, Melbourne, Australia) |
| 1156 |
dino.conicit.ve (Nat. Council for Tech. & Sci. Res., Venezuela) |
| 1157 |
ds.internic.net (InterNIC Directory & DB Svcs., S. Plainfield, NJ) |
| 1158 |
eis.calstate.edu (California State University, Fullerton, CA) |
| 1159 |
krnic.net (Korea Network Information Center, Taejon, Korea) |
| 1160 |
lincoln.technet.sg (Technet Unit, Singapore) |
| 1161 |
malloco.ing.puc.cl (Catholic University of Chile, Santiago) |
| 1162 |
monolith.cc.ic.ac.uk (Imperial College, London, England) |
| 1163 |
mudhoney.micro.umn.edu (University of Minnesota, Minneapolis) |
| 1164 |
netfind.anu.edu.au (Australian National University, Canberra) |
| 1165 |
netfind.ee.mcgill.ca (McGill University, Montreal, Quebec, Canada) |
| 1166 |
netfind.fnet.fr (Association FNET, Le Kremlin-Bicetre, France) |
| 1167 |
netfind.icm.edu.pl (Warsaw University, Warsaw, Poland) |
| 1168 |
netfind.if.usp.br (University of Sao Paulo, Sao Paulo, Brazil) |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Kessler & Shepard [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
netfind.oc.com (OpenConnect Systems, Dallas, Texas) |
| 1178 |
netfind.sjsu.edu (San Jose State University, San Jose, California) |
| 1179 |
netfind.vslib.cz (Liberec Univ. of Technology, Czech Republic) |
| 1180 |
nic.uakom.sk (Academy of Sciences, Banska Bystrica, Slovakia) |
| 1181 |
redmont.cis.uab.edu (University of Alabama at Birmingham) |
| 1182 |
|
| 1183 |
================================================================== |
| 1184 |
** C:\> TELNET DS.INTERNIC.NET |
| 1185 |
SunOS UNIX (ds) |
| 1186 |
|
| 1187 |
** login: netfind |
| 1188 |
|
| 1189 |
=================================================== |
| 1190 |
Welcome to the InterNIC Directory & Database Server |
| 1191 |
=================================================== |
| 1192 |
|
| 1193 |
Top level choices: |
| 1194 |
1. Help |
| 1195 |
2. Search |
| 1196 |
3. Seed database lookup |
| 1197 |
4. Options |
| 1198 |
5. Quit (exit server) |
| 1199 |
** --> 2 |
| 1200 |
|
| 1201 |
** Enter person and keys (blank to exit) --> MAUFER GSFC NASA GOV |
| 1202 |
|
| 1203 |
Please select at most 3 of the following domains to search: |
| 1204 |
0. gsfc.nasa.gov (goddard space flight center, united states |
| 1205 |
national aeronautics and space administration, greenbelt, maryland) |
| 1206 |
1. antwrp.gsfc.nasa.gov (compton gamma ray observatory |
| 1207 |
science support center, goddard space flight center, united states |
| 1208 |
national aeronautics and space administration, greenbelt, maryland) |
| 1209 |
2. enemy.gsfc.nasa.gov (compton gamma ray observatory science |
| 1210 |
support center, goddard space flight center, united states national |
| 1211 |
aeronautics and space administration, greenbelt, maryland) |
| 1212 |
3. upolu.gsfc.nasa.gov (goddard space flight center, united |
| 1213 |
states national aeronautics and space administration, greenbelt, |
| 1214 |
maryland) |
| 1215 |
|
| 1216 |
** Enter selection (e.g., 2 0 1) --> 0 |
| 1217 |
( 1) SMTP_Finger_Search: checking domain gsfc.nasa.gov |
| 1218 |
Mail is forwarded to [email protected] |
| 1219 |
NOTE: this is a domain mail forwarding arrangement - mail intended |
| 1220 |
for "maufer" should be addressed to "[email protected]" |
| 1221 |
rather than "[email protected]". |
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Kessler & Shepard [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
( 1) SMTP_Finger_Search: checking host stimpy.gsfc.nasa.gov |
| 1234 |
------ |
| 1235 |
Domain search completed. Proceeding to host search. |
| 1236 |
------ |
| 1237 |
|
| 1238 |
SYSTEM: kong.gsfc.nasa.gov |
| 1239 |
Login name: maufer In real life: Tom Maufer - CBSI |
| 1240 |
Directory: /vault/maufer Shell: /bin/csh |
| 1241 |
Last login Fri Sep 24, 1993 on ttypc from rocinante.gsfc.n |
| 1242 |
No unread mail |
| 1243 |
No Plan. |
| 1244 |
|
| 1245 |
FINGER SUMMARY: |
| 1246 |
- The most promising email address for "maufer" |
| 1247 |
based on the above finger search is |
| 1248 |
[email protected]. |
| 1249 |
|
| 1250 |
** Continue the search ([n]/y) ? --> N |
| 1251 |
** Enter person and keys (blank to exit) --> |
| 1252 |
|
| 1253 |
Top level choices: |
| 1254 |
1. Help |
| 1255 |
2. Search |
| 1256 |
3. Seed database lookup |
| 1257 |
4. Options |
| 1258 |
5. Quit (exit server) |
| 1259 |
** --> 5 |
| 1260 |
Exiting Netfind server... |
| 1261 |
|
| 1262 |
Connection #0 closed |
| 1263 |
C:\> |
| 1264 |
================================================================== |
| 1265 |
|
| 1266 |
|
| 1267 |
|
| 1268 |
|
| 1269 |
|
| 1270 |
|
| 1271 |
|
| 1272 |
|
| 1273 |
|
| 1274 |
|
| 1275 |
|
| 1276 |
|
| 1277 |
|
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Kessler & Shepard [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Information Servers</span> |
| 1290 |
|
| 1291 |
<span class="h4"><a class="selflink" id="section-2.8.1" href="#section-2.8.1">2.8.1</a>. ARCHIE</span> |
| 1292 |
|
| 1293 |
Archie is a tool for locating files on the Internet, originally |
| 1294 |
developed at the Computer Science Department at McGill University in |
| 1295 |
Montreal. Archie allows users to find software, data, and other |
| 1296 |
information files that reside at anonymous FTP archive sites across |
| 1297 |
the Internet; the name of the program, reportedly, is derived from |
| 1298 |
the word "archive" and not from the comic book character. Archie |
| 1299 |
tracks the contents of over 1,000 anonymous FTP archive sites |
| 1300 |
containing over 2 million files. The Archie server automatically |
| 1301 |
updates the information from each registered site about once a month, |
| 1302 |
providing relatively up-to-date information without unduly stressing |
| 1303 |
the network. |
| 1304 |
|
| 1305 |
Before using Archie, you must identify a server address. The sites |
| 1306 |
below all support Archie; most (but not all) Archie sites support the |
| 1307 |
"servers" command which lists all known Archie servers. Due to the |
| 1308 |
popularity of Archie and its high processing demands, many sites |
| 1309 |
limit access to non-peak hours and/or limit the number of |
| 1310 |
simultaneous Archie users. Available Archie sites include: |
| 1311 |
|
| 1312 |
archie.au 139.130.4.6 Australia |
| 1313 |
archie.edvz.uni-linz.ac.at 140.78.3.8 Austria |
| 1314 |
archie.univie.ac.at 131.130.1.23 Austria |
| 1315 |
archie.uqam.ca 132.208.250.10 Canada |
| 1316 |
archie.funet.fi 128.214.6.100 Finland |
| 1317 |
archie.th-darmstadt.de 130.83.22.60 Germany |
| 1318 |
archie.ac.il 132.65.6.15 Israel |
| 1319 |
archie.unipi.it 131.114.21.10 Italy |
| 1320 |
archie.wide.ad.jp 133.4.3.6 Japan |
| 1321 |
archie.hana.nm.kr 128.134.1.1 Korea |
| 1322 |
archie.sogang.ac.kr 163.239.1.11 Korea |
| 1323 |
archie.uninett.no 128.39.2.20 Norway |
| 1324 |
archie.rediris.es 130.206.1.2 Spain |
| 1325 |
archie.luth.se 130.240.18.4 Sweden |
| 1326 |
archie.switch.ch 130.59.1.40 Switzerland |
| 1327 |
archie.ncu.edu.tw 140.115.19.24 Taiwan |
| 1328 |
archie.doc.ic.ac.uk 146.169.11.3 United Kingdom |
| 1329 |
archie.unl.edu 129.93.1.14 USA (NE) |
| 1330 |
archie.internic.net 198.48.45.10 USA (NJ) |
| 1331 |
archie.rutgers.edu 128.6.18.15 USA (NJ) |
| 1332 |
archie.ans.net 147.225.1.10 USA (NY) |
| 1333 |
archie.sura.net 128.167.254.179 USA (MD) |
| 1334 |
|
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Kessler & Shepard [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
Archie servers may be accessed using TELNET. When TELNETing to an |
| 1346 |
Archie site, login as "archie" (you MUST use lower case); just hit |
| 1347 |
<ENTER> if a password is requested. |
| 1348 |
|
| 1349 |
Once connected, the "help" command assists users in obtaining more |
| 1350 |
information about using Archie. Two more useful Archie commands are |
| 1351 |
"prog", used to search for files in the database, and "whatis", which |
| 1352 |
searches for keywords in the program descriptions. |
| 1353 |
|
| 1354 |
In the accompanying dialogue, the "set maxhits" command is used to |
| 1355 |
limit the number of responses to any following "prog" commands; if |
| 1356 |
this is not done, the user may get an enormous amount of information! |
| 1357 |
|
| 1358 |
In this example, the user issues a request to find entries related to |
| 1359 |
"mpeg", ISO's Moving Pictures Experts Group video compression |
| 1360 |
standard. Armed with this information, a user can use anonymous FTP |
| 1361 |
to examine these directories and files. |
| 1362 |
|
| 1363 |
The next request is for files with "security" as a keyword |
| 1364 |
descriptor. These responses can be used for subsequent "prog" |
| 1365 |
commands. |
| 1366 |
|
| 1367 |
Exit archie using the "exit" command. At this point, TELNET closes |
| 1368 |
the connection and control returns to the local host. |
| 1369 |
|
| 1370 |
Additional information about Archie can be obtained by sending e-mail |
| 1371 |
to Bunyip Information Systems ([email protected]). Client |
| 1372 |
software is not required to use Archie, but can make life a little |
| 1373 |
easier; some such software can be downloaded using anonymous FTP from |
| 1374 |
the "/pub/archie/" directory at host "ftp.cs.widener.edu" or in |
| 1375 |
"/pub/archie/clients/" at "ftp.sura.net". Most shareware and |
| 1376 |
commercial Archie clients hide the complexity described in this |
| 1377 |
section; users usually connect to a pre-configured Archie server |
| 1378 |
merely by typing an "ARCHIE" command line. |
| 1379 |
|
| 1380 |
================================================================== |
| 1381 |
** C:\> TELNET 129.93.1.14 |
| 1382 |
SunOS UNIX (crcnis2) |
| 1383 |
|
| 1384 |
** login: archie |
| 1385 |
** Password: |
| 1386 |
|
| 1387 |
Welcome to the ARCHIE server at the University of Nebraska - Lincoln |
| 1388 |
|
| 1389 |
# Bunyip Information Systems, 1993 |
| 1390 |
|
| 1391 |
** unl-archie> HELP |
| 1392 |
These are the commands you can use in help: |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Kessler & Shepard [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
. go up one level in the hierarchy |
| 1402 |
|
| 1403 |
? display a list of valid subtopics at the current level |
| 1404 |
|
| 1405 |
<newline> |
| 1406 |
done, ^D, ^C quit from help entirely |
| 1407 |
|
| 1408 |
<string> help on a topic or subtopic |
| 1409 |
Eg. |
| 1410 |
"help show" |
| 1411 |
|
| 1412 |
will give you the help screen for the "show" command |
| 1413 |
|
| 1414 |
"help set search" |
| 1415 |
|
| 1416 |
Will give you the help information for the "search" variable. |
| 1417 |
|
| 1418 |
The command "manpage" will give you a complete copy of the archie |
| 1419 |
manual page. |
| 1420 |
** help> DONE |
| 1421 |
|
| 1422 |
** unl-archie> SET MAXHITS 5 |
| 1423 |
** unl-archie> PROG MPEG |
| 1424 |
# Search type: sub. |
| 1425 |
# Your queue position: 1 |
| 1426 |
# Estimated time for completion: 02:18 |
| 1427 |
|
| 1428 |
Host ftp.germany.eu.net (192.76.144.75) |
| 1429 |
Location: /pub/applications/graphics |
| 1430 |
DIRECTORY drwxrwxr-x 512 bytes 00:00 7 Jul 1993 mpeg |
| 1431 |
Location: /pub/comp/amiga/gfx |
| 1432 |
DIRECTORY drwxr-xr-x 512 bytes 00:00 7 Sep 1993 mpeg |
| 1433 |
|
| 1434 |
Host stsci.edu (130.167.1.2) |
| 1435 |
Location: /stsci/epa |
| 1436 |
DIRECTORY drwxr-xr-x 512 bytes 12:55 21 Jun 1994 mpeg |
| 1437 |
|
| 1438 |
Host ftp.nau.edu (134.114.64.70) |
| 1439 |
Location: /graphics |
| 1440 |
DIRECTORY drwxr-xr-x 512 bytes 04:51 3 Apr 1994 mpeg |
| 1441 |
|
| 1442 |
Host gum.isi.edu (128.9.32.31) |
| 1443 |
Location: /share/in-notes/media-types/video |
| 1444 |
FILE -rw-r--r-- 15 bytes 18:45 11 Jan 1994 mpeg |
| 1445 |
|
| 1446 |
** unl-archie> WHATIS SECURITY |
| 1447 |
<a href="./rfc1037">RFC 1037</a> Greenberg, B.; Keene, S. NFILE - a file access |
| 1448 |
protocol. 1987 December; 86 p. |
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Kessler & Shepard [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
<a href="./rfc1038">RFC 1038</a> St. Johns, M. Draft revised IP security option. |
| 1458 |
1988 January; 7 p. |
| 1459 |
cops System Security analysis tool |
| 1460 |
forktest Find security holes in shell-escapes |
| 1461 |
kerberos Host security package |
| 1462 |
safe-mkdir mkdir() and security hole *****FIX**** |
| 1463 |
|
| 1464 |
** unl-archie> EXIT |
| 1465 |
# Bye. |
| 1466 |
Connection #0 closed |
| 1467 |
C:\> |
| 1468 |
================================================================== |
| 1469 |
|
| 1470 |
<span class="h4"><a class="selflink" id="section-2.8.2" href="#section-2.8.2">2.8.2</a>. GOPHER</span> |
| 1471 |
|
| 1472 |
The Internet Gopher protocol was developed at the University of |
| 1473 |
Minnesota's Microcomputer Center in 1991, as a distributed |
| 1474 |
information search and retrieval tool for the Internet. Gopher is |
| 1475 |
described in <a href="./rfc1436">RFC 1436</a> [<a href="#ref-1" title=""The Internet Gopher Protocol"">1</a>]; the name derives from the University's |
| 1476 |
mascot. |
| 1477 |
|
| 1478 |
Gopher provides a tool so that publicly available information at a |
| 1479 |
host can be organized in a hierarchical fashion, allowing it to be |
| 1480 |
perused using a simple menu system. Gopher allows a user to view a |
| 1481 |
file on demand without requiring additional file transfer protocols. |
| 1482 |
Gopher also has the capability to "link" gophers on the Internet, so |
| 1483 |
that each Gopher site can be used as a stepping stone to access other |
| 1484 |
sites and reducing the amount of duplicate information and effort on |
| 1485 |
the network. |
| 1486 |
|
| 1487 |
In many cases, users can access Gopher by TELNETing to a valid Gopher |
| 1488 |
location; if the site provides a remote Gopher client, the user will |
| 1489 |
see a text-based, menu interface. The number of Gopher sites is |
| 1490 |
growing rapidly; as the dialogue below shows, most Gopher sites have |
| 1491 |
a menu item that will allow you to identify other Gopher sites. If |
| 1492 |
using TELNET, login with the username "gopher" (this MUST be in |
| 1493 |
lowercase); no password is required. Note that not all Gopher sites |
| 1494 |
provide a remote Gopher client; users may need local Gopher client |
| 1495 |
software on their system. |
| 1496 |
|
| 1497 |
The Gopher server at "ds.internic.net" has a tremendous amount of |
| 1498 |
information for the new user, including lists of frequently asked |
| 1499 |
questions and pointers to various Internet discussion lists. In the |
| 1500 |
sample dialogue below, the remote Gopher client is accessed by |
| 1501 |
TELNETing to the host. With the menu interface shown here, the user |
| 1502 |
merely follows the prompts. Initially, the main menu will appear; |
| 1503 |
selecting item 2 causes Gopher to seize and display the "InterNIC |
| 1504 |
Information Services" menu. Move to the desired menu item by typing |
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Kessler & Shepard [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
the item number or by moving the "pointer" (-->) down to the desired |
| 1514 |
entry using the <DOWN-ARROW> key on the keyboard, and then hitting |
| 1515 |
<ENTER>. To quit the program at any time, press "q" (quit); "?" and |
| 1516 |
"u" will provide help or go back up to the previous menu, |
| 1517 |
respectively. Users may also search for strings within files using |
| 1518 |
the "/" command or download the file being interrogated using the "D" |
| 1519 |
command. |
| 1520 |
|
| 1521 |
Menu item 7 (selected in the dialogue shown here) is titled |
| 1522 |
"Beginners: Start Here", an excellent place for new users to obtain |
| 1523 |
information about the Internet, available tools, terms and concepts, |
| 1524 |
and, perhaps most importantly, some of the cultural aspects of the |
| 1525 |
Internet community. |
| 1526 |
|
| 1527 |
Further information about Gopher can be obtained by contacting the |
| 1528 |
Internet Gopher Team at the University of Minnesota in Minneapolis |
| 1529 |
([email protected]). This is also the site of the first |
| 1530 |
Gopher server (consultant.micro.umn.edu). A Gopher-related |
| 1531 |
discussion list is maintained at [email protected] |
| 1532 |
(see <a href="#section-3.1">Section 3.1</a> for information on subscribing to Internet |
| 1533 |
discussion lists). More information on Gopher clients can be found |
| 1534 |
in the Gopher Frequently Asked Questions (FAQ) file, which can be |
| 1535 |
downloaded using anonymous FTP in file |
| 1536 |
"/pub/usenet/news.answers/gopher-faq" at the host "rtfm.mit.edu"; |
| 1537 |
this FAQ also lists sources for a number of Gopher clients for a wide |
| 1538 |
range of hardware/software platforms. |
| 1539 |
|
| 1540 |
================================================================== |
| 1541 |
** SMCVAX$ TELNET DS.INTERNIC.NET |
| 1542 |
|
| 1543 |
SunOS UNIX (ds) |
| 1544 |
|
| 1545 |
** login: gopher |
| 1546 |
SunOS Release 4.1.3 (DS) #3: Tue Feb 8 10:52:45 EST 1994 |
| 1547 |
|
| 1548 |
****************************************************************** |
| 1549 |
Welcome to the InterNIC Directory and Database Server. |
| 1550 |
****************************************************************** |
| 1551 |
|
| 1552 |
Internet Gopher Information Client v1.11 |
| 1553 |
Root gopher server: ds0.internic.net |
| 1554 |
|
| 1555 |
--> 1. Information About the InterNIC/ |
| 1556 |
2. InterNIC Information Services (General Atomics)/ |
| 1557 |
3. InterNIC Registration Services (NSI)/ |
| 1558 |
4. InterNIC Directory and Database Services (AT&T)/ |
| 1559 |
|
| 1560 |
Press ? for Help, q to Quit Page: 1/1 |
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Kessler & Shepard [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
** View item number: 2 |
| 1570 |
|
| 1571 |
|
| 1572 |
Internet Gopher Information Client v1.11 |
| 1573 |
InterNIC Information Services (General Atomics) |
| 1574 |
|
| 1575 |
--> 1. README. |
| 1576 |
2. About the InfoGuide/ |
| 1577 |
3. About InterNIC Information Services/ |
| 1578 |
4. About the Internet/ |
| 1579 |
5. Getting Connected to the Internet/ |
| 1580 |
6. Beginners: Start Here/ |
| 1581 |
7. Using the Internet/ |
| 1582 |
8. Internet Resources/ |
| 1583 |
9. Advanced Users: NIC Staff, System Administrators, Programmer |
| 1584 |
10. Frequently Asked Questions at InterNIC IS/ |
| 1585 |
11. Scout Report/ |
| 1586 |
12. WAIS search InfoGuide (and elsewhere) by keyword/ |
| 1587 |
13. InfoGuide INDEX. |
| 1588 |
|
| 1589 |
Press ? for Help, q to Quit Page: 1/1 |
| 1590 |
** View item number: 6 |
| 1591 |
|
| 1592 |
|
| 1593 |
Internet Gopher Information Client v1.11 |
| 1594 |
Beginners: Start Here |
| 1595 |
|
| 1596 |
--> 1. About This Directory. |
| 1597 |
2. Introductions to the Internet/ |
| 1598 |
3. Glossaries And Definitions/ |
| 1599 |
4. Network Tools/ |
| 1600 |
5. Further Reading/ |
| 1601 |
6. Collection of Usenet FAQs/ |
| 1602 |
7. Internet Culture and Netiquette/ |
| 1603 |
|
| 1604 |
Press ? for Help, q to Quit Page: 1/1 |
| 1605 |
** q |
| 1606 |
Really quit (y/n) ? |
| 1607 |
** y |
| 1608 |
|
| 1609 |
Connection closed by Foreign Host |
| 1610 |
SMCVAX$ |
| 1611 |
================================================================== |
| 1612 |
|
| 1613 |
|
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Kessler & Shepard [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
<span class="h4"><a class="selflink" id="section-2.8.3" href="#section-2.8.3">2.8.3</a>. Other Information Servers</span> |
| 1626 |
|
| 1627 |
There are a number of other information servers that are growing in |
| 1628 |
popularity and use. The problem with being blessed with so much |
| 1629 |
information from Archie, Gopher, and other sources is exactly that - |
| 1630 |
too much information. To make it easier for users to locate the |
| 1631 |
system on which their desired information resides, a number of other |
| 1632 |
tools have been created. |
| 1633 |
|
| 1634 |
Veronica (Very Easy Rodent-Oriented Net-wide Index to Computerized |
| 1635 |
Archives) was developed at the University of Nevada in Reno as an |
| 1636 |
adjunct to Gopher. As the number of Gopher sites continues to grow, |
| 1637 |
it has become increasingly harder to find information in |
| 1638 |
"Gopherspace" since Gopher is designed to search a single database at |
| 1639 |
a time. Veronica maintains an index of titles of Gopher items and |
| 1640 |
performs a keyword search on all of the Gopher sites that it has |
| 1641 |
knowledge of and access to, obviating the need for the user to |
| 1642 |
perform a menu-by-menu, site-by-site search for information. When a |
| 1643 |
user selects an item from the menu of a Veronica search, "sessions" |
| 1644 |
are automatically established with the appropriate Gopher servers, |
| 1645 |
and a list of data items is returned to the originating Gopher client |
| 1646 |
in the form of a Gopher menu so that the user can access the files. |
| 1647 |
|
| 1648 |
Veronica is available as an option on many Gopher servers, including |
| 1649 |
"internic.net". |
| 1650 |
|
| 1651 |
Another Gopher-adjunct is Jughead (Jonzy's Universal Gopher Hierarchy |
| 1652 |
Excavation And Display). Jughead supports key word searches and the |
| 1653 |
use of logical operators (AND, OR, and NOT). The result of a Jughead |
| 1654 |
search is a display of all menu items which match the search string |
| 1655 |
which are located in the University of Manchester and UMIST |
| 1656 |
Information Server, working from a static database that is re-created |
| 1657 |
every day. Jughead is available from many Gopher sites (including |
| 1658 |
"internic.net"), although Veronica may be a better tool for global |
| 1659 |
searches. |
| 1660 |
|
| 1661 |
Archie and Gopher are primarily used for the indexing of text-based |
| 1662 |
files. The World Wide Web (WWW or W3) Project, initiated by the CERN |
| 1663 |
Institute for Particle Physics in Geneva, Switzerland, is designed to |
| 1664 |
combine aspects of information retrieval with multimedia |
| 1665 |
communications. The WWW Project is intended to allow users to access |
| 1666 |
information in many different types of formats, including text, |
| 1667 |
sound, image, and video. WWW treats all searchable Internet files as |
| 1668 |
hypertext documents. "Hypertext" is a new term which merely refers |
| 1669 |
to text that contains pointers to other text, allowing a user reading |
| 1670 |
one document to jump to another document for more information on a |
| 1671 |
given topic, and then return to the same location in the original |
| 1672 |
document. The original WWW site is at CERN and may be accessed via |
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Kessler & Shepard [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
Telnet at "nxoc01.cern.ch". The user will be automatically logged in |
| 1682 |
and a help menu can be displayed by entering the "h" command. |
| 1683 |
|
| 1684 |
To generally access WWW servers, users must run client software |
| 1685 |
called a "browser". The browser reads documents from WWW servers and |
| 1686 |
can access files by FTP, gopher, and other methods. WWW can also |
| 1687 |
handle hypermedia documents; "hypermedia" is another new term, |
| 1688 |
referring to a file using any medium that contains pointers to |
| 1689 |
another medium. WWW browsers, then, are able to display images, |
| 1690 |
sound, or animations in addition to text. WWW sources and additional |
| 1691 |
information may be accessed via anonymous FTP from the "/pub/WWW" |
| 1692 |
directory at "info.cern.ch" or the "/Web" directory at |
| 1693 |
"ftp.ncsa.uiuc.edu". |
| 1694 |
|
| 1695 |
The most commonly used WWW browser is Mosaic, developed at the |
| 1696 |
National Center for Supercomputer Applications (NCSA) at the |
| 1697 |
University of Illinois. Mosaic provides a uniform mechanism for |
| 1698 |
finding the location of information, as well as determining the data |
| 1699 |
type, presentation method, and linkages to other information. A |
| 1700 |
large number of shareware Mosaic clients are available at |
| 1701 |
"ftp.ncsa.uiuc.edu". It should be noted that commercial versions of |
| 1702 |
Mosaic will also become available for a variety of platforms after |
| 1703 |
the summer of 1994. |
| 1704 |
|
| 1705 |
The Wide Area Information Server (WAIS, pronounced "ways") was |
| 1706 |
initiated jointly by Apple Computer, Dow Jones, KMPG Peat Marwick, |
| 1707 |
and Thinking Machines Corp. It is a set of free-ware, share-ware, |
| 1708 |
and commercial software products for a wide variety of |
| 1709 |
hardware/software platforms, which work together to help users find |
| 1710 |
information on the Internet. WAIS provides a single interface |
| 1711 |
through which a user can access many different information databases. |
| 1712 |
|
| 1713 |
The user interface allow a query to be formulated in English and the |
| 1714 |
WAIS server will automatically choose the appropriate databases to |
| 1715 |
search. Further information about WAIS can be obtained by reading |
| 1716 |
the WAIS FAQ, from host "rtfm.mit.edu" in file |
| 1717 |
"/pub/usenet/news.answers/wais-faq". |
| 1718 |
|
| 1719 |
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Uniform Resource Locator Format</span> |
| 1720 |
|
| 1721 |
As more and more protocols have become available to identify files, |
| 1722 |
archive and server sites, news lists, and other information resources |
| 1723 |
on the Internet, it was inevitable that some shorthand would arise to |
| 1724 |
make it a little easier to designate these sources. The common |
| 1725 |
shorthand that is employed is called the Uniform Resource Locator |
| 1726 |
(URL) format. |
| 1727 |
|
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Kessler & Shepard [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
The list below provides information on how the URL format should be |
| 1738 |
interpreted for the protocols and resources that have been discussed |
| 1739 |
in this document. A complete description of the URL format may be |
| 1740 |
found in [<a href="#ref-2" title=""Uniform Resource Locators (URL)"">2</a>]. |
| 1741 |
|
| 1742 |
file://"host"/"directory"/"file-name" |
| 1743 |
Used to identify a specific file. E.g., the file "htmlasst" in the |
| 1744 |
"edu" directory at host "ftp.cs.da" would be denoted with URL as: |
| 1745 |
<URL:file://ftp.cs.da/edu/htmlasst> |
| 1746 |
|
| 1747 |
ftp://"user":"password"@"host":"port"/"directory"/"file-name" |
| 1748 |
Used to identify an FTP site. E.g.: |
| 1749 |
<URL:ftp://ftp.eff.org/pub/EFF/Policy/Crypto/*> |
| 1750 |
|
| 1751 |
gopher://"host":"port"/"gopher-path" |
| 1752 |
Used to identify a Gopher site and menu path. E.g.: |
| 1753 |
<URL:gopher://info.umd.edu:901/info/Government/Factbook92> |
| 1754 |
|
| 1755 |
http://"host":"port"/"directory"/"file-name"?"searchpart" |
| 1756 |
Used to identify a WWW server location. "http" refers to the |
| 1757 |
HyperText Transport Protocol; file names commonly use the ".html" |
| 1758 |
extension, indicating use of the HyperText Markup Language. E.g.: |
| 1759 |
<URL:http://info.isoc.org/home.html> |
| 1760 |
|
| 1761 |
mailto:"e-mail address" |
| 1762 |
Identifies an individual Internet mail address. E.g.: |
| 1763 |
<URL:mailto:[email protected]> |
| 1764 |
|
| 1765 |
telnet://"user":"password"@"host":"port"/ |
| 1766 |
Identifies a TELNET site (the trailing "/" is optional). E.g.: |
| 1767 |
<URL:telnet//envnet:[email protected]> |
| 1768 |
|
| 1769 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Discussion Lists</span> |
| 1770 |
|
| 1771 |
Among the most useful features of the Internet are the discussion |
| 1772 |
lists that have become available to allow individuals to discuss |
| 1773 |
topics of mutual concern. Discussion list topics range from SCUBA |
| 1774 |
diving and home brewing of beer to AIDS research and foreign policy. |
| 1775 |
Several, naturally, deal specifically with the Internet, TCP/IP |
| 1776 |
protocols, and the impact of new technologies. |
| 1777 |
|
| 1778 |
Most of the discussion lists accessible from the Internet are |
| 1779 |
"unmoderated", meaning that anyone can send a message to the list's |
| 1780 |
central repository and the message will then be automatically |
| 1781 |
forwarded to all subscribers of the list. These lists provide very |
| 1782 |
fast turn-around between submission of a message and delivery, but |
| 1783 |
often result in a lot of messages (including inappropriate "junk |
| 1784 |
mail"). A "moderated" list has an extra step; a human list moderator |
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Kessler & Shepard [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
examines all messages before they are forwarded to ensure that the |
| 1794 |
messages are appropriate to the list and not needlessly inflammatory! |
| 1795 |
|
| 1796 |
Users should be warned that some lists generate a significant amount |
| 1797 |
of messages each day. Before subscribing to too many lists, be sure |
| 1798 |
that you are aware of local policies and/or charges governing access |
| 1799 |
to discussion lists and e-mail storage. |
| 1800 |
|
| 1801 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Internet Discussion Lists</span> |
| 1802 |
|
| 1803 |
A list of the known interest groups may be found by Gophering to |
| 1804 |
"ds.internic.net". Follow the menu path "InterNIC Information |
| 1805 |
Services" | "Using the Internet" | "Basic Internet Services" | |
| 1806 |
"Electronic Mail" | "Mailing Lists" to find the 8-part list of lists. |
| 1807 |
|
| 1808 |
Be careful if you download these files; the list is nearly 1.5 MB in |
| 1809 |
size, listing over 800 lists! Along the way, you will find a wealth |
| 1810 |
of other information. |
| 1811 |
|
| 1812 |
Mail can be sent to an Internet list at an address with the following |
| 1813 |
form: |
| 1814 |
|
| 1815 |
list_name@host_name |
| 1816 |
|
| 1817 |
The common convention when users want to subscribe, unsubscribe, or |
| 1818 |
handle any other administrative matter is to send a message to the |
| 1819 |
list administrator; do NOT send administrivia to the main list |
| 1820 |
address! The list administrator can usually be found at: |
| 1821 |
|
| 1822 |
list_name-REQUEST@host_name |
| 1823 |
|
| 1824 |
To subscribe to a list, it is often enough to place the word |
| 1825 |
"subscribe" in the main body of the message, although a line with the |
| 1826 |
format: |
| 1827 |
|
| 1828 |
SUBSCRIBE list_name your_full_name |
| 1829 |
|
| 1830 |
will satisfy most mail servers. A similar message may be used to get |
| 1831 |
off a list; just use the word "unsubscribe". |
| 1832 |
|
| 1833 |
Not every list follows this convention, but it is a safe bet if you |
| 1834 |
don't have better information! |
| 1835 |
|
| 1836 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Usenet</span> |
| 1837 |
|
| 1838 |
Usenet, also known as NETNEWS or Usenet news, is another information |
| 1839 |
source with its own set of special interest mailing lists organized |
| 1840 |
into "newsgroups". Usenet originated on UNIX systems but has |
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Kessler & Shepard [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
migrated to many other types of hosts, although most Usenet servers |
| 1850 |
are still UNIX-based. Usenet clients, called "newsreaders", are |
| 1851 |
available for virtually any operating system. |
| 1852 |
|
| 1853 |
While Usenet newsgroups are usually accessible at Internet sites, a |
| 1854 |
prospective Usenet client host must have appropriate newsreader |
| 1855 |
software to be able to read news. Users will have to check with |
| 1856 |
their local host or network administrator to find out what Usenet |
| 1857 |
newsgroups are locally available, as well as the local policies for |
| 1858 |
using them. |
| 1859 |
|
| 1860 |
Usenet newsgroup names are hierarchical in nature. The first part of |
| 1861 |
the name, called the "hierarchy", provides an indication about the |
| 1862 |
general subject area. There are two types of hierarchies, called |
| 1863 |
"mainstream" and "alternative"; the total number of newsgroups is in |
| 1864 |
the thousands. The "news.announce.newusers" newsgroup is a good |
| 1865 |
place for new Usenet users to find a detailed introduction to the use |
| 1866 |
of Usenet, as well as an introduction to its culture. |
| 1867 |
|
| 1868 |
Usenet mainstream hierarchies are established by a process that |
| 1869 |
requires the approval of a majority of Usenet members. Most sites |
| 1870 |
that receive a NETNEWS feed receive all of these hierarchies, which |
| 1871 |
include: |
| 1872 |
|
| 1873 |
comp Computers |
| 1874 |
misc Miscellaneous |
| 1875 |
news Network news |
| 1876 |
rec Recreation |
| 1877 |
sci Science |
| 1878 |
soc Social issues |
| 1879 |
talk Various discussion lists |
| 1880 |
|
| 1881 |
The alternative hierarchies include lists that may be set up at any |
| 1882 |
site that has the server software and disk space. These lists are |
| 1883 |
not formally part of Usenet and, therefore, may not be received by |
| 1884 |
all sites getting NETNEWS. The alternative hierarchies include: |
| 1885 |
|
| 1886 |
alt Alternate miscellaneous discussion lists |
| 1887 |
bionet Biology, medicine, and life sciences |
| 1888 |
bit BITNET discussion lists |
| 1889 |
biz Various business-related discussion lists |
| 1890 |
ddn Defense Data Network |
| 1891 |
gnu GNU lists |
| 1892 |
ieee IEEE information |
| 1893 |
info Various Internet and other networking information |
| 1894 |
k12 K-12 education |
| 1895 |
u3b AT&T 3B computers |
| 1896 |
vmsnet Digital's VMS operating system |
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Kessler & Shepard [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
A list of newsgroups may be found at host "rtfm.mit.edu" in the path |
| 1906 |
"/pub/usenet/news.answers"; see the "/active-newsgroups" and "/alt- |
| 1907 |
hierarchies" subdirectories. |
| 1908 |
|
| 1909 |
There is often some overlap between Usenet newsgroups and Internet |
| 1910 |
discussion lists. Some individuals join both lists in these |
| 1911 |
circumstances or, often, there is cross-posting of messages. Some |
| 1912 |
Usenet newsgroup discussions are forwarded onto an Internet mailing |
| 1913 |
list by an individual site to provide access to those users who do |
| 1914 |
not have Usenet available. |
| 1915 |
|
| 1916 |
Users not connected to Usenet may post messages to a Usenet newsgroup |
| 1917 |
using Internet e-mail. First, replace the periods in the Usenet |
| 1918 |
discussion list name with hyphens (e.g., the folk music discussion |
| 1919 |
list, "rec.music.folk", would become "rec-music-folk"). Then, send |
| 1920 |
an e-mail message to: |
| 1921 |
|
| 1922 |
[email protected] |
| 1923 |
|
| 1924 |
Usenet news may be read using Gopher. Connect to the host |
| 1925 |
"gopher.msu.edu" using the path "News & Weather" | "USENET News" or |
| 1926 |
host "gopher.bham.ac.uk" using the path "Usenet News Reader". |
| 1927 |
|
| 1928 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. BITNET/EARN</span> |
| 1929 |
|
| 1930 |
Another important set of discussion groups is maintained using a |
| 1931 |
program called LISTSERV. LISTSERV is a service provided widely on |
| 1932 |
BITNET and EARN (European Academic and Research Network), although it |
| 1933 |
is also available to Internet users. |
| 1934 |
|
| 1935 |
LISTSERV commands are placed in the main body of e-mail messages sent |
| 1936 |
to an appropriate list server location. To find out what lists are |
| 1937 |
available, send a message to "[email protected]" with the |
| 1938 |
command "list global" in the main body of the message; whatever you |
| 1939 |
place in the "Subject:" field will be ignored. |
| 1940 |
|
| 1941 |
Once you have found a list of interest, you can send a message to the |
| 1942 |
appropriate address with any appropriate command, including: |
| 1943 |
|
| 1944 |
HELP Get help & a list of commands |
| 1945 |
SUBSCRIBE list_name your_full_name Subscribe to a list |
| 1946 |
UNSUBSCRIBE list_name Unsubscribe from a list |
| 1947 |
INDEX Get a list of LISTSERV files |
| 1948 |
GET file_name Obtain a file from the server |
| 1949 |
|
| 1950 |
|
| 1951 |
|
| 1952 |
|
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Kessler & Shepard [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Internet Documentation</span> |
| 1962 |
|
| 1963 |
To fully appreciate and understand what is going on within the |
| 1964 |
Internet community, users might wish to obtain the occasional |
| 1965 |
Internet specification. The main body of Internet documents are |
| 1966 |
Request for Comments (RFCs), although a variety of RFC subsets have |
| 1967 |
been defined for various specific purposes. The sections below will |
| 1968 |
describe the RFCs and other documentation, and how to get these |
| 1969 |
documents. |
| 1970 |
|
| 1971 |
NOTE: For complete, up-to-date information on obtaining Internet |
| 1972 |
documentation, users should Gopher to "ds.internic.net" and follow |
| 1973 |
the path "InterNIC Information Services" | "About the Internet" | |
| 1974 |
"Internet Documentation", and then select the desired set of |
| 1975 |
documents. This Gopher path is referred to as the "documentation |
| 1976 |
root path" in the remainder of this section. |
| 1977 |
|
| 1978 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Request for Comments (RFCs)</span> |
| 1979 |
|
| 1980 |
RFCs are the body of literature comprising Internet protocols, |
| 1981 |
standards, research questions, hot topics, humor (especially those |
| 1982 |
dated 1 April), and general information. Each RFC is uniquely issued |
| 1983 |
a number which is never reused or reissued; if a document is revised, |
| 1984 |
it is given a new RFC number and the old RFC is said to be |
| 1985 |
"obsoleted." Announcements are sent to the RFC-DIST mailing list |
| 1986 |
whenever a new RFC is issued; anyone may join this list by sending e- |
| 1987 |
mail to "[email protected]". |
| 1988 |
|
| 1989 |
RFCs may be obtained through the mail (i.e., postal service), but it |
| 1990 |
is easier and faster to get them on-line. One easy way to obtain |
| 1991 |
RFCs on-line is to use RFC-INFO, an e-mail-based service to help |
| 1992 |
users locate and retrieve RFCs and other Internet documents. To use |
| 1993 |
the service, send e-mail to "[email protected]" and leave the |
| 1994 |
"Subject:" field blank; commands that may go in the main body of the |
| 1995 |
message include: |
| 1996 |
|
| 1997 |
HELP (Help file) |
| 1998 |
HELP: ways_to_get_rfcs (Help file on how to get RFCs) |
| 1999 |
|
| 2000 |
RETRIEVE: RFC |
| 2001 |
Doc-ID: RFCxxxx (Retrieve RFC xxxx; use all 4 digits) |
| 2002 |
|
| 2003 |
LIST: RFC (List all RFCs...) |
| 2004 |
[options] (...[matching the following options]) |
| 2005 |
|
| 2006 |
KEYWORDS: xxx (Title contains string "xxx") |
| 2007 |
AUTHOR: xxx (Written by "xxx") |
| 2008 |
ORGANIZATION: (Issued by company "xxx") |
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Kessler & Shepard [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
DATED-AFTER: mmm-dd-yyyy |
| 2018 |
DATED-BEFORE: mmm-dd-yyyy |
| 2019 |
OBSOLETES: RFCxxxx (List RFCs obsoleting RFC xxxx) |
| 2020 |
|
| 2021 |
An alternative way to obtain RFCs by e-mail is to send an e-mail |
| 2022 |
message to "[email protected]", leaving the "Subject:" field blank. |
| 2023 |
|
| 2024 |
In the main body of the message, use one or more of the following |
| 2025 |
commands. The RFC index, or a specific reference to an RFC, will |
| 2026 |
indicate whether the RFC is available in ASCII text or PostScript |
| 2027 |
format. By convention, all RFCs are available in ASCII while some |
| 2028 |
are also available in PostScript where use of graphics and/or |
| 2029 |
different fonts adds more information or clarity. The instructions |
| 2030 |
below show how to get the index; be aware that this file is very |
| 2031 |
large, containing the citing for over 1,700 documents. Note that not |
| 2032 |
all RFCs numbered below 698 (July 1975) are available on-line: |
| 2033 |
|
| 2034 |
SEND HELP (Help file) |
| 2035 |
SEND RFC/RFC-INDEX (RFC Index) |
| 2036 |
SEND RFC/RFCxxxx.TXT (ASCII version of RFC xxxx) |
| 2037 |
SEND RFC/RFCxxxx.PS (PostScript version of RFC xxxx) |
| 2038 |
|
| 2039 |
------------------------------------------- |
| 2040 |
TABLE 1. Some of the RFC Repositories. |
| 2041 |
|
| 2042 |
REGION HOST ADDRESS DIRECTORY |
| 2043 |
|
| 2044 |
U.S. nic.ddn.mil rfc |
| 2045 |
U.S. nisc.jvnc.net rfc |
| 2046 |
U.S. ftp.isi.edu in-notes |
| 2047 |
U.S. wuarchive.wustl.edu info/rfc |
| 2048 |
U.K. src.doc.ic.ac.uk rfc |
| 2049 |
Europe funet.fi rfc |
| 2050 |
Pacific munnari.oz.au rfc |
| 2051 |
------------------------------------------- |
| 2052 |
|
| 2053 |
To obtain an RFC via anonymous FTP, connect to one of the RFC |
| 2054 |
repositories listed in Table 1 using FTP. After connecting, change |
| 2055 |
to the appropriate RFC directory (as shown in Table 1) using the "cd" |
| 2056 |
command. To obtain a particular file, use the "get" command: |
| 2057 |
|
| 2058 |
GET RFC-INDEX.TXT local_name (RFC Index) |
| 2059 |
GET RFCxxxx.TXT local_name (ASCII version of RFC XXXX) |
| 2060 |
GET RFCxxxx.PS local_name (PostScript version of RFC XXXX) |
| 2061 |
|
| 2062 |
Finally, check out the path "RFC's (Request for Comments)" under the |
| 2063 |
documentation root path for the RFC index, complete instructions on |
| 2064 |
obtaining RFCs, and a complete set of RFCs. |
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Kessler & Shepard [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
The sample dialogue below, although highly abbreviated, shows a user |
| 2074 |
obtaining <a href="./rfc1594">RFC 1594</a> (Answers to Commonly asked "New Internet User" |
| 2075 |
Questions) using the first three methods described above. |
| 2076 |
|
| 2077 |
================================================================== |
| 2078 |
** SMCVAX$ MAIL |
| 2079 |
** MAIL> SEND |
| 2080 |
** To: IN%"[email protected]" |
| 2081 |
** Subject: |
| 2082 |
Enter your message below. Press CTRL/Z when complete, CTRL/C to quit |
| 2083 |
** SEND RFC/RFC1594.TXT |
| 2084 |
** ^Z |
| 2085 |
** MAIL> EXIT |
| 2086 |
|
| 2087 |
** SMCVAX$ MAIL |
| 2088 |
** MAIL> SEND |
| 2089 |
** To: IN%"[email protected]" |
| 2090 |
** Subject: |
| 2091 |
Enter your message below. Press CTRL/Z when complete, CTRL/C to quit |
| 2092 |
** RETRIEVE: RFC |
| 2093 |
** Doc-ID: <a href="./rfc1594">RFC1594</a> |
| 2094 |
** ^Z |
| 2095 |
** MAIL> EXIT |
| 2096 |
|
| 2097 |
** SMCVAX$ FTP NIC.DDN.MIL |
| 2098 |
** Username: ANONYMOUS |
| 2099 |
** Password: |
| 2100 |
** NIC.DDN.MIL> CD rfc |
| 2101 |
** NIC.DDN.MIL> GET <a href="./rfc1594">rfc1594</a>.txt <a href="./rfc1594">RFC-1594</a>.TXT |
| 2102 |
** NIC.DDN.MIL> EXIT |
| 2103 |
SMCVAX$ |
| 2104 |
================================================================== |
| 2105 |
|
| 2106 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Internet Standards</span> |
| 2107 |
|
| 2108 |
RFCs describe many aspects of the Internet. By the early 1990s, |
| 2109 |
however, so many specifications of various protocols had been written |
| 2110 |
that it was not always clear as to which documents represented |
| 2111 |
standards for the Internet. For that reason, a subset of RFCs have |
| 2112 |
been designated as STDs to identify them as Internet standards. |
| 2113 |
|
| 2114 |
Unlike RFC numbers that are never reused, STD numbers always refer to |
| 2115 |
the latest version of the standard. UDP, for example, would be |
| 2116 |
completely identified as "STD-6/RFC-768." Note that STD numbers |
| 2117 |
refer to a standard, which is not necessarily a single document; an |
| 2118 |
STD, therefore, might refer to several RFCs. STD 19, for example, is |
| 2119 |
the NetBIOS Service Protocols standard and comprises RFCs 1001 and |
| 2120 |
1002; a complete citation for this standard would be "STD-19/RFC- |
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Kessler & Shepard [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
1001/RFC-1002." |
| 2130 |
|
| 2131 |
The availability of new STDs is announced on the RFC-DIST mailing |
| 2132 |
list. STD-1 [<a href="#ref-14" title=""Internet Official Protocol Standards"">14</a>] always refers to the latest list of "Internet |
| 2133 |
Official Protocol Standards". The Internet standards process is |
| 2134 |
described in <a href="./rfc1602">RFC 1602</a> [<a href="#ref-6" title=""The Internet Standards Process -- Revision 2"">6</a>] and STD notes are explained in <a href="./rfc1311">RFC 1311</a> |
| 2135 |
[<a href="#ref-15" title=""Introduction to the STD Notes"">15</a>]. |
| 2136 |
|
| 2137 |
STDs can be obtained as RFCs via anonymous FTP from any RFC |
| 2138 |
repository. In addition, some RFC sites (such as "nic.ddn.mil") |
| 2139 |
provide an STD directory so that STD documents can be found in the |
| 2140 |
path "/STD/xx.TXT", where "xx" refers to the STD number. |
| 2141 |
|
| 2142 |
STD documents may be obtained as RFCs using the methods described in |
| 2143 |
<a href="#section-4.1">Section 4.1</a>. STDs may also be obtained via the RFC-INFO server using |
| 2144 |
the "RETRIEVE: STD" and "Doc-ID: STDxxxx" commands. Also, check out |
| 2145 |
the path "STD's (Standard RFC's)" under the documentation root path |
| 2146 |
for the STD index, complete instructions on obtaining STDs, and a |
| 2147 |
complete set of STDs. |
| 2148 |
|
| 2149 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. For Your Information Documents</span> |
| 2150 |
|
| 2151 |
The For Your Information (FYI) series of RFCs provides Internet users |
| 2152 |
with information about many topics related to the Internet. FYI |
| 2153 |
topics range from historical to explanatory to tutorial, and are |
| 2154 |
aimed at the wide spectrum of people that use the Internet. The FYI |
| 2155 |
series includes answers to frequently asked questions by both |
| 2156 |
beginning and seasoned users of the Internet, an annotated |
| 2157 |
bibliography of Internet books, and an explanation of the domain name |
| 2158 |
system. |
| 2159 |
|
| 2160 |
Like the STDs, an FYI number always refers to the latest version of |
| 2161 |
an FYI. FYI 4, for example, refers to the answers to commonly asked |
| 2162 |
questions by new Internet users; its complete citation would be "FYI- |
| 2163 |
4/RFC-1594." The FYI notes are explained in FYI 1 [<a href="#ref-9" title=""F.Y.I. on F.Y.I.: Introduction to the F.Y.I. Notes"">9</a>]. |
| 2164 |
|
| 2165 |
FYIs can be obtained as RFCs via anonymous FTP from any RFC |
| 2166 |
repository. In addition, some RFC sites (such as "nic.ddn.mil") |
| 2167 |
provide an FYI directory so that FYI documents can be found in the |
| 2168 |
path "/FYI/xx.TXT", where "xx" refers to the FYI number. |
| 2169 |
|
| 2170 |
FYI documents may be obtained as RFCs using the methods described in |
| 2171 |
<a href="#section-4.1">Section 4.1</a>. FYIs may also be obtained via the RFC-INFO server using |
| 2172 |
the "RETRIEVE: FYI" and "Doc-ID: FYIxxxx" commands. Also, check out |
| 2173 |
the path "FYI's (For Your Information RFC's)" under the documentation |
| 2174 |
root path for the FYI index, complete instructions on obtaining FYIs, |
| 2175 |
and a complete set of FYIs. |
| 2176 |
|
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Kessler & Shepard [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. RARE Technical Reports</span> |
| 2186 |
|
| 2187 |
The Reseaux Associes pour la Recherche Europeenne (RARE) is the |
| 2188 |
Association of European Research Networks and their users. RARE's |
| 2189 |
charter is to promote and participate in the creation of a high- |
| 2190 |
quality European computer communications infrastructure for the |
| 2191 |
support of research endeavors. RARE member networks use Open Systems |
| 2192 |
Interconnection (OSI) protocols and TCP/IP. Since the summer of |
| 2193 |
1993, to promote a closer relationship between RARE and the IETF, |
| 2194 |
RARE Technical Reports (RTRs) are also published as RFCs. |
| 2195 |
|
| 2196 |
RTR documents may be obtained as RFCs using the methods described in |
| 2197 |
<a href="#section-4.1">Section 4.1</a>. RTRs may also be obtained via the RFC-INFO server using |
| 2198 |
the "RETRIEVE: RTR" and "Doc-ID: RTRxxxx" commands. Also, check out |
| 2199 |
the path "RTR's (RARE Technical Report RFC's)" under the |
| 2200 |
documentation root path for the RTR index, complete instructions on |
| 2201 |
obtaining RTRs, and a complete set of RTRs. They may also be |
| 2202 |
obtained via anonymous FTP from "ftp.rare.nl". |
| 2203 |
|
| 2204 |
NOTE: As of December 1994, RARE and EARN have merged to form TERENA |
| 2205 |
(Trans-European Research and Education Network Association). |
| 2206 |
|
| 2207 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Perusing the Internet...</span> |
| 2208 |
|
| 2209 |
This guide is intended to provide the reader with a rudimentary |
| 2210 |
ability to use the utilities that are provided by TCP/IP and the |
| 2211 |
Internet. By now, it is clear that the user's knowledge, ability, |
| 2212 |
and willingness to experiment are about the only limits to what can |
| 2213 |
be accomplished. |
| 2214 |
|
| 2215 |
The next step is to explore the nooks and crannies of the network. |
| 2216 |
One software tool that will users in this quest is the Merit Computer |
| 2217 |
Center's (Ann Arbor, MI) "Cruise of the Internet", available at no |
| 2218 |
cost from the host "nic.merit.edu" using FTP. For more information, |
| 2219 |
read the "readme" files in the directories "internet/resources/ |
| 2220 |
cruise.mac" and "internet/resources/cruise.dos" for Mac and PC |
| 2221 |
versions, respectively. For general information about resources at |
| 2222 |
this site, see the READ.ME file in the root directory or send e-mail |
| 2223 |
to "[email protected]". |
| 2224 |
|
| 2225 |
Several RFCs provide invaluable information about finding things on |
| 2226 |
the Internet. One of the best such sources is FYI 10/RFC 1402, |
| 2227 |
titled "There's Gold in them thar Networks! -or- Searching for |
| 2228 |
Treasure in all the Wrong Places" [<a href="#ref-11" title=""There's Gold in them thar Networks! Searching for Treasure in all the Wrong Places"">11</a>], an excellent guide for |
| 2229 |
someone who wants to look around the Internet for a wide range of |
| 2230 |
material. Other good sources include the "Hitchhiker's Guide to the |
| 2231 |
Internet" (<a href="./rfc1118">RFC 1118</a>) [<a href="#ref-7" title=""Hitchhiker's Guide to the Internet"">7</a>] and the "Guide to Network Resource Tools" |
| 2232 |
(FYI 23/RFC 1580) [<a href="#ref-3" title=""Guide to Network Resource Tools"">3</a>]. Answers to frequently asked questions for |
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
<span class="grey">Kessler & Shepard [Page 40]</span></pre> |
| 2237 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2238 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2239 |
|
| 2240 |
|
| 2241 |
both new and experienced users of the Internet may be found in FYI |
| 2242 |
4/RFC 1594 [<a href="#ref-10" title=""FYI on Questions and Answers - Answers to Commonly asked 'New Internet User' Questions"">10</a>] and FYI 7/RFC 1207 [<a href="#ref-8" title=""FYI on Questions and Answers: Answers to Commonly Asked 'Experienced Internet User' Questions"">8</a>], respectively. |
| 2243 |
|
| 2244 |
There are many other sources that cite locations from which to access |
| 2245 |
specific information about a wide range of subjects using such tools |
| 2246 |
as FTP, Telnet, Gopher, and WWW. These include: |
| 2247 |
|
| 2248 |
o The INTERNET SERVICES LIST, maintained by Scott Yanoff of the |
| 2249 |
University of Wisconsin in Milwaukee and updated at least once a |
| 2250 |
month. This list can be obtained at <URL:ftp://ftp.csd.uwm.edu/ |
| 2251 |
pub/inet.services.txt> or <URL:gopher://csd4.csd.uwm.edu/Remote |
| 2252 |
Information Services/Special Internet Connections>. |
| 2253 |
|
| 2254 |
o An excellent starting point for searching the World Wide Web is to |
| 2255 |
point your WWW browser at "<a href="http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/StartingPoints/NetworkStartingPoints.html">http://www.ncsa.uiuc.edu/SDG/Software</a> |
| 2256 |
<a href="http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/StartingPoints/NetworkStartingPoints.html">/Mosaic/StartingPoints/NetworkStartingPoints.html</a>". |
| 2257 |
|
| 2258 |
o The Scout Report is a weekly service by the InterNIC Information |
| 2259 |
Services team. To subscribe to the Scout Report mailing list, send |
| 2260 |
e-mail to "[email protected]" and place the line "subscribe |
| 2261 |
scout-report" in the main body of the message. Optionally, Gopher |
| 2262 |
to "ds.internic.net" and follow the path "InterNIC Information |
| 2263 |
Services" | "Scout Report" or point your WWW browser at |
| 2264 |
"<a href="http://www.internic.net/infoguide.html">http://www.internic.net/infoguide.html</a>". |
| 2265 |
|
| 2266 |
o "The INTERNET Yellow Pages" by Harley Hahn and Rick Stout [<a href="#ref-28" title=""The Internet Yellow Pages"">28</a>]. |
| 2267 |
|
| 2268 |
More books and specialized articles came out about the Internet in |
| 2269 |
1993 and 1994 than in all previous years (squared!). Some of them |
| 2270 |
are directly related to finding your way around, or finding things |
| 2271 |
on, the Internet; a very partial list includes: |
| 2272 |
|
| 2273 |
o "The Internet Directory" by Eric Braun [<a href="#ref-21" title=""The Internet Directory"">21</a>] |
| 2274 |
|
| 2275 |
o "The MAC Internet Tour Guide", "The PC Internet Tour Guide", and |
| 2276 |
"The Windows Internet Tour Guide" by Michael Fraase [<a href="#ref-24" title=""The MAC Internet Tour Guide"">24</a>, <a href="#ref-25" title=""The PC Internet Tour Guide"">25</a>, <a href="#ref-26" title=""The Windows Internet Tour Guide"">26</a>] |
| 2277 |
|
| 2278 |
o "The Internet Navigator" by Paul Gilster [<a href="#ref-27" title=""The Internet Navigator"">27</a>] |
| 2279 |
|
| 2280 |
o "Zen and the Art of the Internet" by Brendan Kehoe [<a href="#ref-29" title=""Zen and the Art of the Internet"">29</a>] |
| 2281 |
|
| 2282 |
o "The Whole Internet User's Guide & Catalog" by Ed Krol [<a href="#ref-31" title=""The Whole Internet User's Guide & Catalog"">31</a>] |
| 2283 |
|
| 2284 |
o "INTERNET: Getting Started" by April Marine, Susan Kirkpatrick, |
| 2285 |
Vivian Neou, and Carol Ward [<a href="#ref-33" title=""INTERNET: Getting Started"">33</a>] |
| 2286 |
|
| 2287 |
o "Finding it on the Internet: The Next Challenge for Librarianship" |
| 2288 |
by Brian Nielsen [<a href="#ref-34" title=""Finding it on the Internet: The Next Challenge for Librarianship."">34</a>] |
| 2289 |
|
| 2290 |
|
| 2291 |
|
| 2292 |
<span class="grey">Kessler & Shepard [Page 41]</span></pre> |
| 2293 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2294 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2295 |
|
| 2296 |
|
| 2297 |
o "Navigating the Internet" by Richard Smith and Mark Gibbs [<a href="#ref-35" title=""Navigating the Internet"">35</a>] |
| 2298 |
|
| 2299 |
A much more comprehensive list of Internet-related books may be found |
| 2300 |
in FYI 19/RFC 1463 [<a href="#ref-5" title=""FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings"">5</a>]. |
| 2301 |
|
| 2302 |
Finally, Carl Malamud has written a delightful book called "Exploring |
| 2303 |
the Internet: A Technical Travelogue" [<a href="#ref-32" title=""Exploring the Internet: A Technical Travelogue"">32</a>], chronicling not the |
| 2304 |
Internet as much as the people who built it and use it. This book |
| 2305 |
will not teach you how to perform an anonymous FTP file transfer nor |
| 2306 |
how to use Gopher, but provides insights about our network (and |
| 2307 |
Carl's gastro-pathology) that no mere statistics can convey. |
| 2308 |
|
| 2309 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acronyms and Abbreviations</span> |
| 2310 |
|
| 2311 |
ASCII American Standard Code for Information Interchange |
| 2312 |
BITNET Because It's Time Network |
| 2313 |
DDN Defense Data Network |
| 2314 |
DNS Domain Name System |
| 2315 |
EARN European Academic Research Network |
| 2316 |
FAQ Frequently Asked Questions list |
| 2317 |
FTP File Transfer Protocol |
| 2318 |
FYI For Your Information series of RFCs |
| 2319 |
HTML HyperText Markup Language |
| 2320 |
HTTP HyperText Transport Protocol |
| 2321 |
ICMP Internet Control Message Protocol |
| 2322 |
IP Internet Protocol |
| 2323 |
ISO International Organization for Standardization |
| 2324 |
NetBIOS Network Basic Input/Output System |
| 2325 |
NIC Network Information Center |
| 2326 |
NICNAME Network Information Center name service |
| 2327 |
NSF National Science Foundation |
| 2328 |
NSFNET National Science Foundation Network |
| 2329 |
RFC Request For Comments |
| 2330 |
RARE Reseaux Associes pour la Recherche Europeenne |
| 2331 |
RTR RARE Technical Reports |
| 2332 |
SMDS Switched Multimegabit Data Service |
| 2333 |
SMTP Simple Mail Transfer Protocol |
| 2334 |
STD Internet Standards series of RFCs |
| 2335 |
TCP Transmission Control Protocol |
| 2336 |
TTL Time-To-Live |
| 2337 |
UDP User Datagram Protocol |
| 2338 |
URL Uniform Resource Locator |
| 2339 |
WAIS Wide Area Information Server |
| 2340 |
W3 World Wide Web |
| 2341 |
WWW World Wide Web |
| 2342 |
|
| 2343 |
|
| 2344 |
|
| 2345 |
|
| 2346 |
|
| 2347 |
|
| 2348 |
<span class="grey">Kessler & Shepard [Page 42]</span></pre> |
| 2349 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2350 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2351 |
|
| 2352 |
|
| 2353 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span> |
| 2354 |
|
| 2355 |
Security issues are not discussed in this memo. |
| 2356 |
|
| 2357 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span> |
| 2358 |
|
| 2359 |
Our thanks are given to all sites where we FTPed, TELNETed, GOPHERed, |
| 2360 |
and otherwise used system resources, particularly St. Michael's |
| 2361 |
College in Colchester, Vermont (smcvax.smcvt.edu). We also |
| 2362 |
appreciate the comments and suggestions from our colleagues at Hill |
| 2363 |
Associates, our students, and other members of the Internet |
| 2364 |
community, particularly Mark Delany and the rest of the gang at the |
| 2365 |
Australian Public Access Network Association, Margaret Hall (BBN), |
| 2366 |
John Martin (RARE), Tom Maufer (NASA), Michael Patton (BBN), and |
| 2367 |
Brian Williams. Special thanks are due to Joyce Reynolds for her |
| 2368 |
continued encouragement and direction. |
| 2369 |
|
| 2370 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span> |
| 2371 |
|
| 2372 |
[<a id="ref-1">1</a>] Anklesaria, F., McCahill, M., Lindner, P, Johnson, D., Torrey, |
| 2373 |
D., and B. Alberti, "The Internet Gopher Protocol", <a href="./rfc1436">RFC 1436</a>, |
| 2374 |
University of Minnesota, March 1993. |
| 2375 |
|
| 2376 |
[<a id="ref-2">2</a>] Berners-Lee, T., Masinter, L., and M. McCahill, Editors, "Uniform |
| 2377 |
Resource Locators (URL)", <a href="./rfc1738">RFC 1738</a>, CERN, Xerox PARC, University |
| 2378 |
of Minnesota, December 1994. |
| 2379 |
|
| 2380 |
[<a id="ref-3">3</a>] EARN Staff, "Guide to Network Resource Tools", FYI 23, <a href="./rfc1580">RFC 1580</a>, |
| 2381 |
EARN Association, March 1994. |
| 2382 |
|
| 2383 |
[<a id="ref-4">4</a>] Harrenstien, K., Stahl, M., and E. Feinler, "NICNAME/WHOIS", <a href="./rfc954">RFC</a> |
| 2384 |
<a href="./rfc954">954</a>, SRI, October 1985. |
| 2385 |
|
| 2386 |
[<a id="ref-5">5</a>] Hoffman, E. and L. Jackson, "FYI on Introducing the Internet-- A |
| 2387 |
Short Bibliography of Introductory Internetworking Readings", FYI |
| 2388 |
19, <a href="./rfc1463">RFC 1463</a>, Merit Network, Inc., NASA, May 1993. |
| 2389 |
|
| 2390 |
[<a id="ref-6">6</a>] Internet Architecture Board, Internet Engineering Steering Group, |
| 2391 |
"The Internet Standards Process -- Revision 2", <a href="./rfc1602">RFC 1602</a>, IAB, |
| 2392 |
IESG, March 1994. |
| 2393 |
|
| 2394 |
[<a id="ref-7">7</a>] Krol, E., "Hitchhiker's Guide to the Internet", <a href="./rfc1118">RFC 1118</a>, |
| 2395 |
University of Illinois Urbana, September 1989. |
| 2396 |
|
| 2397 |
[<a id="ref-8">8</a>] Malkin, G., Marine, A., and J. Reynolds, "FYI on Questions and |
| 2398 |
Answers: Answers to Commonly Asked 'Experienced Internet User' |
| 2399 |
Questions", FYI 7, <a href="./rfc1207">RFC 1207</a>, FTP Software, SRI, USC/Information |
| 2400 |
Sciences Institute, February 1991. |
| 2401 |
|
| 2402 |
|
| 2403 |
|
| 2404 |
<span class="grey">Kessler & Shepard [Page 43]</span></pre> |
| 2405 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2406 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2407 |
|
| 2408 |
|
| 2409 |
[<a id="ref-9">9</a>] Malkin, G., and J. Reynolds, "F.Y.I. on F.Y.I.: Introduction to |
| 2410 |
the F.Y.I. Notes", FYI 1, <a href="./rfc1150">RFC 1150</a>, Proteon, USC/Information |
| 2411 |
Sciences Institute, March 1990. |
| 2412 |
|
| 2413 |
[<a id="ref-10">10</a>] Marine, A., Reynolds, J., and G. Malkin, "FYI on Questions and |
| 2414 |
Answers - Answers to Commonly asked 'New Internet User' |
| 2415 |
Questions", FYI 4, <a href="./rfc1594">RFC 1594</a>, NASA Ames Research Center, |
| 2416 |
USC/Information Sciences Institute, Xylogics, March 1994. |
| 2417 |
|
| 2418 |
[<a id="ref-11">11</a>] Martin, J., "There's Gold in them thar Networks! Searching for |
| 2419 |
Treasure in all the Wrong Places", FYI 10, <a href="./rfc1402">RFC 1402</a>, Ohio State |
| 2420 |
University, January 1993. |
| 2421 |
|
| 2422 |
[<a id="ref-12">12</a>] Mockapetris, P., "Domain Names - Concepts and Facilities", STD |
| 2423 |
13, <a href="./rfc1034">RFC 1034</a>, USC/Information Sciences Institute, November 1987. |
| 2424 |
|
| 2425 |
[<a id="ref-13">13</a>] Postel, J., "Domain Name System Structure and Delegation", |
| 2426 |
USC/Information Sciences Institute, <a href="./rfc1591">RFC 1591</a>, March 1994. |
| 2427 |
|
| 2428 |
[<a id="ref-14">14</a>] Postel, J., Editor, "Internet Official Protocol Standards", STD |
| 2429 |
1, <a href="./rfc1720">RFC 1720</a>, Internet Architecture Board, November 1994. |
| 2430 |
|
| 2431 |
[<a id="ref-15">15</a>] Postel, J., "Introduction to the STD Notes", <a href="./rfc1311">RFC 1311</a>, |
| 2432 |
USC/Information Sciences Institute, March 1992. |
| 2433 |
|
| 2434 |
[<a id="ref-16">16</a>] Postel, J., and J. Reynolds, "File Transfer Protocol (FTP), STD |
| 2435 |
9, <a href="./rfc959">RFC 959</a>, USC/Information Sciences Institute, October 1985. |
| 2436 |
|
| 2437 |
[<a id="ref-17">17</a>] Postel, J. and J. Reynolds, "TELNET Protocol Specification", STD |
| 2438 |
8, <a href="./rfc854">RFC 854</a>, USC/Information Sciences Institute, May 1983. |
| 2439 |
|
| 2440 |
[<a id="ref-18">18</a>] Socolofsky, T., and C. Kale, "TCP/IP Tutorial", <a href="./rfc1180">RFC 1180</a>, Spider |
| 2441 |
Systems Ltd., January 1991. |
| 2442 |
|
| 2443 |
[<a id="ref-19">19</a>] Williamson, S., "Transition and Modernization of the Internet |
| 2444 |
Registration Service", <a href="./rfc1400">RFC 1400</a>, Network Solutions, Inc., March |
| 2445 |
1993. |
| 2446 |
|
| 2447 |
[<a id="ref-20">20</a>] Zimmerman, D., "The Finger User Information Protocol", <a href="./rfc1288">RFC 1288</a>, |
| 2448 |
Rutgers University, December 1991. |
| 2449 |
|
| 2450 |
[<a id="ref-21">21</a>] Braun, E., "The Internet Directory", New York: Fawcett Columbine, |
| 2451 |
1994. |
| 2452 |
|
| 2453 |
[<a id="ref-22">22</a>] Comer, D., "Internetworking with TCP/IP, Vol. I: Principles, |
| 2454 |
Protocols, and Architecture", 2/e. Englewood Cliffs (NJ): |
| 2455 |
Prentice-Hall, 1991. |
| 2456 |
|
| 2457 |
|
| 2458 |
|
| 2459 |
|
| 2460 |
<span class="grey">Kessler & Shepard [Page 44]</span></pre> |
| 2461 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2462 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2463 |
|
| 2464 |
|
| 2465 |
[<a id="ref-23">23</a>] Feit, S., "TCP/IP", New York: McGraw-Hill, 1993. |
| 2466 |
|
| 2467 |
[<a id="ref-24">24</a>] Fraase, M., "The MAC Internet Tour Guide", Chapel Hill (NC): |
| 2468 |
Ventana Press, 1994. |
| 2469 |
|
| 2470 |
[<a id="ref-25">25</a>] Fraase, M., "The PC Internet Tour Guide", Chapel Hill (NC): |
| 2471 |
Ventana Press, 1994. |
| 2472 |
|
| 2473 |
[<a id="ref-26">26</a>] Fraase, M., "The Windows Internet Tour Guide", Chapel Hill (NC): |
| 2474 |
Ventana Press, 1994. |
| 2475 |
|
| 2476 |
[<a id="ref-27">27</a>] Gilster, P., "The Internet Navigator", New York: John Wiley & |
| 2477 |
Sons, 1993. |
| 2478 |
|
| 2479 |
[<a id="ref-28">28</a>] Hahn, H., and R. Stout, "The Internet Yellow Pages", Berkeley |
| 2480 |
(CA): Osborne McGraw-Hill, 1994. |
| 2481 |
|
| 2482 |
[<a id="ref-29">29</a>] Kehoe, B., "Zen and the Art of the Internet", Englewood Cliffs |
| 2483 |
(NJ): Prentice-Hall, 1993. |
| 2484 |
|
| 2485 |
[<a id="ref-30">30</a>] Kessler, G., "An Overview of TCP/IP Protocols and the Internet", |
| 2486 |
August 1994. <URL:gopher://ds.internic.net/Information |
| 2487 |
Services/Advanced Users/tcp-ip>. |
| 2488 |
|
| 2489 |
[<a id="ref-31">31</a>] Krol, E., "The Whole Internet User's Guide & Catalog", Sebastopol |
| 2490 |
(CA): O'Reilly & Associates, 1992. |
| 2491 |
|
| 2492 |
[<a id="ref-32">32</a>] Malamud, C., "Exploring the Internet: A Technical Travelogue", |
| 2493 |
Englewood Cliffs (NJ): PTR Prentice Hall, 1992. |
| 2494 |
|
| 2495 |
[<a id="ref-33">33</a>] Marine, A., Kirkpatrick, S., Neou, V., and C. Ward. "INTERNET: |
| 2496 |
Getting Started", Englewood Cliffs (NJ): PTR Prentice Hall, 1993. |
| 2497 |
|
| 2498 |
[<a id="ref-34">34</a>] Nielsen, B., "Finding it on the Internet: The Next Challenge for |
| 2499 |
Librarianship." Database, Vol. 13, October 1990, pp. 105-107. |
| 2500 |
|
| 2501 |
[<a id="ref-35">35</a>] Smith, R., and M. Gibbs, "Navigating the Internet", Carmel (IN): |
| 2502 |
SAMS, 1994. |
| 2503 |
|
| 2504 |
|
| 2505 |
|
| 2506 |
|
| 2507 |
|
| 2508 |
|
| 2509 |
|
| 2510 |
|
| 2511 |
|
| 2512 |
|
| 2513 |
|
| 2514 |
|
| 2515 |
|
| 2516 |
<span class="grey">Kessler & Shepard [Page 45]</span></pre> |
| 2517 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span> |
| 2518 |
<span class="grey"><a href="./rfc1739">RFC 1739</a> Primer on Internet & TCP/IP Tools December 1994</span> |
| 2519 |
|
| 2520 |
|
| 2521 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Authors' Addresses</span> |
| 2522 |
|
| 2523 |
Gary C. Kessler |
| 2524 |
Hill Associates |
| 2525 |
17 Roosevelt Highway |
| 2526 |
Colchester, VT 05446 |
| 2527 |
|
| 2528 |
Phone: +1 802-655-8633 |
| 2529 |
Fax: +1 802-655-7974 |
| 2530 |
EMail: [email protected] |
| 2531 |
|
| 2532 |
|
| 2533 |
Steven D. Shepard |
| 2534 |
Hill Associates |
| 2535 |
17 Roosevelt Highway |
| 2536 |
Colchester, VT 05446 |
| 2537 |
|
| 2538 |
Phone: +1 802-655-8646 |
| 2539 |
Fax: +1 802-655-7974 |
| 2540 |
EMail: [email protected] |
| 2541 |
|
| 2542 |
|
| 2543 |
|
| 2544 |
|
| 2545 |
|
| 2546 |
|
| 2547 |
|
| 2548 |
|
| 2549 |
|
| 2550 |
|
| 2551 |
|
| 2552 |
|
| 2553 |
|
| 2554 |
|
| 2555 |
|
| 2556 |
|
| 2557 |
|
| 2558 |
|
| 2559 |
|
| 2560 |
|
| 2561 |
|
| 2562 |
|
| 2563 |
|
| 2564 |
|
| 2565 |
|
| 2566 |
|
| 2567 |
|
| 2568 |
|
| 2569 |
|
| 2570 |
|
| 2571 |
|
| 2572 |
Kessler & Shepard [Page 46] |
| 2573 |
</pre> |