From neilj@fastmailteam.com Thu Apr 11 23:15:21 2024 Return-Path: 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 9DA37C14F60D; Thu, 11 Apr 2024 23:15:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.096 X-Spam-Level: X-Spam-Status: No, score=-7.096 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 (2048-bit key) header.d=fastmailteam.com header.b="q/EUG7sA"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="TMtrd7nb" 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 rg3fwLoADCnr; Thu, 11 Apr 2024 23:15:16 -0700 (PDT) Received: from wfout3-smtp.messagingengine.com (wfout3-smtp.messagingengine.com [64.147.123.146]) (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 CE9A2C14F61C; Thu, 11 Apr 2024 23:15:16 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfout.west.internal (Postfix) with ESMTP id 133261C000B1; Fri, 12 Apr 2024 02:15:13 -0400 (EDT) Received: from imap43 ([10.202.2.93]) by compute5.internal (MEProxy); Fri, 12 Apr 2024 02:15:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; 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=fm3; t=1712902513; x=1712988913; bh=ktySDMDi/zfSfWrctKfW/RQuk9q0YORwZbiXXk6ku58=; b= q/EUG7sAkLUIGkgKNnaDfhUpmanu9OIz5prcRpd2Xu16+vVFq6QtK5vg1UNKtgWG EPTvRfepOD6ZgyMGFcGlxSY7/agbLGbXu3CK6RfTFKpt/35SU8CnCsdvw3wh8K6b jlUhs4zSiZv74vop1k04MYK6mH/KyscCtCm72dyRH1ePnz8ruKCMQJH2jLTZl96e lnG49CvrD3FD74YrCNm9wbOl46nVsQrfpmSJ74iY18zSYwuEKjRSUoyom1ALbLkc dR7UpsyQPhEvojSiz5xzQGCa4uVhmv4Q+UF4tvar5iJq61YuOvf/Yh9waMsLn4EA pHx0jUzLzcLzUq5D5HH5SQ== 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-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1712902513; x=1712988913; bh=ktySDMDi/zfSfWrctKfW/RQuk9q0 YORwZbiXXk6ku58=; b=TMtrd7nbsdB5k0jjSrpdJVp6/meAjMDT9dVJNKBMafEE 4AzurtfljxrlHVLx7yJaI/jeia8THdZ8csxfA36evLGNIJOiUJz420Zk5H/vXhEW dClJsTCDcQzwuIYjS4IhNPipuVA9jqXvufMjo0k+GQ4GcSJz1MxE3leRl/MMqbgz kHYuTwt3J9HvSneEn6nic8iYd50gMk27zx8x4r3tHxz2K+9wKxvKuUjK3fafWwrr B6+Q8JUswinR+Nd7wQH+HIRjS1BeF3WUgq1xthpHVOSFwsLTk3l83JN8GkXSzI8C BLVWyiAvDVSC0ChZ11YNlQdaKQnA6lExoIxoFYIfug== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudeitddgjedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtsegrtderreerreejnecuhfhrohhmpedfpfgv ihhlucflvghnkhhinhhsfdcuoehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomh eqnecuggftrfgrthhtvghrnhephfdvhefgleekleffgeeiieelteefffdujeekgfekheel ieetkeeuffehueffheeunecuffhomhgrihhnpehivghtfhdrohhrghenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhm rghilhhtvggrmhdrtghomh X-ME-Proxy: Feedback-ID: ibc614277:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3B27E2D4007D; Fri, 12 Apr 2024 02:15:13 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.11.0-alpha0-379-gabd37849b7-fm-20240408.001-gabd37849 MIME-Version: 1.0 X-ThreadId: T46d9800cd85e4acc Message-Id: <619365d6-19bb-426b-83be-feec962c34c5@localhost:3000> In-Reply-To: <171278139226.3382.6687807382149009193@ietfa.amsl.com> References: <171278139226.3382.6687807382149009193@ietfa.amsl.com> Date: Fri, 12 Apr 2024 16:14:51 +1000 From: "Neil Jenkins" To: "Linda Dunbar" , ops-dir@ietf.org Cc: draft-ietf-jmap-contacts.all@ietf.org, "IETF JMAP Mailing List" , last-call@ietf.org Content-Type: multipart/alternative; boundary=64a03c8b957649f08fb659446af510c1 Archived-At: Subject: Re: [Jmap] Opsdir last call review of draft-ietf-jmap-contacts-06 X-BeenThere: jmap@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: JSON Message Access Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Apr 2024 06:15:21 -0000 --64a03c8b957649f08fb659446af510c1 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Linda, > Section 1.3 says: "In servers with support for JMAP Sharing", data may= be > shared with other users. >=20 > Question 1: for servers that don't support JMAP, is the data model spe= cified in > this document only for "Sharing Contacts" but not other information? Not quite. JMAP is a protocol for efficiently synchronising data between= a client and a server. This documents specifies a data model for contac= ts to be synced over the JMAP protocol. This particular sentence is sayi= ng that if the server also supports JMAP Sharing , the contacts data can be con= figured to be shared with other users in the system. To hopefully make this clearer, I've rewritten this as: In servers with support for JMAP Sharing [RFC-TBD ], users may see and configur= e sharing of contact data with others. > Question 2: Does this document extend the data model specified in > draft-ietf-jmap-sharing-07 for sharing Contacts? Yes, that's right =E2=80=94 that's the JMAP Sharing document. This docum= ent uses the data model defined there to allow users to see and configur= e sharing of contact data. Cheers, Neil. --64a03c8b957649f08fb659446af510c1 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Linda,

S= ection 1.3 says: "In servers with support for JMAP Sharing", data may be=
shared with other users.

Que= stion 1: for servers that don't support JMAP, is the data model specifie= d in
this document only for "Sharing Contacts" but not oth= er information?

Not quite. JMA= P is a protocol for efficiently synchronising data between a client and = a server. This documents specifies a data model for contacts to be synce= d over the JMAP protocol. This particular sentence is saying that if the= server also supports JMAP Sharing, the contacts data can be con= figured to be shared with other users in the system.

<= /div>
To hopefully make this clearer, I've rewritten this as:

In servers with support for JMAP Sharing [RFC= -TBD], users may see and configure sharing of contact data with othe= rs.

Question 2: Does this document extend the data model specified i= n
draft-ietf-jmap-sharing-07 for sharing Contacts?

Yes, that's right =E2=80=94 that's th= e JMAP Sharing document. This document uses the data model defined there= to allow users to see and configure sharing of contact data.
<= div>
Cheers,
Neil.
--64a03c8b957649f08fb659446af510c1--