IP: Netiquette Guidelines

[David Farber <farber@central.cis.upenn.edu>]

A new Request for Comments is now available in online RFC libraries.




        FYI 28:
        RFC 1855:


        Title:      Netiquette Guidelines
        Author:     S. Hambridge
        Date:       October 1995
        Mailbox:    sallyh@ludwig.sc.intel.com
        Pages:      21
        Characters: 46,185
        Updates/Obsoletes:  none


        URL:        ftp://ds.internic.net/rfc/rfc1855.txt




This document provides a minimum set of guidelines for Network
Etiquette (Netiquette) which organizations may take and adapt for
their own use.  As such, it is deliberately written in a bulleted
format to make adaptation easier and to make any particular item easy
(or easier) to find.  It also functions as a minimum set of guidelines
for individuals, both users and administrators.  This memo is the
product of the Responsible Use of the Network (RUN) Working Group of
the IETF.


This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.


This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.


Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs.  For example:


        To: rfc-info@ISI.EDU
        Subject: getting rfcs


        help: ways_to_get_rfcs


Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.




Joyce K. Reynolds
USC/Information Sciences Institute


...


Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.


--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"


--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mailserv@ds.internic.net"


Content-Type: text/plain
Content-ID: <951019143732.RFC@ISI.EDU>


SEND /rfc/rfc1855.txt


--OtherAccess
Content-Type:   Message/External-body;
        name="rfc1855.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="rfc"


Content-Type: text/plain
Content-ID: <951019143732.RFC@ISI.EDU>


--OtherAccess--
--NextPart--




----- End Included Message -----