*-*-*-*-*-*-*-*-*-*-*-*-*-*

                                 THE NET
                     USER GUIDELINES AND NETIQUETTE


                          By: Arlene H. Rinaldi
                 Academic/Institutional Support Services
                       Florida Atlantic University
                               July, 1994



                       *-*-*-*-*-*-*-*-*-*-*-*-*-*

                                 PREFACE

The formulation of this guide was motivated by a need to develop
guidelines for all Internet protocols to ensure that users at
Florida Atlantic University realize the Internet capabilities as
a resource available, with the provision that they are
responsible in how they access or transmit information through
the Internet (The Net).

It is assumed that the reader has some familiarization with the
terms and protocols that are referenced in this document.

Permission to duplicate or distribute this document is granted
with the provision that the document remains intact or if used in
pieces, that the original document source be referenced.

For additions, comments, suggestions and requests for revisions,
please send Email to RINALDI@ACC.FAU.EDU.

                       *-*-*-*-*-*-*-*-*-*-*-*-*-*

                            ACKNOWLEDGEMENTS

Much of this guide was developed from comments and suggestions
from NETTRAIN@UBVM (formally NET-TRAIN) LISTSERV subscribers and
from several  sources available on The Net:

A special acknowledgment to Wes Morgan, University of Kentucky
Engineering Computing Center, for his advice and recommendations.

Pete Hoyle,William & Mary; Timothy A. Torres, San Jose State
University; Paul Brians, Washington State University ; Paul F.
Lambert, Bentley College; Philip M. Howard, Saint Mary's
University; Gordon Swan, Florida Atlantic University; Pauline
Kartrude, Florida Atlantic University; Beth Taney, Penn State;
Debbie Shaffer, Penn State and USDA-CIT; Henry DeVries, Cornell;
Jim Milles, SLU Law Library; Martin Raish, State University of
New York at Binghamton; Steve Cisler, Apple Corporation; Tom
Zillner, Wisconsin Interlibrary Services; Tom Goodrich, Stanford
University; Jim Gerland, State University of NY at Buffalo; Ros
Leibensperger, Cornell; Paul White, Northern Michigan University;
Marilyn S. Webb, Penn State, Judith Hopkins, State University of
NY at Buffalo, Ros McCarthy.


                       *-*-*-*-*-*-*-*-*-*-*-*-*-*
                              INTRODUCTION


It is essential for each user on the network to recognize his/her
responsibility in having access to vast services, sites, systems
and people.  The user is ultimately responsible for his/her
actions in accessing network services.

The "Internet" or "The Net", is not a single network; rather, it
is a group of thousands of individual networks which have chosen
to allow traffic to pass among them.  The traffic sent out to the
Internet may actually traverse several different networks before
it reaches its destination.  Therefore, users involved in this
internetworking must be aware of the load placed on other
participating networks.

As a user of the network, you may be allowed to access other
networks (and/or the computer systems attached to those
networks).  Each network or system has its own set of policies
and procedures.  Actions which are routinely allowed on one
network/system may be controlled, or even forbidden, on other
networks.  It is the users responsibility to abide by the
policies and procedures of these other networks/systems.
Remember, the fact that a user *can* perform a particular action
does not imply that they *should* take that action.

The use of the network is a privilege, not a right, which may
temporarily be revoked at any time for abusive conduct.  Such
conduct would include, the placing of unlawful information on a
system, the use of abusive or otherwise objectionable language in
either public or private messages, the sending of messages that
are likely to result in the loss of recipients' work or systems,
the sending of "Chain letters," or "broadcast" messages to lists
or individuals, and any other types of use which would cause
congestion of the networks or otherwise interfere with the work
of others..

Permanent revocations can result from disciplinary actions taken
by a panel judiciary board called upon to investigate network
abuses.


                       *-*-*-*-*-*-*-*-*-*-*-*-*-*

             ELECTRONIC MAIL AND FILES- USER RESPONSIBILITY

The content and maintenance of a user's electronic mailbox is the
users responsibility:

-    Check Email daily and remain within your limited disk quota.

-    Delete unwanted messages immediately since they take up disk
     storage.

-    Keep messages remaining in your electronic mailbox to a
     minimum.

-    Mail messages can be downloaded or extracted to files then
     to disks for future reference.

-    Never assume that your Email can be read by no one except
     yourself; others may be able to read or access your mail.
     Never send or keep anything that you would not mind seeing
     on  the evening news.

The content and maintenance of a user's disk storage area is the
users responsibility:

-    Keep files to a minimum.  Files should be downloaded to your
     personal computer's hard drive or to disks.

-    Routinely and frequently virus scan your system, especially
     when receiving or downloading files from other systems to
     prevent the spread of a virus.

-    Your files may be accessible by persons with system
     privileges,  so do not maintain anything private in your
     disk storage area.

                       *-*-*-*-*-*-*-*-*-*-*-*-*-*
                             TELNET PROTOCOL

-    Many telnetable services have documentation files available
     online  (or via ftp).  Download and review instructions
     locally as opposed  to tying up ports trying to figure out
     the system.

