Draft

[Sally Hambridge <[e-mail]>]

OK here it is.  Let's take a week to check this, make suggestions,
and get references right, then send it in as a draft.  

Looking forward to hearing from all:

Sally
[e-mail]


IETF RUN Working Group
Internet-Draft
draft-ietf-run-netiquette-guide-00.txt
Expires October 24, 1995

                           Netiquette Guidelines

Status of This Memo

     This document is an Internet-Draft.  Internet-Drafts are working
     documents of the Internet Engineering Task Force (IETF), its
     areas, and its working groups.  Note that other groups may also
     distribute working documents as Internet-Drafts.

     Internet-Drafts are draft documents valid for a maximum of six
     months and may be updated, replaced, or obsoleted by other
     documents at any time.  It is inappropriate to use Internet-
     Drafts as reference material or to cite them other than as
     ``work in progress.''

     To learn the current status of any Internet-Draft, please check
     the ``1id-abstracts.txt'' listing contained in the Internet-
     Drafts Shadow Directories on ftp.is.co.za (Africa),
     nic.nordu.net (Europe), munnari.oz.au (Pacific Rim),
     ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast).

Abstract

This document provides a minimum set of guidelines for Network
Etiquette (Netiquette) which organizations may take and adapt for 
their own use.  It also provides a minimum set for individuals, both
users and administrators.

1.0  Introduction

As the Internet grows and as the population of people using the
Internet changes from people who have "grown-up" with the Internet,
who are primarily technically minded, and understand the nature of
the transport and the protocols to those new to the environment, those
unfamiliar with the culture, and those who don't need to know about
transport or protocols ("Newbies").  In order to ameliorate the impact
of the new users, this Guide offers a minimum set of behaviors which
organizations and individuals may take and adapt for their own use.
We've organized this material into 3 sections: One-to-one
communication, which includes mail and talk; One-to-many
communications, which includes mailing lists, Usenet News groups, MOOS
and MUDS; and Information Services, which includes ftp, WWW, Wais, and
Gopher.   Finally, we have a Selected Bibliography, which may be used
for reference.



2.0  One-to-One Communication (eletronic mail, talk)

We define one-to-one communications as those in which a person is
communicating with another person as if face-to-face: a dialog.  In
general, rules of common courtesy for interaction with people should
be in force for any situation, and on the Internet it's doubly
important where, for example, body language and tone of voice must be 
inferred. For more information on Netiquette for communicating
via electronic mail and talk, check references [x,xx,xxx,xxxx] in the
Selected Bibliography. 

2.1 User Guidelines

