Document: draft-ietf-ecrit-lost-planned-changes Title: Validation of Locations Around a Planned Change Reviewer: Joel Halpern Review result: Almost Ready
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-ecrit-lost-planned-changes-18 Reviewer: Joel Halpern Review Date: 2026-06-21 IETF LC End Date: 2026-06-30 IESG Telechat date: Not scheduled for a telechat Summary: This document is almost ready for publication as a Proposed Standard Major issues: At the veyr least, the description of the relationship between ChangeSetID and Ordering is confusing. If I have read it right, it is internally inconsistent. At appears to be the itnent that the client can determine from two ChangeSetIds which one is older, And a server can determine from a ChangeSetId what Change Sets are newer than the given one. The latter can in principle be achieved by the server storing and using timestamps locally in addition to the ChangeSetIds. It is possible that the intention is that clients do not determine ordering from the ChangeSetIds, (The middle of the third paragraph of the introduction says "IDs are ordered so that changes can be completed in the correct order.") Minor issues: N/A Nits/editorial comments: N/A _______________________________________________ Gen-art mailing list -- [email protected] To unsubscribe send an email to [email protected]
