[Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap-list-metadata-04: (with COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Tue, 02 April 2024 23:56 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F701C14F6A5; Tue, 2 Apr 2024 16:56:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-extra-imap-list-metadata@ietf.org, extra-chairs@ietf.org, extra@ietf.org, arnt.gulbrandsen@icann.org, arnt.gulbrandsen@icann.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <171210216510.12233.11260607921485116549@ietfa.amsl.com>
Date: Tue, 02 Apr 2024 16:56:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/0b1M9N_3RucDI1J0A1ZKQTaNEDQ>
Subject: [Extra] Roman Danyliw's No Objection on draft-ietf-extra-imap-list-metadata-04: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 02 Apr 2024 23:56:05 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-extra-imap-list-metadata-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-extra-imap-list-metadata/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you to Behcet Sarikaya for the GENART review.

** Section 8.1.  Nit.
   This document defines the "LIST-METADATA" IMAP capability to be added
   to the registry defined in Section 12.1 of [RFC9051].

Section 12.1 of RFC9051 didn’t define the “IMAP Capabilities” registry, it only
updated it.  RFC3501 created it.  For clarity, name the registry this
capability is being added to, “IMAP Capabilities”, and say that the reference
column should be this document.

** Section 8.2
   This section registers the "METADATA" option to be added to the
   registry defined in Section 9 of [RFC5258].

Section 9 of RFC5282 defines two registries.  Please be explicit on which one. 
 Based on the template used, it appears to be “LIST-EXTENDED Options”
(https://www.iana.org/assignments/imap-list-extended/imap-list-extended.xhtml#imap-list-extended-1)