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

Barry Leiba <barryleiba@computer.org> Fri, 21 December 2018 16:30 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 3C406130E3C for <morg@ietfa.amsl.com>; Fri, 21 Dec 2018 08:30:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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 SFdNBnwiJ6Wq for <morg@ietfa.amsl.com>; Fri, 21 Dec 2018 08:30:34 -0800 (PST)
Received: from mail-it1-f182.google.com (mail-it1-f182.google.com [209.85.166.182]) (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 5FC19130E33 for <morg@ietf.org>; Fri, 21 Dec 2018 08:30:34 -0800 (PST)
Received: by mail-it1-f182.google.com with SMTP id m62so7619666ith.5 for <morg@ietf.org>; Fri, 21 Dec 2018 08:30:34 -0800 (PST)
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:content-transfer-encoding; bh=y21tTsK2cGymCiHjmgoQ+xUU8hd809fDHeOFR+wCDEA=; b=INpl+oB0qo7y/WKsg8WKhTInz43UCntIxc6+kDfd6tFv0Ps+JHdQ/wmd1KEJrTt6yW omB6kPPR9jF+W33In+159pSjxZSyimgc9lY737WZMtTQU0aRvGT5n/XxALLqWDgCbpuA 1eaaNSYJMUAgNABbFdxe+F7wMWRQ43VJIj3U6hcD5rU6X6EhD2g9tG2NY3rmSWLaeFBo RbxslO/KqNsbzFTW8In6HTW7oGcKJUSLlCyuRTYt4Fd1Fr6deUDS9e0O+1UHho19k1rw C79kE+ipxx4hi7kPYjiNBh2PlgeA6BggWhLr+iauLkkUoWkto/XghsESgw8u9b3pWdtk zRDA==
X-Gm-Message-State: AA+aEWZLm+Qiziu9iB6unQkn3KBjzA/mi229X57LgjXkWiWOBzqXPyBl ni2zpXeqs+KSRf6/4CE/pICND0HVrA1XaLOvlTI=
X-Google-Smtp-Source: AFSGD/XdDU5xaG+F071naqbskIvm3c721XWfJQdlLd2mVamVSNsKn1FJ+aQsh/tFUXiWUGyst2kIS4R5xsJt/mNvOy8=
X-Received: by 2002:a24:a04:: with SMTP id 4mr2377208itw.122.1545409833325; Fri, 21 Dec 2018 08:30:33 -0800 (PST)
MIME-Version: 1.0
References: <20181221160018.06A80B81C58@rfc-editor.org> <CALaySJ+q3d+_SQcAVcxTYqc-GxteFO5R+PF+1ETK29m2uERj2A@mail.gmail.com> <CALaySJJ9yQf0dWk_ktcNYOO_phDuSjXwtAAL2Z=VuCiJH+f4kw@mail.gmail.com>
In-Reply-To: <CALaySJJ9yQf0dWk_ktcNYOO_phDuSjXwtAAL2Z=VuCiJH+f4kw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 21 Dec 2018 11:30:22 -0500
Message-ID: <CALaySJLNLR6bj0WCmfobm0zF5TxN9pP+6iWZSEvrqyi14mqvSQ@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: =?UTF-8?B?SmFtaWUgTmljb2xzb24gKOWAquW/l+aYjik=?= <nicolson@google.com>, Ben Campbell <ben@nostrum.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, Adam Roach <adam@nostrum.com>, Timo Sirainen <tss@iki.fi>, contact@emersion.fr, morg <morg@ietf.org>, Randall Gellens <randy@pensive.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/morg/P5-AuduL6ARraC5D3Ssb0IFUgf0>
Subject: Re: [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:30:36 -0000

(Sorry for the noise: one further comment.)
When it's marked "Verified", a comment should be added that it *is* OK
to support special-use without extended list, as specified in the
first paragraph of Section 2, but that the example in 5.2 says it's an
example of use with extended list, so the example is wrong.

Thanks,
Barry

On Fri, Dec 21, 2018 at 11:28 AM Barry Leiba <barryleiba@computer.org>; wrote:
>
> Ah, wait, I see.  The example in Section 5.2 says that it's an example
> of use of extended LIST, but the server doesn't advertise extended
> LIST... that's the problem.  Yes, that's an error in Section 5.2, and
> this report should be marked "Verified".
>
> Barry
>
> On Fri, Dec 21, 2018 at 11:25 AM Barry Leiba <barryleiba@computer.org>; wrote:
> >
> > I believe that Section 2 makes it clear that it works both ways: the
> > first paragraph says how special-use behave with non-extended LIST,
> > and the second paragraph says what it does with extended LIST.
> >
> > Errata reporter, when you re-read those two paragraphs do you still
> > think it's unclear?
> >
> > Barry
> >
> > On Fri, Dec 21, 2018 at 11:00 AM 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/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