Re: IMAP4 non-synchronizing literals - draft-ietf-imapapnd-rfc2088bis-01
Jayantheesh S B <[email protected]> Thu, 28 Jan 2016 21:02:58 +0000
| Newsgroups | gmane.ietf.imapext |
|---|---|
| Message-ID | <[email protected]> |
--===============2374510878797632952== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_32632fae99ba42028794d611b8e31b41SEAMBX01seasamsungcom_" --_000_32632fae99ba42028794d611b8e31b41SEAMBX01seasamsungcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Alexey, I agree with not to restrict this with only APPEND command. All, Kindly share your review comments for this draft-ietf-imapapnd-rfc2088bis-0= 1. Regards, Jay From: imapext [mailto:[email protected]] On Behalf Of Stu Brandt Sent: Tuesday, December 08, 2015 2:12 PM To: [email protected] Subject: Re: [imapext] IMAP4 non-synchronizing literals - draft-ietf-imapap= nd-rfc2088bis-01 Alexey - I agree with Jamie...restricting to just APPEND (and MULTIAPPEND, and CATEN= ATE) seems unnecessary. Thinking of potential new extensions (e.g. REPLAC= E), there could likely be additional cases where the motivation for LITERAL= - applies. - Stu On 12/8/15 10:41 AM, Alexey Melnikov wrote: On 04/12/2015 18:35, Jamie Nicolson wrote: Apologies if this was discussed before, but why limit the LITERAL- size res= triction to APPEND? Why not just make it apply to all commands: any literal= > 4KB must be sent as a synchronizing literal. This might be easier for cl= ients and servers to implement, so that the code for processing literals do= esn't need to know which command it belongs to. The impact on other command= s would be very limited, since they will almost never need to send a litera= l that large. I personally don't mind if it applies to all commands. Other thoughts? On Fri, Dec 4, 2015 at 3:25 AM, S Moonesamy <[email protected]<mailto:sm= [email protected]>> wrote: Hello, The second draft on our charter about "IMAP4 non-synchronizing literals" [1= ]. Could the working group please review draft-ietf-imapapnd-rfc2088bis-01= and send comments to the mailing list? Regards, S. Moonesamy (as imapapdb WG Chair) 1. https://tools.ietf.org/html/draft-ietf-imapapnd-rfc2088bis-01 _______________________________________________ imapext mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/imapext _______________________________________________ imapext mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/imapext _______________________________________________ imapext mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/imapext --_000_32632fae99ba42028794d611b8e31b41SEAMBX01seasamsungcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Malgun Gothic"; panose-1:2 11 5 3 2 0 0 2 0 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} @font-face {font-family:"\@Malgun Gothic"; panose-1:2 11 5 3 2 0 0 2 0 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; margin-bottom:.0001pt; font-size:10.0pt; font-family:"Courier New"; color:black;} span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:Consolas; color:black;} span.EmailStyle19 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Hi Alexey,<o:p></o:p></sp= an></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">I agree with not to restr= ict this with only APPEND command. <o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">All,<o:p></o:p></span></p= > <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Kindly share your review = comments for this draft-ietf-imapapnd-rfc2088bis-01.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span= ></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Jay<o:p></o:p></span></p> <div> <div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:"= ;Tahoma","sans-serif";color:windowtext">From:</span></b><spa= n style=3D"font-size:10.0pt;font-family:"Tahoma","sans-serif= ";color:windowtext"> imapext [mailto:[email protected]] <b>On Behalf Of </b>Stu Brandt<br> <b>Sent:</b> Tuesday, December 08, 2015 2:12 PM<br> <b>To:</b> [email protected]<br> <b>Subject:</b> Re: [imapext] IMAP4 non-synchronizing literals - draft-ietf= -imapapnd-rfc2088bis-01<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <p class=3D"MsoNormal">Alexey -<br> <br> I agree with Jamie...restricting to just APPEND (and MULTIAPPEND, and CATEN= ATE) seems unnecessary. Thinking of potential new extensions (e= .g. REPLACE), there could likely be additional cases where the motivation f= or LITERAL- applies.<br> <br> - Stu<br> <br> On 12/8/15 10:41 AM, Alexey Melnikov wrote:<o:p></o:p></p> </div> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <p class=3D"MsoNormal">On 04/12/2015 18:35, Jamie Nicolson wrote:<br> <br> <o:p></o:p></p> <div> <p class=3D"MsoNormal">Apologies if this was discussed before, but why limi= t the LITERAL- size restriction to APPEND? Why not just make it apply to al= l commands: any literal > 4KB must be sent as a synchronizing literal. T= his might be easier for clients and servers to implement, so that the code for processing literals doesn't need to kno= w which command it belongs to. The impact on other commands would be very l= imited, since they will almost never need to send a literal that large.<o:p= ></o:p></p> </div> <p class=3D"MsoNormal">I personally don't mind if it applies to all command= s. Other thoughts?<br> <br> <o:p></o:p></p> <div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <p class=3D"MsoNormal">On Fri, Dec 4, 2015 at 3:25 AM, S Moonesamy <<a h= ref=3D"mailto:sm+[email protected]" target=3D"_blank">sm+ietf@eland= sys.com</a>> wrote:<o:p></o:p></p> <p class=3D"MsoNormal">Hello,<br> <br> The second draft on our charter about "IMAP4 non-synchronizing literal= s" [1]. Could the working group please review draft-ietf-imapapn= d-rfc2088bis-01 and send comments to the mailing list?<br> <br> Regards,<br> S. Moonesamy (as imapapdb WG Chair)<br> <br> 1. <a href=3D"https://tools.ietf.org/html/draft-ietf-imapapnd-rfc2088bis-01= " target=3D"_blank"> https://tools.ietf.org/html/draft-ietf-imapapnd-rfc2088bis-01</a><br> <br> _______________________________________________<br> imapext mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><= br> <a href=3D"https://www.ietf.org/mailman/listinfo/imapext" target=3D"_blank"= >https://www.ietf.org/mailman/listinfo/imapext</a><o:p></o:p></p> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </div> <p class=3D"MsoNormal"><br> <br> <br> <o:p></o:p></p> <pre>_______________________________________________<o:p></o:p></pre> <pre>imapext mailing list<o:p></o:p></pre> <pre><a href=3D"mailto:[email protected]">[email protected]</a><o:p></o:p></p= re> <pre><a href=3D"https://www.ietf.org/mailman/listinfo/imapext">https://www.= ietf.org/mailman/listinfo/imapext</a><o:p></o:p></pre> <p class=3D"MsoNormal"><br> <br> <br> <br> <o:p></o:p></p> <pre>_______________________________________________<o:p></o:p></pre> <pre>imapext mailing list<o:p></o:p></pre> <pre><a href=3D"mailto:[email protected]">[email protected]</a><o:p></o:p></p= re> <pre><a href=3D"https://www.ietf.org/mailman/listinfo/imapext">https://www.= ietf.org/mailman/listinfo/imapext</a><o:p></o:p></pre> </blockquote> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </body> </html> --_000_32632fae99ba42028794d611b8e31b41SEAMBX01seasamsungcom_-- --===============2374510878797632952== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ imapext mailing list [email protected] https://www.ietf.org/mailman/listinfo/imapext --===============2374510878797632952==--