2.1.1 For mail:

   - Unless you have your own Internet access through an Internet provider,
     be sure to check with your employer about ownership of electronic 
     mail. Laws about the ownership of electronic mail vary from place
     to place.   

   - Unless you are using an encryption device (hardware or software),
     you should assume that mail on the Internet is not secure.  Never put
     in a mail message anything you would not put on a postcard. 

   - Respect the copyright on material that you reproduce.  Almost
     every country has copyright laws.  

   - Ask permission before forwarding, posting, and inserting anything
     from a message you have received.

   - Never send chain letters on the Internet.  In general, this
     causes hostility and may lead your system administrator to
     revoke your Internet privileges.  

  - A good rule of thumb:  Be conservative in what you send and
    liberal in what you receive.  You should not send heated messages
    (we call these "flames") even if you are provoked.  On the other
    hand, you shouldn't be surprised if you get flamed, and it's
    prudent not to respond to flames.

  - In general, it's a good idea to at least check all your mail
    headers before responding to a message.  Sometimes a person who
    asks you for help (or clarification) will send another message
    which effectively says "Never Mind".

  - Make things easy for the recipient.  Many mailers strip header
    information which includes your return address.  In order to
    ensure that people know who you are, be sure to include a line
    or two at the end of your message with contact information.  You
    can create this file ahead of time and add it to the end of your
    messages.  (Some mailers do this automatically.)  In Internet
    parlance, this is known as a ".sig" or "signature" file.  Your
    .sig file takes the place of your business card.

  - In general, most people who use the Internet for business don't
    have the time to answer general questions about the Internet and
    its workings.  Don't send unsolicited mail asking for information
    to people whose names you might have seen in RFCs or on mailing
    lists.  

  - Remember that people with whom you communicate are located across
    the globe.  If you send a message to which you want an immediate
    response, the person receiving it might be at home asleep when it
    arrives.  Give her a chance to wake up, come to work, and login
    before assuming the mail didn't arrive or that she doesn't care.

  - Verify all addresses before initiating long or personal discourse.
    It's also a good practice to include the word "Long" in the
    subject header so the recipient knows the message will take time
    to read and respond to.

  - Know who to contact for help.  Usually you will have resources
    close at hand.  Check locally for people who can help you with
    software and system problems.  Also, know who to go to if you
    receive anything questionable or illegal.

   - Remember that the recipient is a human being whose culture,
     language, and humor have different points of reference from your
     own.  Remember that date formats, measurements, and idioms may
     not travel well.   Be especially careful with sarcasm. 

   - Use mixed case.  UPPER CASE LOOKS AS IF YOU'RE SHOUTING. 

   - Use symbols for emphasis.  That *is* what I meant.  Use underscores
     for underlining. _War_and_Peace_ is my favorite book.  

   - Use smileys to indicate tone of voice, but use them sparingly. 
     ;-) is an example of a smiley (Look sideways).

   - Wait overnight to send emotional responses to messages.  If you
     have really strong feelings about a subject, indicate it via
     FLAME ON/OFF enclosures.  

   - Do not include control characters or non-ASCII attachments in
     messages unless they are MIME attachments. If you send encoded
     messages make sure the recipient can decode them.   

   - Be brief without being overly terse.  When replying to a message,
     include enough original material to be understood.  

   - Limit line length to fewer than 65 characters and end a line
     with a carriage return.  

   - Mail should have a subject heading which reflects 
     the content of the message.  

   - If you include a signature keep it short. 
     Remember that many people pay for connectivity by the
     minute, and the longer your message is, the more they pay. 

   - Just as mail (today) may not be private, mail (and news) are (today)
     subject to forgery and spoofing of various degrees of detectablity. 
     Apply common sense "reality checks" before assuming a message is valid.
     

   - If you think the importance of a message justifies it, immediately reply
     briefly to an e-mail message, to let the sender know you got it, even if
     you will send a longer reply later.  

  - Delivery receipts, non-delivery notices, and vacation programs
    are neither totally standardized nor totally reliable across the 
    range of systems connected to Internet mail.  They are invasive 
    when sent to mailing lists, and some people consider delivery
    receipts an invasion of privacy.   

  - "Reasonable" expectations for conduct via e-mail depend on your
    relationship to a person and the context of the communication. Norms
    learned in a particular e-mail environment may not apply in general 
    to your e-mail communication with people across the Internet.  

  - The cost of delivering an e-mail message is, on the average, paid about
    equally by the sender and the recipient (or their organizations). This is
    unlike other media such as physical mail, telephone, TV, or radio.  Sending
    someone mail may also cost them in other specific ways like network
    bandwidth, disk space or CPU usage.  This is a fundamental enconomic reason
    why unsolicited e-mail advertising is unwelcome (and is forbidden in many
    contexts).  

  - Know how large a message you are sending.  Including large files such as
    Postscript files or programs may make your message so large that it 
    cannot be delivered or at least consumes excessive resources.  Consider 
    file transfer as an alternative.

  - If your mail system allows you to forward mail, beware the dreaded 
    forwarding loop.  Be sure you haven't set up forwarding on several 
    hosts so that a message sent to you gets into an endless loop from 
    one computer to the next to the next.


2.1.2 For talk:

   - Use mixed case  and proper punctuation, as though you were typing
     a letter or sending mail.

   - Don't run off the end of a line and simply let the terminal wrap;
     use a Carriage Return (CR) at the end of the line.

   - Leave some margin; don't write to the edge of the screen.

   - Use 2 CRs to indicate that you are done and the other person may
     start typing.  (blank line).

   - Always say goodby, or some other farewell, and wais to see a 
     farewell from the other person before killing the session.

   - Remember that talk is an interruption to the other person.  Only
     use as appropriate.

   - Talk shows your typing ability.  If you type slowly and make mistakes
     when typing it is often not worth the time of trying to correct, as
     the other person can usually see what you meant.

2.2  Administrator Issues

  - Handle requests in a timely fashion.

  - Respond promptly to people who have concerns about receiving 
    improper or illegal messages.  

  - Explain any system rules, such as disk quotas, to your users.  
    Make sure they understand implications of requesting files by 
    mail such as: Filling up disks; running up phone bills, delaying
    mail, etc.

  - Make sure you have "Postmaster" aliased.



