IETF Logo Mail Archive

[JMAP] Re: [Jmap] Allow clients to specify an id for new calendars

Ben <ben.bucksch@beonex.com> Wed, 17 September 2025 23:10 UTC

Return-Path: <ben.bucksch@beonex.com>
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 AD8EA648ED7E for <jmap@mail2.ietf.org>; Wed, 17 Sep 2025 16:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
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, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 aAJXz65eqTFy for <jmap@mail2.ietf.org>; Wed, 17 Sep 2025 16:10:55 -0700 (PDT)
Received: from mail.server.beonex.com (mail.server.beonex.com [144.76.227.234]) (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 18A9C648ED72 for <jmap@ietf.org>; Wed, 17 Sep 2025 16:10:54 -0700 (PDT)
Received: from mail.beonex.com (fire3.beonex.com [88.99.137.225]) (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 mail.server.beonex.com (Postfix) with ESMTPS id 5E343A00101; Thu, 18 Sep 2025 01:10:44 +0200 (CEST)
Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by mail.beonex.com (Postfix) with ESMTPA id 44287A06F3B2; Wed, 17 Sep 2025 23:10:43 +0000 (UTC)
From: Ben <ben.bucksch@beonex.com>
To: Bron Gondwana <brong=40fastmailteam.com@dmarc.ietf.org>
In-Reply-To: <93b3454c-a5be-4065-9bd6-1c8640ed4c45@app.fastmail.com>
References: <1de36e51-e92a-4874-9c37-989064242a88@app.fastmail.com> <2E12287B-DED4-4667-8CD8-47E1AA56EF45@stalw.art> <f3165910-c429-4cad-b0f6-f20989c51ffe@app.fastmail.com> <4DFE4C16-882C-4271-ADF3-66DEB6079CA3@stalw.art> <afd49249-04ec-490a-9744-61026d9c14d0@app.fastmail.com> <8E4683AD-553B-4EB8-AF22-AD0AFA10FCB5@stalw.art> <CAEi+uC45eBm=7DGYtZf8NEYy3sM5GrG6DXk8nnUSUagTyXLO+g@mail.gmail.com> <823B0BE5-EE4A-4538-B0DC-BE0E39CA55E1@stalw.art> <CAEi+uC4FXG7Lk=1i9eoZHP5gpkiS5JKVWdCKQbmZ_yb9_eyVng@mail.gmail.com> <3a10ea2d-24c1-e53e-ae31-472ae26490fd@beonex.com> <67acd9ff-c0f2-4de3-a8e5-4c2808e8cda1@dogfoodapp.fastmail.com> <93b3454c-a5be-4065-9bd6-1c8640ed4c45@app.fastmail.com>
Message-ID: <34cd488d-6d29-1eeb-934c-2fbd928e7c19@beonex.com>
Date: Wed, 17 Sep 2025 23:10:42 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_NmP-6ddc699661666d06-Part_1"
Authentication-Results: mail.beonex.com; auth=pass smtp.auth=ben@bucksch.name smtp.mailfrom=ben.bucksch@beonex.com
X-Spamd-Bar: /
Message-ID-Hash: 6CYGAWFLFKOW7IXTX53LBX4IMM3KIDZJ
X-Message-ID-Hash: 6CYGAWFLFKOW7IXTX53LBX4IMM3KIDZJ
X-MailFrom: ben.bucksch@beonex.com
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
CC: IETF JMAP Mailing List <jmap@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [JMAP] Re: [Jmap] Allow clients to specify an id for new calendars
List-Id: JSON Meta Access Protocol <jmap.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/v8vTALF_mB7aXszBE99FrPFUSzA>
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>

Bron Gondwana wrote on 17.9.2025, 22:14:

> This is solved by JMAP by having the server decide the identifier, so it can
> do the conflict resolution.

I'm sorry that I added to the confusion with my last post.

Yes, this is sufficient and exactly right for the purposes that I had in mind.

Ben

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