Re: Concerns about Singapore

"HANSEN, TONY L" <tony@att.com> Tue, 12 April 2016 18:33 UTC

Return-Path: <tony@att.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 9AE2012E1D4 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] 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 H186ZKW4EN5j for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:33:15 -0700 (PDT)
Received: from mx0b-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 57FCE12E4B4 for <ietf@ietf.org>; Tue, 12 Apr 2016 11:33:14 -0700 (PDT)
Received: from pps.filterd (m0049463.ppops.net [127.0.0.1]) by m0049463.ppops.net-00191d01. (8.16.0.11/8.16.0.11) with SMTP id u3CIT75k048172; Tue, 12 Apr 2016 14:32:57 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049463.ppops.net-00191d01. with ESMTP id 2294t0usp2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 12 Apr 2016 14:32:57 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u3CIWtrH017114; Tue, 12 Apr 2016 14:32:56 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u3CIWoGw016999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 12 Apr 2016 14:32:53 -0400
Received: from MISOUT7MSGHUBAG.ITServices.sbc.com (MISOUT7MSGHUBAG.itservices.sbc.com [130.9.129.151]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Tue, 12 Apr 2016 18:32:39 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.206]) by MISOUT7MSGHUBAG.ITServices.sbc.com ([130.9.129.151]) with mapi id 14.03.0248.002; Tue, 12 Apr 2016 14:32:39 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: Rich Kulawiec <rsk@gsp.org>, ietf <ietf@ietf.org>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkPrmyaIeX02t9k2vDkQbYq+JzJ9/GEYAgAALigCAAAhOgIAAArkAgAACkgCAAAIPAIABI9GAgAF5/gCAAJkigIAAHRiAgAD2LYCAAATrgIAACooAgAADTgCAAACzAIAAWpOAgABVDYCAABLcgIAAXz+AgAAstICAABnMgIAArDoAgAAWc4CAALrLgIAAN+AA
Date: Tue, 12 Apr 2016 18:32:37 +0000
Message-ID: <A336C66D-2BCD-4693-ADA9-080EA1CD3B70@att.com>
References: <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <20160412110259.GA7267@gsp.org>
In-Reply-To: <20160412110259.GA7267@gsp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.110.240.68]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B1E54FC82D93D5418890AAB578F5F8D2@LOCAL>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-04-12_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603180000 definitions=main-1604120265
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/x4lb73D9thbQU4eECZqFBCgx6KI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 12 Apr 2016 18:33:23 -0000

I encourage people who have suggestions on how to do remote meetings to join the conversation in vmeet@ietf.org.

	Tony Hansen

On 4/12/16, 7:02 AM, "ietf on behalf of Rich Kulawiec" <ietf-bounces@ietf.org on behalf of rsk@gsp.org> wrote:

>On Mon, Apr 11, 2016 at 07:54:25PM -0400, Ted Lemon wrote:
>> If we were to attempt such a thing, how do you think it would work?
>
>Let me preface this by saying that I think attempts to completely
>mimic the current in-person meeting experience as it exists probably
>won't work.  They might: but they probably won't.  But then again,
>I don't think that's entirely necessary: processes and procedures
>change (compare boarding a steamship in 1930 with an aircraft in 2005)
>and evolve in order to work with technology.
>
>So if I were to envision this, things I'd want to experiment with
>would include:
>
>- passive view-only, listen-only read-only access to anyone, anonymously.
>(That is: no registration required.)
>
>- levels of read-write access, perhaps (roughly speaking) distinguished
>as text, audio, and video.  Participants could select based on their
>available bandwidth and on the level they're comfortable with.  I think
>it's reasonable to require registration for write access.
>
>- a channel for presentation content only. Again, this is an option for
>those with limited bandwidth or limited time.
>
>- ability to delay/time-shift.
>
>- perhaps restructuring long sessions into smaller time slots.  If people
>have all travelled to the same place, then it makes sense to get a lot
>done in a short time, and so a four hour session (for example) makes
>sense.  But if people are in disparate locations, then maybe four one-hour
>sessions make more sense.  This also better accomodate people who have
>trouble carving out four hours in the middle of their day.  Or night.
>
>- integrated storage of sessions, so that someone can watch, listen,
>read, and absorb the entire experience.  Useful for someone half a
>planet away who won't be (or can't be) awake for real-time participation.
>
>- translations and/or text captioning and/or some kind of assistance
>for non-native speakers and the hearing impaired.
>
>- emphasis on the inclusion of participants who can't make it to meetings
>today, either because of time, money, politics, distance, family, job, etc.
>
>Over and above all of this: a willingness to experiment and to have
>some of those expirements fail -- which they will.
>
>---rsk