Internet Engineering Task Force S. Harris
INTERNET-DRAFT Merit Network
June 20, 2001A new Request for Comments is now available in online RFC libraries.
BCP 54
RFC 3184
Title: IETF Guidelines for Conduct
<draft-ietf-poisson-code-03.txt>
Status of this Memo
This document is an Internet-Draft and is subject to all provisions
of Section 10 of RFC2026.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
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.
Introduction
The work of the IETF relies on cooperation among
This document is a broad cultural
diversity product of peoples, ideas, and communication styles. The Guidelines
for Conduct inform our interaction as we work together to develop
multiple, interoperable technologies the Process for Organization of Internet
Standards ONgoing Working Group of the Internet. All IETF
participants aim to abide by these Guidelines as we build consensus in
person, at IETF meetings, and in e-mail. If conflicts arise, we resolve
them according to IETF.
This document specifies an Internet Best Current Practices for the procedures outlined in BCP 25.
Principles of Conduct
1. IETF participants extend respect and courtesy to their colleagues
at all times.
IETF participants come from diverse origins and backgrounds
Internet Community, and
are equipped with multiple capabilities requests discussion and ideals. Regardless suggestions for
improvements. Distribution of these individual differences, participants treat their
colleagues with respect as persons--especially when it this memo is
difficult to agree with them. Seeing from another's point of
view unlimited.
This announcement is often revealing, even when it fails sent to be compelling.
English is the de facto language of the IETF, but it is not the
native language of many IETF participants. Native English
speakers attempt to speak clearly and a bit slowly list and to limit the use of slang in order RFC-DIST list.
Requests to accommodate the needs of all
listeners.
2. IETF participants develop and test ideas impartially, without
finding fault with the colleague proposing the idea.
We dispute ideas by using reasoned argument, rather than through
intimidation or ad hominem attack. Or, said in a somewhat more
IETF-like way:
"Reduce the heat and increase the light"
3. IETF participants think globally, devising solutions that meet the
needs of diverse technical and operational environments.
The goal of the IETF is be added to maintain and enhance a working,
viable, scalable, global Internet, and the concomitant problems
are genuinely very difficult. We understand that "scaling is the
ultimate problem" and that many ideas quite workable in or deleted from the small
fail this crucial test. IETF participants use their best
engineering judgement to find the best solution for the whole
Internet, not just the best solution for any particular network,
technology, vendor, or user.
4. Individuals who attend Working Group meetings are prepared distribution list
should be sent to
contribute IETF-REQUEST@IETF.ORG. Requests to the ongoing work of the group.
IETF participants who attend Working Group meetings read the
relevant Internet-Drafts, RFCs, and e-mail archives beforehand,
in order be
added to familiarize themselves with or deleted from the technology under
discussion. This may represent a challenge for newcomers, as
e-mail archives can RFC-DIST distribution list should
be difficult sent to locate and search, and it RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may not be easy to trace the history of longstanding Working
Group debates. With that in mind, newcomers who attend Working
Group meetings are encouraged obtained by sending
an EMAIL message to observe and absorb whatever
material they can, but should not interfere rfc-info@RFC-EDITOR.ORG with the ongoing
process of the group. Working Group meetings run on a very
limited time schedule, and are not intended 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 the education
of individuals. The work of the group will continue on the
mailing list, and many questions would special distribution should be better expressed on
the list in the months that follow.
Acknowledgements
Mike O'Dell wrote addressed to either the first draft
author of the Principles for Conduct, and
many of his thoughts, statements, and observations are included RFC in this
version. Many useful editorial comments were supplied by Dave Crocker.
Members of the POISSON Working Group provided many significant additions question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the text.
Author's Address
Susan Harris
srh@merit.edu
Merit Network, Inc.
4251 Plymouth Rd., Suite C
Ann Arbor, MI 48105-2785
Phone: (734) 936-2100
Fax: (734) 647-3185 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.