Last Call Review of draft-ietf-cbor-edn-literals-09
review-ietf-cbor-edn-literals-09-opsdir-lc-dunbar-2024-06-10-00

Request Review of draft-ietf-cbor-edn-literals
Requested revision No specific revision (document currently at 12)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2024-06-05
Requested 2024-05-22
Authors Carsten Bormann
I-D last updated 2024-06-10
Completed reviews Opsdir Last Call review of -09 by Linda Dunbar (diff)
Genart Last Call review of -09 by Joel M. Halpern (diff)
Secdir Last Call review of -09 by Rifaat Shekh-Yusef (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request Last Call review on draft-ietf-cbor-edn-literals by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/4jOehfEupNe9Fngr62TlexDRU94
Reviewed revision 09 (document currently at 12)
Result Has nits
Completed 2024-06-10
review-ietf-cbor-edn-literals-09-opsdir-lc-dunbar-2024-06-10-00
I have reviewed this document as part of the Ops area directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Ops area directors.
Document editors and WG chairs should treat these comments just like any other
last-call comments.

The document specifies an extension to the CBOR diagnostic notation to include
application-oriented literals for representing date/time and IP
addresses/prefixes. It also defines some additional syntax for handling unknown
application-extension identifiers and elisions (omissions) in the notation. The
document is clear and comprehensive. While the document specifies using tag 999
to represent unknown application-extension identifiers, it does not provide
strict rules on how an EDN consumer should handle such identifiers beyond
preserving the information. It would be nice to have more specific error
handling guidance.

Best regards, Linda Dunbar