Re: [Pesci-discuss] Fw: (from Techspec) Non-Author Editing
sob@harvard.edu (Scott Bradner) Wed, 23 November 2005 14:31 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EevfB-0007Lv-7O; Wed, 23 Nov 2005 09:31:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EevfA-0007Lq-Ly for pesci-discuss@megatron.ietf.org; Wed, 23 Nov 2005 09:31:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08609 for <pesci-discuss@ietf.org>; Wed, 23 Nov 2005 09:31:16 -0500 (EST)
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eevy2-0004ti-43 for pesci-discuss@ietf.org; Wed, 23 Nov 2005 09:51:27 -0500
Received: by newdev.harvard.edu (Postfix, from userid 501) id AB02C58F0DE; Wed, 23 Nov 2005 09:31:41 -0500 (EST)
To: pesci-discuss@ietf.org
Subject: Re: [Pesci-discuss] Fw: (from Techspec) Non-Author Editing
Message-Id: <20051123143141.AB02C58F0DE@newdev.harvard.edu>
Date: Wed, 23 Nov 2005 09:31:41 -0500
From: sob@harvard.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process Evolution Study Committee of the IETF discussion <pesci-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pesci-discuss>
List-Post: <mailto:pesci-discuss@ietf.org>
List-Help: <mailto:pesci-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=subscribe>
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org
Sam sed: > I don't think this is true. I think an IETF consensus can and should > be able to change the text of a WG draft over a WG objection. in theory this sounds like a Good Thing because I think it would result in the best technology & standards but moving from theory and real process could be tricky. The assumption in RFC 2026 etc is that the results of the IETF last call and/or IESG review go back to the WG for the WG to decide what to do (i.e. the pen is not given over to someone else w/o the WG buyin - for example to th RFC Editor notes the IESG can add to Protocol Action notices) Having a process to tell the WG that it MUST make a particular change is not currently in the process but that does not mean that it can not be done. (some people have complained that this happens already when an IESG member makes it clear that a DISCUSS will not be cleared until a particulkar change is made in a document) I do not think that the IESG "can and should be able to change the text of a WG draft over a WG objection" so the process of determining "IETF consensus" for requiring a change over the WG's "better judgement" needs some thinking out so as to not have the IESG be tempted to take on that role Scott _______________________________________________ Pesci-discuss mailing list Pesci-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/pesci-discuss
- [Pesci-discuss] Fw: (from Techspec) Non-Author Ed… Spencer Dawkins
- Re: [Pesci-discuss] Fw: (from Techspec) Non-Autho… Sam Hartman
- RE: [Pesci-discuss] Fw: (from Techspec) Non-Autho… Wijnen, Bert (Bert)
- RE: [Pesci-discuss] Fw: (from Techspec) Non-Autho… Harald Tveit Alvestrand
- Re: [Pesci-discuss] Fw: (from Techspec) Non-Autho… Spencer Dawkins
- Re: [Pesci-discuss] Fw: (from Techspec) Non-Autho… Scott Bradner
- Re: [Pesci-discuss] Fw: (from Techspec) Non-Autho… Sam Hartman
- Re: [Pesci-discuss] Fw: (from Techspec) Non-Autho… Scott Bradner
- Scope [was Re: [Pesci-discuss] Fw: (from Techspec… Brian E Carpenter
- Re: [Pesci-discuss] Fw: (from Techspec) Non-Autho… Brian E Carpenter