[MORG] [Errata Held for Document Update] RFC6154 (4422)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 20 July 2015 07:34 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 []) by ietfa.amsl.com (Postfix) with ESMTP id DA4A11A0102; Mon, 20 Jul 2015 00:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 16iJfuvHJ8lV; Mon, 20 Jul 2015 00:34:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id 723BE1A00CF; Mon, 20 Jul 2015 00:34:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D0AD9180471; Mon, 20 Jul 2015 00:30:31 -0700 (PDT)
To: chris.newman@oracle.com, barryleiba@computer.org, nicolson@google.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150720073031.D0AD9180471@rfc-editor.org>
Date: Mon, 20 Jul 2015 00:30:31 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/morg/AqA0w6O-B28nU14Ttg6hR_Nj64M>
Cc: morg@ietf.org, barryleiba@computer.org, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: [MORG] [Errata Held for Document Update] 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:34:21 -0000

The following errata report has been held for document update 
for RFC6154, "IMAP LIST Extension for Special-Use Mailboxes". 

You may review the report below and at:

Status: Held for Document Update
Type: Technical

Reported by: Chris Newman <chris.newman@oracle.com>
Date Reported: 2015-07-20
Held by: Barry Leiba (IESG)

Section: GLOBAL

Original Text

Corrected Text

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.

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