Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice

S Moonesamy <sm+ietf@elandsys.com> Wed, 06 November 2013 08:15 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90CEE21F9A97 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 00:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.553
X-Spam-Level:
X-Spam-Status: No, score=-103.553 tagged_above=-999 required=5 tests=[AWL=-0.954, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MGA+76IiNdLA for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 00:15:33 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C2AB021F9A8D for <ietf@ietf.org>; Wed, 6 Nov 2013 00:15:33 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.159.23]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id rA68FKXI015074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 6 Nov 2013 00:15:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383725731; bh=SMxBtHw4Cp2V7mSrO4TJXltnVYHVz2+F6pFRLZWpUo0=; h=Date:To:From:Subject:In-Reply-To:References; b=QLAjbwliO1Zqjj1KWwl/HBkTivcbELX/pNZ6oW5XRmKz3fYcNSOQUQE3wYlFgGz8n AZTnCj9LwdoCTV/iLqk2QtY3QQ0k8XiVJ6OylTWDSrqvLSmZUKl/RM95+WSlIe6D9T Fw9Y+dtwIHOGPsHn+Y/SvlQ1z7Xr3EhFPIh029zM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383725731; i=@elandsys.com; bh=SMxBtHw4Cp2V7mSrO4TJXltnVYHVz2+F6pFRLZWpUo0=; h=Date:To:From:Subject:In-Reply-To:References; b=H8nPF9IozgKB8KIoG82GgJSdWQRMlJ+YBJN4srUTdULx1T+tQmSVHaJgIJ8J6AWGh NObmiV6yfaF6zD2mCDZjPoc89b4Sq2/6YmhOnLiUecNNUI1obC38y9GYxP1bL47pjB sUoZLz1FhYcMhfHNuL0MPgO9wNtxuqfYFQtfzbKQ=
Message-Id: <6.2.5.6.2.20131105224144.0ca69c28@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 05 Nov 2013 23:13:42 -0800
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
In-Reply-To: <20131103150309.1554.26103.idtracker@ietfa.amsl.com>
References: <20131103150309.1554.26103.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2013 08:15:34 -0000

Hello,
At 07:03 03-11-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'IETF Guidelines for Conduct'
>   <draft-moonesamy-ietf-conduct-3184bis-03.txt> as Best Current Practice
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-12-01. Exceptionally, comments may be

The draft 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.

The "Note Well" ( https://www.ietf.org/about/note-well.html ) states that:

   "A participant in any IETF activity is deemed to accept all IETF rules of
    process, as documented in Best Current Practices RFCs and IESG Statements."

It may be of interest to IETF participants to read and understand the draft.

Regards,
S. Moonesamy