Hello SM,

We gone through the=C2=A0=C2=A0= BCP 78 {1] and BCP 79 [2].

As per our knowledge, there is no IPR related to=C2=A0draft-ietf-imapapnd-appendlimit-extension.

Thanks

On Wed,= Nov 11, 2015 at 4:56 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

Hi Jay, Naren,
At 13:35 11-11-2015, Jayantheesh S B wrote:

We have not filed any IPR disclosures for draft-ietf-imapapnd-appendlimit-e= xtension-05.

Do we need to file here for this draft ?=C2=A0 https:/= /datatracker.ietf.org/ipr/new-specific/

Kindly guide us in right direction.

Please read BCP 78 {1] and BCP 79 [2].=C2=A0 There is also information abou= t Intellectual Property Rights at https://www.ietf.org/ipr/=C2=A0 Are y= ou aware of any Intellectual Property Rights relating to draft-ietf-imapapn= d-appendlimit-extension?

Regards,
S. Moonesamy

1. https://tools.ietf.org/html/bcp78
2. https://tools.ietf.org/html/bcp79

Thanks & Regards

-Narendra

--001a1139b12ec36da305244b21f7-- From nobody Wed Nov 11 16:58:31 2015 Return-Path: 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 F0B8C1B3C93 for ; Wed, 11 Nov 2015 16:58:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.8 X-Spam-Level: X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=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 k3dQaLW9fws1 for ; Wed, 11 Nov 2015 16:58:28 -0800 (PST) Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C53DF1B3C92 for ; Wed, 11 Nov 2015 16:58:28 -0800 (PST) Received: from SUBMAN.elandsys.com ([197.227.83.251]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id tAC0w4pp003819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Nov 2015 16:58:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1447289897; x=1447376297; bh=i91rWzOibEBWFSCSpmlCeBbHiQ5CamLtd2/xTB0uT68=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gsYx3oNJzZHvudDTGeoiyR83zwR9j0cP2nGhfkPCCovDuanKQ5HfosQNJcsucsZnb /3hPuzhQ0vXUH9qfyQ1hGzoTj9/z0WG1EZHM706tBMhRuUHxqF6s4yqUwKJksnoJEM K8XLHPJUenvllVLLbrTXIdSE7WmgpA0dJuMT3esQ= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1447289897; x=1447376297; i=@elandsys.com; bh=i91rWzOibEBWFSCSpmlCeBbHiQ5CamLtd2/xTB0uT68=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Nyzpc6QGES2cEHnCel7ZCggO3dxoR11/QDUMewtQNSXlDQ+2ozkXiJD4ZWYuyYAy5 htfDgGmaLSY7FGEfjEI46Mqcb1Ojts3qE2Ev/CIpegY4IN6HTGFq+gTGkHwqYjPXWl XVswYv3hW7en0pT2pKaQdO3enEaBrCbCzgakOFPg= Message-Id: <6.2.5.6.2.20151111141742.0c9a8c28@elandnews.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Wed, 11 Nov 2015 14:19:27 -0800 To: Naren From: S Moonesamy In-Reply-To: References: <6.2.5.6.2.20151111134127.0e02bbb0@elandnews.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Archived-At: Cc: Jayantheesh S B , Jayantheesh S B , imapext@ietf.org Subject: Re: [imapext] IPR disclosure - draft-ietf-imapapnd-appendlimit-extension-05 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 00:58:30 -0000 Hi Naren, At 14:12 11-11-2015, Naren wrote: >We gone through the BCP 78 {1] and BCP 79 [2]. >As per our knowledge, there is no IPR related to >draft-ietf-imapapnd-appendlimit-extension. Thanks for the above. Could I also have a statement from Jay as he is listed as a co-author? Regards, S. Moonesamy From nobody Wed Nov 11 17:02:56 2015 Return-Path: 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 B8C451B3C97 for ; Wed, 11 Nov 2015 17:02:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 WtXl2IoiDIjl for ; Wed, 11 Nov 2015 17:02:53 -0800 (PST) Received: from wguard01.sdsamerica.net (bware1.sdsamerica.net [206.67.236.191]) by ietfa.amsl.com (Postfix) with ESMTP id 1CEE01B3C7E for ; Wed, 11 Nov 2015 17:02:53 -0800 (PST) From: Jayantheesh S B To: S Moonesamy , Naren Thread-Topic: [imapext] IPR disclosure - draft-ietf-imapapnd-appendlimit-extension-05 Thread-Index: AQHRHOXbur/V8DrqSU64NNxKHmV6Xw== Date: Thu, 12 Nov 2015 01:02:52 +0000 Message-ID: <5idqmi1hajie9q0n7xkpgomx.1447290015578@email.android.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted Content-Type: multipart/alternative; boundary="_000_5idqmi1hajie9q0n7xkpgomx1447290015578emailandroidcom_" MIME-Version: 1.0 Received-SPF: none Archived-At: Cc: Jayantheesh S B , "imapext@ietf.org" Subject: Re: [imapext] IPR disclosure - draft-ietf-imapapnd-appendlimit-extension-05 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 01:02:54 -0000 --_000_5idqmi1hajie9q0n7xkpgomx1447290015578emailandroidcom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 RGVhciBTTSwNCg0KQXMgcGVyIG15IGtub3dsZWRnZSwgdGhlcmUgaXMgbm8gSVBSIHJlbGF0ZWQg dG8gSU1BUCBhcHBlbmQgbGltaXQgZHJhZnQuDQoNClJlZ2FyZHMsDQpKYXkNClNlbnQgZnJvbSBt eSBWZXJpem9uIFdpcmVsZXNzIDRHIExURSBzbWFydHBob25lDQotLS0tLS0tLSBPcmlnaW5hbCBt ZXNzYWdlIC0tLS0tLS0tDQpGcm9tOiBTIE1vb25lc2FteSA8c20raWV0ZkBlbGFuZHN5cy5jb20+ DQpEYXRlOiAxMS8xMS8yMDE1IDc6NTggUE0gKEdNVC0wNTowMCkNClRvOiBOYXJlbiA8bmFyZW5k cmFzaW5naC5iaXNodEBnbWFpbC5jb20+DQpDYzogSmF5YW50aGVlc2ggUyBCIDxqLnNiQHNlYS5z YW1zdW5nLmNvbT4sIEpheWFudGhlZXNoIFMgQiA8amF5YW50aGVlc2guc2JAZ21haWwuY29tPiwg aW1hcGV4dEBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtpbWFwZXh0XSBJUFIgZGlzY2xvc3VyZSAt IGRyYWZ0LWlldGYtaW1hcGFwbmQtYXBwZW5kbGltaXQtZXh0ZW5zaW9uLTA1DQoNCkhpIE5hcmVu LA0KQXQgMTQ6MTIgMTEtMTEtMjAxNSwgTmFyZW4gd3JvdGU6DQo+V2UgZ29uZSB0aHJvdWdoIHRo ZSAgQkNQIDc4IHsxXSBhbmQgQkNQIDc5IFsyXS4NCj5BcyBwZXIgb3VyIGtub3dsZWRnZSwgdGhl cmUgaXMgbm8gSVBSIHJlbGF0ZWQgdG8NCj5kcmFmdC1pZXRmLWltYXBhcG5kLWFwcGVuZGxpbWl0 LWV4dGVuc2lvbi4NCg0KVGhhbmtzIGZvciB0aGUgYWJvdmUuDQoNCkNvdWxkIEkgYWxzbyBoYXZl IGEgc3RhdGVtZW50IGZyb20gSmF5IGFzIGhlIGlzIGxpc3RlZCBhcyBhIGNvLWF1dGhvcj8NCg0K UmVnYXJkcywNClMuIE1vb25lc2FteQ0KDQo= --_000_5idqmi1hajie9q0n7xkpgomx1447290015578emailandroidcom_ Content-Type: text/html; charset="utf-8" Content-ID: <6070FCCAAB21BE4CBF75FD371C366559@sea.samsung.com> Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdj5EZWFyIFNN LDwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+QXMgcGVyIG15IGtub3dsZWRnZSwgdGhl cmUgaXMgbm8gSVBSIHJlbGF0ZWQgdG8gSU1BUCBhcHBlbmQgbGltaXQgZHJhZnQuPC9kaXY+DQo8 ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5SZWdhcmRzLDwvZGl2Pg0KPGRpdj5KYXk8L2Rpdj4NCjxk aXYgaWQ9ImNvbXBvc2VyX3NpZ25hdHVyZSI+DQo8ZGl2IHN0eWxlPSJmb250LXNpemU6ODUlO2Nv bG9yOiM1NzU3NTciPlNlbnQgZnJvbSBteSBWZXJpem9uIFdpcmVsZXNzIDRHIExURSBzbWFydHBo b25lPC9kaXY+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9ImZvbnQtc2l6ZToxMDAlO2NvbG9yOiMwMDAw MDAiPjwhLS0gb3JpZ2luYWxNZXNzYWdlIC0tPg0KPGRpdj4tLS0tLS0tLSBPcmlnaW5hbCBtZXNz YWdlIC0tLS0tLS0tPC9kaXY+DQo8ZGl2PkZyb206IFMgTW9vbmVzYW15ICZsdDtzbSYjNDM7aWV0 ZkBlbGFuZHN5cy5jb20mZ3Q7IDwvZGl2Pg0KPGRpdj5EYXRlOiAxMS8xMS8yMDE1IDc6NTggUE0g KEdNVC0wNTowMCkgPC9kaXY+DQo8ZGl2PlRvOiBOYXJlbiAmbHQ7bmFyZW5kcmFzaW5naC5iaXNo dEBnbWFpbC5jb20mZ3Q7IDwvZGl2Pg0KPGRpdj5DYzogSmF5YW50aGVlc2ggUyBCICZsdDtqLnNi QHNlYS5zYW1zdW5nLmNvbSZndDssIEpheWFudGhlZXNoIFMgQiAmbHQ7amF5YW50aGVlc2guc2JA Z21haWwuY29tJmd0OywgaW1hcGV4dEBpZXRmLm9yZw0KPC9kaXY+DQo8ZGl2PlN1YmplY3Q6IFJl OiBbaW1hcGV4dF0gSVBSIGRpc2Nsb3N1cmUgLSBkcmFmdC1pZXRmLWltYXBhcG5kLWFwcGVuZGxp bWl0LWV4dGVuc2lvbi0wNQ0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8Zm9u dCBzaXplPSIyIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwcHQ7Ij4NCjxkaXYgY2xhc3M9IlBs YWluVGV4dCI+SGkgTmFyZW4sPGJyPg0KQXQgMTQ6MTIgMTEtMTEtMjAxNSwgTmFyZW4gd3JvdGU6 PGJyPg0KJmd0O1dlIGdvbmUgdGhyb3VnaCB0aGUmbmJzcDsgQkNQIDc4IHsxXSBhbmQgQkNQIDc5 IFsyXS48YnI+DQomZ3Q7QXMgcGVyIG91ciBrbm93bGVkZ2UsIHRoZXJlIGlzIG5vIElQUiByZWxh dGVkIHRvIDxicj4NCiZndDtkcmFmdC1pZXRmLWltYXBhcG5kLWFwcGVuZGxpbWl0LWV4dGVuc2lv bi48YnI+DQo8YnI+DQpUaGFua3MgZm9yIHRoZSBhYm92ZS48YnI+DQo8YnI+DQpDb3VsZCBJIGFs c28gaGF2ZSBhIHN0YXRlbWVudCBmcm9tIEpheSBhcyBoZSBpcyBsaXN0ZWQgYXMgYSBjby1hdXRo b3I/PGJyPg0KPGJyPg0KUmVnYXJkcyw8YnI+DQpTLiBNb29uZXNhbXkgPGJyPg0KPGJyPg0KPC9k aXY+DQo8L3NwYW4+PC9mb250Pg0KPC9ib2R5Pg0KPC9odG1sPg0K --_000_5idqmi1hajie9q0n7xkpgomx1447290015578emailandroidcom_-- From nobody Thu Nov 12 00:48:37 2015 Return-Path: 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 0E3A61ADBFB for ; Thu, 12 Nov 2015 00:48:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.8 X-Spam-Level: X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=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 z1afPdXktdJB for ; Thu, 12 Nov 2015 00:48:34 -0800 (PST) Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D05411AD377 for ; Thu, 12 Nov 2015 00:48:34 -0800 (PST) Received: from SUBMAN.elandsys.com ([197.227.83.251]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id tAC8mGis008855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Nov 2015 00:48:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1447318109; x=1447404509; bh=A97vWazujOX5kB9LuCh0XlZOZbUBIi7nJwGZSGaatVU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RM01siUjHPszKSyv5AjGBnZLsMcY3tvJcMqyK4vFL1xI0bLi7tlEfV66JApgLDzth 8kFG3xPtUyzxGTU50S22iKoxB7RvWupXfJbrmzTGCRM0iDkVYMB6gUdiGUkeemQkIl ydEBotW5NOb/cKa97KE+bqgiprYW/MeL6LNYvvM8= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1447318109; x=1447404509; i=@elandsys.com; bh=A97vWazujOX5kB9LuCh0XlZOZbUBIi7nJwGZSGaatVU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nLFjnluwoZwqTXSVU/HeQqBNJarwNDOqvYghCdiMOfkKd5JxZ06T8jye0PX743kji IlOxz11ia/vxtNGk5BbEqFkGJ0IaKm8IT6LDKmiI3mS3vgawgnk+nH1tUSZPYqKZUO OfN8wo3EFMslkd21wZH0BwyXHSmTW+lSRLVz2DUw= Message-Id: <6.2.5.6.2.20151112000007.0eb26d88@elandnews.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Thu, 12 Nov 2015 00:46:54 -0800 To: Jayantheesh S B , Naren From: S Moonesamy In-Reply-To: <5idqmi1hajie9q0n7xkpgomx.1447290015578@email.android.com> References: <5idqmi1hajie9q0n7xkpgomx.1447290015578@email.android.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Archived-At: Cc: imapext@ietf.org Subject: Re: [imapext] IPR disclosure - draft-ietf-imapapnd-appendlimit-extension-05 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 08:48:36 -0000 Hi Naren, Jay, When an author submits an Internet-Draft to the IETF, he/she is making an IETF Contribution. The author [1] is required to promptly disclose any Intellectual Property Rights (IPR) which may cover the Contribution. The requirement also applies to everyone who is participating in this Working Group. You both confirmed that you are not aware of any IPR covering your Contributions. As such, there is no need for you to file an IPR disclosure. If you become aware in future of any IPR covering the Contribution, you are expected to file an IPR disclosure. Regards, S. Moonesamy (as document shepherd) 1. Please refer to BCP 78 and BCP 79 for the correct explanation. From nobody Thu Nov 12 01:01:13 2015 Return-Path: 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 AC8521B2AD5 for ; Thu, 12 Nov 2015 01:01:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.8 X-Spam-Level: X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=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 WVUG22TUUw6y for ; Thu, 12 Nov 2015 01:01:12 -0800 (PST) Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 042C41B2AD2 for ; Thu, 12 Nov 2015 01:01:11 -0800 (PST) Received: from SUBMAN.elandsys.com ([197.227.83.251]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id tAC90tin028077 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Nov 2015 01:01:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1447318868; x=1447405268; bh=RWJy9SoXGBKQicBpqSNkRnCSuB5+8TwPfJPivTZA85I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OORczn1AysqDMvROVKWY1K7RVAFMATvl/rv7swFwOSO1iH61o/7Kedwjh/okPwXY7 7jlf3YROx2qXTzNu2d2qsvTtnBWwDs0yiAMNYplG0j8HD9Nd98pgRlTuXrtXal1Zp4 gs207z1y5fHlTFkIzVl4KeDTSM6bBLKqaZ/gqDwg= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1447318868; x=1447405268; i=@elandsys.com; bh=RWJy9SoXGBKQicBpqSNkRnCSuB5+8TwPfJPivTZA85I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HT9QIcRcIeNjvn9MQTIa6HLCUtm/hHiwpEuMdCMU5pCVXTCx+xLufdN8TjgeNfGGH tRfAW2VQts4O9RvO4JIHhkFJJnAR0iSP88jrp2SpaBhhfMsfbRDp4lO3m50uaGfnBb UZFG2ozSwJBXSvW57KYC0Nn1VhhNkYpht4NcJQYE= Message-Id: <6.2.5.6.2.20151112004724.0eb35050@elandnews.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Thu, 12 Nov 2015 01:00:28 -0800 To: Jayantheesh S B , Narendra Singh Bisht , imapext@ietf.org From: S Moonesamy In-Reply-To: References: <1995653b48084ecc8db31de40e775e39@SEAMBX02.sea.samsung.com> <6.2.5.6.2.20151111063144.0eabeaf0@elandnews.com> <5643833B.2090606@isode.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Archived-At: Cc: Alexey Melnikov Subject: Re: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-05 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 09:01:12 -0000 Hi Jay, Naren At 13:39 11-11-2015, Jayantheesh S B wrote: >As you mentioned, we will add few words about the benefits of IMAP >Server as well. There is the following text in the Introduction Section of draft-ietf-imapapnd-appendlimit-extension-05: "This results in unnecessary resource usage. Especially in the mobile device environment, appending mail with huge attachment consumes device resources like device battery power and mobile data." I read that as: this results in unnecessary usage in the mobile device environment as it increases the consumption of device battery power and mobile data, i.e. it only benefits IMAP clients in a mobile environment. Could you post some text about how the extension might help the IMAP server to the mailing list? The Working Group can then discuss about that text and agree on what text to add. Regards, S. Moonesamy From nobody Fri Nov 13 12:30:24 2015 Return-Path: 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 D04411B2F72 for ; Fri, 13 Nov 2015 12:30:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 ctCtHqm-s9ma for ; Fri, 13 Nov 2015 12:30:20 -0800 (PST) Received: from wguard02.sdsamerica.net (bware2.sdsamerica.net [206.67.236.192]) by ietfa.amsl.com (Postfix) with ESMTP id A0D661B2F73 for ; Fri, 13 Nov 2015 12:30:20 -0800 (PST) From: Jayantheesh S B To: S Moonesamy , Narendra Singh Bisht , "imapext@ietf.org" Thread-Topic: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-05 Thread-Index: AQHRHJZg+jgS95U7s0i2HDQOgXsYkp6XcYaA///nfjCAARLHAIAB9/OQ Date: Fri, 13 Nov 2015 20:30:17 +0000 Message-ID: <954e4f2882fe484989aa7752b69249ff@SEAMBX01.sea.samsung.com> References: <1995653b48084ecc8db31de40e775e39@SEAMBX02.sea.samsung.com> <6.2.5.6.2.20151111063144.0eabeaf0@elandnews.com> <5643833B.2090606@isode.com> <6.2.5.6.2.20151112004724.0eb35050@elandnews.com> In-Reply-To: <6.2.5.6.2.20151112004724.0eb35050@elandnews.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted Content-Type: multipart/alternative; boundary="_000_954e4f2882fe484989aa7752b69249ffSEAMBX01seasamsungcom_" MIME-Version: 1.0 Received-SPF: none Archived-At: Cc: Alexey Melnikov Subject: Re: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-05 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2015 20:30:23 -0000 --_000_954e4f2882fe484989aa7752b69249ffSEAMBX01seasamsungcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear SM, Please find the updated text below. Kindly review and share your comments. 1. Introduction Several IMAP server have limitation for mail upload size which is not published to the email client. When email client APPEND a mail with huge attachments, it fails due to size restriction set by the IMAP server. This results in unnecessary resource usage. Especially in the mobile device environment, appending mail with huge attachment consumes device resources like device battery power and mobile data. The IMAP APPENDLIMIT extension provides an ability to advertise maximum upload size allowed by the IMAP server, so that email client knows the size limitation beforehand. This extension provides server admins with the capability to configure the = maximum append limit size they will be expecting from the client. By implem= enting this extension, IMAP server side processing of huge attachments abov= e the available limit from the IMAP client can be avoided to a great extent= . Regards, Jay -----Original Message----- From: imapext [mailto:imapext-bounces@ietf.org] On Behalf Of S Moonesamy Sent: Thursday, November 12, 2015 4:00 AM To: Jayantheesh S B; Narendra Singh Bisht; imapext@ietf.org Cc: Alexey Melnikov Subject: Re: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-0= 5 Hi Jay, Naren At 13:39 11-11-2015, Jayantheesh S B wrote: >As you mentioned, we will add few words about the benefits of IMAP >Server as well. There is the following text in the Introduction Section of draft-ietf-imapapnd-appendlimit-extension-05: "This results in unnecessary resource usage. Especially in the mobile device environment, appending mail with huge attachment consumes device resources like device battery power and mobile data." I read that as: this results in unnecessary usage in the mobile device envi= ronment as it increases the consumption of device battery power and mobile = data, i.e. it only benefits IMAP clients in a mobile environment. Could you post some text about how the extension might help the IMAP server= to the mailing list? The Working Group can then discuss about that text a= nd agree on what text to add. Regards, S. Moonesamy _______________________________________________ imapext mailing list imapext@ietf.org https://www.ietf.org/mailman/listinfo/imapext --_000_954e4f2882fe484989aa7752b69249ffSEAMBX01seasamsungcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear SM,

Please find the updated text below. Kindly review= and share your comments.

1. Introduction

Several IMAP server have limitation for mail uplo= ad size which is not

published to the email client. When email c= lient APPEND a mail with

huge attachments, it fails due to size restrictio= n set by the IMAP

server. This results in unnecessary resourc= e usage. Especially in the

mobile device environment, appending mail with hu= ge attachment consumes

device resources like device battery power and mo= bile data.

The IMAP APPENDLIMIT extension provides an abilit= y to advertise maximum

upload size allowed by the IMAP server, so that e= mail client knows the

size limitation beforehand.

This extension provides server admins with the ca= pability to configure the maximum append limit size they will be expecting = from the client. By implementing this extension, IMAP server side processin= g of huge attachments above the available limit from the IMAP client can be avoided to a great extent.

Regards,

Jay

-----Original Message-----
From: imapext [mailto:imapext-bounces@ietf.org] On Behalf Of S Moonesamy Sent: Thursday, November 12, 2015 4:00 AM
To: Jayantheesh S B; Narendra Singh Bisht; imapext@ietf.org
Cc: Alexey Melnikov
Subject: Re: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-0= 5

Hi Jay, Naren

At 13:39 11-11-2015, Jayantheesh S B wrote:<= /o:p>

>As you mentioned, we will add few words about= the benefits of IMAP

>Server as well.

There is the following text in the Introduction S= ection of

draft-ietf-imapapnd-appendlimit-extension-05:

"This results in unnecessary re= source usage. Especially in the

mobile device environment, app= ending mail with huge attachment

consumes device resources like= device battery power and mobile data."

I read that as: this results in unnecessary usage= in the mobile device environment as it increases the consumption of device= battery power and mobile data, i.e. it only benefits IMAP clients in a mob= ile environment.

Could you post some text about how the extension = might help the IMAP server to the mailing list? The Working Group can= then discuss about that text and agree on what text to add.

Regards,

S. Moonesamy

_______________________________________________

imapext mailing list

imapext@ietf.org=

https://www.= ietf.org/mailman/listinfo/imapext

--_000_954e4f2882fe484989aa7752b69249ffSEAMBX01seasamsungcom_-- From nobody Sat Nov 14 04:19:42 2015 Return-Path: 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 26E7C1B66DD for ; Sat, 14 Nov 2015 04:19:42 -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 F1BX_TPFaMEQ for ; Sat, 14 Nov 2015 04:19:40 -0800 (PST) Received: from waldorf.isode.com (waldorf.isode.com [217.34.220.150]) by ietfa.amsl.com (Postfix) with ESMTP id C5D801B66DB for ; Sat, 14 Nov 2015 04:19:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1447503578; d=isode.com; s=selector; i=@isode.com; bh=ceHhz4fYe/MTsUNOpTlAS/K4jPmFnDEhBB58JSSKu+E=; 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=Vafco/F1frj8iv5mQ73cs76g0YdmiJrDjKDhPT2fLxGsC0x1Q9AIZTzerNbnHvyQK9d2z+ znwRTx/CR3+t9CiCSV73pmP5Q6BBzYnxJxCe0JrsrfFUZ7wT+r89hOrRD+IvmkIIkVhjey iiASlc5cwpkBIIzVKY5x1PwAftXPkGQ=; Received: from [192.168.0.6] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id ; Sat, 14 Nov 2015 12:19:38 +0000 X-SMTP-Protocol-Errors: PIPELINING From: Alexey Melnikov X-Mailer: iPad Mail (13B143) In-Reply-To: <954e4f2882fe484989aa7752b69249ff@SEAMBX01.sea.samsung.com> Date: Sat, 14 Nov 2015 12:20:48 +0000 Message-Id: <83D31E9F-B3EE-4B60-A76D-CDD010DBD724@isode.com> References: <1995653b48084ecc8db31de40e775e39@SEAMBX02.sea.samsung.com> <6.2.5.6.2.20151111063144.0eabeaf0@elandnews.com> <5643833B.2090606@isode.com> <6.2.5.6.2.20151112004724.0eb35050@elandnews.com> <954e4f2882fe484989aa7752b69249ff@SEAMBX01.sea.samsung.com> To: Jayantheesh S B MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=Apple-Mail-60A8D4DD-5096-4D4E-8634-637F2880DBC8 Content-Transfer-Encoding: 7bit Archived-At: Cc: Narendra Singh Bisht , S Moonesamy , "imapext@ietf.org" Subject: Re: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-05 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 12:19:42 -0000 --Apple-Mail-60A8D4DD-5096-4D4E-8634-637F2880DBC8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hi Jay, > On 13 Nov 2015, at 20:30, Jayantheesh S B wrote: >=20 > Dear SM, > =20 > Please find the updated text below. Kindly review and share your comments.= > =20 > 1. Introduction > =20 > Several IMAP server have limitation for mail upload size which is not > published to the email client. When email client APPEND a mail with > huge attachments, it fails due to size restriction set by the IMAP > server. This results in unnecessary resource usage. Especially in the > mobile device environment, appending mail with huge attachment consumes > device resources like device battery power and mobile data. > =20 > The IMAP APPENDLIMIT extension provides an ability to advertise maximum > upload size allowed by the IMAP server, so that email client knows the > size limitation beforehand. > =20 > This extension provides server admins with the capability to configure the= maximum append limit size they will be expecting from the client. By implem= enting this extension, IMAP server side processing of huge attachments above= the available limit from the IMAP client can be avoided to a great extent. This is an improvement. This doesn't help if the client doesn't support the e= xtension, but in the context of this document this is probably obvious, so d= oesn't need saying. (I was just wondering whether "the IMAP client" in the l= ast sentence is clear or needs clarifying.) > =20 > Regards, > Jay > -----Original Message----- > From: imapext [mailto:imapext-bounces@ietf.org] On Behalf Of S Moonesamy > Sent: Thursday, November 12, 2015 4:00 AM > To: Jayantheesh S B; Narendra Singh Bisht; imapext@ietf.org > Cc: Alexey Melnikov > Subject: Re: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-= 05 > =20 > Hi Jay, Naren > At 13:39 11-11-2015, Jayantheesh S B wrote: > >As you mentioned, we will add few words about the benefits of IMAP > >Server as well. > =20 > There is the following text in the Introduction Section of > draft-ietf-imapapnd-appendlimit-extension-05: > =20 > "This results in unnecessary resource usage. Especially in the > mobile device environment, appending mail with huge attachment > consumes device resources like device battery power and mobile data." > =20 > I read that as: this results in unnecessary usage in the mobile device env= ironment as it increases the consumption of device battery power and mobile d= ata, i.e. it only benefits IMAP clients in a mobile environment. > =20 > Could you post some text about how the extension might help the IMAP serve= r to the mailing list? The Working Group can then discuss about that text a= nd agree on what text to add. > =20 > Regards, > S. Moonesamy > =20 > _______________________________________________ > imapext mailing list > imapext@ietf.org > https://www.ietf.org/mailman/listinfo/imapext > _______________________________________________ > imapext mailing list > imapext@ietf.org > https://www.ietf.org/mailman/listinfo/imapext --Apple-Mail-60A8D4DD-5096-4D4E-8634-637F2880DBC8 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Hi Jay,

On 13 Nov 2015, at 20:30, Jayantheesh S B <j.sb@sea.samsung.com> wrote:

Dear SM,

Please find the updated text below. Kindly review and share your comments.

1. Introduction

Several IMAP server have limitation for mail upload size which is not

published to the email client. When email client APPEND a mail with

huge attachments, it fails due to size restriction set by the IMAP

server. This results in unnecessary resource usage. Especially in the

mobile device environment, appending mail with huge attachment consumes

device resources like device battery power and mobile data.

The IMAP APPENDLIMIT extension provides an ability to advertise maximum

upload size allowed by the IMAP server, so that email client knows the

size limitation beforehand.

This extension provides server admins with the capability to configure the maximum append limit size they will be expecting from the client. By implementing this extension, IMAP server side processing of huge attachments above the available limit from the IMAP client can be avoided to a great extent.

This is an improvement. This doesn't help if the client doesn't support the extension, but in the context of this document this is probably obvious, so doesn't need saying. (I was just wondering whether "the IMAP client" in the last sentence is clear or needs clarifying.)

Regards,

Jay

-----Original Message-----
From: imapext [mailto:imapext-bounces@ietf.org] On Behalf Of S Moonesamy
Sent: Thursday, November 12, 2015 4:00 AM
To: Jayantheesh S B; Narendra Singh Bisht; imapext@ietf.org
Cc: Alexey Melnikov
Subject: Re: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-05

Hi Jay, Naren

At 13:39 11-11-2015, Jayantheesh S B wrote:

>As you mentioned, we will add few words about the benefits of IMAP

>Server as well.

There is the following text in the Introduction Section of

draft-ietf-imapapnd-appendlimit-extension-05:

   "This results in unnecessary resource usage. Especially in the

    mobile device environment, appending mail with huge attachment

    consumes device resources like device battery power and mobile data."

I read that as: this results in unnecessary usage in the mobile device environment as it increases the consumption of device battery power and mobile data, i.e. it only benefits IMAP clients in a mobile environment.

Could you post some text about how the extension might help the IMAP server to the mailing list? The Working Group can then discuss about that text and agree on what text to add.

Regards,

S. Moonesamy

_______________________________________________

imapext mailing list

imapext@ietf.org

https://www.ietf.org/mailman/listinfo/imapext

_______________________________________________
imapext mailing list
imapext@ietf.org
https://www.ietf.org/mailman/listinfo/imapext

--Apple-Mail-60A8D4DD-5096-4D4E-8634-637F2880DBC8-- From nobody Mon Nov 16 07:55:14 2015 Return-Path: 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 C33631A0387 for ; Mon, 16 Nov 2015 07:55:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 7r_SGiWLrn6r for ; Mon, 16 Nov 2015 07:55:11 -0800 (PST) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 4FA891A0395 for ; Mon, 16 Nov 2015 07:55:06 -0800 (PST) Received: by qkas77 with SMTP id s77so116882221qka.0 for ; Mon, 16 Nov 2015 07:55:05 -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=5xkY+2nFeIz0coPteDOpMmV3kZqFAaPc+QdqVrRPu/E=; b=KZ2gwfkmNPNNHEfMlvaEfX/Jlrw/+wUYRg/RHPMXakA2OcSrJEXtSFUIc9dtlGiKWD rgcYld7QDD7fvxGfK4E7dxTFAyYu8Y3sOhafBUmHUAukhk7IDWbu8pngsbFM5aKpstr1 f5+gkHnaxzpYi0J9D2OMm6GxoU1I14zySxqxDox3XJmamhiGupthaUpXVS+nyyulVyxb XyUioIN3GJUwTdqPUXAc2UXCsF5qlLhfoetqKbDw1MwzEyfEcUP1rvHHH9YdY19sWx0V ZwhM3zK59fVnFxHW1l830gAwjrbz6vLlMm1j+aiutT+xLxtIQVzeXGSYGVt+nmt1oCvY FBgw== X-Received: by 10.140.175.65 with SMTP id v62mr38219508qhv.75.1447689305450; Mon, 16 Nov 2015 07:55:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.92.21 with HTTP; Mon, 16 Nov 2015 07:54:46 -0800 (PST) In-Reply-To: <83D31E9F-B3EE-4B60-A76D-CDD010DBD724@isode.com> References: <1995653b48084ecc8db31de40e775e39@SEAMBX02.sea.samsung.com> <6.2.5.6.2.20151111063144.0eabeaf0@elandnews.com> <5643833B.2090606@isode.com> <6.2.5.6.2.20151112004724.0eb35050@elandnews.com> <954e4f2882fe484989aa7752b69249ff@SEAMBX01.sea.samsung.com> <83D31E9F-B3EE-4B60-A76D-CDD010DBD724@isode.com> From: Naren Date: Mon, 16 Nov 2015 10:54:46 -0500 Message-ID: To: Alexey Melnikov Content-Type: multipart/alternative; boundary=001a113a95decbf1e10524aa6e81 Archived-At: Cc: Jayantheesh S B , S Moonesamy , "imapext@ietf.org" Subject: Re: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-05 X-BeenThere: imapext@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion of IMAP extensions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 15:55:14 -0000 --001a113a95decbf1e10524aa6e81 Content-Type: text/plain; charset=UTF-8 Hi Alexey, Thanks for your review comments. Please find the updated text below. Kindly review and share your views. This extension provides server admins with the capability to configure the maximum append limit size they will be expecting from the client. IMAP server side processing of huge attachments above the available can be avoided to a great extent, if this extension is supported at the IMAP client. Thanks & Regards - Naren On Sat, Nov 14, 2015 at 7:20 AM, Alexey Melnikov wrote: > Hi Jay, > > On 13 Nov 2015, at 20:30, Jayantheesh S B wrote: > > Dear SM, > > > > Please find the updated text below. Kindly review and share your comments. > > > > 1. Introduction > > > > Several IMAP server have limitation for mail upload size which is not > > published to the email client. When email client APPEND a mail with > > huge attachments, it fails due to size restriction set by the IMAP > > server. This results in unnecessary resource usage. Especially in the > > mobile device environment, appending mail with huge attachment consumes > > device resources like device battery power and mobile data. > > > > The IMAP APPENDLIMIT extension provides an ability to advertise maximum > > upload size allowed by the IMAP server, so that email client knows the > > size limitation beforehand. > > > > This extension provides server admins with the capability to configure the > maximum append limit size they will be expecting from the client. By > implementing this extension, IMAP server side processing of huge > attachments above the available limit from the IMAP client can be avoided > to a great extent. > > > This is an improvement. This doesn't help if the client doesn't support > the extension, but in the context of this document this is probably > obvious, so doesn't need saying. (I was just wondering whether "the IMAP > client" in the last sentence is clear or needs clarifying.) > > > > Regards, > > Jay > > -----Original Message----- > From: imapext [mailto:imapext-bounces@ietf.org ] > On Behalf Of S Moonesamy > Sent: Thursday, November 12, 2015 4:00 AM > To: Jayantheesh S B; Narendra Singh Bisht; imapext@ietf.org > Cc: Alexey Melnikov > Subject: Re: [imapext] Review - > draft-ietf-imapapnd-appendlimit-extension-05 > > > > Hi Jay, Naren > > At 13:39 11-11-2015, Jayantheesh S B wrote: > > >As you mentioned, we will add few words about the benefits of IMAP > > >Server as well. > > > > There is the following text in the Introduction Section of > > draft-ietf-imapapnd-appendlimit-extension-05: > > > > "This results in unnecessary resource usage. Especially in the > > mobile device environment, appending mail with huge attachment > > consumes device resources like device battery power and mobile data." > > > > I read that as: this results in unnecessary usage in the mobile device > environment as it increases the consumption of device battery power and > mobile data, i.e. it only benefits IMAP clients in a mobile environment. > > > > Could you post some text about how the extension might help the IMAP > server to the mailing list? The Working Group can then discuss about that > text and agree on what text to add. > > > > Regards, > > S. Moonesamy > > > > _______________________________________________ > > imapext mailing list > > imapext@ietf.org > > https://www.ietf.org/mailman/listinfo/imapext > > _______________________________________________ > imapext mailing list > imapext@ietf.org > https://www.ietf.org/mailman/listinfo/imapext > > -- Thanks & Regards -Narendra --001a113a95decbf1e10524aa6e81 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi Alexey,

=C2=A0

Thanks for your= review comments.

=C2=A0

Please find the= updated text below. Kindly review and share your views.

=C2=A0

This extension provides server admins with the cap= ability to configure the maximum append limit size they will be expecting from th= e client. IMAP server side processing of huge attachments above the availab= le can be avoided to a great extent, if this extension is supported at the IMAP client.

=C2=A0

Thanks & Regards

- Naren

On Sat, No= v 14, 2015 at 7:20 AM, Alexey Melnikov <alexey.melnikov@isode.com<= /a>> wrote:

<= div>Hi Jay,

On 13 Nov 2015, at 20:30, Jayantheesh = S B <j.sb@sea.= samsung.com> wrote:

Dear SM,

=C2=A0

Please find the updated text below. Kindly review and share your comment= s.

=C2=A0

1. Introduction

=C2=A0

Several IMAP server have limitation for mail upload size which is not=

published to the email client.=C2=A0 When email client APPEND a mail wit= h

huge attachments, it fails due to size restriction set by the IMAP

server.=C2=A0 This results in unnecessary resource usage.=C2=A0 Especial= ly in the

mobile device environment, appending mail with huge attachment consumes<= u>

device resources like device battery power and mobile data.

=C2=A0

The IMAP APPENDLIMIT extension provides an ability to advertise maximum<= u>

upload size allowed by the IMAP server, so that email client knows the

size limitation beforehand.

=C2=A0

This extension provides server admins with the capability to configure t= he maximum append limit size they will be expecting from the client. By imp= lementing this extension, IMAP server side processing of huge attachments a= bove the available limit from the IMAP client can be avoided to a great extent.=

This is an improvement. This= doesn't help if the client doesn't support the extension, but in t= he context of this document this is probably obvious, so doesn't need s= aying. (I was just wondering whether "the IMAP client" in the las= t sentence is clear or needs clarifying.)
=C2=A0

Regards,

Jay

-----Original Message-----
From: imapext [mailto:imapext-bounces@ietf.org] On Behalf Of S Moonesamy
Sent: Thursday, November 12, 2015 4:00 AM
To: Jayantheesh S B; Narendra Singh Bisht; imapext@ietf.org
Cc: Alexey Melnikov
Subject: Re: [imapext] Review - draft-ietf-imapapnd-appendlimit-extension-0= 5

=C2=A0

Hi Jay, Naren

At 13:39 11-11-2015, Jayantheesh S B wrote:

>As you mentioned, we will add few words about the benefits of IMAP

>Server as well.

=C2=A0

There is the following text in the Introduction Section of=

draft-ietf-imapapnd-appendlimit-extension-05:

=C2=A0

=C2=A0=C2=A0 "This results in unnecessary resource usage.=C2=A0 Esp= ecially in the

=C2=A0=C2=A0=C2=A0 mobile device environment, appending mail with huge a= ttachment

=C2=A0=C2=A0=C2=A0 consumes device resources like device battery power a= nd mobile data."

=C2=A0

I read that as: this results in unnecessary usage in the mobile device e= nvironment as it increases the consumption of device battery power and mobi= le data, i.e. it only benefits IMAP clients in a mobile environment.=

=C2=A0

Could you post some text about how the extension might help the IMAP ser= ver to the mailing list?=C2=A0 The Working Group can then discuss about tha= t text and agree on what text to add.

=C2=A0

Regards,

S. Moonesamy

=C2=A0

_______________________________________________

imapext mailing list

imapext@ietf.org

https://www.ietf.= org/mailman/listinfo/imapext

___________________= ____________________________
imapext mailing listimapext@ietf.o= rg
https://www.ietf.org/mailman/listinfo/imapext