Re: IAOC requesting input on (potential) meeting cities

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 26 April 2017 14:23 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BAB12EC3D for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 07:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level:
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 cMD9X7t6izRY for <ietf@ietfa.amsl.com>; Wed, 26 Apr 2017 07:23:55 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 2C17212E855 for <ietf@ietf.org>; Wed, 26 Apr 2017 07:17:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 143491000320; Wed, 26 Apr 2017 07:17:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1493216236; bh=h5BjmB+LWZ0h4ogV8yXQnhtekjbMTonW1AMRxpFrtkQ=; h=Subject:To:References:From:Date:In-Reply-To:From; b=epzyqkdHwDgvgNgspiz4Fd5jARAE0kT27UpTiOc610FZ7n0c99Wh+2wt0m9j6VVlw SJMO0xQNq/+IqXLEPw2Ih+xh9U1OLnM/UNgingSiN0Aya35DiEamdLSaLR2IR8Fc9V xI9TOWNwNJ85J+lNV1xjGsGoU5rqgxMDnyJdZ97k=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [195.50.183.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 32A62240C4F; Wed, 26 Apr 2017 07:17:15 -0700 (PDT)
Subject: Re: IAOC requesting input on (potential) meeting cities
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <28718.1493215497@dooku.sandelman.ca>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <b13a768b-fc53-21f3-9e26-d27f16a32433@joelhalpern.com>
Date: Wed, 26 Apr 2017 10:17:13 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <28718.1493215497@dooku.sandelman.ca>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pSQ_8przL0d84VnYUmEBSs6I5pg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 26 Apr 2017 14:23:57 -0000

Whether in the IETF or elsewhere, there is one aspect you do not mention 
that I find useful asa presenter, and one aspect that I find useful in 
well-done presentations as a participant.

1) As a Presenter, if I have managed to do my presentation right, it 
helps me get the important points covered in the right order.  yes, I 
usually remember them.  But not always.  And it helps in getting back on 
track after useful discussions of particular points.

2) As a participant, I find it very helpful if the slide tells me what 
the presenter considers the critical points for me to think about. 
(There are also the not uncommon cases where a diagram helps me 
understand the point the speaker is trying to make.)

Yours,
Joel

On 4/26/17 10:04 AM, Michael Richardson wrote:
>
> Toerless Eckert <tte@cs.fau.de> wrote:
>     > For example, there is a lot of death by powerpoint in meetings that
>     > pushes off high bandwidth discussions ("oh, we're out of time"). AFAIK,
>     > most active work on drafts during IETF meeting week happens outside of
>
> I am among those who pushes back on death by powerpoint, so I agree with you
> strongly.  Presentations are very easily supported through completely remote
> attendance.  Concurrent jabber back-channel discussion among the participants
> can often bring out points that are sometimes lost in the foreground presentation.
>
> {Maybe we should dispense with the meeting rooms, just wire the hotel rooms
> for GbE, and all be on-site, but "remote".  Then the critical criteria for
> which city to meet in is reduced to where the best beer can be had.  (And so
> Prague wins?)}
>
> But, on somewhat more serious note [note lack of :-) above], I have been told
> the following features about the deathly powerpoints:
>   1) provides a record of thoughts for later on.
>   2) permits non-english speakers to understand what is being said by
>      other non-english speakers!!!
>   3) can be pushed through google-translate.
>   4) can be read ahead of time by chairs and participants so that they
>      can ask intelligent questions, and/or can allocate appropriate amounts
>      of time.
>
>
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>