idnits 2.17.1 draft-kessler-primer-v2-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 2350 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 47 instances of too long lines in the document, the longest one being 5 characters in excess of 72. == There are 128 instances of lines with non-RFC2606-compliant FQDNs in the document. == There are 35 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 220 has weird spacing: '...ill.com prefe...' == Line 221 has weird spacing: '...ill.com prefe...' == Line 222 has weird spacing: '...ill.com prefe...' == Line 223 has weird spacing: '...ill.com names...' == Line 224 has weird spacing: '...ill.com names...' == (6 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 27, 1996) is 10073 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '-q' on line 248 -- Looks like a reference, but probably isn't: '-v' on line 248 -- Looks like a reference, but probably isn't: '-R' on line 248 -- Looks like a reference, but probably isn't: '-s' on line 290 -- Looks like a reference, but probably isn't: 'GUEST' on line 580 -- Looks like a reference, but probably isn't: 'KUMQUAT' on line 580 -- Looks like a reference, but probably isn't: 'INLINE' on line 1543 -- Looks like a reference, but probably isn't: 'LINK' on line 1551 -- Looks like a reference, but probably isn't: 'ISMAP' on line 1541 ** Downref: Normative reference to an Informational RFC: RFC 1436 (ref. '1') -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '22' -- Possible downref: Non-RFC (?) normative reference: ref. '23' -- Possible downref: Non-RFC (?) normative reference: ref. '28' ** Obsolete normative reference: RFC 954 (ref. '4') (Obsoleted by RFC 3912) ** Obsolete normative reference: RFC 1602 (ref. '6') (Obsoleted by RFC 2026) -- Possible downref: Non-RFC (?) normative reference: ref. '30' -- Possible downref: Non-RFC (?) normative reference: ref. '32' ** Obsolete normative reference: RFC 1150 (ref. '9') (Obsoleted by RFC 6360) ** Downref: Normative reference to an Informational RFC: RFC 1591 (ref. '13') ** Obsolete normative reference: RFC 1920 (ref. '14') (Obsoleted by RFC 2000) ** Downref: Normative reference to an Informational RFC: RFC 1311 (ref. '15') ** Downref: Normative reference to an Informational RFC: RFC 1180 (ref. '18') ** Downref: Normative reference to an Informational RFC: RFC 1400 (ref. '19') Summary: 19 errors (**), 0 flaws (~~), 10 warnings (==), 18 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet and TCP/IP Tools Primer Gary C. Kessler 2 INTERNET DRAFT BBN Systems and Technologies 3 Expires March 27, 1997 Steven D. Shepard 4 Hill Associates, Inc. 5 September 27, 1996 7 A Primer On Internet and TCP/IP Tools and Utilities 8 10 Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas, 14 and its working groups. Note that other groups may also distribute 15 working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check the 23 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 24 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 25 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 26 ftp.isi.edu (US West Coast). 28 Table of Contents 30 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 31 2. Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 32 3. Finding Information About Internet Hosts and Domains. . . . . . . . . .3 33 3.1. NSLOOKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 34 3.2. Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 35 3.3. Finger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 36 3.4. Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 37 4. The Two Fundamental Tools . . . . . . . . . . . . . . . . . . . . . . 10 38 4.1. TELNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 39 4.2. FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 40 5. User Database Lookup Tools . . . . . . . . . . . . . . . . . . . . . 17 41 5.1. WHOIS/NICNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 42 5.2. KNOWBOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 43 6. Information Servers . . . . . . . . . . . . . . . . . . . . . . . . . 21 44 6.1. Archie . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 45 6.2. Gopher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 46 6.3. VERONICA, JUGHEAD, and WAIS . . . . . . . . . . . . . . . . . . . . 26 47 7. The World Wide Web. . . . . . . . . . . . . . . . . . . . . . . . . . 27 48 7.1. Uniform Resource Locator Format . . . . . . . . . . . . . . . . . . 31 49 7.2. User Directories on the Web . . . . . . . . . . . . . . . . . . . . 31 50 7.3. Other Service Accessible Via the Web. . . . . . . . . . . . . . . . 32 51 8. Discussion Lists and Newsgroups . . . . . . . . . . . . . . . . . . . 33 52 8.1. Internet Discussion Lists . . . . . . . . . . . . . . . . . . . . . 33 53 8.2. LISTSERV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 54 8.3. Majordomo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 55 8.4. Usenet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 56 8.5 Finding Discussion Lists and Newsgroups. . . . . . . . . . . . . . . 36 57 9. Internet Documentation . . . . . . . . . . . . . . . . . . . . . . . 37 58 9.1. Request for Comments (RFCs) . . . . . . . . . . . . . . . . . . . . 37 59 9.2. Internet Standards . . . . . . . . . . . . . . . . . . . . . . . . 39 60 9.3. For Your Information Documents . . . . . . . . . . . . . . . . . . 40 61 9.4. RARE Technical Reports . . . . . . . . . . . . . . . . . . . . . . 40 62 10. Perusing the Internet . . . . . . . . . . . . . . . . . . . . . . . 41 63 11. Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . . 42 64 12. Security Considerations . . . . . . . . . . . . . . . . . . . . . . 43 65 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . 43 66 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 67 15. Authors' Address . . . . . . . . . . . . . . . . . . . . . . . . . . 45 69 1. Introduction 71 This memo is an introductory guide to some of the TCP/IP and Internet 72 tools and utilities that allow users to access the wide variety of 73 information on the network, from determining if a particular host is 74 up to viewing a multimedia thesis on foreign policy. It also 75 describes discussion lists accessible from the Internet, ways to 76 obtain Internet and TCP/IP documents, and some resources that help 77 users weave their way through the Internet. This memo may be used as 78 a tutorial for individual self-learning, a step-by-step laboratory 79 manual for a course, or as the basis for a site's users manual. It is 80 intended as a basic guide only and will refer to other sources for 81 more detailed information. 83 2. Nomenclature 85 The following sections provide descriptions and detailed examples of 86 several TCP/IP utilities and applications, including the reproduction 87 of actual sessions using these utilities (with some extraneous 88 information removed). Each section describes a single TCP/IP-based 89 tool, it's application, and, in some cases, how it works. The text 90 description is usually followed by an actual sample session. 92 The sample dialogues shown below were obtained from a variety of 93 systems, including AIX on an IBM RS/6000, Linux on an Intel 486, 94 Multinet TCP/IP on a VAX running VMS, and FTP Software's OnNet 95 (formerly PC/TCP) running on a DOS/Windows PC. While the examples 96 below can be used as a guide to using and learning about the 97 capabilities of these tools, the reader should understand that not 98 all of these utilities may be found at all TCP/IP hosts nor in all 99 commercial software packages. Furthermore, the user interface for 100 different packages will be different and the actual command line may 101 appear differently than shown here; this will be particularly true 102 for graphical user interfaces running over Windows, X-Windows, OS/2, 103 or Macintosh systems. Windows-based sessions are not shown in this 104 RFC because of the desire to have a text version of this document; in 105 addition, most GUI-based TCP/IP packages obscure some of the detail 106 that is essential for understanding what is really happening when you 107 click on a button or drag a file. The Internet has many exciting 108 things to offer but standardized interfaces to the protocols is not 109 yet one of them! This guide will not provide any detail or 110 motivation about the Internet Protocol Suite; more information about 111 the TCP/IP protocols and related issues may be found in RFC 1180 112 [18], Comer [22], Feit [23], Kessler [30], and Stevens [aa]. 114 In the descriptions below, commands are shown in a Courier font 115 (Postscript only); items appearing in square brackets ([]) are 116 optional, the vertical-bar (|) means "or," parameters appearing with 117 no brackets or within curly brackets ({}) are mandatory, and 118 parameter names that need to be replaced with a specific value will 119 be shown in italics (Postscript version) or within angle brackets 120 (<>, text version). In the sample dialogues, user input is in bold 121 (Postscript version) or denoted with asterisks (**) in the margin 122 (text version). 124 3. Finding Information About Internet Hosts and Domains 126 There are several tools that let you learn information about Internet 127 hosts and domains. These tools provide the ability for an application 128 or a user to perform host name/address reconciliation (NSLOOKUP), 129 determine whether another host is up and available (PING), learn 130 about another host's users (Finger), and learn the route that packets 131 will take to another host (Traceroute). 133 3.1. NSLOOKUP 135 NSLOOKUP is the name server lookup program that comes with many 136 TCP/IP software packages. A user can use NSLOOKUP to examine entries 137 in the Domain Name System (DNS) database that pertain to a particular 138 host or domain; one common use is to determine a host system's IP 139 address from its name or the host's name from its IP address. The 140 general form of the command to make a single query is: 142 nslookup [|] 144 If the program is started without any parameters, the user will be 145 prompted for input; the user can enter either an IP address or host 146 name at that time, and the program will respond with the name and 147 address of the default name sever, the name server actually used to 148 resolve each request, and the IP address and host name that was 149 queried. Exit is used to quit the NSLOOKUP application. 151 Three simple queries are shown in the example below: 153 1 Requests the address of the host named www.hill.com, the World Wide 154 Web server at Hill Associates). As it turns out, this is not the 155 true name of the host, but an alias. The full name of the host and 156 the IP address are listed by NSLOOKUP. 158 2 Requests the address of host syrup.hill.com, which is the same host 159 as in the first query. Note that NSLOOKUP provides a "non- 160 authoritative" answer. Since NSLOOKUP just queried this same 161 address, the information is still in its cache memory. Rather than 162 send additional messages to the name server, the answer is one that 163 it remembers from before; the server didn't look up the information 164 again, however, so it is not guaranteed to still be accurate 165 (because the information might have changed within the last few 166 milliseconds!). 168 3 Requests the name of the host with the given IP address. The result 169 points to the Internet gateway to Australia, munnari.oz.au. 171 One additional query is shown in the dialogue below. NSLOOKUP 172 examines information that is stored by the DNS. The default NSLOOKUP 173 queries examine basic address records (called "A records") to 174 reconcile the host name and IP address, although other information is 175 also available. In the final query below, for example, the user wants 176 to know where electronic mail addressed to the hill.com domain 177 actually gets delivered, since hill.com is not the true name of an 178 actual host. This is accomplished by changing the query type to look 179 for mail exchange (MX) records by issuing a set type command (which 180 must be in lower case). The query shows that mail addressed to 181 hill.com is actually sent to a mail server called mail.hill.com. If 182 that system is not available, mail delivery will be attempted to 183 first mailme.hill.com and then to netcomsv.netcom.com; the order of 184 these attempts is controlled by the "preference" value. This query 185 also returns the name of the domain's name servers and all associated 186 IP addresses. 188 The DNS is beyond the scope of this introduction, although more 189 information about the concepts and structure of the DNS can be found 190 in STD 13/RFC 1034 [12] and RFC 1591 [13]. The help command can be 191 issued at the program prompt for information about NSLOOKUP's more 192 advanced commands. 194 TECHNICAL NOTE: There are other tools that might be available on your 195 system or with your software for examining the DNS. Alternatives to 196 NSLOOKUP include HOST and DIG. 198 ==================================================================== 199 ** SMCVAX$ nslookup 201 Default Server: ns1.ner.bbnplanet.net 202 Address: 192.52.71.5 204 ** > www.hill.com 205 Name: syrup.hill.com 206 Address: 199.182.20.3 207 Aliases: www.hill.com 209 ** > syrup.hill.com 210 Non-authoritative answer: 211 Name: syrup.hill.com 212 Address: 199.182.20.3 214 ** > 128.250.1.21 215 Name: munnari.OZ.AU 216 Address: 128.250.1.21 218 ** > set type=MX 219 ** > hill.com 220 hill.com preference = 20, mail exchanger = mail.hill.com 221 hill.com preference = 40, mail exchanger = mailme.hill.com 222 hill.com preference = 60, mail exchanger = netcomsv.netcom.com 223 hill.com nameserver = nameme.hill.com 224 hill.com nameserver = ns1.noc.netcom.net 225 hill.com nameserver = ns.netcom.com 226 mail.hill.com internet address = 199.182.20.4 227 mailme.hill.com internet address = 199.182.20.3 228 netcomsv.netcom.com internet address = 192.100.81.101 229 ns1.noc.netcom.net internet address = 204.31.1.1 230 ns.netcom.com internet address = 192.100.81.105 232 ** > exit 233 SMCVAX$ 234 ==================================================================== 236 3.2. Ping 238 Ping, reportedly an acronym for the Packet Internetwork Groper, is 239 one of the most widely available tools bundled with TCP/IP software 240 packages. Ping uses a series of Internet Control Message Protocol 241 (ICMP) [bb] Echo messages to determine if a remote host is active or 242 inactive, and to determine the round-trip delay in communicating with 243 it. 245 A common form of the Ping command, showing some of the more commonly 246 available options that are of use to general users, is: 248 ping [-q] [-v] [-R] [-c ] [-i ] [-s ] 249 251 where: 252 -q Quiet output; nothing is displayed except summary lines 253 at startup and completion 255 -v Verbose output, which lists ICMP packets that are 256 received in addition to Echo Responses 258 -R Record route option; includes the RECORD_ROUTE option in 259 the Echo Request packet and displays the route buffer on 260 returned packets 262 -c Count Specifies the number of Echo Requests to be sent before 263 concluding test (default is to run until interrupted with 264 a control-C) 266 -i Wait Indicates the number of seconds to wait between sending 267 each packet (default = 1) 269 -s PacketSize Specifies the number of data bytes to be sent; the 270 total ICMP packet size will be PacketSize+8 bytes 271 due to the ICMP header (default = 56, or a 64 byte 272 packet) 274 Host IP address or host name of target system 276 In the first example below, the user pings the host 277 thumper.bellcore.com, requesting that 6 (-c) messages be sent, each 278 containing 64 bytes (-s) of user data. The display shows the 279 round-trip delay of each Echo message returned to the sending host; 280 at the end of the test, summary statistics are displayed. 282 In the second example, the user pings the host smcvax.smcvt.edu, 283 requesting that 10 messages be sent in quite mode (-q). In this case, 284 a summary is printed at the conclusion of the test and individual 285 responses are not listed. 287 TECHNICAL NOTE: Older versions of the Ping command, which are still 288 available on some systems, had the following general format: 290 ping [-s] {|} [] [] 292 In this form, optional "-s" string tells the system to continually 293 send an ICMP Echo message every second; the optional PacketSize 294 parameter specifies the number of bytes in the Echo message (the 295 message will contain PacketSize-8 bytes of data; the default is 56 296 bytes of data and a 64 byte message); and the optional Count 297 parameter indicates the number of Echo messages to send before 298 concluding the test (the default is to run the test continuously 299 until interrupted). 301 ==================================================================== 302 ** syrup:/home$ ping -c 6 -s 64 thumper.bellcore.com 303 PING thumper.bellcore.com (128.96.41.1): 64 data bytes 304 72 bytes from 128.96.41.1: icmp_seq=0 ttl=240 time=641.8 ms 305 72 bytes from 128.96.41.1: icmp_seq=2 ttl=240 time=1072.7 ms 306 72 bytes from 128.96.41.1: icmp_seq=3 ttl=240 time=1447.4 ms 307 72 bytes from 128.96.41.1: icmp_seq=4 ttl=240 time=758.5 ms 308 72 bytes from 128.96.41.1: icmp_seq=5 ttl=240 time=482.1 ms 310 --- thumper.bellcore.com ping statistics --- 311 6 packets transmitted, 5 packets received, 16% packet loss 312 round-trip min/avg/max = 482.1/880.5/1447.4 ms 314 ** syrup:/home$ ping -q -c 10 smcvax.smcvt.edu 315 PING smcvax.smcvt.edu (192.80.64.1): 56 data bytes 317 --- smcvax.smcvt.edu ping statistics --- 318 10 packets transmitted, 8 packets received, 20% packet loss 319 round-trip min/avg/max = 217.8/246.4/301.5 ms 320 ==================================================================== 322 3.3. Finger 324 The Finger program may be used to find out who is logged in on 325 another system or to find out detailed information about a specific 326 user. This command has also introduced a brand new verb; fingering 327 someone on the Internet is not necessarily a rude thing to do! The 328 Finger User Information Protocol is described in RFC 1288 [20]. The 329 most general format of the Finger command is: 331 finger []@ 333 The first example below shows the result of fingering an individual 334 user at a remote system. The first line of the response shows the 335 username, the user's real name, their process identifier, 336 application, and terminal port number. Additional information may be 337 supplied at the option of the user in "plan" and/or "project" files 338 that they supply; these files are often named PLAN.TXT or 339 PROJECT.TXT, respectively, and reside in a user's root directory (or 340 somewhere in an appropriate search path). 342 The second example shows the result of fingering a remote system. 343 This lists all of the processes currently running at the fingered 344 system or other information, depending upon how the remote system's 345 administrator set up the system to respond to the Finger command. 347 ==================================================================== 348 ** C:\> finger kumquat@smcvax.smcvt.edu 349 [smcvax.smcvt.edu] 350 KUMQUAT Gary Kessler KUMQUAT not logged in 351 Last login Fri 16-Sep-1996 3:47PM-EDT 353 Plan: 355 =================================================================== 356 Gary C. Kessler 357 Adjunct Faculty Member, Graduate College 359 INTERNET: kumquat@smcvt.edu 360 =================================================================== 362 ** C:\> finger @smcvax.smcvt.edu 363 [smcvax.smcvt.edu] 364 Tuesday, September 17, 1996 10:12AM-EDT Up 30 09:40:18 365 5+1 Jobs on SMCVAX Load ave 0.16 0.19 0.21 367 User Personal Name Subsys Terminal Console Location 368 GOODWIN Dave Goodwin LYNX 6.NTY2 waldo.smcvt.edu 369 JAT John Tronoan TELNET 1.TXA5 370 HELPDESK System Manager EDT 2:08.NTY4 [199.93.35.182] 371 SMITH Lorraine Smith PINE .NTY3 [199.93.34.139] 372 SYSTEM System Manager MAIL 23.OPA0 The VAX Console 373 *DCL* SMCVX1$OPA0 The VAX Console 374 ==================================================================== 376 3.4. Traceroute 378 Traceroute is another common TCP/IP tool, this one allowing users to 379 learn about the route that packets take from their local host to a 380 remote host. Although used often by network and system managers as a 381 simple, yet powerful, debugging tool, traceroute can be used by end 382 users to learn something about the ever-changing structure of the 383 Internet. 385 The classic Traceroute command has the following general format 386 (where "#" represents a positive integer value associated with the 387 qualifier): 389 traceroute [-m <#>] [-q <#>] [-w <#>] [-p <#>] 390 {|} 392 where -m is the maximum allowable TTL value, measured as the 393 number of hops allowed before the program terminates 394 (default = 30) 395 -q is the number of UDP packets that will be sent with each 396 time-to-live setting (default = 3) 397 -w is the amount of time, in seconds, to wait for an answer 398 from a particular router before giving up (default = 5) 399 -p is the invalid port address at the remote host (default = 400 33434) 402 The Traceroute example below shows the route between a host at St. 403 Michael's College (domain smcvt.edu) and a host at Hill Associates 404 (www.hill.com), both located in Colchester, VT but served by 405 different Internet service providers (ISP). 407 1 St. Michael's College is connected to the Internet via BBN Planet; 408 since the mid-1980s, BBN operated the NSF's regional ISP, called 409 the New England Academic and Research Network (NEARNET), which was 410 renamed in 1994. The first hop, then, goes to St. Mike's BBN Planet 411 gateway router (smc.bbnplanet.net). The next hop goes to another 412 BBN Planet router (denoted here only by IP address since a name was 413 not assigned to the device), until the packet reaches the BBN 414 Planet T3 backbone. 416 2 The packet takes two hops through routers at BBN Planet's Cambridge 417 (MA) facility and is then forwarded to BBN Planet in New York City, 418 where the packet takes four more hops. The packet is then forwarded 419 to BBN Planet in College Park (MD). 421 3 The packet is sent to BBN Planet's router at MAE-East, MFS 422 Datanet's Network Access Point (NAP) in Washington, D.C. MAE stands 423 for Metropolitan Area Exchange, and is a Fiber Distributed Data 424 Interface (FDDI) ring interconnecting routers from subscribing 425 ISPs. The packet is then forwarded to NETCOM, Hill Associates' ISP. 427 4 The packet now travels through NETCOM's T3 backbone, following 428 links from Washington, D.C. to Chicago to Santa Clara (CA), to San 429 Jose (CA). 431 5 The packet is now sent to Hill Associates router (again, a system 432 designated only by an IP address since the NETCOM side of the 433 router was not named) and then passed to the target system. Note 434 that the host's real name is not www.hill.com, but syrup.hill.com. 436 TECHNICAL NOTE: The original version of Traceroute works by sending a 437 sequence of User Datagram Protocol (UDP) datagrams to an invalid port 438 address at the remote host. Using the default settings, three 439 datagrams are sent, each with a Time-To-Live (TTL) field value set to 440 one. The TTL value of 1 causes the datagram to "timeout" as soon as 441 it hits the first router in the path; this router will then respond 442 with an ICMP Time Exceeded Message (TEM) indicating that the datagram 443 has expired. Another three UDP messages are now sent, each with the 444 TTL value set to 2, which causes the second router to return ICMP 445 TEMs. This process continues until the packets actually reach the 446 other destination. Since these datagrams are trying to access an 447 invalid port at the destination host, ICMP Destination Unreachable 448 Messages are returned indicating an unreachable port; this event 449 signals the Traceroute program that it is finished! The Traceroute 450 program displays the round-trip delay associated with each of the 451 attempts. (Note that some current implementations of Traceroute use 452 the Record-Route option in IP rather than the method described 453 above.) 455 As an aside, Traceroute did not begin life as a general-purpose 456 utility, but as a quick-and-dirty debugging aid used to find a 457 routing problem. The code (complete with comments!) is available by 458 anonymous FTP in the file traceroute.tar.Z from the host 459 ftp.ee.lbl.gov. (See Section 4.2 for a discussion of anonymous FTP.) 461 ==================================================================== 462 ** SMCVAX$ traceroute www.hill.com 463 traceroute to syrup.hill.com (199.182.20.3), 30 hops max, 38 byte 464 packets 465 1 smc.bbnplanet.net (192.80.64.5) 10 ms 0 ms 0 ms 466 2 131.192.48.105 (131.192.48.105) 0 ms 10 ms 10 ms 467 3 cambridge1-cr4.bbnplanet.net (199.94.204.77) 40 ms 40 ms 50 ms 468 4 cambridge1-br1.bbnplanet.net (4.0.1.205) 30 ms 50 ms 50 ms 469 5 nyc1-br2.bbnplanet.net (4.0.1.121) 60 ms 60 ms 40 ms 470 6 nyc2-br2.bbnplanet.net (4.0.1.154) 60 ms 50 ms 60 ms 471 7 nyc2-br2.bbnplanet.net (4.0.1.154) 60 ms 40 ms 50 ms 472 8 nyc2-br1.bbnplanet.net (4.0.1.54) 70 ms 60 ms 30 ms 473 9 collegepk-br2.bbnplanet.net (4.0.1.21) 50 ms 50 ms 40 ms 474 10 maeeast.bbnplanet.net (4.0.1.18) 200 ms 170 ms 210 ms 475 11 fddi.mae-east.netcom.net (192.41.177.210) 60 ms 50 ms 70 ms 476 12 t3-2.was-dc-gw1.netcom.net (163.179.220.181) 70 ms 60 ms 50 ms 477 13 t3-2.chw-il-gw1.netcom.net (163.179.220.186) 70 ms 80 ms 80 ms 478 14 t3-2.scl-ca-gw1.netcom.net (163.179.220.190) 140 ms 110 ms 160 479 ms 480 15 t3-1.sjx-ca-gw1.netcom.net (163.179.220.193) 120 ms 130 ms 120 481 ms 482 16 198.211.141.8 (198.211.141.8) 220 ms 260 ms 240 ms 483 17 syrup.hill.com (199.182.20.3) 220 ms 240 ms 219 ms 484 SMCVAX$ 485 ==================================================================== 487 4. The Two Fundamental Tools 489 The two most basic tools for Internet applications are TELNET and the 490 File Transfer Protocol (FTP). TELNET allows a user to login to a 491 remote host over a TCP/IP network, while FTP, as the name implies, 492 allows a user to move files between two TCP/IP hosts. These two 493 utilities date back to the very early days of the ARPANET. 495 4.1. TELNET 497 TELNET [17] is TCP/IP's virtual terminal protocol. Using TELNET, a 498 user connected to one host can login to another host, appearing like 499 a directly-attached terminal at the remote system; this is TCP/IP's 500 definition of a virtual terminal. The general form of the TELNET 501 command is: 503 telnet [|] [] 505 As shown, a TELNET connection is initiated when the user enters the 506 telnet command and supplies either a host_name or IP_address; if 507 neither are given, TELNET will ask for one once the application 508 begins. 510 In the example below, a user of a PC uses TELNET to attach to the 511 remote host smcvax.smcvt.edu. Once logged in via TELNET, the user can 512 do anything on the remote host that would be possible if connected 513 via a directly-attached terminal or via modem. The commands that are 514 subsequently used are those available on the remote system to which 515 the user is attached. In the sample dialogue below, the user attached 516 to SMCVAX will use basic VAX/VMS commands: 518 o The dir command lists the files having a "COM" file extension. 519 o The mail command enters the VMS MAIL subsystem; the dir command 520 here lists waiting mail. 521 o Ping checks the status of another host. 523 When finished, the logout command logs the user off the remote host; 524 TELNET automatically closes the connection to the remote host and 525 returns control to the local system. 527 It is important to note that TELNET is a very powerful tool, one that 528 may provide users with access to many Internet utilities and services 529 that might not be otherwise available. Many of these features are 530 accessed by specifying a port number with the TELNET command, in 531 addition to a host's address, and knowledge of port numbers provides 532 another mechanism for users to access information with Telnet. 534 This guide discusses several TCP/IP and Internet utilities that 535 require local client software, such as Finger, Whois, Archie, and 536 Gopher. But what if your software does not include a needed client? 537 In some cases, Telnet may be used to access a remote client and 538 provide the same functionality. 540 This is done by specifying a port number with the TELNET command. 541 Just as TCP/IP hosts have a unique IP address, applications on the 542 host are associated with an address, called a port. Finger (see 543 Section 3.3 above), for example, is associated with the well-known 544 port number 79. In the absence of a Finger client, TELNETing to port 545 79 at a remote host may provide the same information. You can finger 546 another host with TELNET by using a command like: 548 telnet 79 550 Other well-known TCP port numbers include 25 (Simple Mail Transfer 551 Protocol), 43 (whois), 80 (Hypertext Transfer Protocol), and 119 552 (Network News Transfer Protocol). 554 Some services are available on the Internet using TELNET and special 555 port numbers. A geographical information database, for example, may 556 be accessed by TELNETing to port 3000 at host martini.eecs.umich.edu 557 and current weather information is available at port 3000 at host 558 downwind.sprl.umich.edu. 560 ==================================================================== 561 ** C:\> telnet smcvax.smcvt.edu 562 FTP Software PC/TCP tn 3.10 01/24/95 02:40 563 Copyright (c) 1986-1995 by FTP Software, Inc. All rights reserved 565 - Connected to St. Michael's College - 567 ** Username: kumquat 568 ** Password: 570 St. Michael's College VAX/VMS System. 571 Node SMCVAX. 573 Last interactive login on Monday, 16-SEP-1996 15:47 574 Last non-interactive login on Wednesday, 6-MAR-1996 08:19 576 You have 1 new Mail message. 578 Good Afternoon User KUMQUAT. Logged in on 17-SEP-1996 at 1:10 PM. 580 User [GUEST,KUMQUAT] has 3225 blocks used, 6775 available, 581 of 10000 authorized and permitted overdraft of 100 blocks on $1$DIA2 583 To see a complete list of news items, type: NEWS DIR 584 To read a particular item, type NEWS followed by 585 the name of the item you wish to read. 587 ** SMCVAX$ dir *.com 588 Directory $1$DIA2:[GUEST.KUMQUAT] 589 BACKUP.COM;24 24 16-JUL-1990 16:22:46.68 (RWED,RWED,RE,) 590 DELTREE.COM;17 3 16-JUL-1990 16:22:47.58 (RWED,RWED,RE,) 591 EXPANDZ.COM;7 2 22-FEB-1993 10:00:04.35 (RWED,RWED,RE,) 592 FTSLOGBLD.COM;3 1 16-JUL-1990 16:22:48.57 (RWED,RWED,RE,) 593 FTSRRR.COM;2 1 16-JUL-1990 16:22:48.73 (RWED,RWED,RE,) 594 LOGIN.COM;116 5 1-DEC-1993 09:33:21.61 (RWED,RWED,RE,) 595 SNOOPY.COM;6 1 16-JUL-1990 16:22:52.06 (RWED,RWED,RE,) 596 SYLOGIN.COM;83 8 16-JUL-1990 16:22:52.88 (RWED,RWED,RE,RE) 597 SYSTARTUP.COM;88 15 16-JUL-1990 16:22:53.21 (RWED,RWED,RE,) 598 WATCH_MAIL.COM;1 173 10-MAY-1994 09:59:52.65 (RWED,RWED,RE,) 599 Total of 10 files, 233 blocks. 601 ** SMCVAX$ mail 602 You have 1 new message. 603 ** MAIL> dir 604 NEWMAIL 605 # From Date Subject 606 1 IN%"ibug@plainfield. 25-SEP-1996 ANNOUNCE: Burlington WWW 607 Conference 608 ** MAIL> exit 610 ** SMCVAX$ ping kestrel.hill.com /n=5 611 PING HILL.COM (199.182.20.24): 56 data bytes 612 64 bytes from 199.182.20.24: icmp_seq=0 time=290 ms 613 64 bytes from 199.182.20.24: icmp_seq=1 time=260 ms 614 64 bytes from 199.182.20.24: icmp_seq=2 time=260 ms 615 64 bytes from 199.182.20.24: icmp_seq=3 time=260 ms 616 64 bytes from 199.182.20.24: icmp_seq=4 time=260 ms 618 ----KESTREL.HILL.COM PING Statistics---- 619 5 packets transmitted, 5 packets received, 0% packet loss 620 round-trip (ms) min/avg/max = 260/266/290 622 ** SMCVAX$ logout 623 KUMQUAT logged out at 12-JUN-1994 15:37:04.29 625 Connection #0 closed 626 C:\> 627 ==================================================================== 629 4.2. FTP 631 FTP [16] is one of the most useful and powerful TCP/IP utilities for 632 the general user. FTP allows users to upload and download files 633 between local and remote hosts. Anonymous FTP, in particular, is 634 commonly available at file archive sites to allow users to access 635 files without having to pre-establish an account at the remote host. 636 TELNET might, in fact, be used for this purpose but TELNET gives the 637 user complete access to the remote system; FTP limits the user to 638 file transfer activities. 640 The general form of the FTP command is: 642 ftp [|] 644 An FTP session can be initiated in several ways. In the example shown 645 below, an FTP control connection is initiated to a host (the Defense 646 Data Network's Network Information Center) by supplying a host name 647 with the FTP command; optionally, the host's IP address in dotted 648 decimal (numeric) form could be used. If neither host name nor IP 649 address are supplied in the command line, a connection to a host can 650 be initiated by typing open host_name or open IP_address once the FTP 651 application has been started. 653 The remote host will ask for a username and password. If a bona fide 654 registered user of this host supplies a valid username and password, 655 then the user will have access to any files and directories to which 656 this username has privilege. For anonymous FTP access, the username 657 anonymous is used. Historically, the password for the anonymous user 658 (not shown in actual use) has been guest, although most systems today 659 ask for the user's Internet e-mail address (and several sites attempt 660 to verify that packets are coming from that address before allowing 661 the user to login). 663 The help ? command may be used to obtain a list of FTP commands and 664 help topics available with your software; although not always shown, 665 nearly all TCP/IP applications have a help command. An example of the 666 help for FTP's type command is shown in the sample dialogue. This 667 command is very important one, by the way; if transferring a binary 668 or executable file, be sure to set the type to image (or binary on 669 some systems). 671 The dir command provides a directory listing of the files in the 672 current directory at the remote host; the UNIX ls command may also 673 usually be used. Note that an FTP data transfer connection is 674 established for the transfer of the directory information to the 675 local host. The output from the dir command will show a file listing 676 that is consistent with the native operating system of the remote 677 host. Although the TCP/IP suite is often associated with UNIX, it can 678 (and does) run with nearly all common operating systems. The 679 directory information shown in the sample dialogue happens to be in 680 UNIX format and includes the following information: 682 o File attributes. The first character identifies the type of file 683 entry as a directory (d), link or symbolic name (l), or individual 684 file (-). The next nine characters are the file access permissions 685 list; the first three characters are for the owner, the next three 686 for the owner's group, and the last three for all other users. 687 Three access privileges may be assigned to each file for each of 688 these groups: read (r), write (w), and execute (x). 690 o Number of entries, or hard links, in this structure. This value 691 will be a "1" if the entry refers to a file or link, or will be the 692 number of files in the listed directory. 694 o File owner 696 o File owner's group. 698 o File size, in bytes. 700 o Date and time of last modification. If the date is followed by a 701 timestamp, then the date is from the current year. 703 o File name. 705 After the directory information has been transferred, FTP closes the 706 data transfer connection. 708 The command cd is used to change to another working directory, in 709 this case the rfc directory (note that file and directory names may 710 be case-sensitive). As in DOS, cd .. will change to the parent of the 711 current directory. The CWD command successful is the only indication 712 that the user's cd command was correctly executed; the show-directory 713 (may be truncated to fewer characters, as shown) command, if 714 available, may be used to see which working directory you are in. 716 Another dir command is used to find all files with the name 717 rfc173*.txt; note the use of the * wildcard character. We can now 718 copy (download) the file of choice (RFC 1739 is the previous version 719 of this primer) by using the get (or receive) command, which has the 720 following general format: 722 get 724 FTP opens another data transfer connection for this file transfer 725 purpose; note that the effective data transfer rate is 93.664 kbps. 727 FTP's put (or send) command allows uploading from the local host to 728 the remote. Put is often not available when using anonymous FTP. 730 Finally, we terminate the FTP connection by using the close command. 731 The user can initiate another FTP connection using the open command 732 or can leave FTP by issuing a quit command. Quit can also be used to 733 close a connection and terminate a session. 735 TECHNICAL NOTE: It is important to note that different FTP packages 736 have different commands available and even those with similar names 737 may act differently. In the example shown here (using MultiNet for 738 VMS), the show command will display the current working directory; in 739 FTP Software's OnNet), show will display a file from the remote host 740 at the local host. Some packages have nothing equivalent to either of 741 these commands. 743 ==================================================================== 744 ** SMCVAX$ ftp nic.ddn.mil 745 SMCVAX.SMCVT.EDU MultiNet FTP user process 3.4(111) 746 Connection opened (Assuming 8-bit connections) 747 <*****Welcome to the DOD Network Information Center***** 748 < *****Login with username "anonymous" and password "guest" 749 ** Username: anonymous 750 help type 756 TYPE 757 Set the transfer type to type. 759 Format 760 TYPE type 762 Additional information available: 763 Parameters Example Restrictions 765 ** TYPE Subtopic? parameters 766 TYPE 767 Parameters 769 type 771 Specify a value of ASCII, BACKUP, BINARY, IMAGE or 772 LOGICAL-BYTE. 774 Use TYPE ASCII (the default) for transferring text files. 776 Use TYPE BACKUP to set the transfer type to IMAGE and write 777 the 778 local file with 2048-byte fixed length records. Use this 779 command 780 to transfer VAX/VMS BACKUP save sets. 782 Use TYPE BINARY to transfer binary files (same as TYPE IMAGE). 784 Use TYPE IMAGE to transfer binary files (for example, .EXE). 786 Use TYPE LOGICAL-BYTE to transfer binary files to or from a 787 TOPS-20 machine. 789 ** TYPE Subtopic? 790 ** Topic? 792 ** NIC.DDN.MIL> dir 793 rfc 804 drwxr-xr-x 2 nic 10 1024 Sep 16 23:00 gosip 805 drwxr-xr-x 2 nic 1 512 Mar 19 1996 home 806 drwxr-xr-x 2 nic 1 512 Mar 19 1996 lost+found 807 lrwxrwxrwx 1 nic 1 8 Mar 19 1996 mgt -> ddn-news 808 drwxr-xr-x 2 nic 1 1024 Sep 13 12:11 netinfo 809 drwxr-xr-x 4 nic 1 512 May 3 23:00 netprog 810 drwxr-xr-x 2 nic 1 1024 Mar 19 1996 protocols 811 drwxr-xr-x 2 nic 1 512 Mar 19 1996 pub 812 drwxr-xr-x 3 140 10 512 Aug 27 21:03 registrar 813 drwxr-xr-x 2 nic 1 29696 Sep 16 23:00 rfc 814 drwxr-xr-x 2 nic 1 5632 Sep 9 23:00 scc 815 drwxr-xr-x 2 nic 1 1536 Sep 16 23:00 std 816 drwxr-xr-x 2 nic 1 1024 Sep 16 23:00 templates 817 drwxr-xr-x 3 nic 1 512 Mar 19 1996 usr 818 cd rfc 823 show 826 <"/rfc" is current directory. 828 ** NIC.DDN.MIL> dir rfc173*.txt 829 get rfc1739.txt primer.txt 845 quit 851 nicname hill.com 907 [198.41.0.5] 908 Hill Associates (HILL-DOM) 909 17 Roosevelt Hwy. 910 Colchester, Vermont 05446 911 US 913 Domain Name: HILL.COM 915 Administrative Contact: 916 Kessler, Gary C. (GK34) g.kessler@HILL.COM 917 802-655-0940 918 Technical Contact, Zone Contact: 919 Monaghan, Carol A. (CAM4) c.monaghan@HILL.COM 920 802-655-0940 921 Billing Contact: 922 Parry, Amy (AP1257) a.parry@HILL.COM 923 802-655-0940 925 Record last updated on 11-Jun-96. 926 Record created on 11-Jan-93. 928 Domain servers in listed order: 930 SYRUP.HILL.COM 199.182.20.3 931 NS1.NOC.NETCOM.NET 204.31.1.1 933 ** C:\> telnet rs.internic.net 934 SunOS UNIX 4.1 (rs1) (ttypb) 936 *********************************************************************** 937 * -- InterNIC Registration Services Center -- 938 * 939 * For wais, type: WAIS 940 * For the *original* whois type: WHOIS [search string] 941 * For referral whois type: RWHOIS [search string] 942 * 944 ********************************************************************** 945 Please be advised that use constitutes consent to monitoring 946 (Elec Comm Priv Act, 18 USC 2701-2711) 948 ** [vt220] InterNIC > whois 949 InterNIC WHOIS Version: 1.2 Wed, 18 Sep 96 09:49:50 951 ** Whois: 199.182.20.0 952 Hill Associates (NET-HILLASSC) 953 17 Roosevelt Highway 954 Colchester, VT 05446 956 Netname: HILLASSC 957 Netnumber: 199.182.20.0 959 Coordinator: 960 Monaghan, Carol A. (CAM4) c.monaghan@HILL.COM 961 802-655-0940 963 Record last updated on 17-May-94. 965 ** Whois: com-dom 966 Commercial top-level domain (COM-DOM) 967 Network Solutions, Inc. 968 505 Huntmar park Dr. 969 Herndon, VA 22070 971 Domain Name: COM 973 Administrative Contact, Technical Contact, Zone Contact: 974 Network Solutions, Inc. (HOSTMASTER) hostmaster@INTERNIC.NET 975 (703) 742-4777 (FAX) (703) 742-4811 977 Record last updated on 02-Sep-94. 978 Record created on 01-Jan-85. 980 Domain servers in listed order: 982 A.ROOT-SERVERS.NET 198.41.0.4 983 H.ROOT-SERVERS.NET 128.63.2.53 984 B.ROOT-SERVERS.NET 128.9.0.107 985 C.ROOT-SERVERS.NET 192.33.4.12 986 D.ROOT-SERVERS.NET 128.8.10.90 987 E.ROOT-SERVERS.NET 192.203.230.10 988 I.ROOT-SERVERS.NET 192.36.148.17 989 F.ROOT-SERVERS.NET 192.5.5.241 990 G.ROOT-SERVERS.NET 192.112.36.4 992 ** Would you like to see the known domains under this top-level domain? 993 n 995 ** Whois: exit 997 ** [vt220] InterNIC > quit 999 Wed Sep 18 09:50:29 1996 EST 1001 Connection #0 closed 1002 C:\> 1003 ==================================================================== 1005 5.2. KNOWBOT 1007 KNOWBOT is an automated username database search tool that is related 1008 to WHOIS. The Knowbot Information Service (KIS), operated by the 1009 Corporation for National Research Initiatives (CNRI) in Reston, 1010 Virginia, provides a simple WHOIS-like interface that allows users to 1011 query several Internet user databases (White Pages services) all at 1012 one time. A single KIS query will automatically search the InterNIC, 1013 MILNET, MCImail, and PSI White Pages Pilot Project; other databases 1014 may also be included. 1016 KNOWBOT may be accessed by TELNETing to host info.cnri.reston.va.us. 1017 The help command will supply sufficient information to get started. 1018 The sample dialogue below shows use of the query command to locate a 1019 user named "Steven Shepard"; this command automatically starts a 1020 search through the default set of Internet databases. 1022 ==================================================================== 1023 ** C:\> telnet info.cnri.reston.va.us 1025 Knowbot Information Service 1026 KIS Client (V2.0). Copyright CNRI 1990. All Rights Reserved. 1028 KIS searches various Internet directory services 1029 to find someone's street address, email address and phone number. 1031 Type 'man' at the prompt for a complete reference with examples. 1032 Type 'help' for a quick reference to commands. 1033 Type 'news' for information about recent changes. 1035 Please enter your email address in our guest book... 1036 ** (Your email address?) > s.shepard@hill.com 1038 ** > query shepard, steven 1039 Trying whois at ds.internic.net... 1040 The ds.internic.net whois server is being queried: 1041 Nothing returned. 1043 The rs.internic.net whois server is being queried: 1045 Shepard, Steven (SS2192) 1046 708-810-5215 1047 Shepard, Steven (SS1302) axisteven@AOL.COM (954) 1048 974-4569 1050 The nic.ddn.mil whois server is being queried: 1052 Shepard, Steven (SS2192) 1053 R.R. Donnelley & Sons 1054 750 Warrenville Road 1055 Lisle, IL 60532 1056 Trying mcimail at cnri.reston.va.us... 1057 Trying ripe at whois.ripe.net... 1058 Trying whois at whois.lac.net... 1059 No match found for .SHEPARD,STEVEN 1061 ** > quit 1062 KIS exiting 1063 Connection #0 closed 1064 C:\> 1065 ==================================================================== 1067 6. Information Servers 1069 File transfer, remote login, and electronic mail remained the primary 1070 applications of the ARPANET/Internet until the early 1990s. But as 1071 the Internet user population shifted from hard-core computer 1072 researchers and academics to more casual users, easier-to-use tools 1073 were needed for the Net to become accepted as a useful resource. That 1074 means making things easier to find. This section will discuss some of 1075 the early tools that made it easier to locate and access information 1076 on the Internet. 1078 6.1. Archie 1080 Archie, developed in 1992 at the Computer Science Department at 1081 McGill University in Montreal, allows users to find software, data, 1082 and other information files that reside at anonymous FTP archive 1083 sites; the name of the program, reportedly, is derived from the word 1084 "archive" and not from the comic book character. Archie tracks the 1085 contents of several thousand anonymous FTP sites containing millions 1086 of files. The archie server automatically updates the information 1087 from each registered site about once a month, providing relatively 1088 up-to-date information without unduly stressing the network. Archie, 1089 however, is not as popular as it once was and many sites have not 1090 updated their information; as the examples below show, many of the 1091 catalog listings are several years old. 1093 Before using archie, you must identify a server address. The sites 1094 below all support archie; most (but not all) archie sites support the 1095 servers command which lists all known archie servers. Due to the 1096 popularity of archie at some sites and its high processing demands, 1097 many sites limit access to non-peak hours and/or limit the number of 1098 simultaneous archie users. Available archie sites include: 1100 archie.au archie.rediris.es 1101 archie.edvz.uni-linz.ac.at archie.luth.se 1102 archie.univie.ac.at archie.switch.ch 1103 archie.uqam.ca archie.ncu.edu.tw 1104 archie.funet.fi archie.doc.ic.ac.uk 1105 archie.th-darmstadt.de archie.unl.edu 1106 archie.ac.il archie.internic.net 1107 archie.unipi.it archie.rutgers.edu 1108 archie.wide.ad.jp archie.ans.net 1109 archie.kr archie.sura.net 1110 archie.sogang.ac.kr 1112 All archie sites can be accessed using archie client software. Some 1113 archie servers may be accessed using TELNET; when TELNETing to an 1114 archie site, login as archie (you must use lower case) and hit 1115 if a password is requested. 1117 Once connected, the help command assists users in obtaining more 1118 information about using archie. Two more useful archie commands are 1119 prog, used to search for files in the database, and whatis, which 1120 searches for keywords in the program descriptions. 1122 In the accompanying dialogue, the set maxhits command is used to 1123 limit the number of responses to any following prog commands; if this 1124 is not done, the user may get an enormous amount of information. In 1125 this example, the user issues a request to find entries related to 1126 "dilbert"; armed with this information, a user can use anonymous FTP 1127 to examine these directories and files. 1129 The next request is for files with "tcp/ip" as a keyword descriptor. 1130 These responses can be used for subsequent prog commands. 1132 Exit archie using the exit command. At this point, TELNET closes the 1133 connection and control returns to the local host. 1135 Additional information about archie can be obtained by sending e-mail 1136 to Bunyip Information Systems (archie-info@bunyip.com). Client 1137 software is not required to use archie, but can make life a little 1138 easier; some such software can be downloaded using anonymous FTP from 1139 the /pub/archie/clients/ directory at ftp.sura.net (note that the 1140 newest program in this directory is dated June 1994). Most shareware 1141 and commercial archie clients hide the complexity described in this 1142 section; users usually connect to a pre-configured archie server 1143 merely by typing an archie command line. 1145 ==================================================================== 1146 ** C:\> telnet archie.unl.edu 1147 SunOS UNIX (crcnis2) 1149 ** login: archie 1150 ** Password: 1152 Welcome to the ARCHIE server at the University of Nebraska - Lincoln 1154 # Bunyip Information Systems, 1993 1156 ** unl-archie> help 1157 These are the commands you can use in help: 1159 . go up one level in the hierarchy 1161 ? display a list of valid subtopics at the current level 1163 1164 done, ^D, ^C quit from help entirely 1166 help on a topic or subtopic 1167 Eg. 1168 "help show" 1170 will give you the help screen for the "show" command 1172 "help set search" 1174 Will give you the help information for the "search" variable. 1176 The command "manpage" will give you a complete copy of the archie 1177 manual page. 1178 ** help> done 1180 ** unl-archie> set maxhits 5 1182 ** unl-archie> prog dilbert 1183 # Search type: sub. 1184 # Your queue position: 2 1185 # Estimated time for completion: 00:20 1187 Host ftp.wustl.edu (128.252.135.4) 1188 Last updated 10:08 25 Dec 1993 1190 Location: /multimedia/images/gif/unindexed/931118 1191 FILE -rw-r--r-- 9747 bytes 19:18 17 Nov 1993 1192 dilbert.gif 1194 ** unl-archie> whatis tcp/ip 1195 RFC 1065 McCloghrie, K.; Rose, M.T. 1196 Structure and identification of management information for 1197 TCP/IP-based 1198 internets. 1988 August; 21 p. (Obsoleted by RFC 1155) 1199 RFC 1066 McCloghrie, K.; Rose, M.T. 1200 Management Information Base for network management of TCP/IP-based 1201 internets. 1988 August; 90 p. (Obsoleted by RFC 1156) 1202 RFC 1085 Rose, M.T. ISO presentation 1203 services on top of TCP/IP based internets. 1988 December; 32 p. 1204 RFC 1095 Warrier, U.S.; Besaw, L. 1205 Common 1206 Management Information Services and Protocol over TCP/IP (CMOT). 1989 1207 April; 67 p. (Obsoleted by RFC 1189) 1208 RFC 1144 Jacobson, V. Compressing 1209 TCP/IP 1210 headers for low-speed serial links. 1990 February; 43 p. 1211 RFC 1147 Stine, R.H.,ed. FYI on a 1212 network management tool catalog: Tools for monitoring and debugging 1213 TCP/IP internets and interconnected devices. 1990 April; 126 p. (Also 1214 FYI 2) 1215 RFC 1155 Rose, M.T.; McCloghrie, K. 1216 Structure and identification of management information for 1217 TCP/IP-based 1218 internets. 1990 May; 22 p. (Obsoletes RFC 1065) 1219 RFC 1156 McCloghrie, K.; Rose, M.T. 1220 Management Information Base for network management of TCP/IP-based 1221 internets. 1990 May; 91 p. (Obsoletes RFC 1066) 1222 RFC 1158 Rose, M.T.,ed. Management 1223 Information Base for network management of TCP/IP-based internets: 1224 MIB-II. 1990 May; 133 p. 1225 RFC 1180 Socolofsky, T.J.; Kale, C.J. 1226 TCP/IP tutorial. 1991 January; 28 p. 1227 RFC 1195 Callon, R.W. Use of OSI IS-IS 1228 for routing in TCP/IP and dual environments. 1990 December; 65 p. 1229 RFC 1213 McCloghrie, K.; Rose, 1230 M.T.,eds. Management Information Base for network management of 1231 TCP/IP-based 1232 internets:MIB-II. 1991 March; 70 p. (Obsoletes RFC 1158) 1233 log_tcp Package to monitor tcp/ip connections 1234 ping PD version of the ping(1) command. Send 1235 ICMP 1236 ECHO requests to a host on the network (TCP/IP) to see whether it's 1237 reachable or not 1239 ** unl-archie> exit 1240 # Bye. 1242 Connection #0 closed 1244 C:\> 1245 ==================================================================== 1247 6.2. Gopher 1249 The Internet Gopher protocol was developed at the University of 1250 Minnesota's Microcomputer Center in 1991, as a distributed 1251 information search and retrieval tool for the Internet. Gopher is 1252 described in RFC 1436 [1]; the name derives from the University's 1253 mascot. 1255 Gopher provides a tool so that publicly available information at a 1256 host can be organized in a hierarchical fashion using simple text 1257 descriptions, allowing files to be perused using a simple menu 1258 system. Gopher also allows a user to view a file on demand without 1259 requiring additional file transfer protocols. In addition, Gopher 1260 introduced the capability of linking sites on the Internet, so that 1261 each Gopher site can be used as a stepping stone to access other 1262 sites and reducing the amount of duplicate information and effort on 1263 the network. 1265 Any Gopher site can be accessed using Gopher client software (or a 1266 WWW browser). In many cases, users can access Gopher by TELNETing to 1267 a valid Gopher location; if the site provides a remote Gopher client, 1268 the user will see a text-based, menu interface. The number of Gopher 1269 sites grew rapidly between 1991 and 1994, although growth tapered due 1270 to the introduction of the Web; in any case, most Gopher sites have a 1271 menu item that will allow you to identify other Gopher sites. If 1272 using TELNET, login with the username gopher (this must be in 1273 lowercase); no password is required. 1275 In the sample dialogue below, the user attaches to the Gopher server 1276 at the Internet Network Information Center (InterNIC) by TELNETing to 1277 ds.internic.net. With the menu interface shown here, the user merely 1278 follows the prompts. Initially, the main menu will appear. Selecting 1279 item 3 causes Gopher to seize and display the "InterNIC Registration 1280 Services (NSI)" menu; move to the desired menu item by typing the 1281 item number or by moving the pointer (-->) down to the desired entry 1282 using the DOWN-ARROW key on the keyboard, and then hitting ENTER. To 1283 quit the program at any time, press q (quit); ? and u will provide 1284 help or go back up to the previous menu, respectively. Users may also 1285 search for strings within files using the / command or download the 1286 file being interrogated using the D command. 1288 Menu item 1 within the first submenu (selected in the dialogue shown 1289 here) is titled "InterNIC Registration Archives." As its submenu 1290 implies, this is a place to obtain files containing the InterNIC's 1291 domain registration policies, domain data, registration forms, and 1292 other information related to registering names and domains on the 1293 Internet. 1295 ==================================================================== 1296 ** SMCVAX$ telnet ds.internic.net 1298 UNIX(r) System V Release 4.0 (ds2) 1300 ** login: gopher 1302 ******************************************************************** 1303 Welcome to the InterNIC Directory and Database Server. 1304 ******************************************************************** 1306 Internet Gopher Information Client v2.1.3 1307 Home Gopher server: localhost 1309 --> 1. About InterNIC Directory and Database Services/ 1310 2. InterNIC Directory and Database Services (AT&T)/ 1311 3. InterNIC Registration Services (NSI)/ 1312 4. README 1314 Press ? for Help, q to Quit Page: 1315 1/1 1316 ** View item number: 3 1318 Internet Gopher Information Client v2.1.3 1319 InterNIC Registration Services (NSI) 1321 --> 1. InterNIC Registration Archives/ 1322 2. Whois Searches (InterNIC IP, ASN, DNS, and POC Registry) 1323 1325 Press ? for Help, q to Quit, u to go up a menu Page: 1326 1/1 1327 ** View item number: 1 1329 Internet Gopher Information Client v2.1.3 1330 InterNIC Registration Archives 1332 --> 1. archives/ 1333 2. domain/ 1334 3. netinfo/ 1335 4. netprog/ 1336 5. policy/ 1337 6. pub/ 1338 7. templates/ 1340 Press ? for Help, q to Quit, u to go up a menu Page: 1341 1/1 1342 ** q 1343 ** Really quit (y/n) ? y 1345 Connection closed by Foreign Host 1346 SMCVAX$ 1347 ==================================================================== 1349 6.3. VERONICA, JUGHEAD, and WAIS 1351 The problem with being blessed with so much information from FTP, 1352 archie, Gopher, and other sources is exactly that - too much 1353 information. To make it easier for users to locate the system on 1354 which their desired information resides, a number of other tools have 1355 been created. 1357 VERONICA (Very Easy Rodent-Oriented Net-wide Index to Computerized 1358 Archives) was developed at the University of Nevada at Reno as an 1359 archie-like adjunct to Gopher. As the number of Gopher sites quickly 1360 grew after its introduction, it became increasingly harder to find 1361 information in gopherspace since Gopher was designed to search a 1362 single database at a time. VERONICA maintains an index of titles of 1363 Gopher items and performs a keyword search on all of the Gopher sites 1364 that it has knowledge of and access to, obviating the need for the 1365 user to perform a menu-by-menu, site-by-site search for information. 1366 When a user selects an item from the menu of a VERONICA search, 1367 "sessions" are automatically established with the appropriate Gopher 1368 servers, and a list of data items is returned to the originating 1369 Gopher client in the form of a Gopher menu so that the user can 1370 access the files. VERONICA is available as an option on many Gopher 1371 servers. 1373 Another Gopher-adjunct is JUGHEAD (Jonzy's Universal Gopher Hierarchy 1374 Excavation And Display). JUGHEAD supports key word searches and the 1375 use of logical operators (AND, OR, and NOT). The result of a JUGHEAD 1376 search is a display of all menu items which match the search string 1377 which are located in the University of Manchester and UMIST 1378 Information Server, working from a static database that is re-created 1379 every day. JUGHEAD is available from many Gopher sites, although 1380 VERONICA may be a better tool for global searches. 1382 The Wide Area Information Server (WAIS, pronounced "ways") was 1383 initiated jointly by Apple Computer, Dow Jones, KMPG Peat Marwick, 1384 and Thinking Machines Corp. It is a set of free-ware, share-ware, and 1385 commercial software products for a wide variety of hardware/software 1386 platforms, which work together to help users find information on the 1387 Internet. WAIS provides a single interface through which a user can 1388 access many different information databases. The user interface allow 1389 a query to be formulated in English and the WAIS server will 1390 automatically choose the appropriate databases to search. Further 1391 information about WAIS can be obtained by reading the WAIS FAQ, from 1392 host rtfm.mit.edu in file /pub/usenet/news.answers/wais-faq. 1394 7. The World Wide Web 1396 The World Wide Web (WWW) is thought (erroneously) by many to be the 1397 same thing as the Internet. But the confusion, in many ways, is 1398 justified; as of early 1996, the WWW accounted for over 40% of all of 1399 the traffic on the Internet. In addition, the number of hosts on the 1400 Internet named www has grown from several hundred in mid-1994 to 1401 17,000 in mid-1995 to 212,000 in mid-1996; and not all WWW servers 1402 are named www. The Web has made information on the Internet 1403 accessible to users of all ages and computer skill levels. It has 1404 provided a mechanism so that nearly anyone can become a content 1405 provider. According to some, growth in the number of WWW users is 1406 unparalleled by any other event in human history. 1408 The WWW was developed in the early 1990s at the CERN Institute for 1409 Particle Physics in Geneva, Switzerland. The Web was designed to 1410 combine aspects of information retrieval with multimedia 1411 communications, unlike archie and Gopher, which were primarily used 1412 for the indexing of text-based files. The Web allows users to access 1413 information in many different types of formats, including text, 1414 sound, image, animation, and video. WWW treats all searchable 1415 Internet files as hypertext documents. Hypertext is a term which 1416 merely refers to text that contains pointers to other text, allowing 1417 a user reading one document to jump to another document for more 1418 information on a given topic, and then return to the same location in 1419 the original document. WWW hypermedia documents are able to employ 1420 images, sound, graphics, video, and animations in addition to text. 1422 To access WWW servers, users must run client software called a 1423 browser. The browser and server use the Hypertext Transfer Protocol 1424 (HTTP) [cc]. WWW documents are written in the Hypertext Markup 1425 Language (HTML) [dd, ee], a simple text-based formatting language 1426 that is hardware and software platform-independent. Users point the 1427 browser at some location using a shorthand format called a Uniform 1428 Resource Locator (URL), which allows a WWW servers to obtain files 1429 from any location on the public Internet using a variety of 1430 protocols, including HTTP, FTP, Gopher, and TELNET. 1432 Mosaic, developed in 1994 at the National Center for Supercomputer 1433 Applications (NCSA) at the University of Illinois at Urbana- 1434 Champaign, was the first widely-used browser. Because it was 1435 available at no cost over the Internet via anonymous FTP, and had a 1436 version for Windows, Mac, and UNIX systems, Mosaic was probably the 1437 single reason that the Web attracted so many users so quickly. The 1438 most commonly used browsers today include the Netscape Navigator 1439 (http://www.netscape.com), Microsoft's Internet Explorer 1440 (http://www.microsoft.com), and NCSA Mosaic 1441 (http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/). 1443 The WWW is ideally suited to a windows environment, or other point- 1444 and-click graphical user interface. Nevertheless, several text-based 1445 Web browsers do exist, although their usefulness is limited if trying 1446 to obtain graphical images, or audio or video clips. One text-based 1447 Web browser is Lynx, and an example of its use is shown below. Items 1448 in square brackets in the sample dialogue are Lynx's way of 1449 indicating an image or other display that cannot be shown on an ASCII 1450 terminal. 1452 ==================================================================== 1453 ** gck@zoo.uvm.edu> lynx www.hill.com 1454 Getting http://www.hill.com/ 1455 Looking up www.hill.com. 1456 Making HTTP connection to www.hill.com.Sending HTTP request. 1457 HTTP request sent; waiting for response.Read 176 bytes of data. 1458 512 of 2502 bytes of data. 1459 1024 of 2502 bytes of data. 1460 536 1461 2048 1462 502 1463 Data transfer complete 1465 Hill Associates 1467 [INLINE] Hill Associates, Inc. 1469 Leaders in Telecommunications Training and Education Worldwide 1470 _________________________________________________________________ 1472 Hill Associates is an international provider of voice and data 1473 telecommunications training and education. We cover the full breadth 1474 of the field, including telephony, computer networks, ISDN, X.25 and 1475 fast packet technologies (frame relay, SMDS, ATM), wireless, TCP/IP 1476 and the Internet, LANs and LAN interconnection, legacy networks, 1477 multimedia and virtual reality, broadband services, regulation, 1478 service strategies, and network security. 1480 Hill Associates' products and services include instructor-led, 1481 computer-based (CBT), and hands-on workshop courses. Courseware 1482 distribution media include audio tape, video tape, CD-ROM, and 3.5" 1483 disks (PC). 1484 _________________________________________________________________ 1486 Hill Associates products, services, and corporate information 1488 * About Hill Associates 1489 * HAI Products and Services Catalog 1490 * Datacomm/2000-ED Series 1491 * HAI Personnel Home Pages 1492 * Contacting Hill Associates 1493 * Employment Opportunities 1495 On-line information resources from Hill Associates 1497 * HAI Telecommunications Acronym List 1498 * "A Tour of TCP/IP and the Internet" (HTML Presentation) 1499 * GCK's Miscellaneous Sites List... 1500 * "Commerce on the Internet: A Technology Update" (HTML Presentation) 1501 * Articles and Papers by HAI Staff 1503 Hill Associates is host to the: 1505 * IEEE Local Computer Networks Conference Home Page... 1506 * Town of Colchester (Vermont) Home Page (Still under development 1507 with the Colchester schools, but you're welcome to browse...) 1508 * Vermont Telecommunications Resource Center 1509 ________________________________________________________________ 1511 Please send any comments or suggestions to the HAI Webmaster. Come 1512 back again soon! 1514 Information at this site (c) 1994, 1995, 1996 Hill Associates. 1516 Arrow keys: Up and Down to move. Right to follow a link; Left to go 1517 back. 1518 H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search 1519 [delete]=history list 1521 ** G 1522 ** URL to open: http://www.bbn.com 1523 Getting http://www.bbn.com/ 1524 Looking up www.bbn.com. 1525 Making HTTP connection to www.bbn.com.Sending HTTP request. 1526 HTTP request sent; waiting for response.Read 119 bytes of data. 1527 500 1528 1000 bytes of data. 1529 2 1530 5 1531 925 1532 Data transfer complete 1534 BBN On The World Wide Web 1536 [LINK] 1537 BBN Reports Fourth-Quarter and Year-End 1996 Results 1539 [INLINE] 1540 [ISMAP] 1541 [ISMAP] 1542 [LINK] 1543 [INLINE] 1545 Who Won Our Sweepstakes 1546 How The Noc Solves Problems 1547 Noc Noc Who's There 1548 BBN Planet Network Map 1550 [LINK][LINK][LINK][LINK][LINK][LINK] 1551 [LINK] 1552 Contact BBN Planet 1553 Directions to BBN 1554 Text only index of the BBN Web site 1555 | 1556 Corporate Disclaimer 1557 Send questions and comments about our site to Webmaster@bbn.com 1558 (c) 1996 BBN Corporation 1560 Arrow keys: Up and Down to move. Right to follow a link; Left to go 1561 back. 1562 H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search 1563 [delete]=history list 1564 ** Q 1566 gck@zoo.uvm.edu> 1567 ==================================================================== 1569 7.1. Uniform Resource Locator Format 1571 As more and more protocols have become available to identify files, 1572 archive and server sites, news lists, and other information resources 1573 on the Internet, it was inevitable that some shorthand would arise to 1574 make it easier to designate these sources. The common shorthand 1575 format is called the Uniform Resource Locator. The list below 1576 provides information on how the URL format should be interpreted for 1577 the protocols and resources that will be discussed in this document. 1578 A complete description of the URL format may be found in [2]. 1580 file:// 1581 Identifies a specific file. E.g., the file htmlasst in the edu 1582 directory at host ftp.cs.da would be denoted, using the full URL 1583 form: . 1585 ftp:// 1586 Identifies an FTP site. E.g.: 1587 ftp://ftp.eff.org/pub/EFF/Policy/Crypto/*. 1589 gopher:// 1590 Identifies a Gopher site and menu path; a "00" at the start of the 1591 path indicates a directory and "11" indicates a file. E.g.: 1592 gopher://info.umd.edu:901/00/info/Government/Factbook92. 1594 http:// 1595 Identifies a WWW server location. E.g.: 1596 http://info.isoc.org/home.html. 1598 mailto: 1599 Identifies an individual's Internet mail address. E.g.: 1600 mailto:s.shepard@hill.com. 1602 telnet:// 1603 Identifies a TELNET location (the trailing "/" is optional). E.g.: 1604 telnet://envnet:henniker@envnet.gsfc.nasa.gov. 1606 7.2. User Directories on the Web 1608 While finding users on the Internet remains somewhat like alchemy if 1609 using the tools and utilities mentioned earlier, the Web has added a 1610 new dimension to finding people. Since 1995, many telephone companies 1611 have placed national white and yellow page telephone directories on- 1612 line, accessible via the World Wide Web. 1614 For a while, it seemed that the easiest and most reliable approach to 1615 finding people's e-mail address on the Internet was to look up their 1616 telephone number on the Web, call them, and ask for their e-mail 1617 address! More recently, however, many third parties are augmenting 1618 the standard telephone directory with an e-mail directory. These 1619 services primarily rely on users voluntarily registering, resulting 1620 in incomplete databases because most users don't know about all of 1621 the services. Nevertheless, some of the personal directory services 1622 available via the Web with which e-mail addresses (and telephone 1623 numbers) can be found include Four11 Directory Services 1624 (http://www.Four11.com/), Excite 1625 (http://www.excite.com/Reference/locators.html), and Yahoo! People 1626 Search (http://www.yahoo.com/search/people/). 1628 In addition, the Knowbot Information Service (KIS), CNRI's automated 1629 username database search tool described earlier in this document, is 1630 also available on the Web, at http://info.cnri.reston.va.us/kis.html. 1631 Users can select several options for the KIS search, including the 1632 InterNIC, MILNET, MCImail, and Latin American Internic databases; 1633 UNIX finger and whois servers; and X.500 databases. 1635 7.3. Other Service Accessible Via the Web 1637 Many of the other utilities described earlier in this document can 1638 also be accessed via the WWW. In general, the Web browser acts as a 1639 viewer to a remote client rather than requiring specialized software 1640 on the user's system. 1642 Several sites provide DNS information, obviating the need for a user 1643 to have a local DNS client such as NSLOOKUP. The hosts 1644 http://ns1.milepost.com/dns/ and 1645 http://sh1.ro.com/~mprevost/netutils/dig.html are among the best DNS 1646 sites, allowing the user to access all DNS information. The site 1647 http://www.bankes.com/nslookup.htm allows users to do multiple, 1648 sequential searches at a given domain. Other Web sites providing 1649 simple DNS name/address translation services include 1650 http://rhinoceros.cs.inf.shizuoka.ac.jp/dns.html, 1651 http://www.engin.umich.edu/htbin/DNSquery, 1652 http://www.lublin.pl/cgi-bin/ns/nsgate, and 1653 http://www.trytel.com/cgi-bin/weblookup. 1655 Ping is another service available on the Web. The 1656 http://sh1.ro.com/~mprevost/netutils/ping.html page allows a user to 1657 select a host name, number of times to ping (1-10), and number of 1658 seconds between each ping (1-10), and returns a set of summary 1659 statistics. Other Web-based ping sites include 1660 http://www.net.cmu.edu/bin/ping (sends ten pings, and reports the 1661 times and min/max/avg summary statistics) and 1662 http://www.uia.ac.be/cc/ping.html (indicates whether the target host 1663 is alive or not). 1665 Traceroute is also available on the Web. Unfortunately, these servers 1666 trace the route from their host to a host that the user chooses, 1667 rather than from the user's host to the target. Nevertheless, 1668 interesting route information can be found at 1669 http://www.net.cmu.edu/bin/traceroute. Traceroute service and a list 1670 of a number of other traceroute sites on the Web can be found at 1671 http://www.lublin.pl/cgi-bin/trace/traceroute. 1673 Access to archie is also available via the WWW, where your browser 1674 acts as the graphical interface to an archie server. To find a list 1675 of archie servers, and to access them via the Web, point your browser 1676 at 1677 http://www.yahoo.com/Computers_and_Internet/Internet/FTP_Sites/Search 1678 ing/Archie/. 1680 Finally, even Finger can be found on the World Wide Web; check out 1681 http://sh1.ro.com/~mprevost/netutils/finger.html. 1683 8. Discussion Lists and Newsgroups 1685 Among the most useful features of the Internet are the discussion 1686 lists that have become available to allow individuals to discuss 1687 topics of mutual concern. Discussion list topics range from SCUBA 1688 diving and home brewing of beer to AIDS research and foreign policy. 1689 Several, naturally, deal specifically with the Internet, TCP/IP 1690 protocols, and the impact of new technologies. 1692 Most of the discussion lists accessible from the Internet are 1693 unmoderated, meaning that anyone can send a message to the list's 1694 central repository and the message will then be automatically 1695 forwarded to all subscribers of the list. These lists provide very 1696 fast turn-around between submission of a message and delivery, but 1697 often result in a lot of messages (including inappropriate junk mail, 1698 or "spam"). A moderated list has an extra step; a human list 1699 moderator examines all messages before they are forwarded to ensure 1700 that the messages are appropriate to the list and not needlessly 1701 inflammatory! 1703 Users should be warned that some lists generate a large number of 1704 messages each day. Before subscribing to too many lists, be sure that 1705 you are aware of local policies and/or charges governing access to 1706 discussion lists and e-mail storage. 1708 8.1. Internet Discussion Lists 1710 Mail can be sent to almost all Internet lists at an address with the 1711 following form: 1713 @ 1715 The common convention when users want to subscribe, unsubscribe, or 1716 handle any other administrative matter is to send a message to the 1717 list administrator; do not send administrivia to the main list 1718 address! The list administrator can usually be found at: 1720 -REQUEST@ 1722 To subscribe to a list, it is often enough to place the word 1723 "subscribe" in the main body of the message, although a line with the 1724 format: 1726 subscribe 1728 will satisfy most mail servers. A similar message may be used to get 1729 off a list; just use the word "unsubscribe" followed by the list 1730 name. Not every list follows this convention, but it is a safe bet if 1731 you don't have better information! 1733 8.2. LISTSERV 1735 A large set of discussion groups is maintained using a program called 1736 LISTSERV. LISTSERV is a service provided widely on BITNET and EARN, 1737 although it is also available to Internet users. A LISTSERV User 1738 Guide can be found on the Web at http://www.earn.net/lug/notice.html. 1740 Mail can be sent to most LISTSERV lists at an address with the 1741 following form: 1743 @ 1745 The common convention when users want to subscribe, unsubscribe, or 1746 handle any other administrative matter is to send commands in a 1747 message to the LISTSERV server; do not send administrivia to the main 1748 list address! The list server can usually be found at: 1750 LISTSERV@ 1752 LISTSERV commands are placed in the main body of e-mail messages sent 1753 to an appropriate list server location. Once you have found a list of 1754 interest, you can send a message to the appropriate address with any 1755 appropriate command, such as: 1757 subscribe Subscribe to a list 1758 unsubscribe Unsubscribe from a 1759 list 1760 help Get help & a list of 1761 commands 1762 index Get a list of LISTSERV 1763 files 1764 get Obtain a file from the 1765 server 1767 8.3. Majordomo 1769 Majordomo is another popular list server for Internet discussion 1770 lists. The Web site http://www.greatcircle.com/majordomo/ has a large 1771 amount of information about Majordomo. 1773 Mail is sent to Majordomo lists using the same general address format 1774 as above: 1776 @ 1778 The common convention when users want to subscribe, unsubscribe, or 1779 handle any other administrative matter is to send a message to the 1780 Majordomo list server; do not send administrivia to the main list 1781 address! The Majordomo server can usually be found at: 1783 MAJORDOMO@ 1785 Majordomo commands are placed in the main body of e-mail messages 1786 sent to an appropriate list server location. Available commands 1787 include: 1789 help Get help & a list of commands 1790 subscribe Subscribe to a list 1791 unsubscribe Unsubscribe from a list 1792 info Send introduction about the list 1793 lists Get a list of this server's lists 1795 8.4. Usenet 1797 Usenet, also known as NETNEWS or Usenet news, is another information 1798 source with its own set of special interest mailing lists organized 1799 into newsgroups. Usenet originated on UNIX systems but has migrated 1800 to many other types of hosts. Usenet clients, called newsreaders, use 1801 the Network News Transfer Protocol [ff] and are available for 1802 virtually any operating system; several web browsers, in fact, have 1803 this capability built in. 1805 While Usenet newsgroups are usually accessible at Internet sites, a 1806 prospective Usenet client host must have appropriate newsreader 1807 software to be able to read news. Users will have to check with their 1808 local host or network administrator to find out what Usenet 1809 newsgroups are locally available, as well as the local policies for 1810 using them. 1812 Usenet newsgroup names are hierarchical in nature. The first part of 1813 the name, called the hierarchy, provides an indication about the 1814 general subject area. There are two types of hierarchies, called 1815 mainstream and alternative; the total number of newsgroups is in the 1816 thousands. The news.announce.newusers newsgroup is a good place for 1817 new Usenet users to find a detailed introduction to the use of 1818 Usenet, as well as an introduction to its culture. 1820 Usenet mainstream hierarchies are established by a process that 1821 requires the approval of a majority of Usenet members. Most sites 1822 that receive a NETNEWS feed receive all of these hierarchies, which 1823 include: 1825 comp Computers 1826 misc Miscellaneous 1827 news Network news 1828 rec Recreation 1829 sci Science 1830 soc Social issues 1831 talk Various discussion lists 1833 The alternative hierarchies include lists that may be set up at any 1834 site that has the server software and disk space. These lists are not 1835 formally part of Usenet and, therefore, may not be received by all 1836 sites getting NETNEWS. The alternative hierarchies include: 1838 alt Alternate miscellaneous discussion lists 1839 bionet Biology, medicine, and life sciences 1840 bit BITNET discussion lists 1841 biz Various business-related discussion lists 1842 ddn Defense Data Network 1843 gnu GNU lists 1844 ieee IEEE information 1845 info Various Internet and other networking information 1846 k12 K-12 education 1847 u3b AT&T 3B computers 1848 vmsnet Digital's VMS operating system 1850 8.5 Finding Discussion Lists and Newsgroups 1852 Armed with the rules for signing up for a discussion list or 1853 accessing a newsgroup, how does one find an appropriate list given 1854 one's interests? 1856 There are tens of thousands of e-mail discussion lists on the 1857 Internet. One List of Lists may be found using anonymous FTP at 1858 ftp://sri.com/netinfo/interest-groups.txt; the List of Lists can be 1859 searched using a Web browser by going to 1860 http://catalog.com/vivian/interest-group-search.html. Other places to 1861 look are the Publicly Accessible Mailing Lists index at 1862 http://www.neosoft.com/internet/paml/byname.html and the LISZT 1863 Directory of E-Mail Discussion Groups at http://www.liszt.com. 1865 To obtain a list of LISTSERV lists, send e-mail to 1866 listserv@bitnic.cren.net with the command lists global in the body of 1867 the message. Alternatively, look on the Web at 1868 http://www.tile.net/tile/listserv/index.html. The Web site 1869 http://www.liszt.com has a Mailing Lists Database of lists served by 1870 LISTSERV and Majordomo. 1872 There are also thousands of Usenet newsgroups. One Usenet archive can 1873 be found at gopher://rtfm.mit.edu/11//pub/usenet/news.answers; see 1874 the /active-newsgroups and /alt-hierarchies subdirectories. Usenet 1875 news may also be read at gopher://gopher.bham.ac.uk/11/Usenet. A good 1876 Usenet search facility can be found at DejaNews at 1877 http://www.dejanews.com/; messages can also be posted to Usenet 1878 newsgroups from this site. 1880 Note that there is often some overlap between Usenet newsgroups and 1881 Internet discussion lists. Some individuals join both lists in these 1882 circumstances or, often, there is cross-posting of messages. Some 1883 Usenet newsgroup discussions are forwarded onto an Internet mailing 1884 list by an individual site to provide access to those users who do 1885 not have Usenet available. 1887 9. Internet Documentation 1889 To fully appreciate and understand what is going on within the 1890 Internet community, users might wish to obtain the occasional 1891 Internet specification. The main body of Internet documents are 1892 Request for Comments (RFCs), although a variety of RFC subsets have 1893 been defined for various specific purposes. The sections below will 1894 describe the RFCs and other documentation, and how to get them. 1896 The Internet standardization process is alluded to in the following 1897 sections. The Internet Engineering Task Force (IETF) is the guiding 1898 body for Internet standards; their Web site is http://www.ietf.org. 1899 The IETF operates under the auspices of the Internet Society (ISOC), 1900 which has a Web site at http://www.isoc.org. For complete, up-to-date 1901 information on obtaining Internet documentation, go to the InterNIC's 1902 Web site at http://ds.internic.net/ds/dspg0intdoc.html. 1904 9.1. Request for Comments (RFCs) 1906 RFCs are the body of literature comprising Internet protocols, 1907 standards, research questions, hot topics, humor (especially those 1908 dated 1 April), and general information. Each RFC is uniquely issued 1909 a number which is never reused or reissued; if a document is revised, 1910 it is given a new RFC number and the old RFC is said to be obsoleted. 1911 Announcements are sent to the RFC-DIST mailing list whenever a new 1912 RFC is issued; anyone may join this list by sending e-mail to rfc- 1913 dist-request@isi.edu. 1915 RFCs may be obtained through the mail (i.e., postal service), but it 1916 is easier and faster to get them on-line. One easy way to obtain RFCs 1917 on-line is to use RFC-INFO, an e-mail-based service to help users 1918 locate and retrieve RFCs and other Internet documents. To use the 1919 service, send e-mail to rfc-info@isi.edu and leave the Subject: field 1920 blank; commands that may go in the main body of the message include: 1922 help (Help file) 1923 help: ways_to_get_rfcs (Help file on how to get RFCs) 1925 RETRIEVE: RFC 1926 Doc-ID: RFCxxxx (Retrieve RFC xxxx; use all 4 digits) 1928 LIST: RFC (List all RFCs...) 1929 [options] (...[matching the following options]) 1930 KEYWORDS: xxx (Title contains string "xxx") 1931 AUTHOR: xxx (Written by "xxx") 1932 ORGANIZATION: xxx (Issued by company "xxx") 1933 DATED-AFTER: mmm-dd-yyyy 1934 DATED-BEFORE: mmm-dd-yyyy 1935 OBSOLETES: RFCxxxx (List RFCs obsoleting RFC xxxx) 1937 Another RFC e-mail server can be found at the InterNIC. To use this 1938 service, send an e-mail message to mailserv@ds.internic.net, leaving 1939 the Subject: field blank. In the main body of the message, use one or 1940 more of the following commands: 1942 help (Help file) 1943 file /ftp/rfc/rfcNNNN.txt (Text version of RFC NNNN) 1944 file /ftp/rfc/rfcNNNN.ps (Postscript version of RFC NNNN) 1945 document-by-name rfcNNNN (Text version of RFC NNNN) 1947 ------------------------------------------------------------------- 1948 TABLE 1. Primary RFC Repositories. 1950 HOST ADDRESS DIRECTORY 1952 ds.internic.net rfc 1953 nis.nsf.net internet/documents/rfc 1954 nisc.jvnc.net rfc 1955 ftp.isi.edu in-notes 1956 wuarchive.wustl.edu info/rfc 1957 src.doc.ic.ac.uk rfc 1958 ftp.ncren.net rfc 1959 ftp.sesqui.net pub/rfc 1960 nis.garr.it mirrors/RFC 1961 funet.fi rfc 1962 munnari.oz.au rfc 1963 ------------------------------------------------------------------- 1965 To obtain an RFC via anonymous FTP, connect to one of the RFC 1966 repositories listed in Table 1 using FTP. After connecting, change to 1967 the appropriate RFC directory (as shown in Table 1) using the cd 1968 command. To obtain a particular file, use the get command: 1970 GET RFC-INDEX.TXT (RFC Index) 1971 GET RFCxxxx.TXT (Text version of RFC xxxx) 1972 GET RFCxxxx.PS (Postscript version of RFC xxxx) 1974 The RFC index, or a specific reference to an RFC, will indicate 1975 whether the RFC is available in ASCII text (.txt) or Postscript (.ps) 1976 format. By convention, all RFCs are available in ASCII while some are 1977 also available in Postscript where use of graphics and/or different 1978 fonts adds more information or clarity. Be aware that the index file 1979 is very large, containing the citing for over 2,000 documents. Note 1980 that not all RFCs numbered below 698 (July 1975) are available on- 1981 line. 1983 Finally, the InterNIC's Web site at 1984 http://ds.internic.net/ds/dspg1intdoc.html contains the RFC index and 1985 a complete set of RFCs. More information about Web-based RFC servers 1986 can be found at http://www.isi.edu/rfc-editor/rfc-sources.html for 1988 The sample dialogue below, although highly abbreviated, shows a user 1989 obtaining RFC 1594 (Answers to Commonly asked "New Internet User" 1990 Questions) using e-mail and anonymous FTP. 1992 ==================================================================== 1993 ** SMCVAX$ mail 1994 ** MAIL> send 1995 ** To: in%"rfc-info@isi.edu" 1996 Subject: 1997 Enter your message below. Press CTRL/Z when complete, CTRL/C to quit 1998 ** retrieve: rfc 1999 ** doc-id: rfc1594 2000 ** ^Z 2001 ** MAIL> exit 2003 ** SMCVAX$ ftp ds.internic.net 2004 ** Username: anonymous 2005 ** Password: 2006 ** NIC.DDN.MIL> cd rfc 2007 ** NIC.DDN.MIL> get rfc1594.txt rfc-1594.txt 2008 ** NIC.DDN.MIL> exit 2009 SMCVAX$ 2010 ==================================================================== 2012 9.2. Internet Standards 2014 RFCs describe many aspects of the Internet. By the early 1990s, 2015 however, so many specifications of various protocols had been written 2016 that it was not always clear as to which documents represented 2017 standards for the Internet. For that reason, a subset of RFCs have 2018 been designated as STDs to identify them as Internet standards. 2020 Unlike RFC numbers that are never reused, STD numbers always refer to 2021 the latest version of the standard. UDP, for example, would be 2022 completely identified as "STD-6/RFC-768." Note that STD numbers 2023 refer to a standard, which is not necessarily a single document; STD 2024 19, for example, is the NetBIOS Service Protocols standard comprising 2025 RFCs 1001 and 1002, and a complete citation for this standard would 2026 be "STD-19/RFC-1001/RFC-1002." 2028 The availability of new STDs is announced on the RFC-DIST mailing 2029 list. STD-1 [14] always refers to the latest list of "Internet 2030 Official Protocol Standards". The Internet standards process is 2031 described in RFC 1602 [6] and STD notes are explained in RFC 1311 2032 [15]. 2034 STDs can be obtained as RFCs via anonymous FTP from any RFC 2035 repository. In addition, some RFC sites (such as ds.internic.net) 2036 provide an STD directory so that STD documents can be found in the 2037 path /STD/xx.TXT, where xx refers to the STD number. 2039 STD documents may be obtained as RFCs using the methods described in 2040 Section 9.1. STDs may also be obtained via the RFC-INFO server using 2041 the RETRIEVE: STD and Doc-ID: STDxxxx commands. Also, check out the 2042 InterNIC's Web site at http://www.internic.net/std/ for the STD index 2043 and a complete set of STDs. 2045 9.3. For Your Information Documents 2047 The For Your Information (FYI) series of RFCs provides Internet users 2048 with information about many topics related to the Internet. FYI 2049 topics range from historical to explanatory to tutorial, and are 2050 aimed at the wide spectrum of people that use the Internet. The FYI 2051 series includes answers to frequently asked questions by both 2052 beginning and seasoned users of the Internet, an annotated 2053 bibliography of Internet books, and an explanation of the domain name 2054 system. 2056 Like the STDs, an FYI number always refers to the latest version of 2057 an FYI. FYI 4, for example, refers to the answers to commonly asked 2058 questions by new Internet users; its complete citation would be "FYI- 2059 4/RFC-1594." The FYI notes are explained in FYI 1 [9]. 2061 FYIs can be obtained as RFCs via anonymous FTP from any RFC 2062 repository. In addition, some RFC sites (such as ds.internic.net) 2063 provide an FYI directory so that FYI documents can be found in the 2064 path /FYI/xx.TXT, where xx refers to the FYI number. 2066 FYI documents may be obtained as RFCs using the methods described in 2067 Section 9.1. FYIs may also be obtained via the RFC-INFO server using 2068 the RETRIEVE: FYI and Doc-ID: FYIxxxx commands. Also, check out the 2069 InterNIC's Web site at http://www.internic.net/fyi/ for the FYI index 2070 and a complete set of FYIs. 2072 9.4. RARE Technical Reports 2074 RARE, the Reseaux Associes pour la Recherche Europeenne (Association 2075 of European Research Networks), has a charter to promote and 2076 participate in the creation of a high-quality European computer 2077 communications infrastructure for the support of research endeavors. 2078 RARE member networks use Open Systems Interconnection (OSI) protocols 2079 and TCP/IP. To promote a closer relationship between RARE and the 2080 IETF, RARE Technical Reports (RTRs) have also been published as RFCs 2081 since the summer of 1993. 2083 RTR documents may be obtained as RFCs using the methods described in 2084 Section 9.1. RTRs may also be obtained via the RFC-INFO server using 2085 the RETRIEVE: RTR and Doc-ID: RTRxxxx commands. Also, check out the 2086 InterNIC's Web site at http://www.internic.net/rtr/ for the RTR index 2087 and a complete set of RTRs. Finally, RTRs may be obtained via 2088 anonymous FTP from ftp://ftp.rare.nl/rare/publications/rtr/. 2090 10. Perusing the Internet... 2092 This guide is intended to provide the reader with a rudimentary 2093 ability to use the utilities that are provided by TCP/IP and the 2094 Internet. By now, it is clear that the user's knowledge, ability, and 2095 willingness to experiment are about the only limits to what can be 2096 accomplished. 2098 There are several books that will help you get started finding sites 2099 on the Internet, including The INTERNET Yellow Pages [28]. But much 2100 more timely and up-to-date information can be found on the Internet 2101 itself, using such search tools as Yahoo! (http://www.yahoo.com), 2102 Excite (http://www.excite.com), Lycos (http://www.lycos.com), 2103 WebCrawler (http://www.webcrawler.com), and AltaAvista 2104 (http://altavista.digital.com). 2106 There are several other sources that cite locations from which to 2107 access specific information about a wide range of subjects using such 2108 tools as FTP, Telnet, Gopher, and WWW. One of the best periodic 2109 lists, and archives, is through the Scout Report, a weekly 2110 publication by the InterNIC's Net Scout Services Project at the 2111 University of Wisconsin's Computer Science Department. To receive the 2112 Scout Report by e-mail each week, join the mailing list by sending 2113 email to listserv@lists.internic.net; place the line subscribe 2114 scout-report your_full_name in the body of the message to receive the 2115 text version or use subscribe scout-report-html your_full_name to 2116 receive the report in HTML. The Scout Report is also available on the 2117 Web at http://www.cs.wisc.edu/scout/report and 2118 http://rs.internic.net/scout/report, or via anonymous FTP at 2119 ftp://rs.internic.net/scout/. 2121 Another list is Yanoff's Internet Services List, which may be found 2122 at http://www.spectracom.com/islist/ or 2123 ftp://ftp.csd.uwm.edu/pub/inet.services.txt. Gary Kessler, one of the 2124 co-author's of this document, maintains his own eclectic 2125 Miscellaneous Sites List at 2126 http://www.together.net/~kessler/gck_site.html. 2128 If you are looking for Internet-specific information, one good 2129 starting point is 2130 http://www.yahoo.com/Computers_and_Internet/Internet/. The InterNIC 2131 is another valuable resource, with their Scout Report and Scout 2132 Toolkit (http://rs.internic.net/scout/toolkit). 2134 There is also a fair amount of rudimentary tutorial information 2135 available on the Internet. The InterNIC cosponsors "The 15 Minute 2136 Series" (http://rs.internic.net/nic-support/15min/), a collection of 2137 free, modular, and extensible training materials on specific Internet 2138 topics. ROADMAP96 (http://www.ua.edu/~crispen/roadmap.html) is a 2139 free, 27-lesson Internet training workshop over e-mail. 2141 More books and specialized articles came out about the Internet in 2142 1993 and 1994 than in all previous years (squared!), and that trend 2143 has nearly continued into 1995, 1996, and beyond. Three books are 2144 worth notable mention because they do not directly relate to finding 2145 your way around, or finding things on, the Internet. Hafner and Lyon 2146 [gg] have written Where Wizards Stay Up Late: The Origins of the 2147 Internet, a history of the development of the Advanced Research 2148 Projects Agency (ARPA), packet switching, and the ARPANET, focusing 2149 primarily on the 1960s and 1970s. While culminating with the 2150 APRANET's 25th Anniversary in 1994, its main thrusts are on the 2151 groups building the ARPANET backbone (largely BBN) and the host-to- 2152 host application and communication protocols (largely the Network 2153 Working Group). Salus' book, Casting The Net: From ARPANET to 2154 INTERNET and beyond... [hh], goes into the development of the network 2155 from the perspective of the people, protocols, applications, and 2156 networks. Including a set of "diversions," his book is a bit more 2157 whimsical than Hafner & xx's. Finally, Carl Malamud has written a 2158 delightful book called Exploring the Internet: A Technical Travelogue 2159 [32], chronicling not the history of the Internet as much as a subset 2160 of the people currently active in building and defining it. This 2161 book will not teach you how to perform an anonymous FTP file transfer 2162 nor how to use Gopher, but provides insights about our network (and 2163 Carl's gastro-pathology) that no mere statistics can convey. 2165 11. Acronyms and Abbreviations 2167 ASCII American Standard Code for Information Interchange 2168 BITNET Because It's Time Network 2169 DDN Defense Data Network 2170 DNS Domain Name System 2171 EARN European Academic Research Network 2172 FAQ Frequently Asked Questions list 2173 FTP File Transfer Protocol 2174 FYI For Your Information series of RFCs 2175 HTML Hypertext Markup Language 2176 HTTP Hypertext Transport Protocol 2177 ICMP Internet Control Message Protocol 2178 IP Internet Protocol 2179 ISO International Organization for Standardization 2180 NetBIOS Network Basic Input/Output System 2181 NIC Network Information Center 2182 NICNAME Network Information Center name service 2183 NSF National Science Foundation 2184 NSFNET National Science Foundation Network 2185 RFC Request For Comments 2186 RARE Reseaux Associes pour la Recherche Europeenne 2187 RTR RARE Technical Reports 2188 SMTP Simple Mail Transfer Protocol 2189 STD Internet Standards series of RFCs 2190 TCP Transmission Control Protocol 2191 TTL Time-To-Live 2192 UDP User Datagram Protocol 2193 URL Uniform Resource Locator 2194 WAIS Wide Area Information Server 2195 WWW World Wide Web 2197 12. Security Considerations 2199 Security issues are not discussed in this memo. 2201 13. Acknowledgements 2203 Our thanks are given to all sites that we accessed or otherwise used 2204 system resources in preparation for this document. We also appreciate 2205 the comments and suggestions from our students and members of the 2206 Internet community, particularly after the last version of this 2207 document was circulated, including Mark Delany and the rest of the 2208 gang at the Australian Public Access Network Association, Margaret 2209 Hall (BBN), John Martin (RARE), Tom Maufer (3Com), Carol Monaghan 2210 (Hill Associates), Michael Patton (BBN), N. Todd Pritsky (Hill 2211 Associates), and Brian Williams. Special thanks are due to Joyce 2212 Reynolds for her continued encouragement and direction. 2214 14. References 2216 [1] Anklesaria, F., M. McCahill, P. Lindner, D. Johnson, D. Torrey, 2217 and B. Alberti, "The Internet Gopher Protocol," RFC 1436, 2218 University of Minnesota, March 1993. 2220 [dd] Berners-Lee, T. and D. Connolly, "Hypertext Markup Language - 2221 2.0," MIT/W3C, November 1995. 2223 [cc] Berners-Lee, T., R. Fielding, and H. Frystyk, "Hypertext Transfer 2224 Protocol - HTTP/1.0," MIT/LCS, UC Irvine, MIT/LCS, May 1996. 2226 [2] Berners-Lee, T., L. Masinter, and M. McCahill, Editors, "Uniform 2227 Resource Locators (URL)," CERN, Xerox Corp., University of 2228 Minnesota, December 1994. 2230 [22] Comer, D. Internetworking with TCP/IP, Vol. I: Principles, 2231 Protocols, and Architecture, 2/e. Englewood Cliffs (NJ): 2232 Prentice-Hall, 1991. 2234 [23] Feit, S. TCP/IP, 2/e. New York: McGraw-Hill, 1997. 2236 [gg] Hafner, K. and M. Lyon. Where Wizards Stay Up Late: The Origins 2237 of the Internet. new York: Simon & Schuster, 1997. 2239 [28] Hahn, H. and R. Stout. The Internet Yellow Pages, 3/e. Berkeley 2240 (CA): Osborne McGraw-Hill, 1996. 2242 [4] Harrenstien, K., M. Stahl, and E. Feinler, "NICNAME/WHOIS," RFC 2243 954, SRI, October 1985. 2245 [6] Internet Architecture Board, Internet Engineering Steering Group, 2246 "The Internet Standards Process -- Revision 2," RFC 1602, March 2247 1994. 2249 [ff] Kantor, B. and P. Lapsley. "Network News Transfer Protocol," RFC 2250 977, 1986. 2252 [30] Kessler, G.C. "An Overview of TCP/IP Protocols and the Internet." 2253 URL: 2254 http://flower.comeng.chungnam.ac.kr/comeng/curri/Network/tcp-ip- 2255 overview. Last accessed: 26 September 1996. 2257 [32] Malamud, C. Exploring the Internet: A Technical Travelogue. 2258 Englewood Cliffs (NJ): PTR Prentice Hall, 1992. 2260 [9] Malkin, G.S. and J.K. Reynolds, "F.Y.I. on F.Y.I.: Introduction 2261 to the F.Y.I. notes," FYI 1/RFC 1150, Proteon, USC/Information 2262 Sciences Institute, March 1990. 2264 [12] Mockapetris, P., "Domain Names - Concepts and Facilities," STD 2265 13/RFC 1034, USC/Information Sciences Institute, November 1987. 2267 [ee] National Center for Supercomputer Applications (NCSA). "A 2268 Beginner's Guide to HTML." 2269 http://www.ncsa.uiuc.edu/General/Internet/WWW/HTMLPrimer.html. 2270 Last accessed: 19 September 1996. 2272 [13] Postel, J., "Domain Name System Structure and Delegation," 2273 USC/Information Sciences Institute, RFC 1591, March 1994. 2275 [bb] Postel, J., "Internet Control Message Protocol," USC/Information 2276 Sciences Institute, RFC 792, September 1981. 2278 [14] Postel, J., Editor, "Internet Official Protocol Standards," STD 2279 1/RFC 1920, Internet Architecture Board, March 1996. 2281 [15] Postel, J., "Introduction to the STD Notes," RFC 1311, 2282 USC/Information Sciences Institute, March 1992. 2284 [16] Postel, J. and J. Reynolds, "File Transfer Protocol (FTP), STD 2285 9/RFC 959, USC/Information Sciences Institute, October 1985. 2287 [17] Postel, J. and J. Reynolds, "TELNET Protocol Specification," STD 2288 8/RFC 854, USC/Information Sciences Institute, May 1983. 2290 [hh] Salus, P.H. Casting The Net: From ARPANET to INTERNET and 2291 beyond... Reading (MA): Addison-Wesley, 1995. 2293 [18] Socolofsky, T.J. and C.J. Kale, "TCP/IP Tutorial," RFC 1180, 2294 Spider Systems Ltd., January 1991. 2296 [aa] Stevens, W.R. TCP/IP Illustrated, Volume 1: The Protocols. 2297 Reading (MA): Addison-Wesley, 1994. 2299 [19] Williamson, S., "Transition and Modernization of the Internet 2300 Registration Service," RFC 1400, Network Solutions, Inc., March 2301 1993. 2303 [20] Zimmerman, D., "The Finger User Information Protocol," RFC 1288, 2304 Rutgers University, December 1991. 2306 15. Authors' Address 2308 Gary C. Kessler 2309 5 Creek Glen 2310 Colchester, VT 05446-3641 2311 Phone: +1 802-879-3375 2312 Fax: +1 802-879-3375 2313 E-mail: kessler@together.net 2315 Steven D. Shepard 2316 Hill Associates 2317 17 Roosevelt Highway 2318 Colchester, VT 05446 2319 Phone: +1 802-655-8646 2320 Fax: +1 802-655-7974 2321 E-mail: s.shepard@hill.com