From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Tue Apr 28 13:44:56 2020 Return-Path: X-Original-To: sc22wg5-dom9 Delivered-To: sc22wg5-dom9@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 44304356E4A; Tue, 28 Apr 2020 13:44:56 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from mail-qt1-f173.google.com (mail-qt1-f173.google.com [209.85.160.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id D381E3566A9 for ; Tue, 28 Apr 2020 13:44:55 +0200 (CEST) Received: by mail-qt1-f173.google.com with SMTP id t20so4901886qtq.13 for ; Tue, 28 Apr 2020 04:44:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stevelionel.com; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=kNbuYwNT5eW+4Rqt911mePA6vWj7fbO8HbTXzYatjOg=; b=ud3QcJFYnIIrSvumVt8XyKfJ4V03PDwqXkgqq6oALZaZutp6INL7xHZG7tGhZvZDBd 2ZOzyUDO6dg4K/M0IJ359U6l7oG4jsvS+BLKTJZExE3WiuVhpV8mXNbV6vBmNFReNPov hvbaWt1+hfTcUJ8YYXTVb08SkAPRZep0A2jEw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=kNbuYwNT5eW+4Rqt911mePA6vWj7fbO8HbTXzYatjOg=; b=Hh50xP9B1yVo3fjploIEK3Y3i9TlWXDyWGMe8Ec8zCACOfX2EOsvzbrD/7FUAeTwm4 hpJ7X5+rZw6iki/3m4Bc4tttDS8XmaNcvDitycZX8nTnkUN4UlA6h3E8d4kzCZQSwSdM 4w14fX9Kq1t3ebgOxrc9wyTref3tk8NBHBoszUSmbC0rj4WAsD8aLc5PF/kdVpfcfZfP oPKd4v/5fNuyJFAXmoIG5aso5m11nCQDSHE3Qm/EaZwBpYGcvmVKal3gWqLEFrvQaHBV SIzQhM1p5Qyg2ICiMBzTe6zrztYywVB8gmR8PKVvidUHL7I8eg02Qjms/yTLSHpe5Whk NjKw== X-Gm-Message-State: AGi0PuZBbIhpGy2YSebM010ApLv3HnG3XUD/mFEqn4kw1D3t6Uwv1EQ1 A3MZH2rUrlQoORMBt/YTS38Qy3SZrNR5nw== X-Google-Smtp-Source: APiQypIsvngvvVBlQlvTIabBhjlbtR2HkvmiO3g+DoFFenUW2wZRe9olJE5+tOuszBs4PsbMbyVY7g== X-Received: by 2002:ac8:7448:: with SMTP id h8mr28665721qtr.225.1588074293842; Tue, 28 Apr 2020 04:44:53 -0700 (PDT) Received: from [192.168.1.2] ([71.241.130.117]) by smtp.gmail.com with ESMTPSA id 103sm13482557qte.82.2020.04.28.04.44.53 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 28 Apr 2020 04:44:53 -0700 (PDT) Subject: Re: [J3] (SC22WG5.6172) October meeting visa invitation letter To: WG5 List References: <20200428004737.19A4F9DB145@www.open-std.org> From: Steve Lionel X-Clacks-Overhead: GNU Terry Pratchett Message-ID: Date: Tue, 28 Apr 2020 07:44:52 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: owner-sc22wg5@open-std.org Precedence: bulk I agree, and I already have a chat with INCITS scheduled for this week where this will be one of the topics. ISO already provides Zoom, but we would need hardware (speakerphones), at least for J3 meetings. (INCITS probably offers Zoom or similar, but I don't recall seeing announcement of that.) WG5 meetings are USUALLY held at locations where speakerphones are available, but as far as I know this doesn't extend to our usual venue for J3. (My experience with people using laptops as speakerphones is not positive.) I will find out what assistance is available and what we're expected to fund on our own. I think it is also a good time to reevaluate the way J3 does its work, with the subgroups splitting off and largely working independently. "time-shifted engagement" is indeed what we likely need. Steve On 4/28/2020 3:43 AM, Nathan Sircombe via J3 wrote: > Hi, > > I wonder, now that the next WG5 meeting is confirmed for October in Las Vegas, if this would be a good time to re-open the discussion about supporting remote attendance? We have just shy of 6 months in hand - plenty of time to prepare. > Maybe this discussion is already taking place? In any case, it would make sense to have that discussion on-list. > > It seems terribly over-optimistic to assume that a meeting in October won't be impacted by the ongoing situation. We have to deal with: the possibility of a second 'wave'; significant changes to, and restrictions on, international travel; a variation in guidance between member countries, and member's employer's; member's personal choice to avoid international travel. > > So, some obvious questions about our preparedness; > - What infrastructure can the venue supply to help enable remote attendance? > - What can ISO, or INCITS, do to help support remote attendance? > - What can we do to reform our workflows to support remote attendance, and some degree of 'time-shifted' engagement with the process. > > > Cheers, > Nathan. > > > >