Re: Procedures for Moving Forward

DRUMS WG Chair <chris.newman@innosoft.com> Thu, 27 July 2000 20:46 UTC

Received: from cs.utk.edu (CS.UTK.EDU [128.169.94.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00610 for <drums-archive@odin.ietf.org>; Thu, 27 Jul 2000 16:46:36 -0400 (EDT)
Received: from localhost (daemon@localhost) by cs.utk.edu with SMTP (cf v2.9s-UTK) id QAA06782; Thu, 27 Jul 2000 16:46:16 -0400 (EDT)
Received: by cs.utk.edu (bulk_mailer v1.13); Thu, 27 Jul 2000 16:46:15 -0400
Received: by cs.utk.edu (cf v2.9s-UTK) id QAA06765; Thu, 27 Jul 2000 16:46:15 -0400 (EDT)
Received: from mercury.Sun.COM (marvin@localhost) by cs.utk.edu with ESMTP (cf v2.9s-UTK) id QAA06749; Thu, 27 Jul 2000 16:46:13 -0400 (EDT)
Received: from mercury.Sun.COM (192.9.25.1 -> mercury.Sun.COM) by cs.utk.edu (smtpshim v1.0); Thu, 27 Jul 2000 16:46:13 -0400
Received: from westmail2.West.Sun.COM ([129.153.100.30]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA14703 for <drums@cs.utk.edu>; Thu, 27 Jul 2000 13:46:11 -0700 (PDT)
Received: from nifty-jr.west.sun.com (nifty-jr.West.Sun.COM [129.153.12.95]) by westmail2.West.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v1.7) with ESMTP id NAA10885 for <drums@cs.utk.edu>; Thu, 27 Jul 2000 13:46:04 -0700 (PDT)
Date: Thu, 27 Jul 2000 13:45:33 -0700
From: DRUMS WG Chair <chris.newman@innosoft.com>
To: Detailed Revision/Update of Message Standards <drums@cs.utk.edu>
Subject: Re: Procedures for Moving Forward
Message-ID: <5989945.3173694333@nifty-jr.west.sun.com>
In-Reply-To: <3884949.3173621722@nifty-jr.west.sun.com>
X-Mailer: Mulberry/2.0.3 (MacOS)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
List-Unsubscribe: <mailto:drums-request@cs.utk.edu?Subject=unsubscribe>
Content-Transfer-Encoding: 7bit

--On Wednesday, July 26, 2000 17:35 -0700 DRUMS WG Chair 
<chris.newman@INNOSOFT.COM> wrote:
> (1) Do not post to this list unless one of the following criteria is met:
>
> (1a) You are raising a single issue of concern with SMTP draft 12,
> include specific text for a proposed change, and use a new subject line
> descriptive of the issue.
>
> (1b) You are expressing support for a post of type (1a), and preserve the
> subject line (with Re: prefix).
>
> (1c) The WG Chair has explicitly declared an issue open for debate, and
> you preserve the subject line (with Re: prefix).
>
> (1d) The WG Chair reserves the right to post procedural comments at any
> time.  If you have issue with WG Chair procedures, send email to the WG
> chair privately.

Posts which violate these rules (I count three so far) will result in a 
private warning from the Chair and will otherwise be ignored.

		- DRUMS WG Chair