Re: [AGENTS] BOF at IETF

John C Klensin <klensin@mail1.reston.mci.net> Sat, 16 November 1996 20:56 UTC

Received: from cnri by ietf.org id aa07175; 16 Nov 96 15:56 EST
Received: from ietf.org by CNRI.Reston.VA.US id aa12733; 16 Nov 96 15:56 EST
Received: from ietf.org by ietf.org id aa07168; 16 Nov 96 15:56 EST
Received: from ns.jck.com by ietf.org id aa07162; 16 Nov 96 15:56 EST
Received: from white-box.jck.com ("port 2047"@white-box.jck.com) by a4.jck.com (PMDF V5.1-3 #16053) with SMTP id <0E0ZE3ANG00HWP@a4.jck.com>; Sat, 16 Nov 1996 15:54:46 -0500 (EST)
Date: Sat, 16 Nov 1996 15:54:45 -0500 (EST)
Sender: iesg-request@ietf.org
From: John C Klensin <klensin@mail1.reston.mci.net>
Subject: Re: [AGENTS] BOF at IETF
In-reply-to: <Pine.SUN.3.94.961116125259.12898L-100000@ester.dsv.su.se>
X-Orig-Sender: john@mail1.reston.mci.net
To: Jacob Palme <jpalme@dsv.su.se>
Cc: Steve Coya <scoya@ietf.org>, Einar Stefferud <stef@nma.com>, Tony Rutkowski <tony@netmagic.com>, iesg@ietf.org, mhtml@segate.sunet.se, fred@cisco.com, directorate@apps.ietf.org
Reply-to: John C Klensin <klensin@mail1.reston.mci.net>
Message-id: <SIMEON.9611161545.B@white-box.mail1.reston.mci.net>
MIME-version: 1.0
X-Mailer: Simeon for Windows Version 4.1a10
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Priority: NORMAL
X-Authentication: none

On Sat, 16 Nov 1996 12:53:46 +0100 (MET) Jacob Palme 
<jpalme@dsv.su.se> wrote:
> There are many other hotels close to the one where IETF intends
> to meet in San Jose. So if there are no rooms at our hotel, we
> might rent rooms at other nearby hotels for additional BOF
> space?

Jacob,

Please see my earlier notes.  We just don't do this -- so-called 
BOFs are an important part of the IETF process and we don't send 
them off somewhere to meet.  Now, if the "agent group" (or OMG 
Agents WG, or whatever,...) decides to rent a room somewhere or pick 
a time in the bar and invite people to come, no one can prevent 
their doing that and few would want to.  But announcements of such 
event do not, by precedent, use any official IETF mechanisms since 
these things aren't part of the IETF agenda.

   john