Hi Thomas, Thank you for your review and suggestions, we have merged the text in to the main branch, will release it soon 😊
Cheers, Cheng -----Original Message----- From: Thomas Fossati <[email protected]> Sent: Tuesday, February 24, 2026 10:29 PM To: [email protected] Cc: [email protected]; [email protected]; [email protected]; [email protected] Subject: Re: draft-ietf-cats-framework-19 ietf last call Genart review Thanks for the quick update, Med! And congrats to the editors and WG, this was a very enjoyable read. On Tue, 24 Feb 2026 at 15:17, <[email protected]> wrote: > > Hi Thomas, > > Many thanks for the review. > > These are excellent suggestions. Except very few one, went with almost all > your suggestions as you can see at: > https://github.com/ietf-wg-cats/draft-ietf-cats-framework/pull/153. > > Cheers, > Med (as author) > > PS: rendered diff can be seen here: > https://author-tools.ietf.org/api/iddiff?url_1=https://ietf-wg-cats.gi > thub.io/draft-ietf-cats-framework/draft-ietf-cats-framework.txt&url_2= > https://ietf-wg-cats.github.io/draft-ietf-cats-framework/boucadair-pat > ch-2/draft-ietf-cats-framework.txt > > > -----Message d'origine----- > > De : Thomas Fossati via Datatracker <[email protected]> Envoyé : > > lundi 23 février 2026 14:23 À : [email protected] Cc : [email protected]; > > [email protected]; last- [email protected] Objet : > > draft-ietf-cats-framework-19 ietf last call Genart review > > > > > > 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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > > Fwiki.ietf.org%2Fen%2Fgroup%2Fgen%2FGenArtFAQ&data=05%7C02%7Cmoham > > ed.boucadair%40orange.com%7Cd81e3ba71ed34d9ef26e08de72deb1ba%7C90c > > 7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639074497970414915%7CUnkno > > wn%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiO > > iJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1iU > > O8Y2mYnRLzLi24zgRatdYUxDWthtee2XWSOcQIWU%3D&reserved=0>. > > > > 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/ > > > > > > ______________________________________________________________________ > ______________________________________ > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc pas etre diffuses, > exploites ou copies sans autorisation. Si vous avez recu ce message > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les > pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or > privileged information that may be protected by law; they should not be > distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > _______________________________________________ Gen-art mailing list -- [email protected] To unsubscribe send an email to [email protected]
