Re: Virtual BOFs
Phillip Hallam-Baker <phill@hallambaker.com> Sun, 10 January 2016 04:47 UTC
Return-Path: <hallam@gmail.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 286951A0060 for <ietf@ietfa.amsl.com>; Sat, 9 Jan 2016 20:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 VJsGx-sH0LFH for <ietf@ietfa.amsl.com>; Sat, 9 Jan 2016 20:47:39 -0800 (PST)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DED4A1A004E for <ietf@ietf.org>; Sat, 9 Jan 2016 20:47:38 -0800 (PST)
Received: by mail-lb0-x22a.google.com with SMTP id cl12so22526427lbc.1 for <ietf@ietf.org>; Sat, 09 Jan 2016 20:47:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=05vaX+zKgqQgiqG3BaKJNVlaTOHTnqD9EH6WBaY43yA=; b=W5kYBOPN8kynhYWJLbm2/oDE1kXpDWLXYRU3Q188O+/QAif+b2Fwjh+PdodiQSnx32 uqeVhTRx6Ri9FiYnEiLytBovK47WRL24v/eblAApaFg4QUZVdt9Lt0FJUqPw7EsTKY3a rfAZDHgCRGB5yXFRfuFhgo9zTG6/YDhNGwBQsu9H7+ytBS5ck5E8xzKNKq7Qjnxzc9Mb BIbCDvgqvcpKTLwfvG4zxxfP7tIoNIfiUxH0Qaucen+v6s2oEt/zj9G1paTplmnrwW9O zUPAfCXUxTY51qUzFrLx2A32nboAC91vEifhUyLHtNWPX6CsnDb2hVEAJU+WI/2obgrH d15A==
MIME-Version: 1.0
X-Received: by 10.112.64.5 with SMTP id k5mr25468695lbs.133.1452401256901; Sat, 09 Jan 2016 20:47:36 -0800 (PST)
Sender: hallam@gmail.com
Received: by 10.112.1.33 with HTTP; Sat, 9 Jan 2016 20:47:36 -0800 (PST)
In-Reply-To: <86BF3589740E7D2FDC2F34EA@JcK-HP8200.jck.com>
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> <280B5E0546882DCF4E8FD4CB@JcK-HP8200.jck.com> <5691542D.4060903@gmail.com> <86BF3589740E7D2FDC2F34EA@JcK-HP8200.jck.com>
Date: Sat, 09 Jan 2016 23:47:36 -0500
X-Google-Sender-Auth: OSVhHSnFeVXVM-irtiRD89Or6zA
Message-ID: <CAMm+Lwgs+vRYUaChyycSePpJf7oLRjkT_1qnZkMv+3wDm-o6kw@mail.gmail.com>
Subject: Re: Virtual BOFs
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mjKPhaesk7jHAAULVun4X1uMucA>
Cc: IETF Discussion Mailing List <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: Sun, 10 Jan 2016 04:47:41 -0000
On Sat, Jan 9, 2016 at 3:53 PM, John C Klensin <john-ietf@jck.com> wrote: > > > --On Sunday, January 10, 2016 07:40 +1300 Brian E Carpenter > <brian.e.carpenter@gmail.com> wrote: > >>> (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. >> >> Speaking from the time-zone-challenged corner, I see a high >> risk of hitting (4) rather frequently. Of course you can argue >> that there is also a high risk of hitting (4) with face2face >> BOFs at unpopular destinations. > > Yes. I could also suggest that the virtual plan gives more > flexibility of scheduling to accommodate people who are > "normally" time-zone-challenged or even of holding two sessions > at different times and collecting information from both. (4) > may certainly happen and, again, if it does, it seems to me that > we gain some small amount of information and don't lose much. > We will clearly have to experiment and learn as we go along but > it seems to me that, if we don't need just about everyone in the > same physical room at the same time, it opens up all sorts of > possibilities. > >> That said, it does seem worth a try. > > thx. > > john > > p.s. I read Phillip's note, but I see most of the issues he has > raised as more "bad charter", "bad WG management", "failure of > the IESG to supervise adequately", or even "not enough > mechanisms for feedback by the broader community into how a WG > is going" and not specifically BOF problems. The BOF part of the issue is what the purpose of the BOF should be. I think we spend rather too little time discussing what the general problem space is. There are main two ways that a WG can fail. The first is that they pick something so big and complex that they can't deliver. We haven't done that for a long time. The second is that they tackle a problem so small that either nobody cares or nobody can actually make use of it without the rest of the support required. We do that a lot. Having a virtual BOF and spending a day or two days brainstorming the problem area is probably a better use of people's time than a lot of other things we do.
- 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