IETF Logo Mail Archive

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

Barry Leiba <barryleiba@computer.org> Wed, 02 February 2022 12:51 UTC

Return-Path: <barryleiba@gmail.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 9E32F3A08BC for <extra@ietfa.amsl.com>; Wed, 2 Feb 2022 04:51:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Level:
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 g_M-q4U6tPXd for <extra@ietfa.amsl.com>; Wed, 2 Feb 2022 04:51:44 -0800 (PST)
Received: from mail-ua1-f45.google.com (mail-ua1-f45.google.com [209.85.222.45]) (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 16AAE3A08BF for <extra@ietf.org>; Wed, 2 Feb 2022 04:51:44 -0800 (PST)
Received: by mail-ua1-f45.google.com with SMTP id u76so18909348uau.3 for <extra@ietf.org>; Wed, 02 Feb 2022 04:51:44 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cLzPChOPL0tDywhYZrP85wBffb0e6AO6at30kESxIZo=; b=ny2SvVkVkct0UfQ+zwnHZVw/qPwmm4ykp+S9tjwdCAtj7JeuRJnBWh9M+6dotglXp9 KI0RIA3w8FIGFYKq8w26H1TBOf31y3DiAE49AVOCqntTUextLOAWmd0M9G3miJ2+ve/M VCM2QqK98iNbHIJiBXXHBAXHROjiKmoEhnAoyRjaRSfRGSMTwyRpgCY5uaidbrCZYq6q B83BZW9Oeh1vTbmgWF++ycuOALFjjiowWRaf0ZhZK8qKTzL911kPy5GGIXTKZsHXL5Gw bgcwD7OaPl2ihTy25keAmdSdkX+Jd39S+L4UWFlhuoFsI3Qeh1QzDR03uL+pTV9aQkAX 2FwA==
X-Gm-Message-State: AOAM531Hm5M3Q29bBkSp8MSYUgWRZc/cRUv9ZYLDvxqvrMkbVaoDQqwe 3XCdFKd18q6V2BbUgrUQYD3KheDQyXUd/eAqPfY=
X-Google-Smtp-Source: ABdhPJxCf/cZx86jIOga9Xp0xQ11CURZ0ivRVx07mysaFb7O9wTaNyilMDtqONRP4MQtg22QWlpJK4eMwQXCqx6fs+w=
X-Received: by 2002:a67:fe88:: with SMTP id b8mr7650648vsr.16.1643806302860; Wed, 02 Feb 2022 04:51:42 -0800 (PST)
MIME-Version: 1.0
References: <20220202080632.AFACDF5CE7@rfc-editor.org> <f3a6edfc-cc3a-5880-db19-6b13f4c06435@isode.com>
In-Reply-To: <f3a6edfc-cc3a-5880-db19-6b13f4c06435@isode.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 02 Feb 2022 07:51:31 -0500
Message-ID: <CALaySJLPTExCKwn3KLrmROPyKviR_6SzktyQitiNMO6iORnUXQ@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, brong@fastmailteam.com, extra@ietf.org, francesca.palombini@ericsson.com, hontvari@flyordie.com, superuser@gmail.com, yaojk@cnnic.cn
Content-Type: multipart/alternative; boundary="000000000000c2f77a05d7087aae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/igXeCel-X2ANZ-jcQ-ofI7rTyEo>
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 12:51:49 -0000

I’d actually go with “rejected” rather than HFDU, as it’s saying exactly
what we meant it to say.  But it’s up to Murray.  In any case, definitely
make it editorial.

Barry

On Wed, Feb 2, 2022 at 6:01 AM Alexey Melnikov <alexey.melnikov@isode.com>
wrote:

> 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