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

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 20 July 2015 07:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: morg@ietfa.amsl.com
Delivered-To: morg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9851A0173 for <morg@ietfa.amsl.com>; Mon, 20 Jul 2015 00:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 esx7FG6CkE6f for <morg@ietfa.amsl.com>; Mon, 20 Jul 2015 00:29:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0882C1A0430 for <morg@ietf.org>; Mon, 20 Jul 2015 00:29:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6923F18020A; Mon, 20 Jul 2015 00:25:30 -0700 (PDT)
To: barryleiba@computer.org, nicolson@google.com, barryleiba@computer.org, rg+ietf@qualcomm.com, barryleiba@computer.org, tss@iki.fi
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150720072530.6923F18020A@rfc-editor.org>
Date: Mon, 20 Jul 2015 00:25:30 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/morg/l7I0impP-e_IxfeagQqrKFdpW0k>
Cc: morg@ietf.org, rfc-editor@rfc-editor.org
Subject: [MORG] [Technical Errata Reported] RFC6154 (4422)
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 20 Jul 2015 07:29:33 -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_search.php?rfc=6154&eid=4422

--------------------------------------
Type: Technical
Reported by: Chris Newman <chris.newman@oracle.com>;

Section: GLOBAL

Original Text
-------------
N/A

Corrected Text
--------------
N/A

Notes
-----
There is missing information in this RFC that resulted in interoperability problems when we performed an informal interop test of multiple implementations on 2015-07-19. This is assumed to be a "hold for document update" errata.

There is no guidance in the document related to how special-use attributes are bootstrapped. Servers may pre-create them but there's no requirement to do so and clients may use the CREATE-SPECIAL-USE or METADATA extensions to bootstrap but there is no requirement to use those mechanisms if the server offers them. This resulted in a server implementation assuming the client would bootstrap these attributes and a client assuming the server would do so, thus interoperability failed.

Given this experience, the fastest way to resolve this interop problem over time is for both client and server to take responsibility for bootstrapping special use mailboxes. This means if clients create a mailbox intended for special use (e.g., drafts, sent, junk, trash, etc), and the CREATE-SPECIAL-USE extension is offered, then clients need to provide the USE extension to improve interoperability.  Servers that are provisioned with an end-user's locale or language need to pre-create appropriate special-use mailboxes to improve interoperability of this extension. For existing accounts where the server is upgraded to support this feature, the server can look for mailboxes with names that imply special use and add the attribute to those mailboxes (especially if the server has locale/language awareness provisioned for users). Clients that implement a name-based search if special use attributes are not present and decide to use a mailbox for a special use based on its name can use the 
 METADATA extension, if offered, to label that mailbox appropriately.

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 (IESG)
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