Re: [Rfced-future] Meeting dates and doodles
Michael StJohns <msj@nthpermutation.com> Mon, 30 November 2020 18:38 UTC
Return-Path: <msj@nthpermutation.com>
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 6D16E3A1038 for <rfced-future@ietfa.amsl.com>; Mon, 30 Nov 2020 10:38:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.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 wKPEIYfN6vq0 for <rfced-future@ietfa.amsl.com>; Mon, 30 Nov 2020 10:38:02 -0800 (PST)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12A0B3A103A for <rfced-future@iab.org>; Mon, 30 Nov 2020 10:38:00 -0800 (PST)
Received: by mail-qt1-x82e.google.com with SMTP id e60so8947893qtd.3 for <rfced-future@iab.org>; Mon, 30 Nov 2020 10:38:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=vs49YVKLskRRXKzHSUXtW3/xqZChrt2j/Q83DcU5CQk=; b=N+mHrT2GRAztYJPBJo4cNNTRwwohKbrqViuNsSjooYl+typA2HeIRncxQqPfq2Nbjy CHLiKN8Dn1BhxwNStt4G66R9SbxSeVXPAL/a5+R0lUhT6vj8N7V2yBA6nArngKMHuZ5+ kT/nw1Pm1AeYMlLq0HaK5OpMQpGjQD+RX8QEdtAEn+Ecznn/MZZmf67XRtj/P+D6Y5Su GuiandqI0nuCEEn94yGdiZKKbpuO/jYcrvX+78mAXalvWeBd7JbcaJQCwepP/qxtAaw5 gz0WhbWO+E6It0EtfPTQLcsbLqFerR8Nk4Vwxgc/HTzODPvm5tYLDan0UzTHRV3U7efb tJtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=vs49YVKLskRRXKzHSUXtW3/xqZChrt2j/Q83DcU5CQk=; b=OWhy/SwEoTmnPNsDU098/gqLtX+E6ucxCqS0qKUnKeuKZ/sqhlUTAdwU+duasBCcHv rxR59eVDbcdOFUHCvkZbZz7lUxFRweRYd3JLsxXB6SESry7mdhoGrP5zSPgFaObAr7DK TLC3KrjwV9EhyJyoDnTN7gfNSIRxbi9vl2PFpXxTbh9eAlONuQe2K7owsk6O1Z5sSL7Q exE+e1NKHR1xfGZfaiXsQVjB+M7JWxuUEHejeVQRGTimMpcKlcUYVNicbkn0fSx+s9cA OFeumwGpgZJmIEvu9dMAqeiOPnfiAiGTAhaktmcbSXq8ywC0kx61R7QzBju1dBYmVmeZ UJxQ==
X-Gm-Message-State: AOAM530+biFdcetmVwBJY6PZfxqC/SYoHrzT6fCVFtgSQYjsanbwKoEt Q3a0yxBcwFSj0C7te7ujN6x4WVMlFkUTnpNG
X-Google-Smtp-Source: ABdhPJwRRhR92MFmUS1fZpdYl1rhbDCn1jfihniJlmFa6Twrq5yDr4h5LiXFtmFYIqR2jG4pfKmPSQ==
X-Received: by 2002:aed:2a84:: with SMTP id t4mr23843664qtd.251.1606761479411; Mon, 30 Nov 2020 10:37:59 -0800 (PST)
Received: from [192.168.1.23] (pool-108-28-189-254.washdc.fios.verizon.net. [108.28.189.254]) by smtp.gmail.com with ESMTPSA id z20sm17213807qtb.31.2020.11.30.10.37.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 30 Nov 2020 10:37:58 -0800 (PST)
To: Eliot Lear <lear@cisco.com>
Cc: rfced-future@iab.org
References: <160653974994.12259.12100973874618348178@ietfa.amsl.com> <f177c551-13d0-1f5c-f514-96b7d3cc993c@comcast.net> <13c48f4a-0ada-d4ae-b8e1-118be9852fb8@nthpermutation.com> <A07039A2-623B-4B91-9E98-42F0B638F303@cisco.com>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <0ecdab62-9fa4-b7b7-8b03-03b6136ea612@nthpermutation.com>
Date: Mon, 30 Nov 2020 13:37:57 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <A07039A2-623B-4B91-9E98-42F0B638F303@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/SiAovKa1LcnBsl4_KB7N6ly5tVc>
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:38:03 -0000
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?) > 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] RFC Editor Future Development (rfc… IAB Executive Administrative Manager
- Re: [Rfced-future] RFC Editor Future Development … Michael StJohns
- Re: [Rfced-future] RFC Editor Future Development … Michael StJohns
- [Rfced-future] Meeting dates and doodles Eliot Lear
- Re: [Rfced-future] Meeting dates and doodles Michael StJohns
- Re: [Rfced-future] Meeting dates and doodles Jay Daley