Early Review of draft-ietf-rats-corim-09
review-ietf-rats-corim-09-artart-early-salz-2025-12-01-00
| Request | Review of | draft-ietf-rats-corim |
|---|---|---|
| Requested revision | No specific revision (document currently at 09) | |
| Type | Early Review | |
| Team | ART Area Review Team (artart) | |
| Deadline | 2025-11-28 | |
| Requested | 2025-11-06 | |
| Requested by | Deb Cooley | |
| Authors | Henk Birkholz , Thomas Fossati , Yogesh Deshpande , Ned Smith , Wei Pan | |
| I-D last updated | 2025-10-27 (Latest revision 2025-10-20) | |
| Completed reviews |
Artart Early review of -09
by Rich Salz
Opsdir Early review of -09 by Giuseppe Fioccola |
|
| Assignment | Reviewer | Rich Salz |
| State | Completed | |
| Request | Early review on draft-ietf-rats-corim by ART Area Review Team Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/art/GAw7mZifrSjTZeUhn2mWUVVrf1Y | |
| Reviewed revision | 09 | |
| Result | Ready w/nits | |
| Completed | 2025-12-01 |
review-ietf-rats-corim-09-artart-early-salz-2025-12-01-00
I am the ART area reviewer for this document. This review is intended primarily for the ART AD's, and should be treated as any other last-call feedback by everyone else. There is nothing actionable here. This specification uses CDDL, CBOR, CWT, etc. Assuming it uses those properly -- and according to the shepherd writeup[1] it has been reviewed by those groups -- then most of the ART issues are resolved "automatically." It might be that I am not familiar enough with the field to understand all the aspects, but I think this document requires a very careful copy-edit and proofread. For example, Sec 2 talks says it is defining "one possible internal representation"; are others expected? Would the document be more clear if it instead talked solely about the items/factors/inputs to the evaluation? *Why* is an internal model described at all? Another thing is that this could have been split into two documents, with sections 8 and following in a separate document: one describes the data, the second describes the evaluation of the data. Were I on the IESG, I would vote "no objection" if I trusted the shepherd doc, WG chairs, document authors, and the Linux Foundation are right in their conclusion: this is needed. I'm skeptical. [1] https://datatracker.ietf.org/doc/draft-ietf-rats-corim/shepherdwriteup/