Last Call Review of draft-ietf-extra-jmapaccess-04
review-ietf-extra-jmapaccess-04-genart-lc-sparks-2023-08-22-00

Request Review of draft-ietf-extra-jmapaccess
Requested revision No specific revision (document currently at 09)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2023-08-28
Requested 2023-08-14
Authors Arnt Gulbrandsen , Bron Gondwana
I-D last updated 2025-01-22 (Latest revision 2024-05-15)
Completed reviews Artart IETF Last Call review of -04 by Barry Leiba (diff)
Genart IETF Last Call review of -04 by Robert Sparks (diff)
Secdir IETF Last Call review of -04 by Daniel Migault (diff)
Assignment Reviewer Robert Sparks
State Completed
Request IETF Last Call review on draft-ietf-extra-jmapaccess by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/Eoc7AUXNJwFgSPcQ5TRkXVNp3dc
Reviewed revision 04 (document currently at 09)
Result Ready
Completed 2023-08-22
review-ietf-extra-jmapaccess-04-genart-lc-sparks-2023-08-22-00
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.