Suresh Krishnan has entered the following ballot position for draft-ietf-alto-incr-update-sse-20: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-alto-incr-update-sse/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Section 3.1.1.: I feel strongly that this document should not restate the pseudo-code for the JSON merge patch algorithm and should instead use a reference to Section 2 of RFC7396 instead. This will avoid inconsistencies (e.g. note that the pseudo code in this draft is *already different* from that in RFC7396 even though the difference is only the braces) and be amenable to updates to RFC7396. References: Is there a reason this document is using the obsoleted JSON reference to RFC7159? Suggest updating the reference to RFC8259. _______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
