Re: [MORG] [Editorial Errata Reported] RFC6154 (5431)

Barry Leiba <barryleiba@computer.org> Thu, 19 July 2018 22:26 UTC

MIME-Version: 1.0
References: <20180719214312.8571CB819EE@rfc-editor.org>
In-Reply-To: <20180719214312.8571CB819EE@rfc-editor.org>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 19 Jul 2018 18:26:03 -0400
Message-ID: <CALaySJJYmREJCwA_xOjtY26qcaX8RVFRXtueMDkCgDEPJzFRPg@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: aamelnikov@fastmail.fm, adam@nostrum.com, ben@nostrum.com, brong@fastmailteam.com, morg@ietf.org, nicolson@google.com, rg+ietf@qualcomm.com, tss@iki.fi
Content-Type: multipart/alternative; boundary="000000000000cd00ec057161aa17"
Archived-At: <https://mailarchive.ietf.org/arch/msg/morg/CdTHDF8LUH4xXPJcL6_o6al4-SI>
Subject: Re: [MORG] [Editorial Errata Reported] RFC6154 (5431)
Precedence: list

> There exist clients which send a non-extended LIST command and will

> correctly display and interact with mailboxes usefully if their

> special-uses are given in the response.

>

> Because of this, many servers are already replying with the special-use

> attributes, and there are no known reports of clients being broken by

> that behaviour.  Because of this, the MAY should be raised to a SHOULD,

> and server implementations should default to turning this on.


That may (ahem) be true now, but the document says exactly what we intended
it to say when it was written.


Alexey, please mark this report REJECTED.


Barry


On Thu, Jul 19, 2018 at 5:51 PM RFC Errata System <rfc-editor@rfc-editor.org>
wrote:

> The following errata report has been submitted for RFC6154,
> "IMAP LIST Extension for Special-Use Mailboxes".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5431
>
> --------------------------------------
> Type: Editorial
> Reported by: Bron Gondwana <brong@fastmailteam.com>
>
> Section: 2
>
> Original Text
> -------------
> An IMAP server that supports this extension MAY include any or all of
> the following attributes in responses to the non-extended IMAP LIST
> command.
>
> Corrected Text
> --------------
> An IMAP server that supports this extension SHOULD include any or all of
> the following attributes in responses to the non-extended IMAP LIST
> command.
>
> Notes
> -----
> There exist clients which send a non-extended LIST command and will
> correctly display and interact with mailboxes usefully if their
> special-uses are given in the response.
>
> Because of this, many servers are already replying with the special-use
> attributes, and there are no known reports of clients being broken by that
> behaviour.  Because of this, the MAY should be raised to a SHOULD, and
> server implementations should default to turning this on.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC6154 (draft-ietf-morg-list-specialuse-06)
> --------------------------------------
> Title               : IMAP LIST Extension for Special-Use Mailboxes
> Publication Date    : March 2011
> Author(s)           : B. Leiba, J. Nicolson
> Category            : PROPOSED STANDARD
> Source              : Message Organization
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG
>
-- 
Barry
--
Barry Leiba  (barryleiba@computer.org)
http://internetmessagingtechnology.org/

[MORG] [Editorial Errata Reported] RFC6154 (5431) RFC Errata System
Re: [MORG] [Editorial Errata Reported] RFC6154 (5… Barry Leiba
Re: [MORG] [Editorial Errata Reported] RFC6154 (5… Bron Gondwana
Re: [MORG] [Editorial Errata Reported] RFC6154 (5… Barry Leiba
Re: [MORG] [Editorial Errata Reported] RFC6154 (5… Ned Freed