Re: [imapext] AD review of draft-ietf-imapapnd-appendlimit-extension-06 (Section 2)
Naren <narendrasingh.bisht@gmail.com> Thu, 10 December 2015 15:52 UTC
Return-Path: <narendrasingh.bisht@gmail.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 DDB421A0126; Thu, 10 Dec 2015 07:52:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 Lk1fEkgurDfe; Thu, 10 Dec 2015 07:52:58 -0800 (PST)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C88BB1A0123; Thu, 10 Dec 2015 07:52:57 -0800 (PST)
Received: by qgeb1 with SMTP id b1so148828946qge.1; Thu, 10 Dec 2015 07:52:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=+C5DviLLWlwfvpiPCs25TI2JcKzANXXoatBR34hE7Pg=; b=CxcLiDjkXUqqZlEkgbJ0+0oFkkRajnZ4f8gEGBSmNw16T96jT7ke/A4eiej6XPDGde nv6CRB3zU7jKjCL0jdnITGmJnwVpLLznRfTbH6SbIgr1kN4rQyn4ElNRFDy3R4QK97YR eFutXAqhYvRuPhIzsPlUkXS/xm/gQnpK4QtNAzWeUrG4i7siUXfhyWt6uv3QxKwzayg2 Mu+CaJ4NoEkovVCv+roZRAZTVaD+/m+p9+QpPdgH7EKZz0nqXSOuBtd59WlkYGyOA1KP 82rHRsYcTZG4yLDE8xS3YJIsjKHFrVzXQGiTpYSwBuMWqJX+zecwD2sDP34gzPRIb57v drQA==
X-Received: by 10.140.239.87 with SMTP id k84mr7899314qhc.87.1449762776748; Thu, 10 Dec 2015 07:52:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.92.21 with HTTP; Thu, 10 Dec 2015 07:52:37 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20151209223348.0d1a66e0@resistor.net>
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>
From: Naren <narendrasingh.bisht@gmail.com>
Date: Thu, 10 Dec 2015 10:52:37 -0500
Message-ID: <CAHC+rVHPmcpLKogQdFrCo+P-GaALoWLLGEw=MeA7hnarQhEYLw@mail.gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary="001a11359be05124bc05268d334e"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/SEX6RetQVmGMs43tR2GsuGmmJrs>
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 15:53:00 -0000
Yes, you right SM. 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. Thanks -Naren On Thu, Dec 10, 2015 at 1:54 AM, S Moonesamy <sm+ietf@elandsys.com> wrote: > Hi Naren, > At 08:52 09-12-2015, Narendra Bisht wrote: > >> -- Section 2 -- >> >> "An IMAP server that supports APPENDLIMIT extension advertises this by >> including the name APPENDLIMIT in its capability list. IMAP server MAY >> advertise this capability after user has logged in." >> >> This says nothing about whether the server is allowed to advertise the >> capability before the user has logged in. I also don't think this is an >> appropriate use of 2119 "MAY". If you mean, "The IMAP server MUST NOT >> advertise this capability until after the user has logged in," >> then you should say it that way. (And if that's not what you mean, >> please discuss it with me and clarify.) >> >> [Naren] We purposefully marked it as a MAY, because it alerts >> implementations to the possibility, but doesn't have any effect in >> interoperability. >> What we mean here is client should be ready to handle this no matter when >> the capability is sent. >> > > Barry highlighted that the MAY can be interpreted in two ways: > > 1. The IMAP server must not advertise this capability until after the > user > has logged in. > > 2. The IMAP server may advertise this capability after the user has > logged in. > > Your explanation could be read as meaning that: > > (a) The IMAP server can advertise this capability before the user has > logged in. > > (b) The IMAP server can advertise this capability after the user has > logged in. > > Does the second sentence in the first paragraph of Section 2 mean (a) and > (b)? > > Regards, > S. Moonesamy (as document shepherd) > -- Thanks & Regards -Narendra
- [imapext] AD review of draft-ietf-imapapnd-append… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- [imapext] Referencing RFC 2088 (was: AD review of… S Moonesamy
- Re: [imapext] Referencing RFC 2088 Alexey Melnikov
- Re: [imapext] Referencing RFC 2088 (was: AD revie… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Narendra Bisht
- Re: [imapext] Referencing RFC 2088 S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] Referencing RFC 2088 (was: AD revie… Naren
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Naren
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Naren
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Stu Brandt
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Stu Brandt
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Arnt Gulbrandsen
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Dave Cridland
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Dave Cridland
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Arnt Gulbrandsen
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Bron Gondwana
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Narendra Bisht
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Stu Brandt
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review draft-ietf-imapapnd-appen… S Moonesamy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Adrien de Croy
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Dave Cridland
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Alexey Melnikov
- Re: [imapext] AD review draft-ietf-imapapnd-appen… Alexey Melnikov
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Jayantheesh S B
- Re: [imapext] AD review of draft-ietf-imapapnd-ap… Barry Leiba