Re: [EXTERNAL] Scheduling Tool

Fred Baker <> Thu, 11 March 2021 21:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A43DA3A0CAE for <>; Thu, 11 Mar 2021 13:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HSc5RC90FNo2 for <>; Thu, 11 Mar 2021 13:20:03 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 24DE03A0C9E for <>; Thu, 11 Mar 2021 13:20:03 -0800 (PST)
Received: by with SMTP id f2-20020a17090a4a82b02900c67bf8dc69so9706094pjh.1 for <>; Thu, 11 Mar 2021 13:20:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:content-transfer-encoding:mime-version:subject:in-reply-to :date:cc:message-id:references:to; bh=/AGHts5swARMeJQiwNK+7qgGnN1ngLMJrd+lBIW6ktM=; b=HskP7PD11tCXUjVZAjLraDHmeMGXrIqjDH85s6jCmZCqTo9CXT35fkHxzHS0uocAn9 EBUneB5qlcobLoepe4q6y0wwjkJZFsYSPMIzvzyOEELMQNEw/o+zglv6eAQpXqJ42s+3 gzAMb2hYpaKYEZXRGsec3MPJVfL8O+/Lh9iwor85im6kl5LIhCfKmFfENaB024cKVlpD +3r4YN+RfZHfV3b0ftqCm00cuRkD5xQYy6cCoS8q/vW0bPmoGpGcet6l7R5eDNq6knXN TtqDVoKVzeuJjBY1s3T3OUMIhnHkKGWMbWzLCBsfhr/pXU+zrlX2OPuEGmsGLDJCzcUO pMtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:in-reply-to:date:cc:message-id:references:to; bh=/AGHts5swARMeJQiwNK+7qgGnN1ngLMJrd+lBIW6ktM=; b=GzuAngSZDfGnjeFen9sr1KYNR8n1C/Gam+XDlYJkNxySx05X7v8uQdmKNuAeFptkwA 9Q2VQlUs4O1rfNAxMSJ7dhTbQ1qe9AKUBJFxWYxwnBivLlYrxRQ5tEa0SdZXkOM3Em4U OMoPcm2Bs8bmmqzopUALa8lIeCw1gKg3NeypKjGlcwFypRIB3mefJH7M8YfUgftdMmYd SorNsZ17kKPQ0WQLjYlaSYlU+fZWcX7jxdiNlXYaAN5gbPxQx+0yjSRaYz2ufqrk8rag jkIH+cwFnuNmggSZ3j6Y25KMhUD8U6Tt5jV2wWBQ4H+mEERdFNbbZvUelnG/ADYUo0/U UcMg==
X-Gm-Message-State: AOAM5314KasnbxyN2wkAq98ZuXGpqLCa2R+LKj3og9hed0Nv2URYobX9 P8211WLK67mgJzHh1yHM8PxLsMTRrLYv0Q==
X-Google-Smtp-Source: ABdhPJzQ/0QGyxmANnzvSoM2TOhZLfDDj6yKhoXKnSRSBlkol/V3XDED2C7rHqf/6ra0GBWqTeXbVQ==
X-Received: by 2002:a17:90a:868c:: with SMTP id p12mr10394811pjn.82.1615497601756; Thu, 11 Mar 2021 13:20:01 -0800 (PST)
Received: from ([2600:8802:5800:567::1003]) by with ESMTPSA id r4sm41532pjl.15.2021. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Mar 2021 13:20:01 -0800 (PST)
From: Fred Baker <>
X-Google-Original-From: Fred Baker <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: [EXTERNAL] Scheduling Tool
In-Reply-To: <>
Date: Thu, 11 Mar 2021 13:20:00 -0800
Cc: Glenn Deen <>,
Message-Id: <>
References: <>
To: Sean Turner <>
X-Mailer: iPhone Mail (18E5164h)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Mar 2021 21:20:05 -0000

I’ll give you a first reaction here that I’m willing to be disabused of using proof.

The IETF seems to prefer to build a tool that it is the only user of and has to go out of its way to explain from scratch in favor of using something that exists, works, and is widely considered to work well.

Show me I’m wrong…

Sent using a machine that autocorrects in interesting ways...

> On Mar 11, 2021, at 1:12 PM, Sean Turner <> wrote:
>> On Mar 11, 2021, at 12:27, Deen, Glenn (NBCUniversal) <> wrote:
>> On 3/11/21, 8:52 AM, "WGChairs on behalf of Sean Turner" < on behalf of> wrote:
>>   Apologies if this has been asked before, I have not done an exhaustive search of the WG Chair's list.
>>   When scheduling meetings for MLS, I have used Google Forms and for TLS I have often used Doodle. I get complaints each time I use one of these for various reasons. I also say some poo-pooing of Doodle in some Meetecho session I was in. What are we supposed to use that is privacy friendly but also not supporting consolidation that actually works?  I have heard of;!!PIZeeW5wscynRQ!6kUZm7HPYcL8nxnTOIArtksHGdgwsvgE7Rntpak62NJzbM8WlBDYV-SVKE6Wn69V$  do others use it?
>> [GD] for what it's worth - I've been using Doodle without complaints from ADD members.   How is Framate one better privacywise than doodle?  It says it requires Javascript and cookies to be active.
>> -glenn
> Honestly, I do not know. I am wondering how much to contort to address these suggestions.
> I am loathe to do something special for IETF when everybody else I interact with uses something else.
> spt