Re: Friday @ IETF61?

Harald Tveit Alvestrand <harald@alvestrand.no> Wed, 01 September 2004 16:20 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04686; Wed, 1 Sep 2004 12:20:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Xsl-00019K-DZ; Wed, 01 Sep 2004 12:22:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2XMB-0004sg-MC; Wed, 01 Sep 2004 11:49:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2VEv-0003oG-Bv for ietf@megatron.ietf.org; Wed, 01 Sep 2004 09:33:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05537 for <ietf@ietf.org>; Wed, 1 Sep 2004 09:33:24 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2UsC-0005E4-3A for ietf@ietf.org; Wed, 01 Sep 2004 09:10:01 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2C12D61B9D; Wed, 1 Sep 2004 15:07:12 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21173-10; Wed, 1 Sep 2004 15:07:10 +0200 (CEST)
Received: from [192.168.1.4] (145.80-202-211.nextgentel.com [80.202.211.145]) by eikenes.alvestrand.no (Postfix) with ESMTP id E04DE61B89; Wed, 1 Sep 2004 15:07:08 +0200 (CEST)
Date: Wed, 01 Sep 2004 15:07:06 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Message-ID: <21B643BC0DEBC0C9E0937043@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20040831110959.GG20023@login.ecs.soton.ac.uk>
References: <20040831110959.GG20023@login.ecs.soton.ac.uk>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Subject: Re: Friday @ IETF61?
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>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit


--On tirsdag, august 31, 2004 12:09:59 +0100 Tim Chown 
<tjc@ecs.soton.ac.uk> wrote:

> So,
>
> Are there any real Friday sessions at IETF 61, or not?
>
> Someone tried to put v6ops on Friday am at IETF 60, before shifting
> it out... it would be nice to either have IETF run out to 2-3pm and
> have some real sessions, or simply make Friday officially BoFs only...

Tim,

so far, the proposal I have the most sympathy for is to add a post-lunch 
Friday session. The San Diego agenda was NOT easy on many!

For the last "n" meetings, we have always started out with Friday morning 
as "real sessions"; as the agenda has developed, the secretariat has tended 
to fill in Friday last, and people have tended to ask for "not Friday" 
meetings - which has been accomodated by the secretariat.

Sometimes this has led to Friday being no sessions, or Friday having just 
"odd" sessions (like second slots). Last time, it was pretty full.

So we're starting out the same as last time: Friday is real.

But - I think "BOF only" is a non-starter; BOFs are our official procedure 
for having an IETF face-to-face discussion on whether or not to start a 
working group. Having all of them on top of each other would be - to put it 
mildly - not optimal.
(Yes, some BOFs have other purposes. But this is one of them.)

                         Harald




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