Re: [Pesci-discuss] [Fwd:I-D ACTION:draft-davies-pesci-initial-considerations-01.txt]

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 27 January 2006 09:30 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 1F2PwQ-0003Ll-L0; Fri, 27 Jan 2006 04:30:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2PwJ-0003K1-UB for pesci-discuss@megatron.ietf.org; Fri, 27 Jan 2006 04:30:46 -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 EAA20323 for <pesci-discuss@ietf.org>; Fri, 27 Jan 2006 04:29:10 -0500 (EST)
Received: from relay1.mail.uk.clara.net ([80.168.70.141]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F2Q6Q-0007E2-An for pesci-discuss@ietf.org; Fri, 27 Jan 2006 04:41:11 -0500
Received: from host12-128.pool81119.interbusiness.it ([81.119.128.12] helo=Puppy) by relay1.mail.uk.clara.net with esmtpa (Exim 4.46) id 1F2Pw2-0009dt-IF; Fri, 27 Jan 2006 09:30:26 +0000
Message-ID: <022301c62324$d9382cd0$06807751@Puppy>
From: Adrian Farrel <adrian@olddog.co.uk>
To: Brian E Carpenter <brc@zurich.ibm.com>, Pekka Savola <pekkas@netcore.fi>
References: <43C92D1B.8040103@zurich.ibm.com><Pine.LNX.4.64.0601161542050.5861@netcore.fi> <43CBBD86.8040809@zurich.ibm.com>
Subject: Re: [Pesci-discuss] [Fwd:I-D ACTION:draft-davies-pesci-initial-considerations-01.txt]
Date: Thu, 26 Jan 2006 08:41:08 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Clara-Relay: Message sent using Claranet Relay Service using auth code: olddog
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Cc: pesci-discuss@ietf.org
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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

It seems to me that P3 already covers taking advice from the IESG.

Further P2 requires rough consensus of the IETF. It seems unlikely to me
that if the IESG objected this would not influence the formation of rough
consensus because they would state their opinions in a public forum and
their opinions would carry weight appropriate to their positions. If, in
Brian's example, the effect of a change was considerable (30% increase in
IESG time, massive cost, etc.) I would expect to see this pointed out by
the IESG during the discussion phase with the effect that either the
proposal was modified or the rough consensus was not achieved.

This, IMHO, is how the IETF rough consensus process is supposed to work.
Thus, while we would clearly want to have buy-in from the IESG and other
bodies, it is relatively unlikely that we would have gotten to the stage
of needing buy-in unless:
- there was already IESG support
- there was massive IETF support
- the difference in opinion was minor and on some small point

Thanks,
Adrian

----- Original Message ----- 
From: "Brian E Carpenter" <brc@zurich.ibm.com>
To: "Pekka Savola" <pekkas@netcore.fi>
Cc: <pesci-discuss@ietf.org>
Sent: Monday, January 16, 2006 3:36 PM
Subject: Re: [Pesci-discuss] [Fwd:I-D
ACTION:draft-davies-pesci-initial-considerations-01.txt]


> Pekka,
>
> >> From Principles, P4 is indeed a tricky one.  I'd say that "Formal
> >
> > consent from [current leadership]" is too strong wording.  I'd say
that
> > they must be allowed to comment on the proposal.  Whether they could
> > consent to it or not is IMHO irrelevant.  The whole point is that if
> > there would be IETF consensus for making the choice, I'm not sure
> > whether it's OK that any of {IESG,IAB,IAOC} alone should be able to
> > block the process.  (I'd be OK if some form of consent was needed from
a
> > majority of the bodies.)
>
> Yes, this is certainly a tricky point. You can imagine the mess if a
> change was agreed by a new process that the IESG decided was completely
> unworkable, or that would cost $500,000 extra in secretariat work. But
note,
> this does not say *approval* by [current leadership]. It says consent.
> We could define the rules for consent in a different way from the normal
> rules for approval of technical documents (e.g. a simple majority vote,
> with nothing like a Discuss option).
>
>      Brian
>
>
>
> _______________________________________________
> Pesci-discuss mailing list
> Pesci-discuss@ietf.org
> https://www1.ietf.org/mailman/listinfo/pesci-discuss
>
>


_______________________________________________
Pesci-discuss mailing list
Pesci-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/pesci-discuss