3.0  One to Many Communication (Mailing Lists, Usenet News)

Anytime you engage in One-to-Many communications, all the rules 
for mail should also apply.  After all, communicating with many people
via one mail message or post is quite analogous to communicating with
one person with the exception of possibly offending a great
many more people than in one-to-one communication.  Therefore, it's
quite important to know as much as you can about the audience of your
message.   


3.1 User Guidelines 

3.1.1 General Guidelines for mailing lists and Usenet News

   - Read both mailing lists and newsgroups for 1-2 months before
     you post anything.  This helps you to get an understanding of 
     the culture of the group.  

   - Do not blame the system administrator for the behavior of the
     system users.  

   - Consider that a large audience will see your posts.
     That may include your present or your next boss.  Take
     care in what you write.  Remember too, that mailing lists and
     Newsgroups are frequently archived, and that your words may be
     stored for a very long time in a place to which many people have
     access.

   - Assume that individuals speak for themselves, and what they
     say does not represent their organization (unless stated explicitly).

   - Remember that both mail and news take system resources.  Pay attention
     to any specific rules covering their uses your organization may have.
     
  - In general, it's not possible to retreive messages once you have
    sent them.  Even your system administrator will not be able to get
    a message back once you have sent it.  This means you must make
    sure you really want the message to go as you have written it. 

  - Messages and articles should be brief and to the point.  Don't 
     wander off-topic, don't ramble and don't send mail or post
     messages soley to point out other people's errors in typing
     or spelling.  These, more than any other behavior, mark you
     as an immature beginner. 

  - Advertising is welcomed on some lists and Newsgroups, and abhorred
    on others!  This is another example of knowing your audience
    before you post.  Unsolicited adversiting which is completely
    off-topic will most certainly guarantee you get hate mail.

  - If you are posting a reply to a message or a posting be sure you
    summarize the original at the top of the message.  This will make
    sure readers have a context when they start to read your response.

  - Again, be sure to have a signature which you attach to your
    message.  This will guarantee that any peculiarities of mailers or
    newsreaders which strip header information will not delete the
    only reference in the message of how people may reach you.

 - Be careful when you reply to messages or postings.  Frequently
   replies are sent back to the address which orginated the post - 
   which in many cases is the address of a list or group!  You may
   accidently send a personal response to a great many people,
   embarrassing all involved.  It's best to type in the address 
   instead of relying on "reply."

  - If you find a personal message has gone to a list or group, send
    an apology.

  - If you should find yourself in a disagreement with one person,
    take your responses to each other via mail rather than continue to
    send messages to the list or the group.  If you are debating a
    point on which the group might have some interest, you may
    summarize for them later.

  - Avoid sending messages or posting articles which are no more than
    gratuitous replies to replies.  

  - There are Newsgroups and Mailing Lists which discuss topics
    of  wide varieties of interests.  These represent a diversity of
    lifestyles, religions, and cultures.  Posting articles or sending
    messages to a group whose point of view is offensive to you 
    simply to tell them they are offensive is not acceptable.
    Sexually and racially harrassing messages may also have legal
    implications.  
      

3.1.2  Mailing List Guidelines
There are a number of places to find information about what mailing
lists exists on the Internet and how to join them.  Make sure you
understand your organization's policy about joining these lists and
posting to them.  In general it is always better to check local
resources first before trying to find information via the Internet.
Nevertheless, there are a set of files posting periodically to
news.xxxx which list the Internet mailing lists and how to subscribe
to them.  This is an invaluable resource for finding lists on any
topic.  See also references [xxxx,xxxxx,xxxxxx] in the Selected
Bibliography.


   - Send subscribe and unsubscribe messages to the appropriate 
     address.  Although some mailing list software is smart enough
     to catch these, not all can ferret these out.  It is your
     responsibility to learn how the lists work, and to send the
     correct mail to the correct place.  

   - Save the subscription messages for any lists you join.  These
     usually tell you how to unsubscribe as well.   

   - The auto-reply feature of many mailers is useful for in-house
     communication, but quite annoying when sent to entire mailing
     lists.  Do not use this feature when subscribed to Internet 
     lists.

   - Don't send large files to mailing lists when URLs or pointers
     to ftp-able versions will do.  

   - Consider unsubscribing or setting a "nomail" option (when it's
     available) when you cannot check your mail for an extended 
     period. 

   - When sending a message to more than 1 mailing list, especially
     if the lists are closely related, apologize for cross-posting.

   - If you survey, be sure to post a summary.  When doing so, truly
     summarize rather than send a cumulation of the messages you receive.

  - Some mailing lists are private.  Do not send mail to these lists
    uninvited.  Do not report mail from these lists to a wider 
    audience.

  - If you are caught in an argument, keep the discussion focused on
    issues rather than the personalities involved.

