| 1 |
<pre>Network Working Group G. Malkin |
| 2 |
Request for Comments: 1206 FTP Software, Inc. |
| 3 |
FYI: 4 A. Marine |
| 4 |
Obsoletes: RFC <a href="./rfc1177">1177</a> SRI |
| 5 |
February 1991 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">FYI on Questions and Answers</span> |
| 9 |
<span class="h1">Answers to Commonly asked "New Internet User" Questions</span> |
| 10 |
|
| 11 |
Status of this Memo |
| 12 |
|
| 13 |
This FYI RFC is one of two FYI's called, "Questions and Answers" |
| 14 |
(Q/A), produced by the User Services Working Group of the Internet |
| 15 |
Engineering Task Force (IETF). The goal is to document the most |
| 16 |
commonly asked questions and answers in the Internet. |
| 17 |
|
| 18 |
This memo provides information for the Internet community. It does |
| 19 |
not specify any standard. Distribution of this memo is unlimited. |
| 20 |
|
| 21 |
Table of Contents |
| 22 |
|
| 23 |
<a href="#section-1">1</a>. Introduction................................................. <a href="#page-1">1</a> |
| 24 |
<a href="#section-2">2</a>. Acknowledgements............................................. <a href="#page-2">2</a> |
| 25 |
<a href="#section-3">3</a>. Questions About the Internet................................. <a href="#page-2">2</a> |
| 26 |
<a href="#section-4">4</a>. Questions About TCP/IP....................................... <a href="#page-4">4</a> |
| 27 |
<a href="#section-5">5</a>. Questions About the Domain Name System....................... <a href="#page-4">4</a> |
| 28 |
<a href="#section-6">6</a>. Questions About Internet Documentation....................... <a href="#page-5">5</a> |
| 29 |
<a href="#section-7">7</a>. Questions about Internet Organizations and Contacts.......... <a href="#page-9">9</a> |
| 30 |
<a href="#section-8">8</a>. Questions About Services..................................... <a href="#page-13">13</a> |
| 31 |
<a href="#section-9">9</a>. Mailing Lists................................................ <a href="#page-16">16</a> |
| 32 |
<a href="#section-10">10</a>. Miscellaneous "Internet lore" questions..................... <a href="#page-17">17</a> |
| 33 |
<a href="#section-11">11</a>. Suggested Reading........................................... <a href="#page-18">18</a> |
| 34 |
<a href="#section-12">12</a>. References.................................................. <a href="#page-19">19</a> |
| 35 |
<a href="#section-13">13</a>. Condensed Glossary.......................................... <a href="#page-20">20</a> |
| 36 |
<a href="#section-14">14</a>. Security Considerations..................................... <a href="#page-31">31</a> |
| 37 |
<a href="#section-15">15</a>. Authors' Addresses.......................................... <a href="#page-32">32</a> |
| 38 |
|
| 39 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 40 |
|
| 41 |
New users joining the Internet community have the same questions as |
| 42 |
did everyone else who has ever joined. Our quest is to provide the |
| 43 |
Internet community with up to date, basic Internet knowledge and |
| 44 |
experience, while moving the redundancies away from the electronic |
| 45 |
mailing lists so that the lists' subscribers do not have to read the |
| 46 |
same queries and answers over and over again. |
| 47 |
|
| 48 |
Future updates of this memo will be produced as User Services members |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">User Services Working Group [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 55 |
|
| 56 |
|
| 57 |
become aware of additional questions that should be included, and of |
| 58 |
deficiencies or inaccuracies that should be amended in this document. |
| 59 |
An additional FYI Q/A will be published which will deal with |
| 60 |
intermediate and advanced Q/A topics. |
| 61 |
|
| 62 |
The Q/A mailing lists are maintained by Gary Malkin at FTP.COM. They |
| 63 |
are used by a subgroup of the User Services Working Group to discuss |
| 64 |
the Q/A FYIs. They include: |
| 65 |
|
| 66 |
[email protected] This is a discussion mailing list. Its |
| 67 |
primary use is for pre-release review of |
| 68 |
the Q/A FYIs. |
| 69 |
|
| 70 |
[email protected] This is how you join the quail mailing list. |
| 71 |
|
| 72 |
[email protected] This is a write-only list which serves as a |
| 73 |
repository for candidate questions and answers. |
| 74 |
It is not necessary to be on the quail mailing |
| 75 |
list to forward to the quail-box. |
| 76 |
|
| 77 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Acknowledgements</span> |
| 78 |
|
| 79 |
The following people deserve thanks for their help and contributions |
| 80 |
to this FYI Q/A: Vint Cerf (CNRI), Ralph Droms (Bucknell), |
| 81 |
Tracy LaQuey Parker (UTexas), Craig Partridge (SICS), Jon Postel (ISI), |
| 82 |
Joyce K. Reynolds (ISI), Karen Roubicek (BBNST), Marty Schoffstall |
| 83 |
(PSI, Inc.), Patricia Smith (Merit), Gene Spafford (Purdue) and |
| 84 |
James Van Bokkelen (FTP Software, Inc.). |
| 85 |
|
| 86 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Questions About the Internet</span> |
| 87 |
|
| 88 |
What is the Internet? |
| 89 |
|
| 90 |
The Internet is a large collection of networks (all of which run |
| 91 |
the TCP/IP protocols) that are tied together so that users of any |
| 92 |
of the networks can use the network services provided by TCP/IP to |
| 93 |
reach users on any of the other networks. The Internet started |
| 94 |
with the ARPANET, but now includes such networks as NSFNET, |
| 95 |
NYSERnet, and thousands of others. There are other major wide |
| 96 |
area networks, such as BITNET and DECnet networks, that are not |
| 97 |
based on the TCP/IP protocols and are thus not part of the |
| 98 |
Internet. However, it is possible to communicate between them and |
| 99 |
the Internet via electronic mail because of mail gateways that act |
| 100 |
as "translators" between the different network protocols involved. |
| 101 |
|
| 102 |
Note: You will often see "internet" with a small "i". This could |
| 103 |
refer to any network built based on TCP/IP, or might refer to |
| 104 |
networks using other protocol families that are composites built |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">User Services Working Group [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 111 |
|
| 112 |
|
| 113 |
of smaller networks. |
| 114 |
|
| 115 |
I just got on the Internet. What can I do now? |
| 116 |
|
| 117 |
You now have access to all the resources you are authorized to use |
| 118 |
on your own Internet host, on any other Internet host on which you |
| 119 |
have an account, and on any other Internet host that offers |
| 120 |
publicly accessible information. The Internet gives you the |
| 121 |
ability to move information between these hosts via file |
| 122 |
transfers. Once you are logged into one host, you can use the |
| 123 |
Internet to open a connection to another, login, and use its |
| 124 |
services interactively (this is known as remote login or |
| 125 |
"TELNETTING". In addition, you can send electronic mail to users |
| 126 |
at any Internet site and to users on many non-Internet sites that |
| 127 |
are accessible via electronic mail. |
| 128 |
|
| 129 |
There are various other services you can use. For example, some |
| 130 |
hosts provide access to specialized databases or to archives of |
| 131 |
information. The Internet Resource Guide provides information |
| 132 |
regarding some of these sites. The Internet Resource Guide lists |
| 133 |
facilities on the Internet that are available to users. Such |
| 134 |
facilities include supercomputer centers, library catalogs and |
| 135 |
specialized data collections. The guide is published by the NSF |
| 136 |
Network Service Center (NNSC) and is continuously being updated. |
| 137 |
The Resource Guide is distributed free via e-mail (send a note to |
| 138 |
[email protected] to join the e-mail |
| 139 |
distribution) and via anonymous FTP (in nnsc.nsf.net:resource- |
| 140 |
guide/*). Hardcopy is available at a nominal fee (to cover |
| 141 |
reproduction costs) from the NNSC. Call the NNSC at 617-873-3400 |
| 142 |
for more information. |
| 143 |
|
| 144 |
How do I find out if a site has a computer on the Internet? |
| 145 |
|
| 146 |
Three good sources to consult are "!%@:: A Directory of Electronic |
| 147 |
Mail Addressing and Networks" by Donnalyn Frey and Rick Adams; |
| 148 |
"The User's Directory of Computer Networks", by Tracy LaQuey; and |
| 149 |
"The Matrix: Computer Networks and Conferencing Systems |
| 150 |
Worldwide", by John Quarterman. |
| 151 |
|
| 152 |
In addition, it is possible to find some information about |
| 153 |
Internet sites in the WHOIS database maintained at the DDN NIC at |
| 154 |
SRI International. The DDN NIC (Defense Data Network, Network |
| 155 |
Information Center) provides an information retrieval interface to |
| 156 |
the database that is also called WHOIS. To use this interface, |
| 157 |
TELNET to NIC.DDN.MIL and type "whois" (carriage return). No |
| 158 |
login is necessary. Type "help" at the whois prompt for more |
| 159 |
information on using the facility. WHOIS will show many sites, |
| 160 |
but may not show every site registered with the DDN NIC (simply |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">User Services Working Group [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 167 |
|
| 168 |
|
| 169 |
for reasons having to do with how the program is set up to search |
| 170 |
the database). |
| 171 |
|
| 172 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Questions About TCP/IP</span> |
| 173 |
|
| 174 |
What is TCP/IP? |
| 175 |
|
| 176 |
TCP/IP (Transmission Control Protocol/Internet Protocol) [<a href="#ref-4" title=""Internet Protocol - DARPA Internet Program Protocol Specification"">4</a>,<a href="#ref-5" title=""Transmission Control Protocol - DARPA Internet Program Protocol Specification"">5</a>,<a href="#ref-6" title=""The DARPA Internet Protocol Suite"">6</a>] |
| 177 |
is the common name for a family of over 100 data-communications |
| 178 |
protocols used to organize computers and data-communications |
| 179 |
equipment into computer networks. TCP/IP was developed to |
| 180 |
interconnect hosts on ARPANET, PRNET (packet radio), and SATNET |
| 181 |
(packet satellite). All three of these networks have since been |
| 182 |
retired; but TCP/IP lives on. It is currently used on a large |
| 183 |
international network of networks called the Internet, whose |
| 184 |
members include universities, other research institutions, |
| 185 |
government facilities, and many corporations. TCP/IP is also |
| 186 |
sometimes used for other networks, particularly local area |
| 187 |
networks that tie together numerous different kinds of computers |
| 188 |
or tie together engineering workstations. |
| 189 |
|
| 190 |
What are the other well-known standard protocols |
| 191 |
in the TCP/IP family? |
| 192 |
|
| 193 |
Other than TCP and IP, the three main protocols in the TCP/IP |
| 194 |
suite are the Simple Mail Transfer Protocol (SMTP) [<a href="#ref-8" title=""Simple Mail Transport Protocol"">8</a>], the File |
| 195 |
Transfer Protocol (FTP) [<a href="#ref-3" title=""File Transfer Protocol (FTP)">3</a>], and the TELNET Protocol [<a href="#ref-9" title=""TELNET Protocol Specification"">9</a>]. There |
| 196 |
are many other protocols in use on the Internet. The Internet |
| 197 |
Activities Board (IAB) regularly publishes an RFC [<a href="#ref-2" title=""IAB Official Protocol Standards"">2</a>] that |
| 198 |
describes the state of standardization of the various Internet |
| 199 |
protocols. This document is the best guide to the current status |
| 200 |
of Internet protocols and their recommended usage. |
| 201 |
|
| 202 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Questions About the Domain Name System</span> |
| 203 |
|
| 204 |
What is the Domain Name System? |
| 205 |
|
| 206 |
The Domain Name System (DNS) is a hierarchical, distributed method |
| 207 |
of organizing the name space of the Internet. The DNS |
| 208 |
administratively groups hosts into a hierarchy of authority that |
| 209 |
allows addressing and other information to be widely distributed |
| 210 |
and maintained. A big advantage to the DNS is that using it |
| 211 |
eliminates dependence on a centrally-maintained file that maps |
| 212 |
host names to addresses. |
| 213 |
|
| 214 |
What is a Fully Qualified Domain Name? |
| 215 |
|
| 216 |
A Fully Qualified Domain Name (FQDN) is a domain name that |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">User Services Working Group [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 223 |
|
| 224 |
|
| 225 |
includes all higher level domains relevant to the entity named. |
| 226 |
If you think of the DNS as a tree-structure with each node having |
| 227 |
its own label, a Fully Qualified Domain Name for a specific node |
| 228 |
would be its label followed by the labels of all the other nodes |
| 229 |
between it and the root of the tree. For example, for a host, a |
| 230 |
FQDN would include the string that identifies the particular host, |
| 231 |
plus all domains of which the host is a part up to and including |
| 232 |
the top-level domain (the root domain is always null). For |
| 233 |
example, PARIS.NISC.SRI.COM is a Fully Qualified Domain Name for |
| 234 |
the host at 192.33.33.109. In addition, NISC.SRI.COM is the FQDN |
| 235 |
for the NISC domain. |
| 236 |
|
| 237 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Questions About Internet Documentation</span> |
| 238 |
|
| 239 |
What is an RFC? |
| 240 |
|
| 241 |
The Request for Comments documents (RFCs) are working notes of the |
| 242 |
Internet research and development community. A document in this |
| 243 |
series may be on essentially any topic related to computer |
| 244 |
communication, and may be anything from a meeting report to the |
| 245 |
specification of a standard. Submissions for Requests for |
| 246 |
Comments may be sent to the RFC Editor, Jon Postel |
| 247 |
([email protected]). |
| 248 |
|
| 249 |
Most RFCs are the descriptions of network protocols or services, |
| 250 |
often giving detailed procedures and formats for their |
| 251 |
implementation. Other RFCs report on the results of policy |
| 252 |
studies or summarize the work of technical committees or |
| 253 |
workshops. All RFCs are considered public domain unless |
| 254 |
explicitly marked otherwise. |
| 255 |
|
| 256 |
While RFCs are not refereed publications, they do receive |
| 257 |
technical review from either the task forces, individual technical |
| 258 |
experts, or the RFC Editor, as appropriate. Currently, most |
| 259 |
standards are published as RFCs, but not all RFCs specify |
| 260 |
standards. |
| 261 |
|
| 262 |
Anyone can submit a document for publication as an RFC. |
| 263 |
Submissions must be made via electronic mail to the RFC Editor. |
| 264 |
Please consult <a href="./rfc1111">RFC 1111</a>, "Instructions to RFC Authors" [<a href="#ref-10" title=""Request for Comments on Request for Comments - Instructions to RFC Authors"">10</a>], for |
| 265 |
further information. RFCs are accessible online in public access |
| 266 |
files, and a short message is sent to a notification distribution |
| 267 |
list indicating the availability of the memo. Requests to be |
| 268 |
added to this distribution list should be sent to RFC- |
| 269 |
[email protected]. |
| 270 |
|
| 271 |
The online files are copied by interested people and printed or |
| 272 |
displayed at their sites on their equipment. (An RFC may also be |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">User Services Working Group [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 279 |
|
| 280 |
|
| 281 |
returned via electronic mail in response to an electronic mail |
| 282 |
query.) This means that the format of the online files must meet |
| 283 |
the constraints of a wide variety of printing and display |
| 284 |
equipment. |
| 285 |
|
| 286 |
Once a document is assigned an RFC number and published, that RFC |
| 287 |
is never revised or re-issued with the same number. There is |
| 288 |
never a question of having the most recent version of a particular |
| 289 |
RFC. However, a protocol (such as File Transfer Protocol (FTP)) |
| 290 |
may be improved and re-documented many times in several different |
| 291 |
RFCs. It is important to verify that you have the most recent RFC |
| 292 |
on a particular protocol. The "IAB Official Protocol Standards" |
| 293 |
[<a href="#ref-2" title=""IAB Official Protocol Standards"">2</a>] memo is the reference for determining the correct RFC to refer |
| 294 |
to for the current specification of each protocol. |
| 295 |
|
| 296 |
How do I obtain RFCs? |
| 297 |
|
| 298 |
RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname |
| 299 |
RFC:RFCnnnn.TXT or RFC:RFCnnnn.PS (where "nnnn" refers to the |
| 300 |
number of the RFC). Login using FTP, username "anonymous" and |
| 301 |
password "guest". The NIC also provides an automatic mail service |
| 302 |
for those sites which cannot use FTP. Address the request to |
| 303 |
[email protected] and in the subject field of the message |
| 304 |
indicate the RFC number, as in "Subject: RFC nnnn" (or "Subject: |
| 305 |
RFC nnnn.PS" for PostScript RFCs). |
| 306 |
|
| 307 |
RFCs can also be obtained via FTP from NIS.NSF.NET. Using FTP, |
| 308 |
login with username "anonymous" and password "guest"; then connect |
| 309 |
to the RFC directory ("cd RFC"). The file name is of the form |
| 310 |
RFCnnnn.TXT-1 (where "nnnn" refers to the number of the RFC). The |
| 311 |
NIS also provides an automatic mail service for those sites which |
| 312 |
cannot use FTP. Address the request to [email protected] and |
| 313 |
leave the subject field of the message blank. The first line of |
| 314 |
the text of the message must be "SEND RFCnnnn.TXT-1", where nnnn |
| 315 |
is replaced by the RFC number. |
| 316 |
|
| 317 |
Requests for special distribution should be addressed to either |
| 318 |
the author of the RFC in question, or to [email protected]. SRI |
| 319 |
International operates NIC.DDN.MIL and has a hardcopy subscription |
| 320 |
service for RFCs as well as several publications which incorporate |
| 321 |
a selection of RFCs defining Internet standards. Unless |
| 322 |
specifically noted otherwise on the RFC itself, all RFCs are for |
| 323 |
unlimited distribution. |
| 324 |
|
| 325 |
How do I obtain a list of RFCs? |
| 326 |
|
| 327 |
The NIC maintains a file that is an index of the RFCs. It lists |
| 328 |
each RFC, starting with the most recent, and for each RFC provides |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">User Services Working Group [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 335 |
|
| 336 |
|
| 337 |
the number, title, author(s), issue date, and number of hardcopy |
| 338 |
pages. In addition, it lists the online formats (PostScript or |
| 339 |
ASCII text) for each RFC and the number of bytes each such version |
| 340 |
is online on the NIC.DDN.MIL host. If an RFC is also an FYI, that |
| 341 |
fact is noted, with the corresponding FYI number. (There is a |
| 342 |
parallel FYI Index available). Finally, the Index notes whether |
| 343 |
or not an RFC is obsoleted or updated by another RFC, and gives |
| 344 |
the number of that RFC, or if an RFC itself obsoletes or updates |
| 345 |
another RFC, and gives that RFC number. The index is updated |
| 346 |
online each time an RFC is issued. |
| 347 |
|
| 348 |
This RFC Index is available online from the NIC.DDN.MIL host as |
| 349 |
RFC:RFC-INDEX.TXT. The FYI Index is online as FYI:FYI-INDEX.TXT. |
| 350 |
It is also available from the NIC in hardcopy for $10, as are |
| 351 |
individual RFCs. Call the NIC at 1-800-235-3155 for help in |
| 352 |
obtaining the file. |
| 353 |
|
| 354 |
Which RFCs are Standards? |
| 355 |
|
| 356 |
See "IAB Official Protocol Standards" (currently, <a href="./rfc1140">RFC 1140</a>) [<a href="#ref-2" title=""IAB Official Protocol Standards"">2</a>]. |
| 357 |
|
| 358 |
What is an Internet Draft? Are there any guidelines available for |
| 359 |
writing one? |
| 360 |
|
| 361 |
Internet Drafts (I-D's) are the current working documents of the |
| 362 |
IETF. Internet Drafts are generally in the format of an RFC with |
| 363 |
some key differences: |
| 364 |
|
| 365 |
- The Internet Drafts are not RFC's and are not a numbered |
| 366 |
document series. |
| 367 |
|
| 368 |
- The words INTERNET-DRAFT appear in place of RFC XXXX |
| 369 |
in the upper left-hand corner. |
| 370 |
|
| 371 |
- The document does not refer to itself as an RFC or as a |
| 372 |
Draft RFC. |
| 373 |
|
| 374 |
- An Internet Draft does not state nor imply that it is a |
| 375 |
proposed standard. To do so conflicts with the role of |
| 376 |
the IAB, the RFC Editor, and the Internet Engineering |
| 377 |
Steering Group (IESG). |
| 378 |
|
| 379 |
An Internet Drafts Directory has been installed to make available, |
| 380 |
for review and comment by the IETF members, draft documents that |
| 381 |
will be submitted ultimately to the IAB and the RFC Editor to be |
| 382 |
considered for publishing as an RFC. The Internet Drafts |
| 383 |
Directories are maintained primarily at the NSFNET Network Service |
| 384 |
Center (NNSC). There are several "shadow" machines which contain |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">User Services Working Group [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 391 |
|
| 392 |
|
| 393 |
the IETF and Internet Drafts Directories. They are: |
| 394 |
|
| 395 |
NSF Network Service Center: nnsc.nsf.net |
| 396 |
DDN NIC: nic.ddn.mil |
| 397 |
Pacific Rim: munnari.oz.au |
| 398 |
Europe: nic.nordu.net (192.36.148.17) |
| 399 |
|
| 400 |
To access these directories, use anonymous FTP. Login with |
| 401 |
username, "anonymous", password, "guest". Once logged in, change |
| 402 |
to the directory, "cd internet-drafts". Internet Draft files can |
| 403 |
then be retrieved. |
| 404 |
|
| 405 |
For further information on the Internet Drafts of the IETF, or if |
| 406 |
you have problems with retrieving Internet Draft documents, |
| 407 |
contact Megan Davies ([email protected]) or Greg Vaudreuil |
| 408 |
([email protected]) for assistance. |
| 409 |
|
| 410 |
How do I obtain OSI Standards documents? |
| 411 |
|
| 412 |
OSI Standards documents are NOT available from the Internet via |
| 413 |
anonymous FTP due to copyright restrictions. These are available |
| 414 |
from: |
| 415 |
|
| 416 |
Omnicom Information Service |
| 417 |
501 Church Street NE |
| 418 |
Suite 304 |
| 419 |
Vienna, VA 22180 USA |
| 420 |
Telephone: (800) 666-4266 or (703) 281-1135 |
| 421 |
Fax: (703) 281-1505 |
| 422 |
|
| 423 |
However, the GOSIP specification which covers the use of OSI |
| 424 |
protocols within the U.S. Government is available from the NIC and |
| 425 |
from the National Institute of Standards and Technology (NIST). |
| 426 |
The final text of GOSIP Version 2 is now available from both |
| 427 |
sites. Version 2 is expected to become a Federal Information |
| 428 |
Processing Standard (FIPS) in early 1991. |
| 429 |
|
| 430 |
Online sources: |
| 431 |
|
| 432 |
Available through anonymous ftp from osi.ncsl.nist.gov |
| 433 |
(129.6.48.100) as: |
| 434 |
|
| 435 |
./pub/gosip/gosip_v2.txt -- ascii |
| 436 |
./pub/gosip/gosip_v2.txt.Z -- ascii compressed |
| 437 |
./pub/gosip/gosip_v2.ps -- PostScript |
| 438 |
./pub/gosip/gosip_v2.ps.Z -- PostScript compressed |
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">User Services Working Group [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 447 |
|
| 448 |
|
| 449 |
Available through anonymous ftp from nic.ddn.mil (192.67.67.20) |
| 450 |
as: |
| 451 |
|
| 452 |
PROTOCOLS:GOSIP-V2.TXT -- ascii |
| 453 |
PROTOCOLS:GOSIP-V2.PS -- PostScript |
| 454 |
Hardcopy sources: |
| 455 |
|
| 456 |
Standards Processing Coordinator (ADP) |
| 457 |
National Institute of Standards and Technology |
| 458 |
Technology Building, Room B-64 |
| 459 |
Gaithersburg, MD 20899 |
| 460 |
(301) 975-2816 |
| 461 |
|
| 462 |
Network Information Systems Center |
| 463 |
SRI International, Room EJ291 |
| 464 |
333 Ravenswood Ave. |
| 465 |
Menlo Park, CA 94025 |
| 466 |
1-800-235-3155 |
| 467 |
|
| 468 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Questions about Internet Organizations and Contacts</span> |
| 469 |
|
| 470 |
What is the IAB? |
| 471 |
|
| 472 |
The Internet Activities Board (IAB) is the coordinating committee |
| 473 |
for Internet design, engineering and management [<a href="#ref-7" title=""The Internet Activities Board"">7</a>]. IAB members |
| 474 |
are deeply committed to making the Internet function effectively |
| 475 |
and evolve to meet a large scale, high speed future. The chairman |
| 476 |
serves a term of two years and is elected by the members of the |
| 477 |
IAB. The current Chair of the IAB is Vint Cerf. The IAB focuses |
| 478 |
on the TCP/IP protocol suite, and extensions to the Internet |
| 479 |
system to support multiple protocol suites. |
| 480 |
|
| 481 |
The IAB performs the following functions: |
| 482 |
|
| 483 |
1) Sets Internet Standards, |
| 484 |
|
| 485 |
2) Manages the RFC publication process, |
| 486 |
|
| 487 |
3) Reviews the operation of the IETF and IRTF, |
| 488 |
|
| 489 |
4) Performs strategic planning for the Internet, identifying |
| 490 |
long-range problems and opportunities, |
| 491 |
|
| 492 |
5) Acts as an international technical policy liaison and |
| 493 |
representative for the Internet community, and |
| 494 |
|
| 495 |
6) Resolves technical issues which cannot be treated within |
| 496 |
the IETF or IRTF frameworks. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">User Services Working Group [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 503 |
|
| 504 |
|
| 505 |
The IAB has two principal subsidiary task forces: |
| 506 |
|
| 507 |
1) Internet Engineering Task Force (IETF) |
| 508 |
|
| 509 |
2) Internet Research Task Force (IRTF) |
| 510 |
|
| 511 |
Each of these Task Forces is led by a chairman and guided by a |
| 512 |
Steering Group which reports to the IAB through its chairman. For |
| 513 |
the most part, a collection of Research or Working Groups carries |
| 514 |
out the work program of each Task Force. |
| 515 |
|
| 516 |
All decisions of the IAB are made public. The principal vehicle |
| 517 |
by which IAB decisions are propagated to the parties interested in |
| 518 |
the Internet and its TCP/IP protocol suite is the Request for |
| 519 |
Comments (RFC) note series and the Internet Monthly Report. |
| 520 |
|
| 521 |
What is the IANA? |
| 522 |
|
| 523 |
The task of coordinating the assignment of values to the |
| 524 |
parameters of protocols is delegated by the Internet Activities |
| 525 |
Board (IAB) to the Internet Assigned Numbers Authority (IANA). |
| 526 |
These protocol parameters include op-codes, type fields, terminal |
| 527 |
types, system names, object identifiers, and so on. The "Assigned |
| 528 |
Numbers" Request for Comments (RFC) [<a href="#ref-1" title=""Assigned Numbers"">1</a>] documents the currently |
| 529 |
assigned values from several series of numbers used in network |
| 530 |
protocol implementations. Internet addresses and Autonomous |
| 531 |
System numbers are assigned by the Network Information Center at |
| 532 |
SRI International. This responsibility has been delegated by the |
| 533 |
IANA to the DDN NIC which serves as the Internet Registry. The |
| 534 |
IANA is located at USC/Information Sciences Institute. |
| 535 |
|
| 536 |
Current types of assignments listed in Assigned Numbers and |
| 537 |
maintained by the IANA are: |
| 538 |
|
| 539 |
Address Resolution Protocol Parameters |
| 540 |
ARPANET and MILNET X.25 Address Mappings |
| 541 |
ARPANET and MILNET Logical Addresses |
| 542 |
ARPANET and MILNET Link Numbers |
| 543 |
BOOTP Parameters and BOOTP Extension Codes |
| 544 |
Domain System Parameters |
| 545 |
IANA Ethernet Address Blocks |
| 546 |
Ethernet Numbers of Interest |
| 547 |
IEEE 802 Numbers of Interest |
| 548 |
Internet Protocol Numbers |
| 549 |
Internet Version Numbers |
| 550 |
IP Time to Live Parameter |
| 551 |
IP TOS Parameters |
| 552 |
Machine Names |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">User Services Working Group [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 559 |
|
| 560 |
|
| 561 |
Mail Encryption Types |
| 562 |
Multicast Addresses |
| 563 |
Network Management Parameters |
| 564 |
Point-to-Point Protocol Field Assignments |
| 565 |
PRONET 80 Type Numbers |
| 566 |
Port Assignments |
| 567 |
Protocol and Service Names |
| 568 |
Protocol/Type Field Assignments |
| 569 |
Public Data Network Numbers |
| 570 |
Reverse Address Resolution Protocol Operation Codes |
| 571 |
TELNET Options |
| 572 |
Terminal Type Names |
| 573 |
Unix Ports |
| 574 |
X.25 Type Numbers |
| 575 |
|
| 576 |
For more information on number assignments, contact [email protected]. |
| 577 |
|
| 578 |
What is a NIC? What is a NOC? |
| 579 |
|
| 580 |
"NIC" stands for Network Information Center. It is an |
| 581 |
organization which provides network users with information about |
| 582 |
services provided by the network. |
| 583 |
|
| 584 |
"NOC" stands Network Operations Center. It is an organization |
| 585 |
that is responsible for maintaining a network. |
| 586 |
|
| 587 |
For many networks, especially smaller, local networks, the |
| 588 |
functions of the NIC and NOC are combined. For larger networks, |
| 589 |
such as mid-level and backbone networks, the NIC and NOC |
| 590 |
organizations are separate, yet they do need to interact to fully |
| 591 |
perform their functions. |
| 592 |
|
| 593 |
What is "The NIC"? |
| 594 |
|
| 595 |
"The NIC" is the Defense Data Network, Network Information Center |
| 596 |
(DDN NIC) at SRI International, which is a network information |
| 597 |
center which holds a primary repository for RFCs and Internet |
| 598 |
Drafts. The host name is NIC.DDN.MIL. Shadow copies of the RFCs |
| 599 |
and the Internet Drafts are maintained by the NSFNET on |
| 600 |
NIS.NSF.NET. |
| 601 |
|
| 602 |
The DDN NIC also provides various user assistance services for DDN |
| 603 |
users; contact [email protected] or call 1-800-235-3155 for more |
| 604 |
information. In addition, the DDN NIC is the Internet |
| 605 |
registration authority for the root domain and several top and |
| 606 |
second level domains; maintains the official DoD Internet Host |
| 607 |
Table; is the site of the Internet Registry (IR); and maintains |
| 608 |
the WHOIS database of network users, hosts, domains, networks, and |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">User Services Working Group [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 615 |
|
| 616 |
|
| 617 |
Points of Contact. |
| 618 |
|
| 619 |
What is the IR? |
| 620 |
|
| 621 |
The Internet Registry (IR) is the organization that is responsible |
| 622 |
for assigning identifiers, such as IP network numbers and |
| 623 |
autonomous system numbers, to networks. The IR also gathers and |
| 624 |
registers such assigned information. The IR may, in the future, |
| 625 |
allocate the authority to assign network identifiers to other |
| 626 |
organizations; however, it will continue to gather data regarding |
| 627 |
such assignments. At present, the DDN NIC at SRI International |
| 628 |
serves as the IR. |
| 629 |
|
| 630 |
What is the IETF? |
| 631 |
|
| 632 |
The Internet has grown to encompass a large number of widely |
| 633 |
geographically dispersed networks in academic and research |
| 634 |
communities. It now provides an infrastructure for a broad |
| 635 |
community with various interests. Moreover, the family of |
| 636 |
Internet protocols and system components has moved from |
| 637 |
experimental to commercial development. To help coordinate the |
| 638 |
operation, management and evolution of the Internet, the IAB |
| 639 |
established the Internet Engineering Task Force (IETF). |
| 640 |
|
| 641 |
The IETF is chaired by Phill Gross and managed by its Internet |
| 642 |
Engineering Steering Group (IESG). The IETF is a large open |
| 643 |
community of network designers, operators, vendors, and |
| 644 |
researchers concerned with the Internet and the Internet protocol |
| 645 |
suite. It is organized around a set of several technical areas, |
| 646 |
each managed by a technical area director. In addition to the |
| 647 |
IETF Chairman, the area directors make up the IESG membership. |
| 648 |
|
| 649 |
The IAB has delegated to the IESG the general responsibility for |
| 650 |
making the Internet work and for the resolution of all short- and |
| 651 |
mid-range protocol and architectural issues required to make the |
| 652 |
Internet function effectively. |
| 653 |
|
| 654 |
What is the IRTF? |
| 655 |
|
| 656 |
To promote research in networking and the development of new |
| 657 |
technology, the IAB established the Internet Research Task Force |
| 658 |
(IRTF). |
| 659 |
|
| 660 |
In the area of network protocols, the distinction between research |
| 661 |
and engineering is not always clear, so there will sometimes be |
| 662 |
overlap between activities of the IETF and the IRTF. There is, in |
| 663 |
fact, considerable overlap in membership between the two groups. |
| 664 |
This overlap is regarded as vital for cross-fertilization and |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">User Services Working Group [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 671 |
|
| 672 |
|
| 673 |
technology transfer. |
| 674 |
|
| 675 |
The IRTF is a community of network researchers, generally with an |
| 676 |
Internet focus. The work of the IRTF is governed by its Internet |
| 677 |
Research Steering Group (IRSG). The chairman of the IRTF and IRSG |
| 678 |
is David Clark. |
| 679 |
|
| 680 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Questions About Services</span> |
| 681 |
|
| 682 |
How do I find someone's electronic mail address? |
| 683 |
|
| 684 |
There are a number of directories on the Internet; however, all of |
| 685 |
them are far from complete. The largest directories are the WHOIS |
| 686 |
database at the DDN NIC, the PSInet White Pages, and KNOWBOT. |
| 687 |
Generally, it is still necessary to ask the person for his or her |
| 688 |
email address. |
| 689 |
|
| 690 |
How do I use the WHOIS program at the DDN NIC? |
| 691 |
|
| 692 |
To use the WHOIS program to search the WHOIS database at the DDN |
| 693 |
NIC, TELNET to the NIC host, NIC.DDN.MIL. There is no need to |
| 694 |
login. Type "whois" to call up the information retrieval program. |
| 695 |
Next, type the name of the person, host, domain, network, or |
| 696 |
mailbox for which you need information. If you are only typing |
| 697 |
part of the name, end your search string with a period. Type |
| 698 |
"help" for a more in-depth explanation of what you can search for |
| 699 |
and how you can search. If you have trouble, send a message to |
| 700 |
[email protected] or call 1-800-235-3155. Bug reports can be sent |
| 701 |
to [email protected] and suggestions for improvements to the |
| 702 |
program can be sent to [email protected]. |
| 703 |
|
| 704 |
How do I become registered in the DDN NIC's WHOIS database? |
| 705 |
|
| 706 |
If you would like to be listed in the WHOIS database, you must |
| 707 |
have an electronic mailbox accessible from the Internet. First |
| 708 |
obtain the file NETINFO:USER-TEMPLATE.TXT. You can either |
| 709 |
retrieve this file via anonymous FTP from NIC.DDN.MIL or get it |
| 710 |
through electronic mail. To obtain the file via electronic mail, |
| 711 |
send a message to [email protected] and put the file name in the |
| 712 |
subject line of the message; that is, "Subject: NETINFO USER- |
| 713 |
TEMPLATE.TXT". The file will be returned to you overnight. |
| 714 |
|
| 715 |
Fill out the name and address information requested in the file |
| 716 |
and return it to [email protected]. Your application will be |
| 717 |
processed and you will be added to the database. Unless you are |
| 718 |
an official Point of Contact for a network entity registered at |
| 719 |
the DDN NIC, the DDN NIC will not regularly poll you for updates, |
| 720 |
so you should remember to send corrections to your information as |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">User Services Working Group [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 727 |
|
| 728 |
|
| 729 |
your contact data changes. |
| 730 |
|
| 731 |
How do I use the White Pages at PSI? |
| 732 |
|
| 733 |
Performance Systems International, Inc. (PSI), sponsors a White |
| 734 |
Pages Pilot Project that collects personnel information from |
| 735 |
member organizations into a database and provides online access to |
| 736 |
that data. This effort is based on the OSI X.500 Directory |
| 737 |
standard. |
| 738 |
|
| 739 |
To access the data, TELNET to WP.PSI.COM and login as "fred" (no |
| 740 |
password is necessary). You may now look up information on |
| 741 |
participating organizations. The program provides help on usage. |
| 742 |
For example, typing "help" will show you a list of commands, |
| 743 |
"manual" will give detailed documentation, and "whois" will |
| 744 |
provide information regarding how to find references to people. |
| 745 |
For a list of the organizations that are participating in the |
| 746 |
pilot project by providing information regarding their members, |
| 747 |
type "whois -org *". |
| 748 |
|
| 749 |
For more information, send a message to [email protected]. |
| 750 |
|
| 751 |
How do I use the Knowbot Information Service? |
| 752 |
|
| 753 |
The Knowbot Information Service is a white pages "meta-service" |
| 754 |
that provides a uniform interface to heterogeneous white pages |
| 755 |
services in the Internet. Using the Knowbot Information Service, |
| 756 |
you can form a single query that can search for white pages |
| 757 |
information from the NIC WHOIS service, the CSNET WHOIS service, |
| 758 |
the PSI White Pages Pilot Project, and MCI Mail, among others, and |
| 759 |
have the responses displayed in a single, uniform format. |
| 760 |
|
| 761 |
Currently, the Knowbot Information Service can be accessed through |
| 762 |
TELNET to port 185 on hosts nri.reston.va.us and sol.bucknell.edu. |
| 763 |
From a UNIX host, use "telnet nri.reston.va.us 185". There is |
| 764 |
also an electronic mail interface avaliable by sending mail to |
| 765 |
netaddress at either nri.reston.va.us or sol.bucknell.edu. |
| 766 |
|
| 767 |
The commands "help" and "man" summarize the command interface. |
| 768 |
Simply entering a user name at the prompt searches a default list |
| 769 |
of Internet directory services for the requested information. |
| 770 |
Organization and country information can be included thorgh the |
| 771 |
syntax: "[email protected]". For example, the queries |
| 772 |
"droms@bucknell" and "[email protected]" are both valid. Note that |
| 773 |
these are not Domain Names, but rather a syntax to specify an |
| 774 |
organization and a country for the search. |
| 775 |
|
| 776 |
The default list of directory services currently includes the |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">User Services Working Group [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 783 |
|
| 784 |
|
| 785 |
whois services at the SRI NIC and the CSNET NIC and the white |
| 786 |
pages service for MCIMail. If an organization is specified, the |
| 787 |
PSI X.500 service is also searched. Other services can be |
| 788 |
requested explicitly. |
| 789 |
|
| 790 |
What is Usenet? What is Netnews? |
| 791 |
|
| 792 |
Usenet and Netnews are common names of a distributed computer |
| 793 |
bulletin board system that some computers on the Internet |
| 794 |
participate in. It is not strictly an Internet service: many |
| 795 |
computers not on the Internet also participate. Netnews can be a |
| 796 |
valuable tool to economize what might otherwise be a large volume |
| 797 |
of traffic from electronic mailing lists. |
| 798 |
|
| 799 |
How do I get on Usenet? How do I get Netnews on my computer? |
| 800 |
|
| 801 |
To get on Usenet, you must acquire the software, which is |
| 802 |
available for some computers at no cost from some anonymous FTP |
| 803 |
sites across the Internet, and you must find an existing Usenet |
| 804 |
site that is willing to support a connection to your computer. In |
| 805 |
many cases, this "connection" merely represents additional traffic |
| 806 |
over existing Internet access channels. |
| 807 |
|
| 808 |
What is anonymous FTP? |
| 809 |
|
| 810 |
Anonymous FTP is a conventional way of allowing you to sign on to |
| 811 |
a computer on the Internet and copy specified public files from it |
| 812 |
[<a href="#ref-3" title=""File Transfer Protocol (FTP)">3</a>]. Some sites offer anonymous FTP to distribute software and |
| 813 |
various kinds of information. You use it like any FTP, but the |
| 814 |
username is "anonymous". Many systems will allow any password and |
| 815 |
request that the password you choose is your userid. If this |
| 816 |
fails, the generic password is usually "guest". |
| 817 |
|
| 818 |
What is "TELNET"? |
| 819 |
|
| 820 |
The term "TELNET" refers to the remote login that's possible on |
| 821 |
the Internet because of the TELNET Protocol [<a href="#ref-9" title=""TELNET Protocol Specification"">9</a>]. The use of this |
| 822 |
term as a verb, as in "telnet to a host" means to establish a |
| 823 |
connection across the Internet from one host to another. Usually, |
| 824 |
you must have an account on the remote host to be able to login to |
| 825 |
it once you've made a connection. However, some hosts, such as |
| 826 |
those offering white pages directories, provide public services |
| 827 |
that do not require a personal account. |
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">User Services Working Group [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Mailing Lists</span> |
| 842 |
|
| 843 |
What is a mailing list? |
| 844 |
|
| 845 |
A mailing list is really nothing more than an alias that has |
| 846 |
multiple destinations. Mailing lists are usually created to |
| 847 |
discuss specific topics. Anybody interested in that topic, may |
| 848 |
(usually) join that list. Some mailing lists have membership |
| 849 |
restrictions, others have message content restrictions, and still |
| 850 |
others are moderated. Most large, "public" mailing lists, such as |
| 851 |
IETF and TCP-IP, have an additional mail address to which requests |
| 852 |
to be added or deleted may be sent. Usually, these are of the |
| 853 |
form listname-request. |
| 854 |
|
| 855 |
There is a "list-of-lists" file available on the host |
| 856 |
ftp.nisc.sri.com that lists most of the major mailing lists, |
| 857 |
describes their primary topics, and explains how to subscribe to |
| 858 |
them. The file is available for anonymous ftp in the netinfo |
| 859 |
directory as interest-groups (that is, the path is: |
| 860 |
netinfo/interest-groups). It can also be obtained via electronic |
| 861 |
mail. Send a message to [email protected] with the body of |
| 862 |
the message reading, "Send netinfo/interest-groups" and the file |
| 863 |
will be returned in moderate size pieces via electronic mail. |
| 864 |
|
| 865 |
How do I contact the administrator of a mailing list rather than |
| 866 |
posting to the entire list? |
| 867 |
|
| 868 |
For every mailing list mentioned in the "interest-groups" file, there |
| 869 |
is a description of how to join the list or send other such |
| 870 |
administrative messages to the person in charge of the list. In |
| 871 |
general, however, it is usually safe to assume that you can send a |
| 872 |
message to an address in the format of ListName-request@domain. The |
| 873 |
convention of having a parallel mailbox conforming to the |
| 874 |
"-request" format is very widely followed. All administrative |
| 875 |
messages regarding using, joining, or quitting the list should be |
| 876 |
sent to that mailbox instead of to the whole list so that the readers |
| 877 |
of the list don't have to read them. |
| 878 |
|
| 879 |
What are some good mailing lists or news groups? |
| 880 |
|
| 881 |
The TCP-IP, IETF, and RFC Distribution lists are primary lists for new |
| 882 |
Internet users who desire further information about current and |
| 883 |
emerging developments in the Internet. The first two lists are |
| 884 |
unmoderated discussion lists, and the latter is an announcement |
| 885 |
service used by the RFC Editor. |
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">User Services Working Group [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 895 |
|
| 896 |
|
| 897 |
How do I subscribe to the TCP-IP mailing list? |
| 898 |
|
| 899 |
To be added to the TCP-IP mailing list, send a message to: |
| 900 |
|
| 901 |
[email protected] |
| 902 |
|
| 903 |
How do I subscribe to the IETF mailing list? |
| 904 |
|
| 905 |
To be added to the IETF mailing list, send a message to: |
| 906 |
|
| 907 |
[email protected] |
| 908 |
|
| 909 |
How do I subscribe to the RFC Distribution list? |
| 910 |
|
| 911 |
To be added to the RFC Distribution list, send a message to: |
| 912 |
|
| 913 |
[email protected] |
| 914 |
|
| 915 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Miscellaneous "Internet lore" questions</span> |
| 916 |
|
| 917 |
What does :-) mean? |
| 918 |
|
| 919 |
In many electronic mail messages, it is sometimes useful to |
| 920 |
indicate that part of a message is meant in jest. It is also |
| 921 |
sometimes useful to communicate emotion which simple words do not |
| 922 |
readily convey. To provide these nuances, a collection of "smiley |
| 923 |
faces" has evolved. If you turn your head sideways to the left, |
| 924 |
:-) appears as a smiling face. Some of the more common faces are: |
| 925 |
|
| 926 |
:-) smile |
| 927 |
|
| 928 |
:) also a smile |
| 929 |
|
| 930 |
:-D laughing |
| 931 |
|
| 932 |
:-} grin |
| 933 |
|
| 934 |
:-] smirk |
| 935 |
|
| 936 |
:-( frown |
| 937 |
|
| 938 |
;-) wink |
| 939 |
|
| 940 |
8-) wide-eyed |
| 941 |
|
| 942 |
:-X close mouthed |
| 943 |
|
| 944 |
:-o oh, no! |
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">User Services Working Group [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 951 |
|
| 952 |
|
| 953 |
What do "btw", "fyi", "imho", "wrt", and "rtfm" mean? |
| 954 |
|
| 955 |
Often commmon expressions are abbreviated in informal network |
| 956 |
postings. These abbreviations stand for "by the way", "for your |
| 957 |
information", "in my humble [or honest] opinion", "with respect |
| 958 |
to", and "read the f*ing manual" (with the "f" word varying |
| 959 |
according to the vehemence of the reader). |
| 960 |
|
| 961 |
What is the "FAQ" list? |
| 962 |
|
| 963 |
This list provides answers to "Frequently Asked Questions" that |
| 964 |
often appear on various Usenet newsgroups. The list is posted |
| 965 |
every four to six weeks to the news.announce.newusers group. It |
| 966 |
is intended to provide a background for new users learning how to |
| 967 |
use the news. As the FAQ list provide new users with the answers |
| 968 |
to such questions, it helps keep the newsgroups themselves |
| 969 |
comparatively free of repetition. Often specific newsgroups will |
| 970 |
have and frequently post versions of a FAQ list that are specific |
| 971 |
to their topics. |
| 972 |
|
| 973 |
Other information is also routinely posted. Here are the subject |
| 974 |
lines of several general information postings provided on Usenet: |
| 975 |
|
| 976 |
Answers to Frequently Asked Questions (the "FAQ" list) |
| 977 |
Introduction to news.announce |
| 978 |
Rules for posting to Usenet |
| 979 |
How to Create a New Newsgroup |
| 980 |
How to Create a New Trial Newsgroup |
| 981 |
A Primer on How to Work With the Usenet Community |
| 982 |
Emily Postnews Answers Your Questions on Netiquette |
| 983 |
Hints on writing style for Usenet |
| 984 |
USENET Software: History and Sources |
| 985 |
List of Active Newsgroups |
| 986 |
Alternative Newsgroup Hierarchies |
| 987 |
How to Construct the Mailpaths File |
| 988 |
Regional Newsgroup Hierarchies |
| 989 |
List of Moderators |
| 990 |
Publicly Accessible Mailing Lists |
| 991 |
List of Periodic Informational Postings |
| 992 |
How to Get Information about Networks |
| 993 |
A Guide to Social Newsgroups and Mailing Lists |
| 994 |
|
| 995 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Suggested Reading</span> |
| 996 |
|
| 997 |
For further information about the Internet and its protocols in |
| 998 |
general, you may choose to obtain copies of the following works: |
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">User Services Working Group [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
Bowers, K., T. LaQuey, J. Reynolds, K. Roubicek, M. Stahl, and A. |
| 1010 |
Yuan, "Where to Start - A Bibliography of General Internetworking |
| 1011 |
Information", <a href="./rfc1175">RFC 1175</a>, FYI 3, CNRI, U Texas, ISI, BBN, SRI, |
| 1012 |
Mitre, August 1990. |
| 1013 |
|
| 1014 |
Comer, D., "Internetworking with TCP/IP: Principles, Protocols, |
| 1015 |
and Architecture", Prentice Hall, New Jersey, 1989. |
| 1016 |
|
| 1017 |
Krol, E., "The Hitchhikers Guide to the Internet", <a href="./rfc1118">RFC 1118</a>, |
| 1018 |
University of Illinois Urbana, September 1989. |
| 1019 |
|
| 1020 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span> |
| 1021 |
|
| 1022 |
[<a id="ref-1">1</a>] Reynolds, J., and J. Postel, "Assigned Numbers", <a href="./rfc1060">RFC 1060</a>, |
| 1023 |
USC/Information Sciences Institute, March 1990. |
| 1024 |
|
| 1025 |
[<a id="ref-2">2</a>] Postel, J., Editor, "IAB Official Protocol Standards", <a href="./rfc1140">RFC 1140</a>, |
| 1026 |
Internet Activities Board, May 1990. |
| 1027 |
|
| 1028 |
[<a id="ref-3">3</a>] Postel, J., and J. Reynolds, "File Transfer Protocol (FTP), <a href="./rfc959">RFC</a> |
| 1029 |
<a href="./rfc959">959</a>, USC/Information Sciences Institute, October 1985. |
| 1030 |
|
| 1031 |
[<a id="ref-4">4</a>] Postel, J., "Internet Protocol - DARPA Internet Program Protocol |
| 1032 |
Specification", <a href="./rfc791">RFC 791</a>, DARPA, September 1981. |
| 1033 |
|
| 1034 |
[<a id="ref-5">5</a>] Postel, J., "Transmission Control Protocol - DARPA Internet |
| 1035 |
Program Protocol Specification", <a href="./rfc793">RFC 793</a>, DARPA, September 1981. |
| 1036 |
|
| 1037 |
[<a id="ref-6">6</a>] Leiner, B., R. Cole, J. Postel, and D. Mills, "The DARPA Internet |
| 1038 |
Protocol Suite", IEEE INFOCOM85, Washington D.C., March 1985. |
| 1039 |
Also in IEEE Communications Magazine, March 1985. Also as |
| 1040 |
ISI/RS-85-153. |
| 1041 |
|
| 1042 |
[<a id="ref-7">7</a>] Cerf, V., "The Internet Activities Board" <a href="./rfc1160">RFC 1160</a>, CNRI, May |
| 1043 |
1990. |
| 1044 |
|
| 1045 |
[<a id="ref-8">8</a>] Postel, J., "Simple Mail Transport Protocol", <a href="./rfc788">RFC 788</a>, |
| 1046 |
USC/Information Sciences Institute, November 1981. |
| 1047 |
|
| 1048 |
[<a id="ref-9">9</a>] Postel, J., and J. Reynolds, "TELNET Protocol Specification", <a href="./rfc854">RFC</a> |
| 1049 |
<a href="./rfc854">854</a>, USC/Information Sciences Institute, May 1983. |
| 1050 |
|
| 1051 |
[<a id="ref-10">10</a>] Postel, J., "Request for Comments on Request for Comments - |
| 1052 |
Instructions to RFC Authors", <a href="./rfc1111">RFC 1111</a>, USC/Information Sciences |
| 1053 |
Institute, August 1989. |
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">User Services Working Group [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Condensed Glossary</span> |
| 1066 |
|
| 1067 |
As with any profession, computers have a particular terminology all |
| 1068 |
their own. Below is a condensed glossary to assist in making some |
| 1069 |
sense of the Internet world. |
| 1070 |
|
| 1071 |
ACM Association for Computer Machinery |
| 1072 |
A group established in 1947 to promote professional |
| 1073 |
development and research on computers. |
| 1074 |
|
| 1075 |
address There are two separate uses of this term in internet |
| 1076 |
networking: "electronic mail address" and "internet |
| 1077 |
address". An electronic mail address is the string |
| 1078 |
of characters that you must give an electronic mail |
| 1079 |
program to direct a message to a particular person. |
| 1080 |
See "internet address" for its definition. |
| 1081 |
|
| 1082 |
AI Artificial Intelligence |
| 1083 |
The branch of computer science which deals with the |
| 1084 |
simulation of human intelligence by computer systems. |
| 1085 |
|
| 1086 |
AIX Advanced Interactive Executive |
| 1087 |
IBM's version of Unix. |
| 1088 |
|
| 1089 |
ANSI American National Standards Institute |
| 1090 |
A group that certifies organizations which develop U.S. |
| 1091 |
standards for the information processing industry. ANSI |
| 1092 |
accredited groups participate in defining network protocol |
| 1093 |
standards. |
| 1094 |
|
| 1095 |
ARP Address Resolution Protocol |
| 1096 |
An Internet protocol which runs on Ethernet and all IEEE |
| 1097 |
802.X LANs which maps internet addresses to MAC addresses. |
| 1098 |
|
| 1099 |
ARPA Advanced Research Projects Agency |
| 1100 |
The former name of what is now called DARPA. |
| 1101 |
|
| 1102 |
ARPANET Advanced Research Projects Agency Network |
| 1103 |
A pioneering long haul network funded by ARPA. It |
| 1104 |
served as the basis for early networking research as |
| 1105 |
well as a central backbone during the development of |
| 1106 |
the Internet. The ARPANET consisted of individual |
| 1107 |
packet switching computers interconnected by leased lines. |
| 1108 |
|
| 1109 |
AS Autonomous System |
| 1110 |
A collection of gateways (routers) under a single |
| 1111 |
administrative authority using a common Interior Gateway |
| 1112 |
Protocol for routing packets. |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">User Services Working Group [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
ASCII American Standard Code for Information Interchange |
| 1122 |
|
| 1123 |
|
| 1124 |
B Byte |
| 1125 |
One character of information, usually eight bits wide. |
| 1126 |
|
| 1127 |
b bit - binary digit |
| 1128 |
The smallest amount of information which may be stored |
| 1129 |
in a computer. |
| 1130 |
|
| 1131 |
BBN Bolt Beranek and Newman, Inc. |
| 1132 |
The Cambridge, MA company responsible for development, |
| 1133 |
operation and monitoring of the ARPANET, and later, |
| 1134 |
the Internet core gateway system, the CSNET Coordination |
| 1135 |
and Information Center (CIC), and NSFNET Network |
| 1136 |
Service Center (NNSC). |
| 1137 |
|
| 1138 |
BITNET Because It's Time Network |
| 1139 |
BITNET has about 2,500 host computers, primarily at |
| 1140 |
universities, in many countries. It is managed by |
| 1141 |
EDUCOM, which provides administrative support and |
| 1142 |
information services. There are three |
| 1143 |
main constituents of the network: BITNET in the United |
| 1144 |
States and Mexico, NETNORTH in Canada, and EARN in |
| 1145 |
Europe. There are also AsiaNet, in Japan, and |
| 1146 |
connections in South America. See CREN. |
| 1147 |
|
| 1148 |
bps bits per second |
| 1149 |
A measure of data transmission speed. |
| 1150 |
|
| 1151 |
BSD Berkeley Software Distribution |
| 1152 |
Term used when describing different versions |
| 1153 |
of the Berkeley UNIX software, as in "4.3BSD |
| 1154 |
UNIX". |
| 1155 |
|
| 1156 |
|
| 1157 |
catenet A network in which hosts are connected to networks |
| 1158 |
with varying characteristics, and the networks |
| 1159 |
are interconnected by gateways (routers). The |
| 1160 |
Internet is an example of a catenet. |
| 1161 |
|
| 1162 |
CCITT International Telegraph and Telephone |
| 1163 |
Consultative Committee |
| 1164 |
|
| 1165 |
core gateway |
| 1166 |
Historically, one of a set of gateways (routers) |
| 1167 |
operated by the Internet Network Operations Center |
| 1168 |
at BBN. The core gateway system forms a central part |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">User Services Working Group [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
of Internet routing in that all groups had to advertise |
| 1178 |
paths to their networks from a core gateway. |
| 1179 |
|
| 1180 |
CREN The Corporation for Research and Educational Networking |
| 1181 |
BITNET and CSNET have recently merged to form CREN. |
| 1182 |
|
| 1183 |
CSNET Computer + Science Network |
| 1184 |
A large data communications network for institutions doing |
| 1185 |
research in computer science. It uses several different |
| 1186 |
protocols including some of its own. CSNET sites include |
| 1187 |
universities, research laboratories, and commercial |
| 1188 |
companies. See CREN. |
| 1189 |
|
| 1190 |
|
| 1191 |
DARPA U.S. Department of Defense Advanced Research Projects Agency |
| 1192 |
The government agency that funded the ARPANET and later |
| 1193 |
started the Internet. |
| 1194 |
|
| 1195 |
datagram |
| 1196 |
The unit transmitted between a pair of internet modules. |
| 1197 |
The Internet Protocol provides for transmitting blocks of |
| 1198 |
data, called datagrams, from sources to destinations. |
| 1199 |
The Internet Protocol does not provide a reliable |
| 1200 |
communication facility. There are no acknowledgements |
| 1201 |
either end-to-end or hop-by-hop. There is no error |
| 1202 |
control for data, only a header checksum. There are |
| 1203 |
no retransmissions. There is no flow control. See IP. |
| 1204 |
|
| 1205 |
DCA Defense Communications Agency |
| 1206 |
The government agency responsible for installation of |
| 1207 |
the Defense Data Network (DDN), including the ARPANET |
| 1208 |
and MILNET lines and PSNs. Currently, DCA administers |
| 1209 |
the DDN, and supports the user assistance and network |
| 1210 |
registration services of the DDN NIC. |
| 1211 |
|
| 1212 |
DDN Defense Data Network |
| 1213 |
Comprises the MILNET and several other DoD networks. |
| 1214 |
|
| 1215 |
DDN NIC The network information center at SRI International. |
| 1216 |
It is the primary repository for RFCs and Internet Drafts, |
| 1217 |
as well as providing other services. |
| 1218 |
|
| 1219 |
DEC Digital Equipment Corporation |
| 1220 |
|
| 1221 |
DECnet Digital Equipment Corporation network |
| 1222 |
A networking protocol for DEC computers and network devices. |
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">User Services Working Group [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
default route |
| 1234 |
A routing table entry which is used to direct any data |
| 1235 |
addressed to any network numbers not explicitly listed |
| 1236 |
in the routing table. |
| 1237 |
|
| 1238 |
DNS The Domain Name System is a mechanism used in |
| 1239 |
the Internet for translating names of host computers |
| 1240 |
into addresses. The DNS also allows host computers |
| 1241 |
not directly on the Internet to have registered |
| 1242 |
names in the same style, but returns the electronic |
| 1243 |
mail gateway which accesses the non-Internet network |
| 1244 |
instead of an IP address. |
| 1245 |
|
| 1246 |
DOD U.S. Department of Defense |
| 1247 |
|
| 1248 |
DOE U.S. Department of Energy |
| 1249 |
|
| 1250 |
dot address (dotted address notation) |
| 1251 |
Dot address refers to the common notation for Internet |
| 1252 |
addresses of the form A.B.C.D; where each letter represents, |
| 1253 |
in decimal, one byte of the four byte IP address. |
| 1254 |
|
| 1255 |
EARN European Academic Research Network |
| 1256 |
One of three main constituents of BITNET. |
| 1257 |
|
| 1258 |
EBCDIC Extended Binary-coded Decimal Interchange Code |
| 1259 |
|
| 1260 |
EGP Exterior Gateway Protocol |
| 1261 |
A protocol which distributes routing information to the |
| 1262 |
gateways (routers) which connect autonomous systems. |
| 1263 |
|
| 1264 |
Ethernet |
| 1265 |
A network standard for the hardware and data link levels. |
| 1266 |
There are two types of Ethernet: Digital/Intel/Xerox (DIX) |
| 1267 |
and IEEE 802.3. |
| 1268 |
|
| 1269 |
|
| 1270 |
FDDI Fiber Distributed Data Interface |
| 1271 |
FDDI is a high-speed (100Mb) token ring LAN. |
| 1272 |
|
| 1273 |
FIPS Federal Information Processing Standard |
| 1274 |
|
| 1275 |
FTP File Transfer Protocol |
| 1276 |
The Internet standard high-level protocol for |
| 1277 |
transferring files from one computer to another. |
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">User Services Working Group [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
gateway See router |
| 1290 |
|
| 1291 |
GB Gigabyte |
| 1292 |
A unit of data storage size which represents 2^30 (over |
| 1293 |
1 billion) characters of information. |
| 1294 |
|
| 1295 |
Gb Gigabit |
| 1296 |
2^30 bits of information (usually used to express a |
| 1297 |
data transfer rate; as in, 1 gigabit/second = 1Gbps). |
| 1298 |
|
| 1299 |
GNU Gnu's Not UNIX |
| 1300 |
A UNIX-compatible operating system developed by the |
| 1301 |
Free Software Foundation. |
| 1302 |
|
| 1303 |
|
| 1304 |
header The portion of a packet, preceding the actual data, |
| 1305 |
containing source and destination addresses and |
| 1306 |
error-checking fields. |
| 1307 |
|
| 1308 |
host number |
| 1309 |
The part of an internet address that designates which |
| 1310 |
node on the (sub)network is being addressed. |
| 1311 |
|
| 1312 |
HP Hewlett-Packard |
| 1313 |
|
| 1314 |
HYPERchannel |
| 1315 |
High-speed communications link. |
| 1316 |
|
| 1317 |
|
| 1318 |
I/O Input/Output |
| 1319 |
|
| 1320 |
IAB Internet Activities Board |
| 1321 |
The IAB is the coordinating committee for Internet |
| 1322 |
design, engineering and management. |
| 1323 |
|
| 1324 |
IBM International Business Machines Corporation |
| 1325 |
|
| 1326 |
ICMP Internet Control Message Protocol |
| 1327 |
ICMP is an extension to the Internet Protocol. It |
| 1328 |
allows for the generation of error messages, |
| 1329 |
test packets and informational messages related to IP. |
| 1330 |
|
| 1331 |
IEEE Institute for Electrical and Electronics Engineers |
| 1332 |
|
| 1333 |
IETF Internet Engineering Task Force |
| 1334 |
The IETF is a large open community of network designers, |
| 1335 |
operators, vendors, and researchers whose purpose is to |
| 1336 |
coordinate the operation, management and evolution of |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">User Services Working Group [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
the Internet, and to resolve short- and mid-range |
| 1346 |
protocol and architectural issues. It is a major source |
| 1347 |
of proposed protocol standards which are submitted to the |
| 1348 |
Internet Activities Board for final approval. The IETF |
| 1349 |
meets three times a year and extensive minutes of the |
| 1350 |
plenary proceedings are issued. |
| 1351 |
|
| 1352 |
internet |
| 1353 |
internetwork |
| 1354 |
Any connection of two or more local or wide-area networks. |
| 1355 |
|
| 1356 |
Internet |
| 1357 |
The global collection of interconnected local, mid-level and |
| 1358 |
wide-area networks which use IP as the network layer |
| 1359 |
protocol. |
| 1360 |
|
| 1361 |
internet address |
| 1362 |
An assigned number which identifies a host in an internet. |
| 1363 |
It has two or three parts: network number, optional subnet |
| 1364 |
number, and host number. |
| 1365 |
|
| 1366 |
IP Internet Protocol |
| 1367 |
The network layer protocol for the Internet. It is a packet |
| 1368 |
switching, datagram protocol defined in <a href="./rfc791">RFC 791</a>. |
| 1369 |
|
| 1370 |
IRTF Internet Research Task Force |
| 1371 |
The IRTF is a community of network researchers, |
| 1372 |
generally with an Internet focus. The work of the IRTF |
| 1373 |
is governed by its Internet Research Steering Group (IRSG). |
| 1374 |
|
| 1375 |
ISO International Organization for Standardization |
| 1376 |
|
| 1377 |
|
| 1378 |
KB Kilobyte |
| 1379 |
A unit of data storage size which represents 2^10 |
| 1380 |
(1024) characters of information. |
| 1381 |
|
| 1382 |
Kb Kilobit |
| 1383 |
2^10 bits of information (usually used to express a |
| 1384 |
data transfer rate; as in, 1 kilobit/second = 1Kbps = 1Kb). |
| 1385 |
|
| 1386 |
|
| 1387 |
LAN Local Area Network |
| 1388 |
A network that takes advantage of the proximity of computers |
| 1389 |
to offer relatively efficient, higher speed communications |
| 1390 |
than long-haul or wide-area networks. |
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">User Services Working Group [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
LISP List Processing Language |
| 1402 |
A high-level computer language invented by Professor John |
| 1403 |
McCarthy in 1961 to support research into computer based |
| 1404 |
logic, logical reasoning, and artificial intelligence. It |
| 1405 |
was the first symbolic (as opposed to numeric) computer |
| 1406 |
processing language. |
| 1407 |
|
| 1408 |
|
| 1409 |
MAC Medium Access Control |
| 1410 |
For broadcast networks, it is the method which devices use |
| 1411 |
to determine which device has line access at any given |
| 1412 |
time. |
| 1413 |
|
| 1414 |
Mac Apple Macintosh computer. |
| 1415 |
|
| 1416 |
MAN Metropolitan Area Network |
| 1417 |
|
| 1418 |
MB Megabyte |
| 1419 |
A unit of data storage size which represents over |
| 1420 |
2^20 (one million) characters of information. |
| 1421 |
|
| 1422 |
Mb Megabit |
| 1423 |
2^20 bits of information (usually used to express a |
| 1424 |
data transfer rate; as in, 1 megabit/second = 1Mbps). |
| 1425 |
|
| 1426 |
MILNET Military Network |
| 1427 |
A network used for unclassified military production |
| 1428 |
applications. It is part of the DDN and the Internet. |
| 1429 |
|
| 1430 |
MIT Massachusetts Institute of Technology |
| 1431 |
|
| 1432 |
MTTF Mean Time to Failure |
| 1433 |
The average time between hardware breakdown or loss of |
| 1434 |
service. This may be an empirical measurement or a |
| 1435 |
calculation based on the MTTF of component parts. |
| 1436 |
|
| 1437 |
MTTR Mean Time to Recovery (or Repair) |
| 1438 |
The average time it takes to restore service after a |
| 1439 |
breakdown or loss. This is usually an empirical measurement. |
| 1440 |
|
| 1441 |
MVS Multiple Virtual Storage |
| 1442 |
An IBM operating system based on OS/1. |
| 1443 |
|
| 1444 |
|
| 1445 |
NASA National Aeronautics and Space Administration |
| 1446 |
|
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">User Services Working Group [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
NBS National Bureau of Standards |
| 1458 |
Now called NIST. |
| 1459 |
|
| 1460 |
network number |
| 1461 |
The part of an internet address which designates the |
| 1462 |
network to which the addressed node belongs. |
| 1463 |
|
| 1464 |
NFS Network File System |
| 1465 |
A network service that lets a program running on one |
| 1466 |
computer to use data stored on a different computer on |
| 1467 |
the same internet as if it were on its own disk. |
| 1468 |
|
| 1469 |
NIC Network Information Center |
| 1470 |
An organization which provides network users with |
| 1471 |
information about services provided by the network. |
| 1472 |
|
| 1473 |
NOC Network Operations Center |
| 1474 |
An organization that is responsible for maintaining |
| 1475 |
a network. |
| 1476 |
|
| 1477 |
NIST National Institute of Standards and Technology |
| 1478 |
Formerly NBS. |
| 1479 |
|
| 1480 |
NSF National Science Foundation |
| 1481 |
|
| 1482 |
NSFNET National Science Foundation Network |
| 1483 |
The NSFNET is a highspeed "network of networks" which is |
| 1484 |
hierarchical in nature. At the highest level is a network |
| 1485 |
that spans the continental United States. Attached to that |
| 1486 |
are mid-level networks and attached to the mid-levels are |
| 1487 |
campus and local networks. NSFNET also has connections out |
| 1488 |
of the U.S. to Canada, Mexico, Europe, and the Pacific Rim. |
| 1489 |
The NSFNET is part of the Internet. |
| 1490 |
|
| 1491 |
NSFNET Mid-level Level Network |
| 1492 |
A network connected to the highest level of the NSFNET that |
| 1493 |
covers a region of the United States. It is to mid-level |
| 1494 |
networks that local sites connect. The mid-level networks |
| 1495 |
were once called "regionals". |
| 1496 |
|
| 1497 |
OSI Open Systems Interconnection |
| 1498 |
A set of protocols designed to be an international standard |
| 1499 |
method for connecting unlike computers and networks. Europe |
| 1500 |
has done most of the work developing OSI and will probably |
| 1501 |
use it as soon as possible. |
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">User Services Working Group [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
OSI Reference Model |
| 1514 |
An "outline" of OSI which defines its seven layers and |
| 1515 |
their functions. Sometimes used to help describe other |
| 1516 |
networks. |
| 1517 |
|
| 1518 |
OSPF Open Shortest-Path First Interior Gateway Protocol |
| 1519 |
A proposed replacement for RIP. It addresses some |
| 1520 |
problems of RIP and is based upon principles that have |
| 1521 |
been well-tested in non-internet protocols. Originally |
| 1522 |
acronymed as OSPFIGP. |
| 1523 |
|
| 1524 |
|
| 1525 |
packet The unit of data sent across a packet switching network. |
| 1526 |
The term is used loosely. While some Internet |
| 1527 |
literature uses it to refer specifically to data sent |
| 1528 |
across a physical network, other literature views |
| 1529 |
the Internet as a packet switching network |
| 1530 |
and describes IP datagrams as packets. |
| 1531 |
|
| 1532 |
PC Personal Computer |
| 1533 |
|
| 1534 |
PCNFS Personal Computer Network File System |
| 1535 |
|
| 1536 |
POSIX Portable Operating System Interface |
| 1537 |
Operating system based on UNIX. |
| 1538 |
|
| 1539 |
PPP Point-to-Point Protocol |
| 1540 |
The Point-to-Point Protocol (PPP) provides a method for |
| 1541 |
transmitting datagrams over serial point-to-point links. |
| 1542 |
|
| 1543 |
protocol |
| 1544 |
A formal description of message formats and the rules |
| 1545 |
two computers must follow to exchange those messages. |
| 1546 |
Protocols can describe low-level details of |
| 1547 |
machine-to-machine interfaces (e.g., the order in |
| 1548 |
which bits and bytes are sent across a wire) |
| 1549 |
or high-level exchanges between allocation |
| 1550 |
programs (e.g., the way in which two programs |
| 1551 |
transfer a file across the Internet). |
| 1552 |
|
| 1553 |
|
| 1554 |
RFC The Internet's Request for Comments documents series |
| 1555 |
The RFCs are working notes of the Internet research and |
| 1556 |
development community. A document in this series may be on |
| 1557 |
essentially any topic related to computer communication, and |
| 1558 |
may be anything from a meeting report to the specification of |
| 1559 |
a standard. |
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">User Services Working Group [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
RIP Routing Interchange Protocol |
| 1570 |
One protocol which may be used on internets simply to pass |
| 1571 |
routing information between gateways. It is used on may |
| 1572 |
LANs and on some of the NSFNET intermediate level networks. |
| 1573 |
|
| 1574 |
RJE Remote Job Entry |
| 1575 |
The general protocol for submitting batch jobs and |
| 1576 |
retrieving the results. |
| 1577 |
|
| 1578 |
RLOGIN Remote Login |
| 1579 |
A service on internets very similar to TELNET. RLOGIN was |
| 1580 |
invented for use between Berkeley Unix systems on the same |
| 1581 |
LAN at a time when TELNET programs didn't provide all the |
| 1582 |
services users wanted. Berkeley plans to phase it out. |
| 1583 |
|
| 1584 |
router A special-purpose dedicated computer that attaches to |
| 1585 |
two or more networks and routes packets from one |
| 1586 |
network to the other. In particular, an Internet |
| 1587 |
gateway routes IP datagrams among the networks it |
| 1588 |
connects. Gateways route packets to other |
| 1589 |
gateways until they can be delivered to the final |
| 1590 |
destination directly across one physical network. |
| 1591 |
|
| 1592 |
RPC Remote Procedure Call |
| 1593 |
An easy and popular paradigm for implementing the |
| 1594 |
client-server model of distributed computing. |
| 1595 |
|
| 1596 |
|
| 1597 |
server A computer that shares its resources, such as printers |
| 1598 |
and files, with other computers on the network. An |
| 1599 |
example of this is a Network Files System (NFS) |
| 1600 |
Server which shares its disk space with one or more |
| 1601 |
workstations that may not have local disk drives of |
| 1602 |
their own. |
| 1603 |
|
| 1604 |
SLIP Serial Line Internet Protocol |
| 1605 |
SLIP is currently a defacto standard, commonly used for |
| 1606 |
point-to-point serial connections running TCP/IP. It is |
| 1607 |
not an Internet standard but is defined in <a href="./rfc1055">RFC 1055</a>. |
| 1608 |
|
| 1609 |
SMTP Simple Mail Transfer Protocol |
| 1610 |
The Internet standard protocol for transferring |
| 1611 |
electronic mail messages from one computer to another. |
| 1612 |
SMTP specifies how two mail systems interact and the |
| 1613 |
format of control messages they exchange to transfer mail. |
| 1614 |
|
| 1615 |
SNA System Network Architecture |
| 1616 |
IBM's data communications protocol. |
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">User Services Working Group [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
SNMP Simple Network Management Protocol |
| 1626 |
The Simple Network Management Protocol (<a href="./rfc1157">RFC 1157</a>) is the |
| 1627 |
Internet's standard for remote monitoring and management |
| 1628 |
of hosts, routers and other nodes and devices on a network. |
| 1629 |
|
| 1630 |
subnet A portion of a network, which may be a physically independent |
| 1631 |
network, which shares a network address with other portions |
| 1632 |
of the network and is distinguished by a subnet number. A |
| 1633 |
subnet is to a network what a network is to an internet. |
| 1634 |
|
| 1635 |
subnet number |
| 1636 |
A part of the internet address which designates a subnet. |
| 1637 |
It is ignored for the purposes internet routing, but is |
| 1638 |
used for intranet routing. |
| 1639 |
|
| 1640 |
T1 A term for a digital carrier facility used to transmit a |
| 1641 |
DS-1 formatted digital signal at 1.544 megabits per second. |
| 1642 |
|
| 1643 |
T3 A term for a digital carrier facility used to transmit a DS-3 |
| 1644 |
formatted digital signal at 44.746 megabits per second. |
| 1645 |
|
| 1646 |
TCP Transmission Control Protocol |
| 1647 |
A transport layer protocol for the Internet. It is a |
| 1648 |
connection oriented, stream protocol defined by <a href="./rfc793">RFC 793</a>. |
| 1649 |
|
| 1650 |
TCP/IP Transmission Control Protocol/Internet Protocol |
| 1651 |
This is a common shorthand which refers to the suite |
| 1652 |
of application and transport protocols which run over IP. |
| 1653 |
These include FTP, TELNET, SMTP, and UDP (a transport |
| 1654 |
layer protocol). |
| 1655 |
|
| 1656 |
Telenet A public packet-switching network operated by US Sprint. |
| 1657 |
Also known as "SprintNet". |
| 1658 |
|
| 1659 |
TELNET The Internet standard protocol for remote terminal |
| 1660 |
connection service. TELNET allows a user at one site |
| 1661 |
to interact with a remote timesharing system at |
| 1662 |
another site as if the user's terminal was connected |
| 1663 |
directly to the remote computer. |
| 1664 |
|
| 1665 |
THEnet The Texas Higher Education Network, a multiprotocol |
| 1666 |
network connecting most major academic and research |
| 1667 |
institutions in the State of Texas, as well as several |
| 1668 |
institutions in Mexico. |
| 1669 |
|
| 1670 |
Token Ring |
| 1671 |
A type of LAN. Examples are IEEE 802.5, ProNET-10/80 and |
| 1672 |
FDDI. The term "token ring" is often used to denote 802.5 |
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">User Services Working Group [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
Tymnet A public character-switching/packet-switching network |
| 1682 |
operated by British Telecom. |
| 1683 |
|
| 1684 |
|
| 1685 |
UDP User Datagram Protocol |
| 1686 |
A transport layer protocol for the Internet. It is a |
| 1687 |
datagram protocol which adds a level of reliability and |
| 1688 |
multiplexing to IP datagrams. It is defined in <a href="./rfc768">RFC 768</a>. |
| 1689 |
|
| 1690 |
ULTRIX UNIX-based operating system for Digital Equipment Corporation |
| 1691 |
computers. |
| 1692 |
|
| 1693 |
UNIX An operating system developed by Bell Laboratories that |
| 1694 |
supports multiuser and multitasking operations. |
| 1695 |
|
| 1696 |
UUCP UNIX-to-UNIX Copy Program |
| 1697 |
A protocol used for communication between consenting |
| 1698 |
UNIX systems. |
| 1699 |
|
| 1700 |
|
| 1701 |
VMS Virtual Memory System |
| 1702 |
A Digital Equipment Corporation operating system. |
| 1703 |
|
| 1704 |
|
| 1705 |
WAN Wide Area Network |
| 1706 |
|
| 1707 |
WHOIS An Internet program which allows users to query a database of |
| 1708 |
people and other Internet entities, such as domains, |
| 1709 |
networks, and hosts, kept at the NIC. The information for |
| 1710 |
people shows a person's company name, address, phone number |
| 1711 |
and email address. |
| 1712 |
|
| 1713 |
|
| 1714 |
XNS Xerox Network System |
| 1715 |
A data communications protocol suite developed by Xerox. It |
| 1716 |
uses Ethernet to move the data between computers. |
| 1717 |
|
| 1718 |
X.25 A data communications interface specification developed to |
| 1719 |
describe how data passes into and out of public data |
| 1720 |
communications networks. The public networks such as |
| 1721 |
Sprintnet and Tymnet use X.25 to interface to customer |
| 1722 |
computers. |
| 1723 |
|
| 1724 |
|
| 1725 |
<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Security Considerations</span> |
| 1726 |
|
| 1727 |
Security issues are not discussed in this memo. |
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">User Services Working Group [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc1206">RFC 1206</a> FYI Q/A - for New Internet Users February 1991</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
<span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>. Authors' Addresses</span> |
| 1738 |
|
| 1739 |
Gary Scott Malkin |
| 1740 |
FTP Software, Inc. |
| 1741 |
26 Princess Street |
| 1742 |
Wakefield, MA 01880 |
| 1743 |
|
| 1744 |
Phone: (617) 246-0900 |
| 1745 |
|
| 1746 |
EMail: [email protected] |
| 1747 |
|
| 1748 |
|
| 1749 |
April N. Marine |
| 1750 |
SRI International |
| 1751 |
Network Information Systems Center |
| 1752 |
333 Ravenswood Avenue, EJ294 |
| 1753 |
Menlo Park, CA 94025 |
| 1754 |
|
| 1755 |
Phone: (415) 859-5318 |
| 1756 |
|
| 1757 |
EMail: [email protected] |
| 1758 |
|
| 1759 |
|
| 1760 |
|
| 1761 |
|
| 1762 |
|
| 1763 |
|
| 1764 |
|
| 1765 |
|
| 1766 |
|
| 1767 |
|
| 1768 |
|
| 1769 |
|
| 1770 |
|
| 1771 |
|
| 1772 |
|
| 1773 |
|
| 1774 |
|
| 1775 |
|
| 1776 |
|
| 1777 |
|
| 1778 |
|
| 1779 |
|
| 1780 |
|
| 1781 |
|
| 1782 |
|
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
User Services Working Group [Page 32] |
| 1789 |
</pre> |