-    Be courteous to other users wishing to seek information or
     the  institution might revoke Telnet access; remain only on
     the system long enough to get your information, then exit
     off of the system.

-    Screen captured data or information should be downloaded to
     your personal computer's hard disk or to disks.

                       *-*-*-*-*-*-*-*-*-*-*-*-*-*

                 ANONYMOUS FTP - FILE TRANSFER PROTOCOL

-    Users should respond to the PASSWORD prompt with their Email
     address, so if that site chooses, it can track the level of
     FTP usage. If your Email address causes an error, enter
     GUEST for the next PASSWORD prompt.

-    When possible limit downloads, especially large downloads (1
     Meg+), for after normal business hours locally and for the
     remote ftp host; preferably late in the evening.

-    Adhere to time restrictions as requested by archive sites.
     Think in terms of the current time at the site that's being
     visited, not of local time.

-    Copy downloaded files to your personal computer hard drive
     or disks to remain within disk quota.

-    When possible, inquiries to Archie should be in mail form.

-    It's the user's responsibility when downloading programs, to
     check for copyright or licensing agreements.  If the program
     is beneficial to your use, pay any authors registration fee.
     If there is any doubt, don't copy it; there have been many
     occasions on which copyrighted software has found its way
     into ftp archives. Support for any downloaded programs
     should be requested from the originator of the application.
     Remove unwanted programs from your systems.

                       *-*-*-*-*-*-*-*-*-*-*-*-*-*

                        ELECTRONIC COMMUNICATIONS
           (Email, LISTSERV groups, Mailing lists, and Usenet)

-    Keep paragraphs and messages short and to the point.

-    Focus on one subject per message and always include a
     pertinent subject title for the message, that way the user
     can locate the message quickly.

-    Don't use the academic networks for commercial or
     proprietary work.

-    Include your signature at the bottom of Email messages.
     Your signature footer should include your name, position,
     affiliation and Internet and/or BITNET addresses and should
     not exceed more than 4 lines.  Optional information could
     include your address and phone number.

-    Capitalize words only to highlight an important point or to
     distinguish a title or heading.  *Asterisks* surrounding a
     word  also can be used to make a stronger point.
     Capitalizing whole words  that are not titles is generally
     termed as SHOUTING!

-    Limit line length and avoid control characters.

-    Follow chain of command procedures for corresponding with
     superiors. For example, don't send a complaint via Email
     directly to the "top" just because you can.

-    Be professional and careful what you say about others.
     Email is easily forwarded.

-    Cite all quotes, references and sources and respect
     copyright and license agreements.

-    It is considered extremely rude to forward personal email to
     mailing lists or Usenet without the original author's
     permission.

-    Be careful when using sarcasm and humor. Without face to
     face communications your joke may be viewed as criticism.

-    Acronyms can be used to abbreviate when possible, however 
     messages that are filled with acronyms can be confusing
     and annoying to the reader.
     Examples: IMHO=  in my humble/honest opinion
               FYI =  for your information
               BTW =  by the way
               Flame  =  antagonistic criticism
               :-) =  happy face for humor


                    *-*-*-*-*-*-*-*-*-*-*-*-*-*

               LISTSERVS/MAILING LISTS/ DISCUSSION GROUPS

Some mailing lists have low rates of traffic, others can flood
your mailbox with several hundred mail messages per day.
Numerous incoming messages from various listservers or mailing
lists by multiple users, requires extensive system processing
which can tie up valuable resources. Subscription to Interest
Groups or Discussion Lists should be kept to a minimum and should
not exceed what your disk quota can handle, or you for that
matter.

-    When you join a list, monitor the messages for a few days to
     get a feel for what common questions are asked, and what
     topics are deemed off-limits.  This is commonly referred to
     as lurking.  When you feel comfortable with the group, then
     start posting.

-    See if there is a FAQ (Frequently Asked Questions) for a
     group that you are interested in joining.  Veteran members
     get annoyed when they see the same questions every few
     weeks, or at the start of each semester.

-    Follow any and all guidelines that the listowner has posted;
     the listowner establishes the local "netiquette" standards
     for her/his list.

-    Keep in mind that some discussion lists or Usenet groups
     have members from many countries.  Don't assume that they
     will understand a reference to TV, movies, pop culture, or
     current events in your country.  If you must use the
     reference, please explain it.
-    Don't join a list just to post inflammatory messages - this
     upsets most system administrators and you could lose access
     to the net ("mail bombing").

-    Keep your questions and comments relevant to the focus of
     the discussion group.

-    If another person posts a comment or question that is off
     the subject, do NOT reply to the list and keep the off-
     subject conversation going publicly.

-    When someone posts an off-subject note, and someone else
     criticizes that posting, you should NOT submit a gratuitous
     note saying "well, I liked it and lots of people probably
     did as well and you guys ought to lighten up and not tell us
     to stick to the subject".

-    When going away for more than a week, unsubscribe or suspend
     mail from any mailing lists or LISTSERV services.

-    If you can respond to someone else's question, do so through
     email.  Twenty people answering the same question on a large
     list can fill your mailbox (and those of everyone else on
     the list) quickly.