IETF Logo Mail Archive

Re: STRAW PROPOSAL RFC Editor charter

Brian E Carpenter <brc@zurich.ibm.com> Mon, 20 March 2006 17:47 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLOTg-000152-QQ; Mon, 20 Mar 2006 12:47:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLOTf-00014x-NF for ietf@ietf.org; Mon, 20 Mar 2006 12:47:35 -0500
Received: from mtagate4.uk.ibm.com ([195.212.29.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLOTe-0003cq-Aj for ietf@ietf.org; Mon, 20 Mar 2006 12:47:35 -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 k2KHlXl6304910 for <ietf@ietf.org>; Mon, 20 Mar 2006 17:47:33 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/VER6.8) with ESMTP id k2KHluXR193846 for <ietf@ietf.org>; Mon, 20 Mar 2006 17:47:56 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 k2KHlWXj020991 for <ietf@ietf.org>; Mon, 20 Mar 2006 17:47:32 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 k2KHlWhn020982; Mon, 20 Mar 2006 17:47:32 GMT
Received: from zurich.ibm.com (sig-9-145-248-136.de.ibm.com [9.145.248.136]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id SAA37478; Mon, 20 Mar 2006 18:47:30 +0100
Message-ID: <441EEAB1.6060703@zurich.ibm.com>
Date: Mon, 20 Mar 2006 18:47:29 +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: RJ Atkinson <rja@extremenetworks.com>
References: <E1FK1Xy-00061r-Ep@ietf.org> <6ACEA2C7-996D-4EC2-96D0-017DE756A0BA@extremenetworks.com> <4419FB64.5020709@thinkingcat.com> <441A85AF.6070806@zurich.ibm.com> <81D34F8A-CC15-4E56-9C5C-0B1B6243814F@extremenetworks.com>
In-Reply-To: <81D34F8A-CC15-4E56-9C5C-0B1B6243814F@extremenetworks.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ietf@ietf.org
Subject: Re: STRAW PROPOSAL RFC Editor charter
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

Ran,

I could argue with quite a lot of what you say, but
I won't. Cutting to the chase:

RJ Atkinson wrote:
...
>     The IAB (or possibly ISoc BoT, but more obviously IAB and
> not the IESG) ought to be running and driving any process to create
> or modify a formal RFC Editor charter, at least as long as we have
> the current organisational structure.

The IAB is doing so. This thread was started by the IAB Chair
and I'm an IAB member.

   That process should be
> as open as possible and should include specific outreach to members
> of the Internet R&E community, not primarily focused on IETF folks.

I think it *should* be primarily focussed on the IETF and IRTF
communities. Those are, objectively, the people who generate the
overwhelming majority of RFCs.

     Brian


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

v2.23.0 | Report a Bug | By Email