3.1.3  Usenet News Guidelines
Usenet News is a globally distributed system which allows people to
communicate on topics of specific interest.  It is divided into a
hierarchy, with the major divisions being: sci - science related
discussions; comp - computer related discussions; news - for
discussions which center around Usenet News itself; rec - recreational
activities; soc - social issues; talk - long-winded never-ending
discussions; biz - business related postings; and alt - the alternate
hierarchy.  Alt is so named because creating an alt group does not go
through the same process as creating a group in the other parts of the
hierarchy.  Additionally, the Alt groups contain some discussions of
alternate life-styles.  For longer discussions on News see references
[yy,yyy,yyyy] in the Selected Bibliography.

   - Read all of a thread before posting replies.  Avoid posting "Me Too"
     messages, where content is limited to agreement with previous posts.
     Content of a follow-up post should exceed quoted content.

   - Send mail when an answer to a question is for 1 person only.  Remember
     that News has global distribution and the whole world probably is NOT
     interested in a personal response.  However, don't hesitate to post
     when something will be of general interest to the Newsgroup participants.

   - Understand the difference between posting and follow-ups.  
     Posting means posting a new article.  Follow-up means commenting
     on a thread in progress.  Always check the follow-ups line in the
     header to ensure the groups receiving your post are the ones you 
     expect. 

   - Check the "Distribution" section of the header, but don't
     depend on it.  Due to the complex method by which News is
     distributed it is unreliable.  

   - If you feel an article will be of interest to more than 1 Newsgroup,
     be sure to CROSSPOST the article rather than individually post it
     to those groups.  In general, probably only 5-6 groups will have
     similar enough interests to warrant this.  

   - Consider using Reference sources (Computer Manuals, Newspapers,
     help files) before posting a question.  Asking a Newsgroup where
     answers are readily available elsewhere generates grumpy "RTFM"
     (read the fine manual - although a more vulgar meaning of the
     word beginning with "f" is usually implied) messages.

   - Although there are Newsgroups which welcome advertising, 
     in general it is considered nothing less than criminal
     to adverstise off-topic products.  Sending an advertisment
     to each and every group will pretty much guarantee your loss of
     connectivity.  

   - If you discover an error in your post, cancel it as soon as 
     possible. 

   - If you've posting something and don't see it immediately,
     don't assume it's failed and post it again. 

   -  Some groups permit (and some welcome) posts which in other
      circumstances would be considered to be in questionable taste.
      Still, there is no guarantee that all people reading the group
      will appreciate the material as much as you do.  Use the Rotate
      utility (which rotates all the characters in your post by 13 
      positions in the alphabet) to avoid offense. 

   - In groups which discuss movies or books it is considered essential
     to mark posts which disclose significant content as "Spoilers".
     Put this word in your Subject: line.  You may add blank lines to
     the beginning of your post to keep content out of sight, or you
     may Rotate it.  

   - Forging of news articles is generally censured. 

   - Postings via anonymous servers are accepted in some Newsgroups
     and disliked in others.  Material which is inappropriate when
     posted under one's own name is still inappropriate when posted
     anonymously. 

   - Don't get involved in flame wars.  Neither post nor respond
     to incendiary material. 

      
3.2    Administrator Guidelines

3.2.1 General Issues 


   - Clarify any policies your site has regarding its subscription
     to Usenet Newsgroups and about subscribing to mailing lists. 

  - Clarify any policies your site has about posting to Usenet News
    groups or to mailing lists, including use of disclaimers in .sigs.

  - Clarify and publicize archive policy.  (How long are articles kept?)

  - Investigate accusations about your users promptly and with an open mind. 

3.2.2  Mailing Lists

   - Keep mailing lists up to date to avoid the "bouncing mail" problem.

   - Help list owners when problems arise.

   - Inform listowners of any maintanance windows or planned downtime. 
  
   - Be sure to have "-request" aliases for list subscription.  


3.2.3. Usenet News 

  - 

3.3 Moderator Guidelines

3.3.1 General Guidelines

 - Make sure your FAQ is posted at regular intervals.  Include your
   guidelines for article/messages. 

 - Make sure you maintain a good welcome message, which contains
   subscribe and unsubscribe information.


