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

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

Return-Path: <barryleiba@gmail.com>
X-Original-To: morg@ietfa.amsl.com
Delivered-To: morg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34587130E14 for <morg@ietfa.amsl.com>; Thu, 19 Jul 2018 15:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.42
X-Spam-Level:
X-Spam-Status: No, score=-1.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=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 1m5zO7BKwd-M for <morg@ietfa.amsl.com>; Thu, 19 Jul 2018 15:26:15 -0700 (PDT)
Received: from mail-it0-f54.google.com (mail-it0-f54.google.com [209.85.214.54]) (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 A5107130E59 for <morg@ietf.org>; Thu, 19 Jul 2018 15:26:15 -0700 (PDT)
Received: by mail-it0-f54.google.com with SMTP id p4-v6so12097239itf.2 for <morg@ietf.org>; Thu, 19 Jul 2018 15:26:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TCrB07Megp268vMtA5fqoN4XEfHM8aavplN2Wlg6YPw=; b=C63YTsiuQIpcTBcgpA0oBTfoAeeAWiia26UP8gO0nSlHTRrHRqFdKPXjhJx1io0n2W 2hcx8wPZDvt/9rYMYYi9cAMHSOcA0N98JUqm5ymoMBBj9C4od8j1jSjM3LSW2gaI+EeL UC8tUTF/ALSiMltZ4hpZyiGxBimTFyW4upFt53Z2nFXtLLRjgc5JFxOiXfooKeWr7krX ptYm35ABa3pYjzJSQceQ9Cqgs8sIw1Y1FukI0SHk+HOaMKsWT77KjvFoJ4IegMgf4NZ0 pFBEexNK0r3x1bUi0JhtXjHRnarlPVmzUMOdlSjFHE8+AFYFgkcXzCWiVLxzmkAtOZsk +pWw==
X-Gm-Message-State: AOUpUlH83TMaQRz4lR3ML/peiNk2X2cAnVMEPo3Sk04ZdU34iGk51J4f r3YjWhj5imh6zhxSexikW+4GZnxe9/VBTXfvYdg=
X-Google-Smtp-Source: AAOMgpfkzsYBfLzWJ9lBN3PulL34a+yvAE0z7/ItgvfXNLlwQVK8f0SPlIuf4y3W9ZFqg5UnquW13W0CgC1Ua2gDHfc=
X-Received: by 2002:a24:684d:: with SMTP id v74-v6mr7414780itb.88.1532039174879; Thu, 19 Jul 2018 15:26:14 -0700 (PDT)
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)
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/morg/>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2018 22:26:18 -0000

> 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/