IETF Logo Mail Archive

Re: IESG Statement on disruptive posting

Brian E Carpenter <brc@zurich.ibm.com> Sun, 19 February 2006 08:02 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAjWB-00063D-ME; Sun, 19 Feb 2006 03:02:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAjW9-000635-W0 for ietf@ietf.org; Sun, 19 Feb 2006 03:02:05 -0500
Received: from mtagate4.de.ibm.com ([195.212.29.153]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAjW7-0001NI-Is for ietf@ietf.org; Sun, 19 Feb 2006 03:02:05 -0500
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate4.de.ibm.com (8.12.10/8.12.10) with ESMTP id k1J822VV242962 for <ietf@ietf.org>; Sun, 19 Feb 2006 08:02:02 GMT
Received: from d12av03.megacenter.de.ibm.com (d12av03.megacenter.de.ibm.com [9.149.165.213]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k1J829Gh214428 for <ietf@ietf.org>; Sun, 19 Feb 2006 09:02:09 +0100
Received: from d12av03.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av03.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id k1J822fo020185 for <ietf@ietf.org>; Sun, 19 Feb 2006 09:02:02 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av03.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id k1J8212V020174 for <ietf@ietf.org>; Sun, 19 Feb 2006 09:02:01 +0100
Received: from zurich.ibm.com (sig-9-145-251-220.de.ibm.com [9.145.251.220]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id JAA66134 for <ietf@ietf.org>; Sun, 19 Feb 2006 09:02:00 +0100
Message-ID: <43F825F6.8000408@zurich.ibm.com>
Date: Sun, 19 Feb 2006 09:01:58 +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: ietf@ietf.org
References: <6.2.3.4.2.20060218024811.0600eeb0@pop.online.fr> <tsl1wy1mmsk.fsf@cz.mit.edu> <6.2.3.4.2.20060218032046.05e6a8b0@pop.online.fr>
In-Reply-To: <6.2.3.4.2.20060218032046.05e6a8b0@pop.online.fr>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
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

Somebody said:

> ... You cannot 
> fight disruption without formality. 

An IESG statement issued under the authority granted to the
IESG by RFC 2026 is formal.

    Brian Carpenter
    IETF Chair


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email