Internet DRAFT - draft-ietf-poisson-code

draft-ietf-poisson-code



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


        BCP 54
        RFC 3184

        Title:      IETF Guidelines for Conduct
        Author(s):  S. Harris
        Status:     Best Current Practice 
        Date:       October 2001
        Mailbox:    srh@merit.edu
        Pages:      4
        Characters: 7413
        SeeAlso/Updates/Obsoletes:    None

        I-D Tag:    draft-ietf-poisson-code-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3184.txt


This document provides a set of guidelines for personal interaction
in the Internet Engineering Task Force.  The Guidelines recognize the
diversity of IETF participants, emphasize the value of mutual
respect, and stress the broad applicability of our work.

This document is a product of the Process for Organization of Internet
Standards ONgoing Working Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.