Re: [Extra] AD review of draft-ietf-extra-specialuse-important-02

Neil Jenkins <neilj@fastmailteam.com> Fri, 11 May 2018 05:30 UTC

Return-Path: <neilj@fastmailteam.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC97D12DB71 for <extra@ietfa.amsl.com>; Thu, 10 May 2018 22:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.883
X-Spam-Level:
X-Spam-Status: No, score=-1.883 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3eQBe383JZHr for <extra@ietfa.amsl.com>; Thu, 10 May 2018 22:30:36 -0700 (PDT)
Received: from forward3-smtp.messagingengine.com (forward3-smtp.messagingengine.com [66.111.4.237]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C41312420B for <extra@ietf.org>; Thu, 10 May 2018 22:30:36 -0700 (PDT)
Received: from mailredirect.nyi.internal (imap22.nyi.internal [10.202.2.72]) by mailforward.nyi.internal (Postfix) with ESMTP id D0D1A13F2; Fri, 11 May 2018 01:30:34 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by mailredirect.nyi.internal (Postfix) with ESMTP id B9C1ACA1CA; Fri, 11 May 2018 01:30:34 -0400 (EDT)
Message-Id: <799439eb-8593-4c9c-befd-a6fa0ea76447@sloti22d1t06>
User-Agent: Cyrus-JMAP/3.1.3-565-g1e559eb-next
x-jmap-identity-id: 64588216
In-Reply-To: <CALaySJ+HK79CB92CVgj6xuobCh4nPKV4mBkPK+2ouCtYxMNbjw@mail.gmail.com>
References: <CALaySJ+HK79CB92CVgj6xuobCh4nPKV4mBkPK+2ouCtYxMNbjw@mail.gmail.com> <5AE72EAD.9050307@isode.com> <CAC4RtVB7Wh1qmZfx620hp_a3t0szMKWfgcPRMjwi-oUoY+dr6g@mail.gmail.com> <1525158666.2389818.1356559416.235763DA@webmail.messagingengine.com>
Date: Fri, 11 May 2018 01:30:34 -0400
From: Neil Jenkins <neilj@fastmailteam.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: extra@ietf.org
Content-Type: multipart/alternative; boundary="00eae7d33129411cb054128eb20bbc0d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/o4AIscXRnWszN4xUzeoB6NqHTC8>
Subject: Re: [Extra] AD review of draft-ietf-extra-specialuse-important-02
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 05:30:38 -0000

On Tue, 1 May 2018, at 11:22 PM, Barry Leiba wrote:
How does JMAP handle situations where it's used to access things like
IETF mailing lists or usenet news groups, where there can be tens or
hundreds of thousands of mailboxes, and the user is only interested in
a few of them?

Sorry for the late reply to this. The answer in the current spec is it was presumed individual clients would keep track of which mailboxes they are interested in. However, we can easily add an isSubscribed: Boolean property to the JMAP Mailbox object, as a direct equivalent to the \Subscribed IMAP attribute, so this can be synchronised between clients. This could then be used with Mailbox/query to just return subscribed mailboxes etc. in much the same was as you can with various LIST options in IMAP. I've https://github.com/jmapio/jmap/issues/204" rel="nofollow">created a GitHub issue for this.

This does highlight the slight weirdness of sharing this registry between IMAP and JMAP. The mailbox attributes in IMAP are a mix of things that are analogous to individual properties on the JMAP object (so need to be marked as not relevant), and mailbox roles (which is what we do want to reuse). Hence the need to mark quite a few as not relevant.

Neil.