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

Barry Leiba <barryleiba@computer.org> Fri, 21 December 2018 16:28 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 574A5130E3C for <morg@ietfa.amsl.com>; Fri, 21 Dec 2018 08:28:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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, 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 zH4DPimjoEZ2 for <morg@ietfa.amsl.com>; Fri, 21 Dec 2018 08:28:18 -0800 (PST)
Received: from mail-it1-f180.google.com (mail-it1-f180.google.com [209.85.166.180]) (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 48A1C130E33 for <morg@ietf.org>; Fri, 21 Dec 2018 08:28:18 -0800 (PST)
Received: by mail-it1-f180.google.com with SMTP id i145so7612772ita.4 for <morg@ietf.org>; Fri, 21 Dec 2018 08:28:18 -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=3Qnvpl+S1lLpWJiHcKAsLmbrL4Z6oIb3FACLHNeHybw=; b=KVrYMNf1XPhvpOIM/YIkIv0r43XT7PxUPpMejodnE0tg+L6dhrYKVW3/vOuRJGa9AZ XGNpYpnoNJQ/fd9wi0XVC+cUlomMqUvvimRPai0ImPqhOdVjWeFziJhIcDSfkcdk4cr0 wtTM1QDfCjRV2UQL8KFiauXEieaMPTpb3eWinp7hTgnJ/XoIeiW4gtgHcn02Ny2nTh7W mdn/KXsO2OFzmZMpyLd1oQhVjL/fQT7o4JXqbJkQ6epGZ91jsfezpblQFVDt+UdigSTf a/WnSpJ/FJofMO8T5IYncOmg1CPqwKFVg09r67bNe0vqNj684RTzG1FeVwOn4vktZDIX d2oQ==
X-Gm-Message-State: AA+aEWbDGLgRb1Gco0+WbJeXM+FMyAdgUN+3OBV+IYpGFl45maajQGla guyVNCj+uv75y8p7kjPEZvt4Tv22V3p6vFOKNlo=
X-Google-Smtp-Source: AFSGD/WD/riuMwsgzT/eQ7YxRRX5A01QnshIjnfXO8BJ+ROvCGR+LBBDaEzeu+tsG7xcX8A10afmc+1rTUSPz1p/AxA=
X-Received: by 2002:a24:dd8d:: with SMTP id t135mr2263265itf.84.1545409697225; Fri, 21 Dec 2018 08:28:17 -0800 (PST)
MIME-Version: 1.0
References: <20181221160018.06A80B81C58@rfc-editor.org> <CALaySJ+q3d+_SQcAVcxTYqc-GxteFO5R+PF+1ETK29m2uERj2A@mail.gmail.com>
In-Reply-To: <CALaySJ+q3d+_SQcAVcxTYqc-GxteFO5R+PF+1ETK29m2uERj2A@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 21 Dec 2018 11:28:06 -0500
Message-ID: <CALaySJJ9yQf0dWk_ktcNYOO_phDuSjXwtAAL2Z=VuCiJH+f4kw@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/_edlOTkYCWyW5iA2TMdFYkWys3w>
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:28:20 -0000

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