Re: For Review: IESG Statement on Guidance on Face-to-Face and Virtual Interim Meetings
Nadeau Thomas <tnadeau@lucidvision.com> Fri, 11 December 2015 14:19 UTC
Return-Path: <tnadeau@lucidvision.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 4AB141ACEEF for <ietf@ietfa.amsl.com>; Fri, 11 Dec 2015 06:19:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level:
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 908FAXsX6IQi for <ietf@ietfa.amsl.com>; Fri, 11 Dec 2015 06:19:45 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [64.71.170.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AEFC1ACDBB for <ietf@ietf.org>; Fri, 11 Dec 2015 06:19:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lucidvision.com; s=default; t=1449843560; bh=BVsdAeGl/qG5gmwr+eq4H6xLFvDYk1YxqV2+DpmHbCk=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=UZ5fiWNCx6Jw00b1dqldIhU5rJ3h42anq60fiy3Tqxkm6ITn0dq7BnpHJhmK1Zjc3 olePKTeP13/WLuBLx1iGRJx+YVkyNdj59HVn5B2P3+N+yvQmnL0Bj2CFoMVo6E78qD Py0hm7C80vxrbr6ypFE5qbX0o4H53HlawcfSmvqM=
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.255.148.181;
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Subject: Re: For Review: IESG Statement on Guidance on Face-to-Face and Virtual Interim Meetings
From: Nadeau Thomas <tnadeau@lucidvision.com>
In-Reply-To: <566A95C3.8040106@cisco.com>
Date: Fri, 11 Dec 2015 09:19:40 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <87ACBDDF-4D38-4FCC-BF62-BB334AEB2C7E@lucidvision.com>
References: <20151210164031.22024.98672.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA6BEBFAA5@AZ-FFEXMB04.global.avaya.com> <A588E0AF-ADA4-4A3B-8C53-264A7812B1E0@piuha.net> <9904FB1B0159DA42B0B887B7FA8119CA6BEC023E@AZ-FFEXMB04.global.avaya.com> <566A95C3.8040106@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.3096.5)
X-Authenticated-User: tnadeau@lucidvision.com
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=3 Stars=0 Good=0 Friend=0 Surbl=0 Catch=0 r=0 ip=50.255.148.181
X-IP-stats: Notspam Incoming Last 0, First 210, in=2826, out=0, spam=0 Known=true ip=50.255.148.181
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KyaFQ3BRYyqfC8Kt2ViGhLcOCwU>
Cc: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "ietf@ietf.org" <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: Fri, 11 Dec 2015 14:19:46 -0000
I agree. Groups should actually be free to use whatever tools make sense for the task at hand. One group I run in ODL simply uses IRC and makes fine progress, but another uses G Hangouts, and NETMOD uses WebEx + Etherpad. It shouldn’t matter as long as the collaboration is as effective as possible for the participants. If it isn’t, the WG Chairs should be empowered to make it so. —Tom > On Dec 11, 2015:4:22 AM, at 4:22 AM, Benoit Claise <bclaise@cisco.com> wrote: > > Hi Dan, > > I understand your arguments: cost and the ease of having a meetecho/webex these days. > However, I've been in at least one interim meeting focused on white board sessions. > And, even with all the good will, white board sessions and remote participations, just don't work together. > > I favor a should in your initial sentence: > "Remote participation (via Meetecho or similar) must be provided" > > Regards, Benoit >> Hi Jari, >> >> I oscillated between 'should' and 'must' myself. The principal reason I ended with a 'must' was that agreeing on exceptions can be perceived as excluding people from the process. In the real world some of us live justifying funds for 1-2 days interim of one WG is more difficult than getting a full IETF week approved. Remote participation is the only option. The 'must' requirement also seems pretty ubiquitous nowadays - it translates into 'the host of a f2f interim must ensure that a microphone and external phone connection exists in the room and the chairs must activate Meetecho or Webex'. >> >> Regards, >> >> Dan >> >> >>> -----Original Message----- >>> From: Jari Arkko [mailto:jari.arkko@piuha.net] >>> Sent: Thursday, December 10, 2015 10:02 PM >>> To: Romascanu, Dan (Dan) >>> Cc: ietf@ietf.org >>> Subject: Re: For Review: IESG Statement on Guidance on Face-to-Face and >>> Virtual Interim Meetings >>> >>> Dan, >>> >>>> I suggest to add the following bullet to the face-to-face interim guidelines: >>>> >>>> - Remote participation (via Meetecho or similar) must be provided >>> I think that's a good addition, although I'd probably use the keyword 'should' >>> to leave some wiggle room for special situations. We don't need to specify >>> everything that the working groups do as rules. >>> If the WG has reasonable leadership, they will do the right thing. >>> >>> Jari >> . >> >
- For Review: IESG Statement on Guidance on Face-to… IESG Secretary
- Re: For Review: IESG Statement on Guidance on Fac… Dave Crocker
- Re: For Review: IESG Statement on Guidance on Fac… Eliot Lear
- RE: For Review: IESG Statement on Guidance on Fac… Adrian Farrel
- RE: For Review: IESG Statement on Guidance on Fac… Romascanu, Dan (Dan)
- Re: For Review: IESG Statement on Guidance on Fac… Fred Baker (fred)
- Re: For Review: IESG Statement on Guidance on Fac… Brian E Carpenter
- Re: For Review: IESG Statement on Guidance on Fac… Jari Arkko
- Re: For Review: IESG Statement on Guidance on Fac… Thomas Narten
- RE: For Review: IESG Statement on Guidance on Fac… Romascanu, Dan (Dan)
- Re: For Review: IESG Statement on Guidance on Fac… Harald Alvestrand
- Re: For Review: IESG Statement on Guidance on Fac… Benoit Claise
- Re: For Review: IESG Statement on Guidance on Fac… Jari Arkko
- Re: For Review: IESG Statement on Guidance on Fac… Benoit Claise
- Re: For Review: IESG Statement on Guidance on Fac… Joel M. Halpern
- Re: For Review: IESG Statement on Guidance on Fac… Benoit Claise
- RE: For Review: IESG Statement on Guidance on Fac… Romascanu, Dan (Dan)
- Re: For Review: IESG Statement on Guidance on Fac… Harald Alvestrand
- RE: For Review: IESG Statement on Guidance on Fac… Romascanu, Dan (Dan)
- Re: For Review: IESG Statement on Guidance on Fac… Nadeau Thomas
- Re: For Review: IESG Statement on Guidance on Fac… Nadeau Thomas
- Re: For Review: IESG Statement on Guidance on Fac… Dave Crocker
- Re: For Review: IESG Statement on Guidance on Fac… Ben Campbell
- Re: For Review: IESG Statement on Guidance on Fac… Dave Crocker
- Re: For Review: IESG Statement on Guidance on Fac… Alia Atlas
- Re: For Review: IESG Statement on Guidance on Fac… Brian E Carpenter
- Re: For Review: IESG Statement on Guidance on Fac… Michael Richardson
- Re: For Review: IESG Statement on Guidance on Fac… Yoav Nir
- Re: For Review: IESG Statement on Guidance on Fac… Rich Kulawiec
- Re: For Review: IESG Statement on Guidance on Fac… Michael Richardson
- Re: For Review: IESG Statement on Guidance on Fac… Brian E Carpenter
- Re: For Review: IESG Statement on Guidance on Fac… Andrew Sullivan