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

Barry Leiba <barryleiba@computer.org> Thu, 19 July 2018 22:40 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 5B72E130E59 for <morg@ietfa.amsl.com>; Thu, 19 Jul 2018 15:40:31 -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 xzL7C9Gp15Ke for <morg@ietfa.amsl.com>; Thu, 19 Jul 2018 15:40:29 -0700 (PDT)
Received: from mail-it0-f42.google.com (mail-it0-f42.google.com [209.85.214.42]) (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 E593A130E3A for <morg@ietf.org>; Thu, 19 Jul 2018 15:40:28 -0700 (PDT)
Received: by mail-it0-f42.google.com with SMTP id q20-v6so12164170ith.0 for <morg@ietf.org>; Thu, 19 Jul 2018 15:40:28 -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=vb1e4t2/tPkg+SXzaYvS+CxZ8ebl/HnvjAsGOhTt+o4=; b=a685jMI+A6VykXBm1Li67MWputPPz1meNzs0c4SjegjGl0tyrio5rs01i9sorq/IYd HmQ3P2K3GTpd5BztlVJzsYVidvJk0y5uGtKTW6FFOpT4vAjDkIdN7ZMQuM59aQ9Ixv2m R0dKmv4gzjWAn/hRyU50PQrfTCt9bx+HNlg8fpe2CjpPlMLtybDcgm24leYzkNkCdTkd W0qRElZyCl+kedbk6fUJoAsCojmEhWZVKFVDIzX0cNjmoCCVmx+6KzwQp48nZuJwqoZO B73oTRjgWATEYTxr/YglB442tbx+64/P6fJZsgRnroa1VAy7XQPaxeHkSihi55gCPl3z /b1Q==
X-Gm-Message-State: AOUpUlERHOdbzmyvLeeXCngli2fdx5CMGqSp/ywIQLtHTO8BKXKL8M9r TvI+cOuUtaylKg6pS3mHHBgRhUpbjcOrhkzC8Z7jAEf5
X-Google-Smtp-Source: AAOMgpd+fA5oEo+p+bsPGsqEG9igLuTkXNcKViQsNmlZxHnn/tr7U+hyi54QrBcm91tV6EoFD9Qjm+VL3n6dS3QOlw4=
X-Received: by 2002:a24:ad45:: with SMTP id a5-v6mr7278390itj.0.1532040028151; Thu, 19 Jul 2018 15:40:28 -0700 (PDT)
MIME-Version: 1.0
References: <20180719214312.8571CB819EE@rfc-editor.org> <CALaySJJYmREJCwA_xOjtY26qcaX8RVFRXtueMDkCgDEPJzFRPg@mail.gmail.com> <1532039609.216542.1446679184.57EA6E86@webmail.messagingengine.com>
In-Reply-To: <1532039609.216542.1446679184.57EA6E86@webmail.messagingengine.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 19 Jul 2018 18:40:17 -0400
Message-ID: <CALaySJ+q83s3TqAPAW+7qG9sY9LfaGZdxE_wCTn0aaT+_QuAxw@mail.gmail.com>
To: Bron Gondwana <brong@fastmailteam.com>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, aamelnikov@fastmail.fm, adam@nostrum.com, ben@nostrum.com, morg@ietf.org, nicolson@google.com, rg+ietf@qualcomm.com, tss@iki.fi
Content-Type: multipart/alternative; boundary="000000000000a8e4c2057161dd4f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/morg/Gi4d1fc6qaxUYjW5FRCLovCa2Ss>
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:40:31 -0000

Write an update RFC.  Or we’ll put it into rev4.2

On Thu, Jul 19, 2018 at 6:33 PM Bron Gondwana <brong@fastmailteam.com>;
wrote:

> Fair enough! Is there a better way to say "if you're implementing now,
> please do this to get best interop"?
>
>
> On Fri, Jul 20, 2018, at 08:26, Barry Leiba wrote:
>
> > 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/
>
>
> --
>   Bron Gondwana, CEO, FastMail Pty Ltd
>   brong@fastmailteam.com
>
> --
Barry
--
Barry Leiba  (barryleiba@computer.org)
http://internetmessagingtechnology.org/