Document: draft-ietf-cats-framework Title: A Framework for Computing-Aware Traffic Steering (CATS) Reviewer: Thomas Fossati Review result: 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-cats-framework-?? Reviewer: Thomas Fossati Review Date: 2026-02-23 IETF LC End Date: 2026-03-03 IESG Telechat date: Not scheduled for a telechat Summary: This document is ready for publication as an Informational RFC. It clearly describes the CATS functional components, their interaction and high-level workflows. The terminology section is extensive and clear. The security and privacy considerations are also well written and to the point. The diagrams are very nice and really help the reader grasp and connect the concepts. (I have a few suggestions on how to improve them further, but I could not easily find the repository that hosts the document, so I could not provide the suggestions in the form of a PR.) Major issues: none Minor issues: none Nits/editorial comments: a few, see below. §1 slight reflow: OLD The CATS framework is an overlay framework for the selection of the suitable service contact instances from a set of candidates. NEW The CATS framework is an overlay framework that selects suitable service contact instances from a set of candidates. typo: OLD [...] combination of networking and computing metrics determine NEW [...] combination of networking and computing metrics determines §2 s/decision making/decision-making/ s/as distinct from/as opposed to/ §3.1 s/other than they are reachable/other than that they are reachable/ §3.2 slight reflow: OLD This document does not make any assumption about the structure and semantic of this identifier. An example of such ID is a unicast IP address that uniquely identifies the location of a service instance. NEW This document makes no assumptions about the structure or semantics of this identifier. One example of such an ID is a unicast IP address, which uniquely identifies the location of a service instance. s/deployment specific/deployment-specific/ §3.4.1 s/that run in same/that run in the same/ §3.4.6 s/computing related/computing-related/ §4.3 s/in order to not constrain/so as not to constrain/ s/will be removed and/will be removed, and/ §4.4 s/the flow or packets identification type/the flow or packet identification type/ §5.1 s/Such correlation/Such a correlation/ or s/Such a correlation/This correlation/ §5.2 s/Retrieve active classification table/Retrieve the active classification table/ §5.4 s/this document suggests to implement the normalization function/this document suggests implementing the normalization function/ §6 s/may be modified by an attacker resulting in disrupted service delivery/may be modified by an attacker, resulting in disrupted service delivery §7 s/at the application/protocol level depending/at the application/protocol level, depending/ _______________________________________________ Gen-art mailing list -- [email protected] To unsubscribe send an email to [email protected]
