Re: [97attendees] Liked the Shared Conference Room

John C Klensin <john-ietf@jck.com> Thu, 24 November 2016 08:56 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: 97attendees@ietfa.amsl.com
Delivered-To: 97attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09CF1129B69 for <97attendees@ietfa.amsl.com>; Thu, 24 Nov 2016 00:56:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.397
X-Spam-Level:
X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dd3JruldVU0a for <97attendees@ietfa.amsl.com>; Thu, 24 Nov 2016 00:56:43 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A1E0129B48 for <97attendees@ietf.org>; Thu, 24 Nov 2016 00:56:09 -0800 (PST)
Received: from [198.252.137.10] (helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1c9pp9-000Ofi-PN; Thu, 24 Nov 2016 03:56:07 -0500
Date: Thu, 24 Nov 2016 03:56:02 -0500
From: John C Klensin <john-ietf@jck.com>
To: ggm@apnic.net, 97attendees@ietf.org
Message-ID: <7D2167937A52546C4ABCBA1E@JcK-HP8200>
In-Reply-To: <CAA=nHSJ6RbNAykG6frFfeZ30NDjF9416PUM1rO9ew8fFWUe20g@mail.gmail.com>
References: <EA2116C2-B17A-45BD-B0F1-17BA562D0A7E@cable.comcast.com> <1E5278AD-9499-4E1B-80F9-D582A2BEFE55@gmail.com> <8445456c11e249d69a45af96ceae1d17@NXMDA2.org.apnic.net> <CAA=nHSJ6RbNAykG6frFfeZ30NDjF9416PUM1rO9ew8fFWUe20g@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/97attendees/u5Mu1IauQbvyG3vlz5K-p910wtY>
Subject: Re: [97attendees] Liked the Shared Conference Room
X-BeenThere: 97attendees@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Mailing list of IETF 97 attendees that have opted in on this list." <97attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/97attendees>, <mailto:97attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/97attendees/>
List-Post: <mailto:97attendees@ietf.org>
List-Help: <mailto:97attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/97attendees>, <mailto:97attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2016 08:56:50 -0000


--On Thursday, November 17, 2016 16:53 +0900 George Michaelson
<ggm@apnic.net> wrote:

> Used it, appreciated it. I suspect as word spreads we'll find
> we want more, and this begs many questions about what IETF is,
> because these things, ephemeral meetings we all do, are
> becoming a stronger driver than WG activity for some people.
> 
> The assumption we want more of these short-term-use easy
> private access spaces begs questions I don't think I
> understand.

Wasn't there, but two observations:

(1) If the hotel or conference facility doesn't provide informal
sitting/gathering space (with the typical lobby coffee area/ bar
as an example), then some sort of reserve-able meeting space may
be very important.

(2) Independent of side conversations that are largely unrelated
to IETF work, people should remember that our IPR requirements
and other procedures more or less assume that we've only got two
flavors of f2f meetings for IETF work: WG meetings that are
announced in advance, open, produce minutes or equivalent
meeting notes, etc. and design team meetings (on which there are
some explicit constraints).  If we are going to encourage and
legitimize potentially-closed small group meetings by providing
space, sign up sheets, and other facilities, do those
requirements and procedures need review and possible revision,
particularly to lower the odds that such meetings can be
mistaken for IETF-facilitated secret cabals to influence the
content of standards?

Just trying to think ahead.

    best,
    john