IETF Logo Mail Archive

Re: [Extra] [Technical Errata Reported] RFC9051 (6826)

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 02 February 2022 11:01 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29B0A3A2E0E for <extra@ietfa.amsl.com>; Wed, 2 Feb 2022 03:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 TgCq5VqaXiPl for <extra@ietfa.amsl.com>; Wed, 2 Feb 2022 03:01:06 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA1B3A2E0F for <extra@ietf.org>; Wed, 2 Feb 2022 03:01:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1643799664; d=isode.com; s=june2016; i=@isode.com; bh=vbb4V+BknFOYwnur5PAVYtmcGA9m6MXxFSNmOEZNH1o=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=DOVECuXGLl80rWixjOPQTffAMiG49Rr/lKa16JtRG3xyuuHTeJ/gbS4gKUxfH15qsgp23G qbEBLVSDsH6L7DbgHitI1rdPwFLYGt8FKJuRREzWhGc23WEYAp9jo0g1UjRovR0o5UjMgy B+Ev0U5lq3fiqbZkAtQO0h+6pzVg3yI=;
Received: from [192.168.1.222] (host31-49-219-0.range31-49.btcentralplus.com [31.49.219.0]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <YfpkbgAyEaat@waldorf.isode.com>; Wed, 2 Feb 2022 11:01:04 +0000
Message-ID: <f3a6edfc-cc3a-5880-db19-6b13f4c06435@isode.com>
Date: Wed, 02 Feb 2022 11:00:56 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
To: RFC Errata System <rfc-editor@rfc-editor.org>, barryleiba@computer.org, superuser@gmail.com, francesca.palombini@ericsson.com, brong@fastmailteam.com, yaojk@cnnic.cn
Cc: extra@ietf.org, hontvari@flyordie.com
References: <20220202080632.AFACDF5CE7@rfc-editor.org>
From: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <20220202080632.AFACDF5CE7@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/XacvvFijpfMryjuew2d3_j8FSXk>
Subject: Re: [Extra] [Technical Errata Reported] RFC9051 (6826)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2022 11:01:12 -0000

I think I would change this to Editorial, because pure IMAP4rev2 clients 
wouldn't use items whether they are marked as deprecated or as removed.

I think "hold for update" is the best disposition for this erratum.

On 02/02/2022 08:06, RFC Errata System wrote:
> The following errata report has been submitted for RFC9051,
> "Internet Message Access Protocol (IMAP) - Version 4rev2".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6826
>
> --------------------------------------
> Type: Technical
> Reported by: Hontvári Levente <hontvari@flyordie.com>
>
> Section: GLOBAL
>
> Original Text
> -------------
>     18.  RFC822, RFC822.HEADER, and RFC822.TEXT FETCH data items were
>          deprecated.  Clients should use the corresponding BODY[]
>          variants instead.
>
> Corrected Text
> --------------
>     18.  RFC822, RFC822.HEADER, and RFC822.TEXT FETCH data items were
>          removed. Clients should use the corresponding BODY[]
>          variants instead.
>
> Notes
> -----
> Contrary to the original text, these data items are not deprecated but they were completely removed from the text of the RFC. As far as I see other deprecated items are not removed completely but moved to a '...obsolete...' token in the formal syntax.
>
> 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.
>
> --------------------------------------
> RFC9051 (draft-ietf-extra-imap4rev2-30)
> --------------------------------------
> Title               : Internet Message Access Protocol (IMAP) - Version 4rev2
> Publication Date    : August 2021
> Author(s)           : A. Melnikov, Ed., B. Leiba, Ed.
> Category            : PROPOSED STANDARD
> Source              : Email mailstore and eXtensions To Revise or Amend
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG
>
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra

v2.23.0 | Report a Bug | By Email