| Internet-Draft | CATS C-SMA/C-PS Snapshots | November 2026 |
| Zhang, et al. | Expires 22 May 2027 | [Page] |
This document defines a service-metrics snapshot published by a CATS Service Metric Agent (C-SMA) to a CATS Path Selector (C-PS). The snapshot conveys service-metric records and their observation window, together with publication context supporting versioning and the FULL, INVALIDATE, and WITHDRAW operations.¶
The document defines the snapshot contract and two transport modes for the C-SMA-to-C-PS interface: Centralized Mode, using YANG-modeled operational state delivered by gNMI, and Distribution Mode, proposing a BGP-LS service-metadata mapping. The BGP-LS mapping is illustrative until its wire encoding and code points are specified.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 22 May 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Computing-Aware Traffic Steering (CATS) framework [RFC10053] assigns the C-SMA the role of collecting service capabilities and status and advertising CS-IDs with metrics to C-PSes. It allows metrics to be reported per service contact instance, as aggregates, or both. The C-PS uses service information together with network information and local policy to select a destination and path. The CATS data model [I-D.ietf-cats-data-model-00] defines service identifiers and metric-type identities. Neither document defines a common C-SMA-to-C-PS snapshot format or its transport encoding.¶
Independent C-SMA and C-PS implementations need to agree on the identity, scope, metrics, observation context, and lifecycle of each publication, and on how that information is represented by the chosen transport.¶
This document defines the C-SMA-to-C-PS snapshot contract and two transport modes for delivering service-metrics snapshots:¶
Centralized Mode: A C-SMA exposes snapshot state to a C-PS through a direct gNMI subscription. This mode is suitable when a C-PS centrally obtains service information from one or more C-SMAs for path selection.¶
Distribution Mode: A C-SMA distributes snapshot information through BGP-LS so that multiple C-PSes can receive the same service information via the routing control plane. A C-PS may be located at an ingress CATS-Forwarder, but the defining characteristic is distributed dissemination rather than the placement of path computation.¶
This document defines a single abstract service-metrics snapshot model, and specifies the two alternative transport bindings for carrying this snapshot from C-SMA to C-PS. The upstream SCI-to-C-SMA interface is not defined in this document; it is treated as an input source for C-SMA. If C-SMA and C-PS are co-located and built by a single vendor, their interaction is a private internal interface and this specification is not required. Standardization applies only to cross-node, cross-vendor C-SMA -> C-PS interworking.¶
This document contains normative requirements for:¶
Abstract model of the C-SMA service-metrics snapshot, including service-metric records, observation window, publication context, versioning, FULL, INVALIDATE, and WITHDRAW semantics;¶
Rules for identifying successive publications and obtaining a fresh FULL snapshot after synchronization is lost;¶
Two transport modes for the C-SMA-to-C-PS interface:¶
This document explicitly excludes from normative scope:¶
SCI-to-C-SMA metric snapshot format and interaction (referenced from a separate specification);¶
Individual service metric definitions, metric registry entries;¶
Existing CATS YANG configuration and state models beyond the service-metrics snapshot structure;¶
Generic transport protocol characteristics and protocol applicability evaluation;¶
Generic session keepalive, fault detection and link recovery from the CATS OAM framework;¶
Internal C-SMA logic: metric aggregation methods, service selection or nomination algorithms, and caching policies.¶
NOTE: An implementation of C-SMA MAY support one or both transport bindings. A deployment selects one binding according to its control-plane architecture. Mixed bindings in the same control domain are permitted but not required.¶
The two binding modes are distinguished by how snapshot information is delivered from the C-SMA to C-PSes. A common snapshot model enables the same service information and observation context to be conveyed in either mode.¶
Centralized Mode uses a direct subscription-based C-SMA-to-C-PS exchange, whereas Distribution Mode uses routing-protocol dissemination to reach multiple C-PSes. The abstract snapshot semantics are independent of the selected binding.¶
Centralized Mode (Transport Binding 1): A C-PS subscribes directly to YANG-modeled snapshot state exposed by a C-SMA. Binding 1 defines complete snapshot delivery, lifecycle handling, and resynchronization.¶
Distribution Mode (Transport Binding 2): Snapshot content is disseminated to C-PSes through BGP-LS service attributes, reusing the routing control plane's distribution and withdrawal mechanisms. A receiving C-PS may perform selection at an ingress forwarding node or elsewhere.¶
This approach retains one snapshot model while allowing deployments to choose direct collection in Centralized Mode or routing-based dissemination in Distribution Mode.¶
The abstract snapshot model consists of two data parts: service metrics and an observation window. Service metrics follow the service-metric identifiers, attributes, counters, and metric-type/metric-value structure derived from the CATS YANG data model [I-D.ietf-cats-data-model-00]. Individual metric definitions and identities (such as Global Available Slots (GAS) and Computing Time) are defined in those YANG models rather than enumerated individually here. The observation window provides the time context for the reported values. Each publication also carries a snapshot-version field as publication context for the FULL, INVALIDATE, and WITHDRAW operations.¶
| Part | Field / metric | Meaning | YANG representation |
|---|---|---|---|
| Snapshot context | Snapshot version | Monotonically increasing publication generation within the same publisher, publisher epoch, and CS-ID; used to identify FULL snapshots targeted by INVALIDATE. | snapshot-version (uint64) |
| Service metrics | Service metric (metric-type and metric-value) | Service metrics derived from the CATS YANG data model; each entry pairs a metric-type identity with its reported uint32 value. | metrics/metric/metric-type (identityref), metrics/metric/metric-value (uint32, optional) |
| Observation window | Window start | Beginning of the observation interval represented by the snapshot. | window-start (yang:date-and-time) |
| Observation window | Window end | End of the observation interval; later than window-start. | window-end (yang:date-and-time) |
| Observation window | Observation time | Optional per-record timestamp when the observation time differs from the common window end. | observation-time (yang:date-and-time, optional) |
CS-ID and CSCI-ID identify the reported service and contact instance; they are not measurements. All service metrics are represented generically using metric-type and metric-value derived from the CATS YANG data model rather than dedicated leaves. Each metric identity requires a defined interpretation and, where applicable, a unit and scaling rule compatible with uint32. The observation window applies to the complete FULL snapshot; observation-time is optional for a record observed at another instant. Snapshot version is publication context rather than a service metric.¶
Each publication includes publisher-id, publisher-epoch, cs-id, and snapshot-version as publication context. snapshot-version increases for each new event for the same publisher, epoch, and CS-ID. An INVALIDATE event carries invalidated-version to identify a previous FULL snapshot; snapshot-version identifies the INVALIDATE event itself. A receiver MUST ignore an event with an older or duplicate snapshot-version in the same publication scope. The publisher MUST change publisher-epoch after losing version continuity; after an epoch change, a receiver MUST obtain a FULL snapshot before accepting the new publication state.¶
The reporting policy determines when the C-SMA publishes information. The periodic refresh and significant-change triggers described in [I-D.zhangb-cats-service-metrics-op] may be used for this purpose. A threshold-triggered report is a report caused by a change; it does not imply an INCREMENTAL payload. This document defines the publication content and its meaning on the C-SMA-to-C-PS interface, not the threshold values, reporting interval, or local metric cache.¶
A publisher sends a FULL snapshot for each publisher and CS-ID when a C-PS first establishes its view, on a periodic refresh, and after a significant change in reported service metrics. Each FULL snapshot contains the complete current set of service-metric records, including their service identifiers, attributes, metric-type/metric-value entries, and the associated observation window for that publisher and CS-ID. Its version is greater than the preceding version for the same publisher, epoch, and CS-ID. After restart or loss of version state, the publisher changes its epoch and sends a new FULL snapshot. A new FULL snapshot replaces the preceding publication in that scope; the receiver MUST NOT retain metric records omitted from the replacement FULL snapshot.¶
If service capacity or other reported metrics change significantly, including when Global Available Slots (GAS) reaches zero, the publisher sends a new FULL snapshot according to the reporting policy. A change in a service-metric value or the omission of a previously reported service-metric record in a replacement FULL snapshot does not by itself constitute a WITHDRAW of the CS-ID publication.¶
An INVALIDATE signal identifies a previously published FULL snapshot by invalidated-version within its publisher, epoch, and CS-ID scope. It carries no replacement service-metrics data. The receiver MUST NOT invalidate a newer FULL snapshot when invalidated-version refers to an older generation. If invalidated-version matches the current FULL snapshot, the receiver MUST cease using that snapshot until a valid replacement is obtained. A WITHDRAW explicitly removes the current publication for the identified publisher and CS-ID; it does not withdraw an individual metric or CSCI-ID. Both operations are subject to the event ordering rules above. Deletion of a YANG state node and passage of time do not themselves constitute a publisher-issued WITHDRAW. The C-PS decides how to handle stale or absent metric data under local policy.¶
This profile uses complete FULL snapshots for both periodic and change-triggered reporting. It does not define INCREMENTAL payloads. A future extension may add them only with explicit base-version, ordering, and resynchronization rules for each binding.¶
In Centralized Mode, the C-SMA acts as a gNMI target and exposes its service-metrics snapshot state to an authorized C-PS acting as a gNMI client. The interface uses the gNMI Subscribe RPC with TLS protection [GNMI-SPEC]. This binding uses the abstract snapshot semantics and the YANG operational-state schema defined in Section 8.¶
The gNMI target MUST expose a YANG-modeled operational-state subtree keyed by publisher-id and cs-id, containing publication context and the complete current service-metric records and observation window. Section 8 defines this subtree. The canonical path is /cats-ns:nomination-snapshots/nomination-snapshot with publisher-id and cs-id list keys.¶
The C-PS establishes a STREAM subscription to the snapshot state subtree. A target supporting ON_CHANGE for this subtree SHOULD use ON_CHANGE and send updates following each FULL publication. Where ON_CHANGE is not supported, a SAMPLE subscription MAY be used with an operator-selected sample interval. In either mode, the target MUST provide a complete consistent FULL snapshot for each subscribed publisher and CS-ID on initial synchronization and after a change that affects the snapshot. A gNMI Notification may contain multiple Update messages; the receiver MUST NOT treat an arbitrary individual Update as a complete snapshot unless the encoding explicitly identifies the complete publication boundary.¶
The snapshot context includes publisher-id, publisher-epoch, cs-id, and snapshot-version. For the same publisher, epoch, and CS-ID, a higher-version FULL publication replaces the previous publication, including its complete service-metrics records and observation window. An omitted record in the replacement FULL snapshot is removed from the receiver's current view; this is not a WITHDRAW of the entire CS-ID publication. INVALIDATE and WITHDRAW MUST be represented as explicit lifecycle events with their scope and, for INVALIDATE, the targeted version; a gNMI Delete operation on a state path alone does not establish the abstract WITHDRAW semantics. The operational-state schema defines explicit invalidated-version and withdrawn cases. The target MUST send the complete list entry as one JSON_IETF-valued gNMI Update at the keyed entry path, not as independently consumable leaf updates; receivers MUST apply it atomically. This is a binding requirement, not a guarantee provided by gNMI for arbitrary multi-update Notifications.¶
If a subscription is interrupted, an update is missed, or a complete publication cannot be reconstructed, the C-PS MUST resubscribe and obtain a new complete FULL snapshot before treating subsequent data as synchronized. The C-SMA changes its publisher epoch if restart loses version continuity. Reporting triggers follow [I-D.zhangb-cats-service-metrics-op]; this document does not prescribe thresholds or sampling intervals.¶
gNMI subscription synchronization establishes the transport's initial state view; it does not supersede the snapshot's publisher-epoch and snapshot-version ordering rules. The C-PS MUST validate these fields when accepting a publication and MUST NOT merge fields from different versions, including across subscription reconnection.¶
In Distribution Mode, this section proposes a BGP-LS mapping for disseminating snapshot information from a C-SMA to C-PSes through the routing control plane. The exact NLRI, TLV definitions, field mapping, and code-point allocations remain to be specified. Appendix A illustrates the intended deployment without defining a wire encoding.¶
This proposed profile is limited to a service whose CS-ID maps unambiguously to one service prefix and for which one authorized publisher owns that prefix advertisement in the distribution domain. A future BGP-LS encoding could use the corresponding Prefix NLRI and associate a service-metadata TLV in the BGP-LS Attribute. Its CATS-specific sub-TLVs would carry Snapshot Context (publisher identity, epoch, CS-ID, event version and operation), Observation Window, and repeated Service-Metric records (CSCI-ID, source type, attributes, metrics and counters). INVALIDATE also needs invalidated-version. The exact NLRI-to-CS-ID mapping, TLV and sub-TLV types, lengths, cardinality, duplicate handling, and code points require separate specification and IDR coordination.¶
In a future encoding, a replacement advertisement would carry a complete current FULL snapshot; a changed metric value or omitted metric record would not itself withdraw the NLRI. INVALIDATE would require an explicit operation indication with its invalidated-version without withdrawing the associated NLRI. WITHDRAW would remove the publication, provided that the association of the BGP withdrawal with the publisher and CS-ID is unambiguous. The current document does not specify a deployable interoperable wire encoding or claim that every BGP UPDATE has snapshot-atomicity semantics [I-D.zhangb-cats-service-metrics-op]; a threshold-triggered report is still encoded as a FULL snapshot. A changed service-metric value or a changed set of service-metric records is represented in a replacement FULL snapshot and does not withdraw the NLRI. To signal INVALIDATE while retaining the NLRI, the future Snapshot Context sub-TLV needs an explicit invalid indication and the targeted version. WITHDRAW removes the whole publication by withdrawing the NLRI. The encoding must make the publisher and CS-ID scope of that withdrawal unambiguous.¶
A receiver joining or restarting could obtain the latest complete FULL advertisement after synchronization, rather than reconstructing earlier deltas. This document does not map INCREMENTAL payloads into BGP UPDATEs. It defines neither a new BGP session behavior nor an address family. Appendix A illustrates the restricted prefix-addressable case; general CS-ID and multi-publisher cases need further identification and withdrawal rules.¶
This section defines the normative YANG 1.1 [RFC7950] module ietf-cats-nomination-snapshot for C-SMA-to-C-PS service-metrics snapshots. The module exposes read-only operational state under /cats-ns:nomination-snapshots/nomination-snapshot keyed by publisher-id and cs-id.¶
To avoid schema duplication, the module directly reuses service-metric attributes and the metric-type/metric-value structure from the CATS YANG data model ietf-cats [I-D.ietf-cats-data-model-00], augmenting each service-metric record with a per-record observation-time and pairing the list with a shared snapshot observation window (window-start and window-end) and explicit lifecycle operations (full, invalidate, and withdraw). It also imports ietf-yang-types [RFC9911] for yang:uuid and yang:date-and-time.¶
The following tree diagram (per [RFC8340]) illustrates the structure of the ietf-cats-nomination-snapshot module:¶
module: ietf-cats-nomination-snapshot
+--ro nomination-snapshots
+--ro nomination-snapshot* [publisher-id]
+--ro publisher-id string
+--ro publisher-epoch yang:uuid
+--ro snapshot-version uint64
+--ro (publication-content)
+--:(full)
| +--ro full-snapshot!
| +--ro window-start yang:date-and-time
| +--ro window-end yang:date-and-time
| +--rw service-metrics
| +--rw service-metric* [cs-id csci-id source-type]
| +--rw cs-id cs-id
| +--rw csci-id csci-id
| +--rw source-type identityref
| +--rw priority? uint8
| +--rw affinity? uint8
| +--rw location? inet:ip-address
| +--rw metrics
| | +--rw metric* [metric-type]
| | +--rw metric-type identityref
| | +--rw metric-value? uint32
| +--ro forwarded-packets? yang:zero-based-counter64
| +--ro forwarded-bytes? yang:zero-based-counter64
+--:(invalidate)
| +--ro invalidated-version uint64
+--:(withdraw)
+--ro withdrawn? empty
¶
module ietf-cats-nomination-snapshot {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-cats-nomination-snapshot";
prefix cats-ns;
import ietf-yang-types {
prefix yang;
reference "RFC 9911: Common YANG Data Types";
}
import ietf-cats {
prefix cats;
reference
"draft-ietf-cats-data-model-00: Data Model for Computing-Aware
Traffic Steering (CATS)";
}
organization "IETF CATS Working Group";
contact "WG mailing list: cats@ietf.org";
description
"C-SMA to C-PS service-metrics snapshot operational state.
Service identifiers, attributes, metrics, and counters are
reused directly from the ietf-cats data model.";
revision 2026-11-18 {
description
"Simplified operational-state snapshot model keyed by
publisher-id and reusing cats:service-metrics.";
}
container nomination-snapshots {
config false;
description
"Read-only C-SMA publication state for gNMI Subscribe or
YANG-Push datastore subscriptions.";
list nomination-snapshot {
key "publisher-id";
description
"Latest complete publication or explicit lifecycle event
for a publisher. The entire list entry is retrieved as
one atomic JSON_IETF update.";
leaf publisher-id {
type string {
length "1..max";
}
description "Identity of the publishing C-SMA.";
}
leaf publisher-epoch {
type yang:uuid;
mandatory true;
description "Publisher generation identifier.";
}
leaf snapshot-version {
type uint64;
mandatory true;
description "Monotonically increasing event version in scope.";
}
choice publication-content {
mandatory true;
description "Explicit current publication or lifecycle event.";
case full {
container full-snapshot {
presence "Complete published snapshot is available.";
description
"Service metrics and observation window of a FULL
snapshot.";
leaf window-start {
type yang:date-and-time;
mandatory true;
description "Start of the aggregate observation window.";
}
leaf window-end {
type yang:date-and-time;
mandatory true;
description
"End of the aggregate observation window, later than
window-start.";
}
uses cats:service-metrics;
}
}
case invalidate {
leaf invalidated-version {
type uint64;
mandatory true;
description "Version explicitly invalidated.";
}
}
case withdraw {
leaf withdrawn {
type empty;
description "Explicit withdrawal of this publication.";
}
}
}
}
}
}
¶
Service-metrics snapshots can influence traffic steering and must be protected against forgery, unauthorized publication, replay, and stale observations. Implementations MUST authenticate and authorize publishers and receivers and MUST protect publication integrity. Receivers MUST check publisher-epoch and snapshot-version when processing FULL, INVALIDATE, and WITHDRAW, and SHOULD reject metrics whose observation window is outside locally configured freshness bounds.¶
gNMI transport: authenticate and authorize the C-SMA target and C-PS client, protect the gRPC exchange using TLS, and restrict Subscribe access to the intended snapshot paths;¶
BGP-LS transport: distribution must be restricted to authorized CATS nodes and the intended administrative domain. The final BGP-LS encoding must identify mechanisms for publisher authentication, integrity, confidentiality, and freshness; TCP-AO or BGPsec alone does not provide all of these properties.¶
The YANG namespace and module name in Section 8 require registration if this document advances. The gNMI operational-state schema and paths are defined in Section 8. The proposed BGP-LS mapping requires TLV and sub-TLV assignments only after its encoding is specified and reviewed with IDR. No BGP-LS code points are requested by this version.¶
This appendix is informative. It illustrates a possible mapping for a service whose CS-ID is unambiguously associated with an IP prefix. The names and values below are examples; no NLRI, TLV, sub-TLV, or code point is allocated by this appendix.¶
Suppose CS-ID 42 is associated with service prefix 2001:db8:42::/48. C-SMA csma-1 publishes a FULL snapshot for CSCI-IDs 101 and 102, each with a source-type and metric entries. For example, CSCI-ID 101 could report Global Available Slots (GAS) of 20 available slots and a Computing Time of 15 milliseconds, while CSCI-ID 102 reports GAS of 8 available slots and a Computing Time of 30 milliseconds, observed during 2026-10-23T09:59:00Z to 2026-10-23T10:00:00Z. The publication carries publisher-epoch and snapshot-version 7.¶
For this prefix-addressable case, a future BGP-LS binding could associate a Prefix NLRI for 2001:db8:42::/48 with service metadata containing Snapshot Context, Observation Window, and Service-Metric records for CSCI-IDs 101 and 102. The example does not assign TLV types, metric-type identities, or code points. The service prefix identifies CS-ID 42 only where the association is configured or otherwise specified unambiguously.¶
If the available slots (GAS) for CSCI-ID 102 fall from 8 to 0 and its Computing Time increases to 100 milliseconds, csma-1 can publish a later FULL snapshot, version 8, with the changed values and a newer observation window. That replacement does not withdraw the service prefix or an individual metric. INVALIDATE may target version 8 without invalidating a later FULL; WITHDRAW removes the complete publication in the specified publisher and CS-ID scope.¶
Authorized BGP-LS distribution delivers the advertised service information to C-PSes. An interoperable binding must define the exact wire representation, bounds, validation, operation encoding, and treatment of NLRI ownership before this example can be deployed.¶
As an alternative to gNMI in Centralized Mode, a C-SMA MAY expose the /cats-ns:nomination-snapshots/nomination-snapshot operational-state subtree from Section 8 via YANG-Push datastore subscriptions [RFC8641] over RESTCONF and HTTPS [RFC8040]. A C-PS establishes a dynamic subscription using [RFC8639] and [RFC8650] targeting the operational datastore path /cats-ns:nomination-snapshots, obtains the subscription URI, and receives push-update or push-change-update notifications over a server-sent event stream. Only authorized C-PS clients may access the stream.¶
The C-SMA sends a complete snapshot entry for each CS-ID on initial synchronization (push-update) and on periodic or significant-change triggers (push-change-update). A higher-version FULL snapshot replaces the previous publication in the same publisher, epoch, and CS-ID scope. INVALIDATE identifies an invalid version via invalidated-version, while WITHDRAW explicitly marks the publication as withdrawn for the CS-ID. A change or omission of a metric record in a later FULL publication is not a WITHDRAW. After stream interruption or suspected event loss, the C-PS establishes a new subscription and reconstructs its view from fresh FULL snapshot state.¶
This appendix describes a potential alternative and does not alter the primary gNMI binding in the body of this document.¶
This section illustrates the JSON encoding of a YANG-Push push-update notification [RFC8641] carrying the nomination-snapshot operational-state entry from Section 8 when delivered over the optional HTTPS/RESTCONF binding. The RESTCONF event stream adds the data: prefix and event framing described in [RFC8040], and JSON member names and values follow [RFC7951]. These examples illustrate the optional RESTCONF binding and introduce no additional fields or update semantics.¶
The following push-update delivers version 7 for CS-ID 42 with one service-metric record for CSCI-ID 101 and an observation window. The example uses existing source-type-static along with illustrative GAS (20 available slots) and Computing Time (15 milliseconds) metric entries derived from the CATS data model. Numeric uint64 values follow the RFC 7951 string representation.¶
{
"ietf-restconf:notification": {
"eventTime": "2026-10-23T10:00:01Z",
"ietf-yang-push:push-update": {
"id": 101,
"datastore-contents": {
"ietf-cats-nomination-snapshot:nomination-snapshots": {
"nomination-snapshot": [
{
"publisher-id": "csma-1",
"publisher-epoch": "f81d4fae-7dec-11d0-a765-00a0c91e6bf6",
"snapshot-version": "7",
"full-snapshot": {
"window-start": "2026-10-23T09:59:00Z",
"window-end": "2026-10-23T10:00:00Z",
"service-metrics": {
"service-metric": [
{
"cs-id": 42,
"csci-id": 101,
"source-type": "ietf-cats:source-type-static",
"metrics": {
"metric": [
{
"metric-type": "ietf-cats:metric-gas",
"metric-value": 20
},
{
"metric-type": "ietf-cats:metric-computing-time",
"metric-value": 15
}
]
}
}
]
}
}
}
]
}
}
}
}
}
¶
The authors thank the CATS working group for their valuable feedback and contributions to this document.¶