4.0  Information Services (Gopher, Wais, WWW, ftp, telnet)
In recent Internet history, the 'Net has exploded with new and vaired
Information services.  Gopher, Wais, World Wide Web (WWW), Multi-User
Dimensions (MUDs) Multi-User Dimensions which are Object Oriented
(MOOs) are a few of these new areas.  Although the ability to find
information is exploding, "Caveat Emptor" remains constant.  For more
information on these services, check references [z,zz,zzz] in the
Selected Bibliography.

4.1 User Guidelines

4.1.1. General guidelines

 - If you have problems with any form of information service, start
   problem solving by checking locally:  Check file configurations,
   software setup, network connections, etc.  Do this before assuming
   the problem is at the provider's end and/or is the provider's
   fault.

  - Although there are naming conventions for file-types used, don't
    depend on these file naming conventions to be enforced.

  - Information services also use conventions, such as www.abc.com.
    While it is useful to know these conventions, again, don't
    necessarily rely on them. 

  - Know how file names work on your own system.

  - Be aware of conventions used for providing information during
    sessions.  FTP sites usually have files named README in a top
    level directory which have information about the files available.
    But, don't assume that the files are necessarily up-to-date and/or
    accurate.

  - Do NOT assume that ANY information you find is up-to-date and/or
    accurate.  Remember that new technologies allow just about anyone
    to be a publisher, but not all people have discovered the
    responibilities which accompany publishing.

  - Remember that unless you are sure that security and authentication
    technology is in use, that any information you submit to a system
    is being transmitted over the Internet "in the clear", with no
    protection from "sniffers".

  - Since the Internet spans the globe, remember that Information
    Services might reflect culture and life-style markedly different
    from your own community.  Materials you find offensice may
    orginate in a geography which finds them acceptable.  Keep an open
    mind.

  - When accessing a popular site, be sure to use a mirror that's
    close if a list is provided.

 - Do not use someone else's FTP site to dump materials.

4.2 Administraor Guidelines

4.2.1 General Guidelines

  - Make clear what's copiable.

  - Describe what's available on your site, and your organization.
    Be sure any general policies are clear.

  - Keep information, especially READMEs, up-to-date.  Provide READMEs
    in plain ascii text.  

  - Present a list of mirrors of your site.  Make sure you include
    a statement of copyright applicable to your mirrors.  List
    their update schedule if possible.

  - Make sure that popular (and massive) information has the bandwidth
    to support it.

  - Use conventions for file extensions  - .txt for ascii text; .html
    or .htm for HTML; .ps for Postsciprt; .pdf for Portable Document
    Format; .sgml or .sgm for SGML; .exe for executables, etc.

  - For files being transferred, try to make filenames unique in the
    first 8 characters.

  - When providing Information, make sure your site has something
    unique to offer.  Avoid bringing up an information service which
    simply points to other services on the Internet.

  - Remember that setting up an information service is more than just
    design and implementation.  It's also maintenance.

  - Make sure your posted materials are appropriate for the supporting
    organization.

  - Test applications with a variety of tools.  Don't assue everything
    works if you;ve tested with only one client.  Also, assume the low
    end of technology for clients and don't create applications which
    can only be used by Graphical User Interfaces.

  - Have a consistent view of your information.  Make sure the look 
    and feel stays the same throughout your applications.

  - Be sensitive to the longevity of your information.  Be sure to
    date time-sensitive materials, and be vigilant about keeping
    this information well maintained.

  - Export restrictions vary from country to country.  Be sure you
    understand the implications of export restrictions when you post.
    Your mileage may vary!

5.0 Selected Bibliography
This bibliography was used to gather most of the information in the
sections above as well as for general reference.  Items not
specifically found in these works were gathers from the IETF-RUN
Working Group's experience.  


Selected Bibliography

1.
Angell, David; Brent Heslop. _The Elements of E-mail Style_. New York:
  Addison-Wesley, 1994.

2.
"Answers to Frequently Asked Questions about Usenet"
  Original author: [e-mail] (Jerry Schwarz)
  Maintained by:  [e-mail] (Mark Moraes)
  Archive-name: usenet-faq/part1

3.
Dern, Daniel.  _The Internet Guide for New Users_. New York: McGraw-Hill,
   1994.

4.
"Emily Postnews Answers Your Questions on Netiquette"
  Original author: [e-mail] (Brad Templeton)
  Maintained by:  [e-mail] (Mark Moraes)
  Archive-name: emily-postnews/part1

