[MORG] [Technical Errata Reported] RFC6154 (5581)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 21 December 2018 16:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 04D15130E0E for <morg@ietfa.amsl.com>; Fri, 21 Dec 2018 08:00:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 6uVhCPq5k-_C for <morg@ietfa.amsl.com>; Fri, 21 Dec 2018 08:00:19 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 199F3130DFD for <morg@ietf.org>; Fri, 21 Dec 2018 08:00:19 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 06A80B81C58; Fri, 21 Dec 2018 08:00:18 -0800 (PST)
To: barryleiba@computer.org, nicolson@google.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, rg+ietf@qualcomm.com, barryleiba@computer.org, tss@iki.fi
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: contact@emersion.fr, morg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20181221160018.06A80B81C58@rfc-editor.org>
Date: Fri, 21 Dec 2018 08:00:18 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/morg/8GJeU207UFtX9ZjfayoWtCB5ueU>
Subject: [MORG] [Technical Errata Reported] RFC6154 (5581)
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 21 Dec 2018 16:00:21 -0000

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

--------------------------------------
Type: Technical
Reported by: Not clear whether SPECIAL-USE implies LIST-EXTENDED <contact@emersion.fr>;

Section: 5.2

Original Text
-------------

     C: t1 CAPABILITY
     S: * CAPABILITY IMAP4rev1 SPECIAL-USE
     S: t1 OK done

Corrected Text
--------------

     C: t1 CAPABILITY
     S: * CAPABILITY IMAP4rev1 SPECIAL-USE LIST-EXTENDED
     S: t1 OK done

Notes
-----
Is it okay for a server to support SPECIAL-USE without supporting LIST-EXTENDED? The example seems to imply this, but it's not clear from the RFC text. Section 2 starts with: "For the extended list command [RFC5258]", but doesn't say the server MUST support LIST-EXTENDED.

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