Skip to main content

IETF Last Call Review of draft-ietf-calext-jscontact-profiles-09
review-ietf-calext-jscontact-profiles-09-genart-lc-sarikaya-2025-11-25-00

Request Review of draft-ietf-calext-jscontact-profiles
Requested revision No specific revision (document currently at 14)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2025-11-25
Requested 2025-11-11
Authors Robert Stepanek , Mario Loffredo
I-D last updated 2026-02-17 (Latest revision 2026-02-17)
Completed reviews Genart IETF Last Call review of -09 by Behcet Sarikaya (diff)
Artart IETF Last Call review of -09 by Paul Kyzivat (diff)
Artart Telechat review of -11 by Paul Kyzivat (diff)
Assignment Reviewer Behcet Sarikaya
State Completed
Request IETF Last Call review on draft-ietf-calext-jscontact-profiles by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/Utjq9CB00UITfWZO0tcjH1OzZj0
Reviewed revision 09 (document currently at 14)
Result Ready w/nits
Completed 2025-11-25
review-ietf-calext-jscontact-profiles-09-genart-lc-sarikaya-2025-11-25-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-calext-jscontact-profiles-09
Reviewer: Behcet Sarikaya
Review Date: 2025-11-25
IETF LC End Date: 2025-11-25
IESG Telechat date: Not scheduled for a telechat

Summary: The document defines JSContact profiles, a method of
JSContact [RFC9553] contact card data model and format subsetting. It is short,
to the point and well-written. It has a few nits listed below. Major issues:None

Minor issues:None

Nits/editorial comments:
idnits tool shows several long lines,
in
Figure 1 there is one long line, the first line

and Table 1, all lines are long.
They can be fixed easily in the revised draft.

idnits also points to two lines with non Ascii characters.
They are on page 8, localizations where a Japanese given name and surname are
given in Kanji characters. So it can be ignored.

page 6.
all IANA-registered Card object properties.

it may be good to clarify which IANA-registry, by adding

Card object is in JSON Contact Properties registry.