idnits 2.17.1 draft-ietf-poisson-code-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 BCP 54 4 RFC 3184 6 Title: IETF Guidelines for Conduct 7 Author(s): S. Harris 8 Status: Best Current Practice 9 Date: October 2001 10 Mailbox: srh@merit.edu 11 Pages: 4 12 Characters: 7413 13 SeeAlso/Updates/Obsoletes: None 15 I-D Tag: draft-ietf-poisson-code-04.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3184.txt 19 This document provides a set of guidelines for personal interaction 20 in the Internet Engineering Task Force. The Guidelines recognize the 21 diversity of IETF participants, emphasize the value of mutual 22 respect, and stress the broad applicability of our work. 24 This document is a product of the Process for Organization of Internet 25 Standards ONgoing Working Group of the IETF. 27 This document specifies an Internet Best Current Practices for the 28 Internet Community, and requests discussion and suggestions for 29 improvements. Distribution of this memo is unlimited. 31 This announcement is sent to the IETF list and the RFC-DIST list. 32 Requests to be added to or deleted from the IETF distribution list 33 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 34 added to or deleted from the RFC-DIST distribution list should 35 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 37 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 38 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 39 help: ways_to_get_rfcs. For example: 41 To: rfc-info@RFC-EDITOR.ORG 42 Subject: getting rfcs 44 help: ways_to_get_rfcs 46 Requests for special distribution should be addressed to either the 47 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 48 specifically noted otherwise on the RFC itself, all RFCs are for 49 unlimited distribution.echo 50 Submissions for Requests for Comments should be sent to 51 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 52 Authors, for further information.