IETF Guidelines for Conduct
draft-moonesamy-ietf-conduct-3184bis-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in gen area)
Last updated 2013-12-11 (latest revision 2013-12-02)
Stream IETF
Intended RFC status Best Current Practice
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation
Telechat date
Needs 2 more YES or NO OBJECTION positions to pass.
Responsible AD Jari Arkko
Send notices to sm+ietf@elandsys.com, draft-moonesamy-ietf-conduct-3184bis@tools.ietf.org,mariainesrobles@googlemail.com
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
INTERNET-DRAFT                                         S. Moonesamy, Ed.
Obsoletes: 3184 (if approved)                                           
Intended Status: Best Current Practice                                  
Expires: June 5, 2014                                   December 2, 2013

                      IETF Guidelines for Conduct
                draft-moonesamy-ietf-conduct-3184bis-04

Abstract

   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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
 

                          Expires June 5, 2014                  [Page 1]
S. Moonesamy          IETF Guidelines for Conduct       December 2, 2013

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process. 
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials,this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

1. Introduction

   The work of the IETF relies on cooperation among a diverse range of
   people, ideas, and communication styles.  The Guidelines for Conduct
   inform our interaction as we work together to develop interoperable
   technologies for the Internet.  All IETF participants aim to abide by
   these Guidelines as we build consensus in person and through email
   discussions.  If conflicts arise they are resolved according to the
   procedures outlined in RFC 2026 [RFC2026].

   This document obsoletes and replaces RFC 3184 [RFC3184].

2. Guidelines for Conduct

   1. IETF participants extend respect and courtesy to their colleagues
      at all times.

      IETF participants come from diverse origins and backgrounds; there
      can be different expectations or assumptions.  Regardless of these
      individual differences, participants treat their colleagues with
      respect as persons especially when it is difficult to agree with
      them; treat other participants as you would like to be treated.

      English is the de facto language of the IETF.  However, it is not
      the native language of many IETF participants.  All participants,
      particularly those with English as a first language, attempt to
      accommodate the needs of other participants by communicating
      clearly.  When faced with English that is difficult to understand
      IETF participants make a sincere effort to understand each other
      and engage in conversation to clarify what was meant.

   2. IETF participants have impersonal discussions.
 

                          Expires June 5, 2014                  [Page 2]
S. Moonesamy          IETF Guidelines for Conduct       December 2, 2013
Show full document text