IETF Logo Mail Archive

Re: [Jmap] JMAP for Migration and Data Portability

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Wed, 22 March 2023 11:35 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 534F2C15171B for <jmap@ietfa.amsl.com>; Wed, 22 Mar 2023 04:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 IfUhCgHdoQWA for <jmap@ietfa.amsl.com>; Wed, 22 Mar 2023 04:35:07 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (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 85398C151719 for <jmap@ietf.org>; Wed, 22 Mar 2023 04:35:07 -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 46219C0018; Wed, 22 Mar 2023 11:35:04 +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=1679484904; bh=np919mnH6srrIWP4IEMQL5a8osZoUDetl4COEO6FtFg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=qhrvC4EEY1fXvgDuK0Hr4TG/NejMwSfAWoFACwXoXEdC23ny0zjMQKSuQecJwSYxy VxI/jbGEqNcZI+blXdOebHBzBHGPsRTCwtUcAt8h1xQh321Qc0KYYhPWs3hwnvnUwc EkvVeYQRs9RWvcdTFrGIHB8MIlwxTE5PWUFYiCOU=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1679484903-3385-29110/9/1; Wed, 22 Mar 2023 11:35:03 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Joris Baum <joris@audriga.com>
Cc: jmap@ietf.org
Date: Wed, 22 Mar 2023 12:35:02 +0100
Mime-Version: 1.0
Message-Id: <2206f2d4-1f1c-4c78-8435-656d6206b6de@gulbrandsen.priv.no>
In-Reply-To: <c2520b63-c0bd-fb39-6a1d-5c409570bb00@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> <f5b655a5-7751-4357-9da7-4b08ec8fe581@gulbrandsen.priv.no> <c2520b63-c0bd-fb39-6a1d-5c409570bb00@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/SqqBnTjZJaGHVFZ_Pho5y6Pg2TY>
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: Wed, 22 Mar 2023 11:35:12 -0000

Joris Baum writes:
> Hi Arndt,
>
> I hope I am following correctly. As far as I understand, you 
> are voicing your support for having an informational RFC that 
> outlines how to implement a minimal version of JMAP with zero 
> optional features? This is because it might surface interop 
> issues with common, but optional JMAP features?

Right.

Arnt

v2.23.0 | Report a Bug | By Email