IETF Logo Mail Archive

Re: [Jmap] JMAP for Migration and Data Portability

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Tue, 21 March 2023 15:09 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E00C14CE30 for <jmap@ietfa.amsl.com>; Tue, 21 Mar 2023 08:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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_NONE=0.001, 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 (1024-bit key) header.d=gulbrandsen.priv.no
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 Qxnq2sHln7cp for <jmap@ietfa.amsl.com>; Tue, 21 Mar 2023 08:09:52 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [144.76.73.169]) (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 5DC83C14EB1E for <jmap@ietf.org>; Tue, 21 Mar 2023 08:09:51 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 50FACC019B; Tue, 21 Mar 2023 15:09:48 +0000 (GMT)
Authentication-Results: stabil.gulbrandsen.priv.no; dmarc=none (p=none dis=none) header.from=gulbrandsen.priv.no
Authentication-Results: stabil.gulbrandsen.priv.no; spf=none smtp.mailfrom=gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1679411388; bh=upER6sJeFyr0sp51d4Jd6xjbLuIl8umlfrlKTc5k8nM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OxuZZY2xTnKIDTcE5OeDGyaoKEtGYldU50HuWaQSFUnIm2xgQQoApaLXNq9XyG6FF LxrEMN480F+kfRRLoKNfn0KPi0awwIhcyq3lQ9in7ibwBwsxKELUUtqeBJs1VfOwh3 VVto0VwK8oiiVz/mNmJpwDyDShpL1Gc2wJ7Eeazs=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1679411387-3600-29110/9/6; Tue, 21 Mar 2023 15:09:47 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: jmap@ietf.org
Date: Tue, 21 Mar 2023 16:09:47 +0100
Mime-Version: 1.0
Message-Id: <f5b655a5-7751-4357-9da7-4b08ec8fe581@gulbrandsen.priv.no>
In-Reply-To: <1741b4e1-9226-dccf-6f28-602127bc7e65@audriga.com>
References: <79005001-f72d-26b2-53b7-7832d1758af0@audriga.com> <d3e58e51-0055-4fa3-930e-ae3f079257dc@dogfoodapp.fastmail.com> <1741b4e1-9226-dccf-6f28-602127bc7e65@audriga.com>
User-Agent: Trojita/v0.7-553-gf1ba577f; Qt/5.15.2; xcb; Linux; Devuan GNU/Linux 4 (chimaera)
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/JU3xcGjvrbwD9XLaB_aBA_Lodhg>
Subject: Re: [Jmap] JMAP for Migration and Data Portability
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Mar 2023 15:09:56 -0000

I would guess that creating an implementation that lacks many features 
existing implementations have is likely to cause confusion and interop 
woes.

It doesn't matter whether a feature such as batching is optional in the 
spec: If all servers support batching, related client bugs will go 
undetected and after a while the feature isn't really optional any more. 
SIP people sing sad songs about this, and cry in their beer.

It would be awesome to have some servers with zero optional features 
though. Better short-term interop pain than a long-term fate like SIP.

Arnt

v2.23.0 | Report a Bug | By Email