This document describes the Computing-Aware Traffic Steering (CATS) framework. In particular, it defines the CATS components and the related procedures. I think the document is generally clear and well written.


From an OPSDIR point of view, I think it is good to have a section on "Operational and Manageability Considerations", as also highlighted in draft-opsarea-rfc5706bis. I understand that the specific means are out of scope, but, since NETCONF and IPFIX are mentioned, I would also add the references to RESTCONF and YANG Push, just for completeness.

Regarding the possible deployment scenarios, I would add a pointer to draft-ietf-cats-usecases-requirements, because it reports the CATS use cases.

I suggest to clarify in the text whether the framework covers only the case of single service provider. Otherwise, it would be better to provide some deployment considerations about the case of multiple service providers.


I have additional suggestions for your consideration:

- The client is defined in Section 2 as an endpoint that connects to a service provider network, but later in the text it is mentioned the case of the multi-homed client. Therefore the definition should be reviewed.

- I would add in Section 4 a flow chart to report the sequential steps. They might also be deducted from the text but a diagram would definitely help the reader.

- In Section 4.2, I would split the different metric distribution models (distributed, centralized, hybrid) in separate subsections to improve readability.

- In Section 6 and 7, I would highlight the different security and privacy implications if a single service provider or multiple service providers are involved.