[JMAP] Re: [Jmap] Allow clients to specify an id for new calendars
Hugo Osvaldo Barrera <hugo@whynothugo.nl> Wed, 17 September 2025 21:06 UTC
Return-Path: <hugo@whynothugo.nl>
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 0A602648135B for <jmap@mail2.ietf.org>; Wed, 17 Sep 2025 14:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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_DNSWL_LOW=-0.7, 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=whynothugo.nl header.b="tdM+J7AO"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="IvN4Vb6+"
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 sWqmSNlEUElL for <jmap@mail2.ietf.org>; Wed, 17 Sep 2025 14:06:06 -0700 (PDT)
Received: from fout-a5-smtp.messagingengine.com (fout-a5-smtp.messagingengine.com [103.168.172.148]) (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 ABB41648134D for <jmap@ietf.org>; Wed, 17 Sep 2025 14:06:06 -0700 (PDT)
Received: from phl-compute-10.internal (phl-compute-10.internal [10.202.2.50]) by mailfout.phl.internal (Postfix) with ESMTP id 9AB16EC0317; Wed, 17 Sep 2025 17:06:06 -0400 (EDT)
Received: from phl-imap-11 ([10.202.2.101]) by phl-compute-10.internal (MEProxy); Wed, 17 Sep 2025 17:06:06 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=whynothugo.nl; h=cc:cc:content-type:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to; s=fm2; t=1758143166; x= 1758229566; bh=EUpfU00JLAkhnzyO2VhBE59oes5Raao37YL+LUd6u/Q=; b=t dM+J7AOLKDPlbnR2t6PPius1k/xE8OGlX0Vpf+X0ixtkeMzWyf4KaplZJl1s5ToD tNRYpdLML/ZXjrMuTFao8SoUL2O4xQUtBAXAaylc/kIGoje+4PIBFzn1sH9T+Nkx xwCiL1OI8NQJifa5K0zJVnRpFZiAy5RZvPAjLq8wPx1nEUKaOvfgZgZDZz5vjLSU OZwrSrVe6zvp72v7SJ1hY2r+N4VnyWtF016xEkbftbNwdMNS36mxoET3lOjIN8M2 HRYhn5OJ1t3lsVC96tZUBwG32co4GmlObiJtuZW2hMKUnMOZZ+YSd5WRAF3Hy1d6 0/COA92gzrpiHAGlCxCgg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1758143166; x=1758229566; bh=EUpfU00JLAkhnzyO2VhBE59oes5Raao37YL +LUd6u/Q=; b=IvN4Vb6+zCWWEmkYYA6JMQW++Ai/b/WCGd0dSs6sOGf1AKy3cGw b6V23ToBzMtCvrbmtNabE28ztOka+/SJ/swedmyKz0nas7OPqoawd3Dzhb9XvThc hOwRABZ9H3/nt0Vy47tv3zqJfqT2qYbCmkXgAl5H26VSRPEvC8ilSHRRs9wlJOGX 8UewbXAjOw6/eKodhJrv3Wy/huwvjh6JoUZmMnfbUczXW5fc7mN3s7C98n6y7r7u 3A8PQGLwrFxGXGZMvcL63WbxTRyAW425gj0o1ZSjlwg8GtBHmK2ODiwZd0CqmV0U /mQ34g1FIAHH4G+/61rzSqk649fONdkgKqw==
X-ME-Sender: <xms:viLLaH43RUN46RxJ-Lvjj0XBm0RNKQPH5c4jDOxHt2beFWhpd18ktQ> <xme:viLLaM7wcYhJpnC-XMBDdKn445MD05ljmoqUztX1YPXSMA530bZOdt506pZPqJ5q8 2B7D8MRR_ELiq3X3Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggdeggeegkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefoggffhffvvefkjghfufgtsegrtderreertddtnecuhfhrohhmpedfjfhughhoucfq shhvrghlughouceurghrrhgvrhgrfdcuoehhuhhgohesfihhhihnohhthhhughhordhnlh eqnecuggftrfgrthhtvghrnhepueejhfettefgieduleevjedvjeetuefhledutdehjedv feefudffheevleevleefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhephhhughhoseifhhihnhhothhhuhhgohdrnhhlpdhnsggprhgtphhtthho peeipdhmohguvgepshhmthhpohhuthdprhgtphhtthhopegsvghnrdgsuhgtkhhstghhse gsvghonhgvgidrtghomhdprhgtphhtthhopegsrhhonhhgpeegtdhfrghsthhmrghilhht vggrmhdrtghomhesughmrghrtgdrihgvthhfrdhorhhgpdhrtghpthhtohepnhgvihhljh epgedtfhgrshhtmhgrihhlthgvrghmrdgtohhmsegumhgrrhgtrdhivghtfhdrohhrghdp rhgtphhtthhopehlihhsrgdrughushhsvggruhhlthesghhmrghilhdrtghomhdprhgtph htthhopehjmhgrphesihgvthhfrdhorhhgpdhrtghpthhtohepmhgruhhrohesshhtrghl fidrrghrth
X-ME-Proxy: <xmx:viLLaKiKZnXtMbBmbZXRfR-4bPyARERunYKwWhHs7tVUqZCm9iRmkw> <xmx:viLLaCZwJK4W8uI0OdqZtHKkvqftMpxxi15OfZc-l8u7h9YQm2LUFw> <xmx:viLLaHroGziieOO-8fgnNDFjSwdzu8Xp9ra48u5ngkxivR5WMEtSUw> <xmx:viLLaPNze_49zvWxApOnm8K2nz-ib6oWlMhILpGmohDy4W50_ElBPg> <xmx:viLLaF3RpISwGyePngc-1EhOOnuNXPv5xF-PctwIX1D8z5FIAP3HnCJl>
Feedback-ID: ib8c04050:Fastmail
Received: by mailuser.phl.internal (Postfix, from userid 501) id 232F41B4006F; Wed, 17 Sep 2025 17:06:06 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
MIME-Version: 1.0
X-ThreadId: AXLjjUNeL3_R
Date: Wed, 17 Sep 2025 23:05:45 +0200
From: Hugo Osvaldo Barrera <hugo@whynothugo.nl>
To: Bron Gondwana <brong=40fastmailteam.com@dmarc.ietf.org>, Neil Jenkins <neilj=40fastmailteam.com@dmarc.ietf.org>, Ben Bucksch <ben.bucksch@beonex.com>, Lisa Dusseault <lisa.dusseault@gmail.com>, Mauro De Gennaro <mauro@stalw.art>
Message-Id: <e4369391-cf5f-40d4-b1e9-dfd1d97a5b82@app.fastmail.com>
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>
Content-Type: multipart/alternative; boundary="eca3e004ba134726a3bd29119024e799"
Message-ID-Hash: UJPRKTVKSFEKOBKUOO5DXHFHR3QAH3JO
X-Message-ID-Hash: UJPRKTVKSFEKOBKUOO5DXHFHR3QAH3JO
X-MailFrom: hugo@whynothugo.nl
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/04TvDvunKmo3iHoowslvGSWCXwc>
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>
On Wed, 17 Sep 2025, at 22:14, Bron Gondwana wrote: > On Tue, Sep 16, 2025, at 19:57, Neil Jenkins wrote: >> I'm very confused about what's being requested here. Everything already has a unique id. It's assigned by the server. The original request was about syncing from another server to your JMAP server, and therefore wanting to store the remote id of the item so you know what you're syncing with. As Mauro said, you could do this with a metadata extension. What am I missing? > > Yeah, there seem to be two conflicting requirements here: > > 1) that every item has a unique identifier > 2) that (every?) client can specify the unique identifier that an object has > > Those two conflict as soon as two different clients decide to give the same unique identifier to different objects. What happens there? This is solved by JMAP by having the server decide the identifier, so it can do the conflict resolution. I don't see the conflict in requirements. The server can to enforce uniqueness. That's why I used filenames in a filesystem as an analogy; two filesystem clients can try to create files with the same path, but only will will succeed. In this case, two JMAP clients can try and create items with the same client-given id, but only one would succeed. > > (and yes, this really can happen with something like contacts or calendar events if two disconnected clients change them in different ways and then try to save them to the same JMAP account) > > Bron. > > -- > Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC > brong@fastmailteam.com > > > _______________________________________________ > JMAP mailing list -- jmap@ietf.org > To unsubscribe send an email to jmap-leave@ietf.org > -- Hugo
- [Jmap] Allow clients to specify an id for new cal… Hugo Osvaldo Barrera
- [Jmap] Re: Allow clients to specify an id for new… Mauro De Gennaro
- [Jmap] Re: Allow clients to specify an id for new… Ben Bucksch
- [Jmap] Re: Allow clients to specify an id for new… Lisa Dusseault
- [Jmap] Re: Allow clients to specify an id for new… Mauro De Gennaro
- [Jmap] Re: Allow clients to specify an id for new… Bron Gondwana
- [JMAP] Re: [Jmap] Allow clients to specify an id … Hugo Osvaldo Barrera
- [JMAP] Re: Allow clients to specify an id for new… Arnt Gulbrandsen
- [JMAP] Re: [Jmap] Allow clients to specify an id … Mauro De Gennaro
- [JMAP] Re: [Jmap] Allow clients to specify an id … Lisa Dusseault
- [JMAP] Re: [Jmap] Allow clients to specify an id … Mauro De Gennaro
- [JMAP] Re: [Jmap] Allow clients to specify an id … Lisa Dusseault
- [JMAP] Re: [Jmap] Allow clients to specify an id … Ben
- [JMAP] Re: [Jmap] Allow clients to specify an id … Neil Jenkins
- [JMAP] Re: [Jmap] Allow clients to specify an id … Bron Gondwana
- [JMAP] Re: [Jmap] Allow clients to specify an id … Hugo Osvaldo Barrera
- [JMAP] Re: [Jmap] Allow clients to specify an id … Ben