Re: [Extra] IMAP4rev2: how to signal canonical mailbox name after CREATE

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 17 June 2020 11:51 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 9D8DE3A0A03 for <extra@ietfa.amsl.com>; Wed, 17 Jun 2020 04:51:55 -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 RieNeWMjejUW for <extra@ietfa.amsl.com>; Wed, 17 Jun 2020 04:51:54 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 752983A0A02 for <extra@ietf.org>; Wed, 17 Jun 2020 04:51:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1592394713; d=isode.com; s=june2016; i=@isode.com; bh=Jexp+Euj9jSzjI8tGWmVYvyUKTNizb9A+LDbyHLMGw4=; 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=cV5LAG9K4odRLmjvjnKPV6KJPIiP1M95HJOqL15DONEKvQtWka7hS1M+DqSBHf8ipfUiUo j0nUYS5wtK7AOGPMzchc+M7zoH/78kP72bZS8kSA1zyQVbEjVDjWLOY9m8p+BK/Y3WC96/ VoUHzrJyD9mqgF08TfyB3MMpdlLXVeE=;
Received: from [192.168.1.222] (host31-49-142-105.range31-49.btcentralplus.com [31.49.142.105]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <XuoD2QBLOQDD@statler.isode.com>; Wed, 17 Jun 2020 12:51:53 +0100
To: Bron Gondwana <brong@fastmailteam.com>, Timo Sirainen <timo@sirainen.com>
Cc: 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>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <9c674fad-dabe-cc9d-649d-30cb40f5c506@isode.com>
Date: Wed, 17 Jun 2020 12:51:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
In-Reply-To: <0fd3e8e2-1865-4021-b80c-11c4987b7d64@dogfood.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------A3D376111D71ADDC04788626"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/6-QCMgi3i0g6E4CzatC9dR1XsZ8>
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: Wed, 17 Jun 2020 11:51:56 -0000

On 17/06/2020 12:07, Bron Gondwana wrote:

> On Wed, Jun 17, 2020, at 21:00, Alexey Melnikov wrote:
>>
>> To elaborate on why I excluded "literal" string is because response 
>> codes are defines as:
>>
>>   atom [SP 1<any TEXT-CHAR except "]">]
>>
>> and TEXT-CHAR excludes CR and LF.
>>
>
> Here's another problem:
>
> . CREATE INBOX.HELLO[]
> . OK [MAILBOXID (f3633f0c-3a4d-4df2-9b2f-618464b97504)] Completed
>
> * LIST (\HasNoChildren) "." INBOX.HELLO[]

Right, I was just about to mention that. I think we have a choice:

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.

or

2) just describe limitations (e.g. no mailbox with "]" in it can have 
this response code) and make them a special case.

Hopefully will discuss this later today at the interim meeting.