[Gen-art] Genart last call review of draft-ietf-extra-jmapaccess-04

Robert Sparks via Datatracker <noreply@ietf.org> Tue, 22 August 2023 19:00 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
Cc: draft-ietf-extra-jmapaccess.all@ietf.org, extra@ietf.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <169273084467.16878.11065354795302493891@ietfa.amsl.com>
Reply-To: Robert Sparks <rjsparks@nostrum.com>
Date: Tue, 22 Aug 2023 12:00:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Eoc7AUXNJwFgSPcQ5TRkXVNp3dc>
Subject: [Gen-art] Genart last call review of draft-ietf-extra-jmapaccess-04

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-extra-jmapaccess-04
Reviewer: Robert Sparks
Review Date: 2023-08-22
IETF LC End Date: 2023-08-28
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as a proposed standard RFC

Nits/editorial comments:

At:
   A few IMAP client maintainers have asked for ways to use features
   that are available in JMAP without having to drop their expensively
   tested IMAP code.

Why does this need to be in the document at all? It will not age well. Consider just removing it.

[Gen-art] Genart last call review of draft-ietf-e… Robert Sparks via Datatracker
Re: [Gen-art] Genart last call review of draft-ie… Arnt Gulbrandsen