Re: [Sml] Use case: Calendar availability

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 08 February 2024 19:06 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: sml@ietfa.amsl.com
Delivered-To: sml@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4E2C15198D for <sml@ietfa.amsl.com>; Thu, 8 Feb 2024 11:06:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sz2VmPHv95d0 for <sml@ietfa.amsl.com>; Thu, 8 Feb 2024 11:06:33 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00523C14F6A2 for <sml@ietf.org>; Thu, 8 Feb 2024 11:06:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id BE81F3898D; Thu, 8 Feb 2024 14:06:17 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gj8qPicCLBzZ; Thu, 8 Feb 2024 14:06:17 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 229C13898C; Thu, 8 Feb 2024 14:06:17 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1707419177; bh=WRMxnMVsTxOqYuM50YcmGlLJIhJFuYzt1dlQ6wMAd0Y=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=AkSqPbAlBM94Fcc827Moy0wvyimR0CEoSGRX82V9gC/z/rNYMKlRHANWF237QnTac 1c+tsX+QrbROKqnaOTJPHT/AYxVVZFvmMnf3ptQDlEguE/PrlPCdyKzeCMb2zmxkqa RubuGb7NakGRwWCRxRQOkY8tGdgxVlVo4JiLAkXp0BOHPwzNHKgkjg0jYvdcPcTein YlzVJqhybShP962qP8gk9tgttDOfTMMwHv43Cbx6vgBNBYVdzZ3cgvj38Eha/gJxwO Vl0QjpwVJ0PzWuSx0VguEcN+xb74uY1SeXoUBG376Hx08doCqQ/jlSvU/dJABX2wKW 3QBmX34K1bKgg==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1E1C72B3; Thu, 8 Feb 2024 14:06:17 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ben Bucksch <ben.bucksch@beonex.com>
cc: sml@ietf.org
In-Reply-To: <806aee50-97a4-4d3f-87c0-3c13988da723@beonex.com>
References: <a6eaa5b9-76b3-4d9e-ade5-de4f06ef7db8@raffika.com> <806aee50-97a4-4d3f-87c0-3c13988da723@beonex.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 08 Feb 2024 14:06:17 -0500
Message-ID: <30450.1707419177@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/na-tUTo9oQfdXCymXLckY6vPzP8>
Subject: Re: [Sml] Use case: Calendar availability
X-BeenThere: sml@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Structured Email <sml.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sml>, <mailto:sml-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sml/>
List-Post: <mailto:sml@ietf.org>
List-Help: <mailto:sml-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sml>, <mailto:sml-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2024 19:06:37 -0000

Ben Bucksch <ben.bucksch@beonex.com> wrote:
    > I noticed that, while trying to schedule an appointment ..., it took us
    > 6 days to figure out when we were both free. It was already challenging
    > for him to check messages, and when he was available, I wasn't, and
    > vice versa. I thought, 'how easy it would be if I gave him the
    > opportunity to check my calendar and see my availability directly.' He
    > could schedule an appointment in no time.

Many calendaring systems will provide a weakly authenticated freebusy feed in
iCS format. (Weakly authenticated: the URL is sometimes random)
Some provide ics and http interfaces.

In addition there are services that will look at your calendar (via OAUTH or
freebusy feed), and then display that nicely to others, and then can via
calendar integrtion book you.  They generally require a fee (or advertising),
and are limited to top 4 centralized calendaring systems.

    > So, I thought about the possibility of integrating this feature by
    > inserting one's availability (from the calendar we already have)
    > directly into the email we are writing. This way, the recipient just
    > needs to click, see when you are free, figure out a suitable time for
    > him, and respond with the exact day and time.

It's a good idea and I want to encourage you to build something.
How much freebusy information can you include?  How many days/weeks in my
future do you include?   What happens as my calendar fills up between sending
the email and you receiving it?

For this kind of thing, what I'd like to be able to do is specify five or six
possibilities and then have you pick one.   Doing that seems to fall straight
into ICS, and not exactly SML itself.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide