Re: Protocol Action: 'INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS' to Proposed Standard
Alexey Melnikov <alexey.melnikov@isode.com> Fri, 04 April 2008 11:12 UTC
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m34BCZYQ090258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Apr 2008 04:12:35 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m34BCZ9q090257; Fri, 4 Apr 2008 04:12:35 -0700 (MST) (envelope-from owner-ietf-imapext@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m34BCQNe090239 for <ietf-imapext@imc.org>; Fri, 4 Apr 2008 04:12:26 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <R=YNGAAMIiPZ@rufus.isode.com>; Fri, 4 Apr 2008 12:12:25 +0100
Message-ID: <47F60D06.5070008@isode.com>
Date: Fri, 04 Apr 2008 12:12:06 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Mark Crispin <mrc@Washington.EDU>
CC: Russ Housley <housley@vigilsec.com>, Bob Braden <braden@ISI.EDU>, iesg-secretary@ietf.org, ietf-imapext@imc.org, iab@iab.org, imapext-chairs@tools.ietf.org, rfc-editor@rfc-editor.org
Subject: Re: Protocol Action: 'INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS' to Proposed Standard
References: <200804032127.OAA00874@gra.isi.edu> <200804032151.m33LpNRu029496@balder-227.proper.com> <alpine.OSX.1.10.0804031455090.595@pangtzu.panda.com>
In-Reply-To: <alpine.OSX.1.10.0804031455090.595@pangtzu.panda.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="Shift_JIS"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>
Mark Crispin wrote: > > The author of the document(s) in question hereby states his complete > lack of concern as to whether the title of the published RFC is > uppercase or titlecase. He was doing nothing other than following past > precedents; and those precedents that he used were all uppercase. > > Of greater concern to the author is the BLOBCHAR/NONWSP issue. I have > already contacted Chris Newman on this matter. This change can be > interpreted as imposing a mandate on IMAP server implementations that > does not currently exist; arguably conflicts with RFC 5051; and in > real life is moot due to external specifications (RFC 2822 among > others). Due to the last point, a string that triggers this rule is an > invalid string. > > With Chris' permission, I request that this particular RFC Editor note > either be waived or be made as a documentation suggestion only. Speaking as an individual: +1. According to <https://datatracker.ietf.org/idtracker/ballot/1157/> Chris agreed with this and he updated his comment to only mention adding the reference to RFC 3629. > On Thu, 3 Apr 2008, Russ Housley wrote: > >> >> See RFC 3501 >> >> At 05:27 PM 4/3/2008, Bob Braden wrote: >> >>> *> The IESG has approved the following document: >>> *> >>> *> - 'INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSIONS ' >>> *> <draft-ietf-imapext-sort-20.txt> as a Proposed Standard >>> *> >>> >>> Why is this document shouting at us? Title case is the norm for >>> RFCs. >>> >>> RFC Editor/bb >>> >>> *> Two simple/optional improvements: >>> *> Add a normative reference to STD 63 (RFC3629) for UTF-8. >>> *> Instead of allowing any 8-bit in BLOBCHAR and NONWSP, reference >>> the rules >>> *> in RFC 3629 for well-formed UTF-8 (UTF8-2, UTF8-3, UTF8-4). >>> *> >>
- Re: Protocol Action: 'INTERNET MESSAGE ACCESS PRO… Russ Housley
- Re: Protocol Action: 'INTERNET MESSAGE ACCESS PRO… Mark Crispin
- Re: Protocol Action: 'INTERNET MESSAGE ACCESS PRO… Alexey Melnikov
- Re: Protocol Action: 'INTERNET MESSAGE ACCESS PRO… Mark Crispin
- Re: Protocol Action: 'INTERNET MESSAGE ACCESS PRO… Russ Housley
- Protocol Action: 'INTERNET MESSAGE ACCESS PROTOCO… The IESG