@techreport{mo-cats-agent-state-affinity-00,
    number =    {draft-mo-cats-agent-state-affinity-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-mo-cats-agent-state-affinity/00/},
    author =    {Yijun Mo and Dewei Yang and 周诚宇},
    title =     {{State, Storage, and Compute Affinity for AI Agent Service Selection in Computing-Aware Traffic Steering}},
    pagetotal = 48,
    year =      2026,
    month =     oct,
    day =       5,
    abstract =  {AI agent services are stateful and long-running: the speed with which a step can be served depends on whether the session's context, retrieved data, tool results, and model-side state such as a key-value (KV) cache are already available at, or near, the selected service contact instance, and on whether the computation that the step needs is ready there. Computing-Aware Traffic Steering (CATS) exposes computing and network metrics and defines service contact instance affinity, but it does not expose the availability of reusable state, does not distinguish a hard locality constraint on state from a preference for reusing it, does not provide a way to compare the cost of moving state with the cost of recomputing it, and does not represent the readiness of a specific computation. This document describes affinity in three coupled dimensions -- state, storage, and compute -- for agent service selection. It states the motivation and the goals of introducing affinity, the requirements and constraints that affinity places on the mapping of an agent workload onto storage and compute resources, the metrics and measurement methods by which affinity is observed, the mechanisms and the procedure by which affinity is assured, and two cases in detail: a long-horizon session that passes through several stages, and a group of similar agents or of tenants served by shared reusable state. This document defines no wire protocol, no encoding, and no data model, and it does not define the transfer mechanisms themselves.},
}