Re: [ipwave] Fwd: IETF 108 will be an online meeting
Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 18 May 2020 09:31 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E3873A0A1D for <its@ietfa.amsl.com>; Mon, 18 May 2020 02:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.176
X-Spam-Level: ***
X-Spam-Status: No, score=3.176 tagged_above=-999 required=5 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=no 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 ZmMn6EYPRdA1 for <its@ietfa.amsl.com>; Mon, 18 May 2020 02:31:48 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 C412A3A0A1A for <its@ietf.org>; Mon, 18 May 2020 02:31:47 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 04I9VjN2046017 for <its@ietf.org>; Mon, 18 May 2020 11:31:45 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B6AA5211741 for <its@ietf.org>; Mon, 18 May 2020 11:31:45 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id AD4EA21173F for <its@ietf.org>; Mon, 18 May 2020 11:31:45 +0200 (CEST)
Received: from [10.11.245.214] ([10.11.245.214]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 04I9VjJb030962 for <its@ietf.org>; Mon, 18 May 2020 11:31:45 +0200
To: its@ietf.org
References: <83D4CBCE-E464-4CCC-8679-592531EF7448@ietf.org> <995BE6E5-0EBC-480D-91EA-30A72139A22E@vigilsec.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <c58dadfe-a23d-5ea9-53d2-80be7d67d28a@gmail.com>
Date: Mon, 18 May 2020 11:31:44 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <995BE6E5-0EBC-480D-91EA-30A72139A22E@vigilsec.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/iGfZIEhPBmF2k-m6O9lA6p88qig>
Subject: Re: [ipwave] Fwd: IETF 108 will be an online meeting
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2020 09:31:50 -0000
Hi, Russ, Thank you for having forwarded that message. It is indeed very important. I am subscribed to the IETF-announce email list, but I did not receive it. That list's archive does display it, among others around May 14th, at https://mailarchive.ietf.org/arch/browse/ietf-announce/ But this kind of message is very important to each WG, because it says the essential thing of a WG: how to meet. In that sense, I am surprised that the WG chairmanship has to manually forward that message. It seems to me like the administration somewhere high up in the clouds - maybe just a bit too high(?) - does not feel like it needs to inform directly the WG about it. In my feeling (it is just a feeling) this might invite someone like me, to think about proposing intermediary meetings, without asking consent from Administration. Why should we meet when the _Administration_ wants to, when we could meet when _we_ want to? Why should a single WG follow the population statistics of IETF overall in order to decide for a timeslot? For example, right now the agenda proposes an IETF virtual meeting end of July, on a timeslot 11hAM to 16hPM UTC, because that's what the IETF doodle gave. But if a group has most likely participants on Vanuatu timezone, why should that group choose an European timeslot? (or vice-versa). It is highly likely here now that a timeslot 1hAM UTC would be more attractive to a larger number of potential participants. Remark the discrepancy in timeslot. The good reason that might be necessary to coordinate with IETF Administration, is because of a need of relationship with other WGs. For example, IPWAVE might need info to/from 6MAN. But 6MAN also meets virtually. There might be other WGs to need to coordinate with. It might be that the common timeslot might be the key ressource to deal with in organizing virtual meetings. But one does not organize timeslots for virtual meetings as one organizes week-constrained same-timezone f2f meetings. Alex Le 15/05/2020 à 21:23, Russ Housley a écrit : > Just in case you do not read the **IETF-Announce mail list... > > Russ > > >> *From: *IETF Chair <chair@ietf.org <mailto:chair@ietf.org>> >> *Subject: **IETF 108 will be an online meeting* *Date: *May 14, >> 2020 at 4:07:47 PM CDT *To: *IETF-Announce <ietf-announce@ietf.org >> <mailto:ietf-announce@ietf.org>>, irtf-announce@irtf.org >> <mailto:irtf-announce@irtf.org>, IETF <ietf@ietf.org >> <mailto:ietf@ietf.org>> *Reply-To: *IETF <ietf@ietf.org >> <mailto:ietf@ietf.org>> >> >> The Internet Engineering Steering Group (IESG), the IETF LLC Board >> of Directors, and the Internet Research Task Force (IRTF) Chair >> have decided to replace the in-person IETF 108 Madrid meeting with >> an online meeting. This decision is based on the IETF Executive >> Director’s recommendation, which was made after conducting an >> assessment of local conditions using the criteria set out in the >> assessment framework [1] developed with community input. >> >> The recommendation and full assessment are available at: >> https://www.ietf.org/media/documents/IETF_108_Madrid_go_no-go_assessment.pdf >> >> >> The online IETF 108 meeting will take place 27-31 July from 11:00 to >> 16:00 UTC each day. The end time of 16:00 UTC is approximate; some >> days may be shorter depending on scheduling. These time blocks >> were chosen based on the survey feedback [2] we received. >> >> Further details about the online meeting will be shared as they >> become available. >> >> Sincerely, Alissa Cooper, IETF Chair Colin Perkins, IRTF Chair >> Jason Livingood, IETF LLC Board Chair >> >> [1] >> https://www.ietf.org/blog/assessment-criteria-decision-personvirtual-ietf-108/? >> >> [2] >> https://www.ietf.org/media/documents/survey-planning-possible-online-meetings-responses.pdf > >> > > _______________________________________________ its mailing list > its@ietf.org https://www.ietf.org/mailman/listinfo/its >
- [ipwave] Fwd: IETF 108 will be an online meeting Russ Housley
- Re: [ipwave] Fwd: IETF 108 will be an online meet… Alexandre Petrescu
- Re: [ipwave] Fwd: IETF 108 will be an online meet… Alexandre Petrescu