Last Call Review of draft-ietf-jsonpath-base-17
review-ietf-jsonpath-base-17-genart-lc-dunbar-2023-08-10-00

Request Review of draft-ietf-jsonpath-base
Requested revision No specific revision (document currently at 21)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2023-08-09
Requested 2023-07-26
Authors Stefan Gössner , Glyn Normington , Carsten Bormann
I-D last updated 2023-08-10
Completed reviews Secdir Last Call review of -17 by Dan Harkins (diff)
Artart Last Call review of -16 by Darrel Miller (diff)
Genart Last Call review of -17 by Linda Dunbar (diff)
Opsdir Last Call review of -16 by Joe Clarke (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request Last Call review on draft-ietf-jsonpath-base by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/cnQJKq1Dow65ZjgWZxwNUZpVPxE
Reviewed revision 17 (document currently at 21)
Result Not ready
Completed 2023-08-10
review-ietf-jsonpath-base-17-genart-lc-dunbar-2023-08-10-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-jsonpath-base-17
Reviewer: Linda Dunbar
Review Date: 2023-08-10
IETF LC End Date: 2023-08-09
IESG Telechat date: Not scheduled for a telechat

Summary:

The document specifies a method to parse the JSON objects to get values and
specifies the syntax to retrieve a list of values. The document reads well.
However, like any software programs, errors can be encountered at run time even
after careful review.

Major issues:
The major issue is that this document should not be “Standard Track” because:
1.      Existing parsers for JSON data don’t need to change to comply with the
syntax specified in this document. 2.      Like SQL, this document specified
syntax may change as more ways being developed by implementers to parse the
JSON objects. 3.      It is not clear why IANA registration is needed.

Minor issues:

Nits/editorial comments:

Thanks, Linda Dunbar