Re: IESG Statement on disruptive posting
Brian E Carpenter <brc@zurich.ibm.com> Wed, 22 February 2006 07:41 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBocv-0008GB-12; Wed, 22 Feb 2006 02:41:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBocs-0008Fx-U9 for ietf@ietf.org; Wed, 22 Feb 2006 02:41:30 -0500
Received: from mtagate4.uk.ibm.com ([195.212.29.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBocr-0004zr-D4 for ietf@ietf.org; Wed, 22 Feb 2006 02:41:30 -0500
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id k1M7fSl6257122 for <ietf@ietf.org>; Wed, 22 Feb 2006 07:41:28 GMT
Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k1M7fZEE224862 for <ietf@ietf.org>; Wed, 22 Feb 2006 07:41:35 GMT
Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id k1M7fSa6002777 for <ietf@ietf.org>; Wed, 22 Feb 2006 07:41:28 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id k1M7fRZA002772; Wed, 22 Feb 2006 07:41:27 GMT
Received: from zurich.ibm.com (sig-9-146-220-210.de.ibm.com [9.146.220.210]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id IAA29538; Wed, 22 Feb 2006 08:41:23 +0100
Message-ID: <43FB5465.6060301@zurich.ibm.com>
Date: Tue, 21 Feb 2006 18:56:53 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: "Gray, Eric" <Eric.Gray@marconi.com>
References: <313680C9A886D511A06000204840E1CF0DAC16F2@whq-msgusr-02.pit.comms.marconi.com>
In-Reply-To: <313680C9A886D511A06000204840E1CF0DAC16F2@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: 'Sam Hartman' <hartmans-ietf@mit.edu>, ietf@ietf.org
Subject: Re: IESG Statement on disruptive posting
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
Eric, Gray, Eric wrote: ... > ... there is a need to define who > is what, he has a valid point. I moderate the MPLS mailing list, but > there are others who are authorized to do so as well - including the > ADs and WG Chairs. I assume this is true of other mailing lists as > well, and I do not think that it is obvious to everyone who is on the > list of people with authority to manage each list. That is the reason for the specific reference to the administrators listed at https://datatracker.ietf.org/public/nwg_list.cgi. > > ... the comment that Brian's terminology use > is not consistent (Brian says "the moderators or maintainers of IETF > mailing lists that are not WG mailing lists" in the beginning of his > message and "where the administrators are listed" later on), It's not *my* terminology, it's an IESG statement. The inconsistent language in the two parts of the statement has been noted. > ... reasonable in saying that a decision > should name the AD consulted Reasonable and should, yes. https://datatracker.ietf.org/public/nwg_list.cgi lists the Areas, which gets you to a choice of two ADs at most, so the responsible AD is not hard to find. > I believe that at least a formal notification must occur and it > must list those people involved in making the decision. Yes, I agree. > It would also be good from the list administrator's perspective > if the notification was at least backed up by the consulted AD - if it > does not in fact come from the consulted AD(s). Not sure I see why, but I'd certainly expect the AD to be copied. > ... if there are lists that are > maintained by the IETF site that do not properly belong under IESG > authority, Those would not be at https://datatracker.ietf.org/public/nwg_list.cgi, so would be out of scope. > or if there are lists maintained elsewhere that are kept on > behalf of the IETF, but do not fall under IESG authority. I don't know > that such lists exist, but it is possible that they do. If they do, they *are* are at https://datatracker.ietf.org/public/nwg_list.cgi > Would BoF mailing lists fall into this category? If they are listed at https://datatracker.ietf.org/public/nwg_list.cgi. > ... there should > be an announcement that "such-and-such" list now falls under the > IESG authority Ideally yes, but since the list of such lists is public at https://datatracker.ietf.org/public/nwg_list.cgi, this is low on my list of change requests to the secretariat. Brian _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: IESG Statement on disruptive posting JFC (Jefsey) Morfin
- Re: IESG Statement on disruptive posting Sam Hartman
- Re: IESG Statement on disruptive posting Sam Hartman
- Re: IESG Statement on disruptive posting Sam Hartman
- Re: IESG Statement on disruptive posting Brian E Carpenter
- RE: IESG Statement on disruptive posting Gray, Eric
- RE: IESG Statement on disruptive posting JFC (Jefsey) Morfin
- Re: IESG Statement on disruptive posting Jefsey Morfin
- Re: IESG Statement on disruptive posting Sam Hartman
- Re: IESG Statement on disruptive posting Brian E Carpenter
- Re: IESG Statement on disruptive posting JFC (Jefsey) Morfin
- RE: IESG Statement on disruptive posting Gray, Eric
- Re: IESG Statement on disruptive posting JFC (Jefsey) Morfin
- Re: IESG Statement on disruptive posting Sam Hartman
- Re: IESG Statement on disruptive posting JFC (Jefsey) Morfin