RE: IESG Statement on disruptive posting

"Gray, Eric" <Eric.Gray@marconi.com> Wed, 22 February 2006 17:05 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBxR7-0001ii-ID; Wed, 22 Feb 2006 12:05:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBxR6-0001ia-CL for ietf@ietf.org; Wed, 22 Feb 2006 12:05:56 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBxR6-0004Ii-1O for ietf@ietf.org; Wed, 22 Feb 2006 12:05:56 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id k1MH5tgL021139; Wed, 22 Feb 2006 12:05:55 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA09273; Wed, 22 Feb 2006 12:05:55 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2657.72) id <FG7R4F19>; Wed, 22 Feb 2006 12:05:54 -0500
Message-ID: <313680C9A886D511A06000204840E1CF0DAC170E@whq-msgusr-02.pit.comms.marconi.com>
From: "Gray, Eric" <Eric.Gray@marconi.com>
To: 'Brian E Carpenter' <brc@zurich.ibm.com>, "Gray, Eric" <Eric.Gray@marconi.com>
Date: Wed, 22 Feb 2006 12:05:54 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
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

Brian,

	Thanks for the clarification!

--
Eric 

--> -----Original Message-----
--> From: Brian E Carpenter [mailto:brc@zurich.ibm.com] 
--> Sent: Tuesday, February 21, 2006 12:57 PM
--> To: Gray, Eric
--> Cc: 'Sam Hartman'; ietf@ietf.org
--> Subject: Re: IESG Statement on disruptive posting
--> 
--> 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