Re: [Extra] IMAP4rev2: how to signal canonical mailbox name after CREATE
Alexey Melnikov <alexey.melnikov@isode.com> Fri, 10 July 2020 10:48 UTC
Return-Path: <alexey.melnikov@isode.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 329393A08BB for <extra@ietfa.amsl.com>; Fri, 10 Jul 2020 03:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 uyv6LcVL0_Dx for <extra@ietfa.amsl.com>; Fri, 10 Jul 2020 03:48:01 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id C77B23A08B7 for <extra@ietf.org>; Fri, 10 Jul 2020 03:48:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1594378081; d=isode.com; s=june2016; i=@isode.com; bh=eIj0hlHiDAVE0WwWyDM3cRulGjX8wmqyx9OJW2utwwI=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=lhh6LpENaKeOT1OxrUaJ+m3ZRiXHlsFprFLxocRN6CUkVhA61vGS3v5U9Q4OEIBV/g/3ej 7jQEa3Tyn5ClS3KQ5ut+PIGcDcoTLkW8AAHS9BUnuqZ/cuFCKDVB0Rkwg0M086U98N27GM w7oP6I2zaLee7F9GuIoyO0fCHlLHlpM=;
Received: from [172.27.254.207] (connect.isode.net [172.20.0.72]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <XwhHXAAFT65Y@statler.isode.com>; Fri, 10 Jul 2020 11:48:00 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Bron Gondwana <brong@fastmailteam.com>, extra@ietf.org
References: <9fdfa8e8-147d-4248-a0c1-48de171ac675@dogfood.fastmail.com> <872422BE-C8FA-4AA0-8EF1-2ECA79F64926@sirainen.com> <96BAB7A5-420A-49AF-977F-1F722746E5DD@isode.com> <5FAA4D04-F1A8-4E23-B9F2-817EBAFF8021@sirainen.com> <5fe122d9-5313-8be1-199e-075a61d1bb2a@isode.com> <0fd3e8e2-1865-4021-b80c-11c4987b7d64@dogfood.fastmail.com> <9c674fad-dabe-cc9d-649d-30cb40f5c506@isode.com> <1BC59434-C16C-4A32-AB3C-D2783092CF9B@sirainen.com> <2fe5352f-f2c5-4e50-b9c4-6da38fbcc4d0@dogfood.fastmail.com> <93c5effc-bf6c-b36b-282f-c334883c2966@isode.com> <178ba905-36d9-493e-a02f-ac1a91f3ae68@dogfood.fastmail.com>
Message-ID: <c2e87d73-6a19-9c20-de75-81a98a2e7b2a@isode.com>
Date: Fri, 10 Jul 2020 11:47:29 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
In-Reply-To: <178ba905-36d9-493e-a02f-ac1a91f3ae68@dogfood.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------F953B8A3472B7F3BFB5D856A"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/b60TDfBoqRV09P8p1UBknM3R4tA>
Subject: Re: [Extra] IMAP4rev2: how to signal canonical mailbox name after CREATE
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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, 10 Jul 2020 10:48:03 -0000
On 07/07/2020 00:30, Bron Gondwana wrote: > On Tue, Jul 7, 2020, at 03:38, Alexey Melnikov wrote: >> >> On 17/06/2020 13:27, Bron Gondwana wrote: >> >>> On Wed, Jun 17, 2020, at 22:15, Timo Sirainen wrote: >>>>> >>>>> 1) abandon use of this response code (and use a new response >>>>> instead), e.g. >>>>> >>>>> * CREATED "a123" "Denormalized name" MAILBOXID "123456" >>>>> >>>>> This would require clients to ignore an extra response, if they >>>>> don't recognize it. >>>>> >>>> >>>> Somehow I've a feeling that there are going to be clients that will >>>> break if they see these kind of unknown untagged replies. But >>>> that's just a guess, so maybe not. We could of course send it only >>>> when client has used ENABLE IMAP4REV2 and then there wouldn't be >>>> any problems. >>> >>> I like this. Only send if IMAP4REV2 is enabled and all[tm] your >>> problems go away. >> >> Following on the suggestion to use LIST extended data items for this >> >> >> C: C04 create NonCannonicalName >> S: * LIST () "/" "CannonicalName" ("TAG" ("C04")) >> S: C04 OK done >> >> >> In the example above imagine that "CannonicalName" is the canonical >> (normalized) version of "NonCannonicalName" >> >> >> And the corresponding ABNF: >> >> tag-extended-item = "TAG" SP "(" tag-string ")" >> ; Complies with <mbox-list-extended-item> >> ; The value complies with <tagged-ext-val> >> ; The value is the tag of the corresponding >> ; CREATE command. >> >> >> And a similar extended data item can be used to return MAILBOXID >> (when supported). >> > > Yes, this works for me. After thinking a bit more about this, I remembered that we already registered OLDNAME extended data item in Section 5.4 of RFC 5465. (We can think of canonical mailbox name as the server "renaming" the mailbox.) Matching to oldname is easier than matching to the tag of the command that generated the change. So unless there are objections, I would go with that instead.
- [Extra] Review: draft-ietf-extra-imap4rev2-11 Bron Gondwana
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Timo Sirainen
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Bron Gondwana
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Timo Sirainen
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Alexey Melnikov
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Timo Sirainen
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Bron Gondwana
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Alexey Melnikov
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Alexey Melnikov
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Alexey Melnikov
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Bron Gondwana
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Alexey Melnikov
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Bron Gondwana
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Bron Gondwana
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Alexey Melnikov
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Ken Murchison
- [Extra] IMAP4rev2: how to signal canonical mailbo… Alexey Melnikov
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Bron Gondwana
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Alexey Melnikov
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Timo Sirainen
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Bron Gondwana
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Alexey Melnikov
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Alexey Melnikov
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Bron Gondwana
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Bron Gondwana
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Alexey Melnikov
- Re: [Extra] Review: draft-ietf-extra-imap4rev2-11 Bron Gondwana
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Timo Sirainen
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Alexey Melnikov
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Timo Sirainen
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Alexey Melnikov
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Alexey Melnikov
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Bron Gondwana
- Re: [Extra] IMAP4rev2: how to signal canonical ma… Alexey Melnikov