Virtual BOFs (was: Re: Venue Announcement for IETFs 98, 99, 102 and 111)
John C Klensin <john-ietf@jck.com> Sat, 09 January 2016 14:55 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC3501A87C4 for <ietf@ietfa.amsl.com>; Sat, 9 Jan 2016 06:55:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 olzVTM3vyGQB for <ietf@ietfa.amsl.com>; Sat, 9 Jan 2016 06:55:04 -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 03E8E1A87BF for <ietf@ietf.org>; Sat, 9 Jan 2016 06:55:04 -0800 (PST)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aHuuv-0007XG-Tw; Sat, 09 Jan 2016 09:54:57 -0500
Date: Sat, 09 Jan 2016 09:54:52 -0500
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>, Nadeau Thomas <tnadeau@lucidvision.com>
Subject: Virtual BOFs (was: Re: Venue Announcement for IETFs 98, 99, 102 and 111)
Message-ID: <280B5E0546882DCF4E8FD4CB@JcK-HP8200.jck.com>
In-Reply-To: <5E3C5BC3-B3ED-43F6-92E9-D5BEEBBE71FA@piuha.net>
References: <20160105210603.26728.22600.idtracker@ietfa.amsl.com> <AB383E7EE1632A97AC7D544E@JcK-HP8200.jck.com> <2AED06ED-932E-45A5-860B-93FC2E78BE27@isoc.org> <02FAD6B271183972FE511EF0@JcK-HP8200.jck.com> <alpine.OSX.2.01.1601071125550.21147@rabdullah.local> <92612612B8B7E9BC3EE54AB7@JcK-HP8200.jck.com> <7EA5887F-FD0E-49E7-B164-E7BC37C635DB@thinkingcat.com> <422D84C5-86A9-47C8-8131-775A1566E189@lucidvision.com> <5E3C5BC3-B3ED-43F6-92E9-D5BEEBBE71FA@piuha.net>
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: <http://mailarchive.ietf.org/arch/msg/ietf/z4MozE9vRoj3V5wE0QGq6gDDgng>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jan 2016 14:55:05 -0000
--On Saturday, January 09, 2016 11:21 +0200 Jari Arkko <jari.arkko@piuha.net> wrote: > Here's a question that I think would be worthwhile to > consider. We do create working groups in some cases even > without running a physical BOF meeting, but mostly in cases > where the creation of that working group is a no brainer. What > would it take to run the next interesting/controversial BOF as > a virtual meeting? It would great if we could do this, but > I'm not sure it is easy either. (I'm not trying to > eliminate the meetings as a useful venue to do BOFs, but in > many cases the ability to decide the matter when it comes up > as opposed to many months away might be useful for other > reasons.) Jari, Probably an excellent idea, especially since I can only see four possible outcomes from any given attempt: (1) "We know enough now, form the WG". In that case, we save calendar and meeting time and are able to get on with the work sooner. (2) "This is conclusively a bad idea or not ready for IETF work" or "it is now clear that no one other than the author cares". As with the above, saves time and allows us to get on with our lives. (3) "Don't know enough, need either another virtual meeting or an in-person BOF". In that case, we haven't really lost anything and probably have more information than we would have had from mailing list discussion alone. (4) "Couldn't make a determination, due eitherto lack of attendance by key people or some technical issue.". As with (3), little has been lost and we can always hold a physical BOF under traditional rules if needed. Each of those seems to me to be a win, although in different ways. Equally useful, if we encouraged people to hold these virtual sessions well before the request cut-off date for in-meeting BOFs, those who requested them will be able to submit normal request if needed, will have more information, and IETF work will be better spread out between meetings. best, john
- Re: Venue Announcement for IETFs 98, 99, 102 and … Lou Berger
- Re: Venue Announcement for IETFs 98, 99, 102 and … Mary Barnes
- Re: Venue Announcement for IETFs 98, 99, 102 and … Michael Richardson
- Venue Announcement for IETFs 98, 99, 102 and 111 IETF Administrative Director
- Re: Venue Announcement for IETFs 98, 99, 102 and … John C Klensin
- Re: Venue Announcement for IETFs 98, 99, 102 and … Ray Pelletier
- Re: Venue Announcement for IETFs 98, 99, 102 and … Behcet Sarikaya
- Re: Venue Announcement for IETFs 98, 99, 102 and … John C Klensin
- Re: Venue Announcement for IETFs 98, 99, 102 and … Ole Jacobsen
- Re: Venue Announcement for IETFs 98, 99, 102 and … John C Klensin
- Re: Venue Announcement for IETFs 98, 99, 102 and … Leif Johansson
- Re: Venue Announcement for IETFs 98, 99, 102 and … Scott Bradner
- Re: Venue Announcement for IETFs 98, 99, 102 and … Leslie Daigle
- Re: Venue Announcement for IETFs 98, 99, 102 and … Nadeau Thomas
- Re: Venue Announcement for IETFs 98, 99, 102 and … Michael StJohns
- Re: Venue Announcement for IETFs 98, 99, 102 and … Jari Arkko
- Re: Venue Announcement for IETFs 98, 99, 102 and … Leif Johansson
- Re: Venue Announcement for IETFs 98, 99, 102 and … thomas nadeau
- Virtual BOFs (was: Re: Venue Announcement for IET… John C Klensin
- Re: Virtual BOFs Brian E Carpenter
- Re: Virtual BOFs Phillip Hallam-Baker
- Re: Virtual BOFs John C Klensin
- Re: Venue Announcement for IETFs 98, 99, 102 and … Doug Barton
- Re: Virtual BOFs Phillip Hallam-Baker
- Re: Virtual BOFs John C Klensin