IETF Logo Mail Archive

[JMAP] Re: JMAP for Calendars comments

Mauro De Gennaro <mauro@stalw.art> Fri, 10 October 2025 12:04 UTC

Return-Path: <mauro@stalw.art>
X-Original-To: jmap@mail2.ietf.org
Delivered-To: jmap@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 1DD51709D1A0 for <jmap@mail2.ietf.org>; Fri, 10 Oct 2025 05:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
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, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=stalw.art header.b="qUEy8aBn"; dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=stalw.art header.b="yedeqOJw"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ZPiwv09iFF2 for <jmap@mail2.ietf.org>; Fri, 10 Oct 2025 05:04:12 -0700 (PDT)
Received: from mail.stalw.art (mail.stalw.art [135.181.195.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 99DE2709D199 for <jmap@ietf.org>; Fri, 10 Oct 2025 05:04:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; s=202404r; d=stalw.art; c=relaxed/relaxed; h=Message-Id:To:Date:Subject:From; t=1760097851; bh=im+j/MRlP/Z+cvhPwtn9tc3 5PlfuX18VYSLaD4vl6zM=; b=qUEy8aBn+MU6FwVysrQq58GMQA1h6HGXxV861ZS4RRcVnjHz/k SuibDocMQTUccokTmbtxK0Jr19oRo5EnlGjiCOEA0v184J6cPaW7MYCmbiXbq3qcjsFU3XHH3+b c1Mq567TjRb49GQf+8K2nlSTnR1d/yf69albvttvVW1JUcCUqDU0eZFSOQ30kKmK33HQAD1F/ZR TzAZXucoFB7W/maAU6fMtqJJ52RjvNypm8VzYMobN/i4Nz4I1plKzSnC10VB83C59nGFy3nhEaj +dFlNWTSGtWYNGTXWvvNaubxRfEnlt4AE1wKa3Qq0FlaVXsYjPJz0v+6mVOGnCxB+cA==;
DKIM-Signature: v=1; a=ed25519-sha256; s=202404e; d=stalw.art; c=relaxed/relaxed; h=Message-Id:To:Date:Subject:From; t=1760097851; bh=im+j/MRlP/Z+cvhPwtn9tc3 5PlfuX18VYSLaD4vl6zM=; b=yedeqOJwnorQQDKWAY5CPSO5AGDdUmKUhR4GR6WzbMjkYUTf5m I+YDVRebqO+gIYa3UuEJ6xWzGTQGYwc5U3DQ==;
From: Mauro De Gennaro <mauro@stalw.art>
Content-Type: multipart/alternative; boundary="Apple-Mail=_00F8C593-644C-46AB-8487-F6213C809CF6"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.11\))
Date: Fri, 10 Oct 2025 14:04:00 +0200
References: <101DEC25-A12F-4063-90FB-446C6E5190BF@stalw.art> <4aa2017d-5ef4-486f-a264-2c8e2bec6094@dogfoodapp.fastmail.com> <34E1318A-C0D3-495F-9076-6B914C60D59F@stalw.art> <4561708e-c41a-4ef5-a644-0444eabbc083@dogfoodapp.fastmail.com> <7A250971-CC56-4D31-9B23-058B29A38E68@stalw.art>
To: IETF JMAP Mailing List <jmap@ietf.org>
In-Reply-To: <7A250971-CC56-4D31-9B23-058B29A38E68@stalw.art>
Message-Id: <E0A3FBE5-F99D-4AEA-8055-6C28C14011E3@stalw.art>
X-Mailer: Apple Mail (2.3731.700.6.1.11)
Message-ID-Hash: 5G2PFYR7LA6O72H4AMR43FANYIW2VSFK
X-Message-ID-Hash: 5G2PFYR7LA6O72H4AMR43FANYIW2VSFK
X-MailFrom: mauro@stalw.art
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-jmap.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [JMAP] Re: JMAP for Calendars comments
List-Id: JSON Meta Access Protocol <jmap.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/hU2V2iHN6F0gsPoY0pSYiQ3mF_U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Owner: <mailto:jmap-owner@ietf.org>
List-Post: <mailto:jmap@ietf.org>
List-Subscribe: <mailto:jmap-join@ietf.org>
List-Unsubscribe: <mailto:jmap-leave@ietf.org>

>>> It’s unclear what busyStatus should be used when participationStatus is needsAction, tentative (and maybe also that delegated should not be included).
>> "tentative" — The event status is "tentative" or the Principal's "participationStatus" is "tentative".
>> 
>> That's an "or", so if the event status is tentative, the busyStatus here would be tentative, according to the spec. (Or have I misunderstood your question?)
> 
> I was referring to the busyStatus of the BusyPeriod object, which can be confirmed, tentative, or unavailable. My question was which value should be used when the participant’s participationStatus is needsAction (I mistakenly included tentative earlier). It might also be worth clarifying (though perhaps it’s obvious) that when participation is delegated, the participant should be considered available during that time.

Please disregard this comment. I had been expecting a direct mapping between participationStatus and busyStatus, but after re-reading the relevant event criteria, I see that it clearly states only events with a participationStatus of "accepted" or "tentative" are included.


Best,
Mauro

v2.34.0 | Report a Bug | By Email | System Status