Re: [Rfced-future] Meeting dates and doodles

Jay Daley <jay@ietf.org> Mon, 30 November 2020 18:46 UTC

Return-Path: <jay@ietf.org>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E9CC3A104B for <rfced-future@ietfa.amsl.com>; Mon, 30 Nov 2020 10:46:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, URIBL_BLOCKED=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 2o4z6ezTTrZh; Mon, 30 Nov 2020 10:46:18 -0800 (PST)
Received: from [192.168.1.101] (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 5FF113A0AC1; Mon, 30 Nov 2020 10:46:18 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-D734F0A4-B47D-4E3A-9FFC-00676182F10D"
Content-Transfer-Encoding: 7bit
From: Jay Daley <jay@ietf.org>
Mime-Version: 1.0 (1.0)
Date: Tue, 01 Dec 2020 07:46:16 +1300
Message-Id: <05EEAB53-BD4B-4073-9FEA-CAAA83F350EE@ietf.org>
References: <0ecdab62-9fa4-b7b7-8b03-03b6136ea612@nthpermutation.com>
Cc: Eliot Lear <lear@cisco.com>, rfced-future@iab.org
In-Reply-To: <0ecdab62-9fa4-b7b7-8b03-03b6136ea612@nthpermutation.com>
To: Michael StJohns <msj@nthpermutation.com>
X-Mailer: iPad Mail (18B92)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/KEpfkAUFCY9WJ1ktfdc63bWaWEk>
Subject: Re: [Rfced-future] Meeting dates and doodles
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2020 18:46:20 -0000



> On 1/12/2020, at 7:38 AM, Michael StJohns <msj@nthpermutation.com> wrote:
> 
> On 11/30/2020 3:19 AM, Eliot Lear wrote:
>> Hi Mike,
>> 
>> Just on this:
>> 
>>>> We used to do this by Doodle poll but the last two times (I'm including the time we didn't end up meeting due to pushback by the participants shortly before the IETF meeting) the chairs have just appeared to pick a date and time without reaching out for our schedules.   I'm still waiting for a meeting time that's actually during my working day and during my working week.
>>> 
>>> This still applies.
>> 
>> The goal here is to rotate times and to meet approximately every month, as agreed.
> 
> This will be the I think  the 6th meeting including the two at IETFs.  I've lost track.  Only one of which have been scheduled for a work time for me (e.g. during the previous virtual IETF which worked out to be about 9am for me) and two of which have been scheduled after midnight ( I'm including the Bangkok IETF one).  This will be the second one scheduled during my nominal dinner time.   Not generally a problem, but we're in the holiday season and doing what we can to deal with Covid distances.
> 
>>  I wanted to hold true to that which is why I proposed just a hair less a month after the previous meeting.  You should expect the next meeting to take place during the week of the 11th of January during the morning hours, EST, afternoon hours Europe, evening hours in India, and at inconvenient hours AU/NZ/CN/JP.
> 
> Do we actually have anyone participating from India or even Japan/China?   I ran the numbers and 3PM EST looked like a time slot where no one had to be up after midnight  nor up before 8am assuming the lack of those participants.   I don't have a problem with sharing the pain if there are active participants from that region.   (Jay - apologies if I've got you located in the wrong region - I *think* you're somewhere in Australia - not India?)

Even simpler - New Zealand, as are Nevil and Brian.

Jay
-- 
Jay Daley
IETF Executive Director
> 
> 
>>  Again, this is a hair less than a full month, but again one full month falls on a weekend, and a holiday weekend in the US.
>> 
>> The following meeting would take place approximately the week of the 15th of February during the morning hours in Europe, afternoon hours in India, evening hours in AU/NZ/JP/CN, and inconvenient hours EST.
> 
> And depending on the time also inconvenient hours for PST.
> 
> That would be the third time for inconvenient - e.g. post midnight hours - for me  (5/27, IETF Bangkok virtual being the other two).   Seems high for  8 meetings given that you seem to be slicing the world into 4 or 5 pieces.
> 
>> This might be a bit longer than four weeks, but evens spacing between the previous meeting and the IETF.
>> 
>> I will put out a doodle first for the January meeting and next for the February meeting.  Ok?
>> 
>> Eliot
>> 
>> 
> Later, Mike
> 
> 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future
>