5.
Gaffin, Adam. _Everybody's guide to the internet_.  Cambridge, Mass. :
   MIT Press, c1994.

6.
"Guidelines for Responsible Use of the Internet"
  from the US house of Representatives gopher, at:
  <URL:gopher://gopher.house.gov:70/OF-1%3a208%3aInternet%20Etiquette>

7.
How to find the right place to post (FAQ)
  by [e-mail] (Aliza R. Panitz)
  Archive-name: finding-groups/general

8.
Hambridge, Sally, Jeffrey C. Sedayao. "Horses and Barn Doors: Evolution
  of Corporate Guideliens for Internet Usage." LISA VII, Usenix, November
  1-5, 1993, pp. 9-16. <URL: http://www.intel.com/about-intel/papers/horses.
  html>

9.
Heslop, Brent D; David Angell.  _The instant Internet guide : hands-on global 
  networking_. Reading, Mass. : Addison-Wesley, 1994.
 
10.
Horwitz, Stan.  _Internet Etiquette Tips_. 
   <ftp://ftp.temple.edu/pub/info/help-net/netiquette.infohn>

11.
Internet Activities Board. "Ethics and the Internet". January, 1989.
  RFC 1087. <URL: ftp://ds.internic.net/rfc/rfc1087.txt>

12.
Kehoe, Brendan.  _Zen and the Art of the Internet: A Beginner's
  Guide_.  Netiquette information is spread through the chapters
  of this work.  3rd ed. Englewood Cliffs, NJ: Prentice-Hall, 1994.

13.
Kochmer, Jonathan. _Internet passport : NorthWestNet's guide to our 
world online_.  4th ed.  Bellevue, Wash. : NorthWestNet :
    Northwest Academic Computing Consortium, c1993.
 
14.
Krol, Ed.  _The Whole Internet: User's Guide and
  Catalog_.  Sebastopol, CA: O'Reilly & Associates,
  1992.

15.
Lane, Elizabeth S.; Craig Summerhill.  _Internet primer for information 
  professionals : a basic guide to Internet networking technology_. 
  Westport, CT: Meckler, c1993.

16.
LaQuey, Tracy.  _The Internet Companion_.  Chapter3 "Communicating 
  with People" pp 41-74. Reading, MA: Addison-Wesley, 1993.

17.
Mandel, Thomas F. "Surfing the Wild Internet".  SRI International Business
  Intelligence Program, Scan No. 2109.  March, 1993. <URL: gopher://is.
  internic.net:70/00/infoguide/beginners/internet-intros/surfing-the-
  wild-internet>

18.
Martin, J. "There's Gold in them thar Networks! or Searching for
  Treasure in all the Wrong Places." January, 1993. RFC 1402, FYI
  10. <URL: ftp://ds.internic.net/rfc/rfc1402.txt>

19.
Polly, Jean Armour.  "Surfing the Internet: an Introduction", Version 2.0.3.
  Revised May 15, 1993.  <URL: gopher://is.internic.net:70/00/infoguide/ 
  beginnners/internet-intros/surfing-the-internet>

20.
"A Primer on How to Work With the Usenet Community"
   Original author: [e-mail] (Chuq Von Rospach)
   Maintained by:  [e-mail] (Mark Moraes)
   Archive-name: usenet-primer/part1

21.
Rinaldi, Arlene H. "The Net: User Guidelines and Netiquette". September
  3, 1992.  <URL: gopher://is.internic.net:70/00/infoguide/about-internet/
  culture/netiquette-guide>.

22.
"Rules for posting to Usenet"
  Original author: [e-mail] (Gene Spafford)
  Maintained by:  [e-mail] (Mark Moraes)
  Archive-name: posting-rules/part1

23.
Shea, Virginia.  _Netiquette_. San Francisco: Albion Books, 1994?. 

24.
Strangelove, Michael; with Aneurin Bosley.  _How to Advertise on
  the Internet_.  ISSN 1201-0758

25.
Tenant, Roy. "Internet Basics". ERIC Clearinghouse of Information 
  Resources, EDO-IR-92-7.  September, 1992.   <URL: gopher://is.internic.net
  :70:00/infoguide/beginners/internet-intros/internet-basics>

26.
Wiggins, Richard W. _The Internet for everyone : a guide for 
  users and providers_. New York : McGraw-Hill, c1995.