[Pesci-discuss] Face-to-face meetings (was: Re: IETF Meeting Venue Selection Criteria)

"Spencer Dawkins" <spencer@mcsr-labs.org> Thu, 20 October 2005 18:36 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESfGl-0004Q1-Pf; Thu, 20 Oct 2005 14:36:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESfGk-0004Pv-Cp for pesci-discuss@megatron.ietf.org; Thu, 20 Oct 2005 14:36:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05610 for <pesci-discuss@ietf.org>; Thu, 20 Oct 2005 14:35:52 -0400 (EDT)
Received: from sccrmhc14.comcast.net ([63.240.77.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESfSi-0003x6-V2 for pesci-discuss@ietf.org; Thu, 20 Oct 2005 14:48:26 -0400
Received: from s73602 (unknown[65.104.224.98]) by comcast.net (sccrmhc14) with SMTP id <2005102018354801400rpn5be>; Thu, 20 Oct 2005 18:35:48 +0000
Message-ID: <017d01c5d5a5$0a9e8c10$f5087c0a@china.huawei.com>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "PESCI Discuss Mailing List" <pesci-discuss@ietf.org>
References: <0BDFFF51DC89434FA33F8B37FCE363D502882EEB@zcarhxm2.corp.nortel.com> <43577097.7040503@zurich.ibm.com>
Date: Thu, 20 Oct 2005 13:35:22 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Subject: [Pesci-discuss] Face-to-face meetings (was: Re: IETF Meeting Venue Selection Criteria)
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

Brian just posted a couple of notes on the IETF discussion list about 
"income that we badly need" from attendees at face-to-face IETF meetings.

I had the privilege of attending the SHIM6 and Softwires interim meetings 
last week (I guess they needed a note-taker :-), and the leadeship at both 
meetings was saying, "much more productive than an IETF face-to-face 
meeting".

This mode of operation (lock the same group in a room for multiple days) is 
what I see at the IETF meetings in the SIP community, where they start 
meeting together at 9:00 AM on Monday morning, and stay together through 
multiple meetings of SIP, SIPPING, SIMPLE, and only diffuse slightly into 
ECRIT, XCON, ENUM, AVT/MMUSIC, and BEHAVE (what did I leave out?) - and I 
note there's an ad hoc on SIP peer-to-peer scheduled for Friday afternoon in 
Vancouver.

This is very different from what I think is "normal" for the IETF (attend a 
couple of WGs that meet a couple of times during the week, attend a couple 
of BoFs, and spend the rest of the week talking to people). It's a lot more 
like what I think is "normal" for IEEE (the group stays together for the 
balance of the week, during IEEE plenary meetings).

There were several interim meeting participants who were not planning to 
attend in Vancouver, including one serious contributor who may be missing 
three face-to-face meetings in a row. All this would be fine, except that we 
seem to be financially dependent on meeting fees from the IETF face-to-face 
meetings.

Do we think that the IETF face-to-face meetings are sacred cows that we 
can't eliminate without eliminating the IETF completely? If "yes", is this 
only for financial reasons, or are there others?

Disclaimer - I like attending IETF face-to-face meetings, and even talking 
with you guys while I'm there, so I'm not trying to stir up trouble, only 
trying to understand where we're headed.

Spencer

>> Maybe I am an optimist.  I believe the world is a big place, and are
>> lots of venues where the IETF has not yet met, which would work for all
>> of us, and attract a lot of local participation.
>
> Which, BTW, means income that we badly need.
>
>>
>> My sense of why we are discussing "venue selection criteria" is that we
>> wish to encourage people to volunteer to be local hosts for future IETF
>> meetings.  To make the best use of the prospective local hosts' time, it
>> would help if we could articulate the venues that would be acceptable,
>> versus ones that would not 'meet' (pardon the pun) our venue selection
>> criteria.
>
> It will also help the IAD significantly in comparing hosting offers.
> We also badly need hosts for financial reasons. 


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