IETF Logo Mail Archive

Re: [imapext] AD review of draft-ietf-imapapnd-appendlimit-extension-06 (Section 2)

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 10 December 2015 17:18 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 420991A8F38; Thu, 10 Dec 2015 09:18:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 EAaLRMhT_p5k; Thu, 10 Dec 2015 09:18:11 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 75B3D1A8EA9; Thu, 10 Dec 2015 09:18:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1449767890; d=isode.com; s=selector; i=@isode.com; bh=A9+89MYivEfOGeFwGTXxKIsqkWJn9F3R49gdnPfFxpY=; 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=fCPxoYsbJIG7Zhq9UddAlQtCuCIw3HRfh0THnFyuXWzYz62C7ECUXh4Hg9ZgOJjv1YYv6u CdjDWh0TH5hEt0N9+miqIGXsjDNlTqG2NvPhbRlzaHNXVv6MfziuT/WVomQ37udmfk6dPb GUUH7VqqT4KyuzLSUXTPOXNLm3McE6A=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <Vmmz0QBBx7ka@statler.isode.com>; Thu, 10 Dec 2015 17:18:10 +0000
To: Naren <narendrasingh.bisht@gmail.com>, S Moonesamy <sm+ietf@elandsys.com>
References: <CALaySJLE_6+vbeB-SeMk1VHDAtq2VvS9yKe9dhQ2LTzr4y=oTg@mail.gmail.com> <DEA84B8F15992B4EA87D5CF3D0EC5F98AE4FCFD8@DRTW-EXMB04.telecom.sna.samsung.com> <6.2.5.6.2.20151209223348.0d1a66e0@resistor.net> <CAHC+rVHPmcpLKogQdFrCo+P-GaALoWLLGEw=MeA7hnarQhEYLw@mail.gmail.com> <6.2.5.6.2.20151210080422.10a00dc0@elandnews.com> <CAHC+rVEoexsnruY_uAY7t_S4z3PQs6ff8aX7x=48g==98pU4Vg@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5669B3B9.6070802@isode.com>
Date: Thu, 10 Dec 2015 17:17:45 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
In-Reply-To: <CAHC+rVEoexsnruY_uAY7t_S4z3PQs6ff8aX7x=48g==98pU4Vg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------010008060704010007030501"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/NdOSdsEGmSaVhMajx_Npn4molcs>
Cc: Narendra Bisht <ns.bisht@sta.samsung.com>, draft-ietf-imapapnd-appendlimit-extension@ietf.org, Barry Leiba <barryleiba@computer.org>, imapext@ietf.org
Subject: Re: [imapext] AD review of draft-ietf-imapapnd-appendlimit-extension-06 (Section 2)
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Dec 2015 17:18:13 -0000

On 10/12/2015 17:15, Naren wrote:
> Hi SM,
>
> We can rephrase that sentence to
>
> "IMAP server MAY advertise this CAPABILITY before or after user has 
> logged in.The client SHOULD

IMHO, this is not correct use of SHOULD. The client that doesn't support 
both is broken. I suggest you replace SHOULD with "needs to" or the like.

> be ready to handle this CAPABILITY irrespective of user authenticated 
> state"
>
> We do not see any implications in this being advertised before user 
> logged in.
> Can you elaborate more about your concern on this.
>
> Thanks
>
> On Thu, Dec 10, 2015 at 11:32 AM, S Moonesamy <sm+ietf@elandsys.com 
> <mailto:sm+ietf@elandsys.com>> wrote:
>
>     Hi Naren,
>     At 07:52 10-12-2015, Naren wrote:
>
>         Our MAY means
>         (a) The IMAP server can advertise this capability before the
>         user has logged in.
>         OR
>         (b) The IMAP server can advertise this capability after the
>         user has logged in.
>
>
>     Based on the AD review [1] and the short discussion about that
>     sentence in Section 2, my opinion is that the intent of the what
>     is written in the draft is not clear.  What are the implications
>     of (a) and (b)?  What if the IMAP server advertises that there is
>     a limit which applies to all mailboxes before the user has logged in?
>
>     Regards,
>     S. Moonesamy (as document shepherd)
>
>     1. http://www.ietf.org/mail-archive/web/imapext/current/msg05633.html
>
>
>
>
> -- 
> Thanks & Regards
> -Narendra
>
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext

v2.23.0 | Report a Bug | By Email