[Cats] Re: What's next for CATS? Vienna and beyond

Jing Wang <wangjingjc@chinamobile.com> Mon, 01 June 2026 07:31 UTC

Return-Path: <wangjingjc@chinamobile.com>
X-Original-To: cats@mail2.ietf.org
Delivered-To: cats@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E5D98F88C037; Mon, 1 Jun 2026 00:31:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780299109; bh=sFDWmDQbD2jcS1WRLO59UX3yTbjj3y1WhmENLbYsL8I=; h=Date:From:To:Cc:Subject:References; b=U7Y2A0U8TuJKhVLXTyUtb5WcDtKE2BAlTcrA4EsnbuhrV/7ZceaxbntELWOHxyG1i JzOTs3SbLsKpv89j5gZYDPHEFl0Z8QvnvXZtuLw/gtFzYGQikhBwy6yZNhyCvGibNr BRAjZdbswBOi+SZ2R3wG/B5QkwyrXq/7kYSOAlLk=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.986
X-Spam-Level:
X-Spam-Status: No, score=-0.986 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=chinamobile.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id De8CEeirPYr1; Mon, 1 Jun 2026 00:31:47 -0700 (PDT)
Received: from cmccmta6.chinamobile.com (cmccmta6.chinamobile.com [111.22.67.139]) by mail2.ietf.org (Postfix) with ESMTP id 4BBE1F88C023; Mon, 1 Jun 2026 00:31:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chinamobile.com; s=default; l=0; h=from:subject:message-id:to:cc:mime-version; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=CB52ufJ6mDY4UQYnahf74C3AA7dOh8dAjfHaChe/U/U1wFFJb5fb3zwrepacf+9byK6mgHVCNXrq5 lUP7a8b7U4wsuYkaaXTU2jaHQhbzFt1sg0hzjjBs1ldoNcKYFV6IihliQWslQwyfOlO6152yKDwzkr sOO6cXuNikg5Di4c=
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[10.188.0.87]) by rmmx-syy-dmz-app05-12005 (RichMail) with SMTP id 2ee56a1d355a57d-7b708; Mon, 01 Jun 2026 15:31:38 +0800 (CST)
X-RM-TRANSID: 2ee56a1d355a57d-7b708
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from LAPTOP-5GS3BPC8 (unknown[10.2.147.11]) by rmsmtp-syy-appsvr07-12007 (RichMail) with SMTP id 2ee76a1d3559090-3a0a4; Mon, 01 Jun 2026 15:31:38 +0800 (CST)
X-RM-TRANSID: 2ee76a1d3559090-3a0a4
Date: Mon, 01 Jun 2026 15:31:37 +0800
From: Jing Wang <wangjingjc@chinamobile.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "cats-chairs@ietf.org" <cats-chairs@ietf.org>
References: <048e01dcedc8$09061d30$1b125790$@olddog.co.uk>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.542[cn]
Mime-Version: 1.0
Message-ID: <2026060115294614969713@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart463105437387_=----"
Message-ID-Hash: 4G3HPT447I3GTWSVU5PCK6DFUQZUDZO7
X-Message-ID-Hash: 4G3HPT447I3GTWSVU5PCK6DFUQZUDZO7
X-MailFrom: wangjingjc@chinamobile.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "cats@ietf.org" <cats@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Cats] Re: What's next for CATS? Vienna and beyond
List-Id: "Computing-Aware Traffic Steering (CATS)" <cats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/3QGz1klZlR8qvnLSaZWgZ4L405U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cats>
List-Help: <mailto:cats-request@ietf.org?subject=help>
List-Owner: <mailto:cats-owner@ietf.org>
List-Post: <mailto:cats@ietf.org>
List-Subscribe: <mailto:cats-join@ietf.org>
List-Unsubscribe: <mailto:cats-leave@ietf.org>

Hi Chairs,

Thanks a lot for leading the WG and moving our work ahead.

I’d like to share a few minor comments. Please see below.

Best regards,
Jing

From: Adrian Farrel
Date: 2026-05-27 19:00
To: cats@ietf.org
CC: cats-chairs
Subject: [Cats] What's next for CATS? Vienna and beyond
Hello CATS,
As we start preparations for meeting in Vienna, the chairs have been
considering what is next for the working group.
= Metrics = 
 
We only have one milestone left: "submit metrics to the IESG". That's going
OK, with two new revisions this month - thanks to the authors.
-07 at the start of the month was followed by an email to the list saying
that it was a "first round of revision, trying to address your comments".
-08 a week later contained some more changes of substance, but there wasn't
email to the list.
I have four remaining concerns:
1. Have all outstanding issues been addressed? The authors should be
able to answer this.
2. The Security Considerations section is fairly light. I have
commissioned an "early" SecDir review to help with this.
3. There is no Operational Considerations section (although there are
operational considerations within the document. I have commissioned an
"early" OpsDir review to help with this.
4. There has not been a lot of discussion of the draft on the list? Has
anyone read it in the last 12 months? If not, why not?!
5. There are some new I-Ds around metrics, please also figure out any
points that could help improve the working group documents.
= What is next for the working group? =
Our charter describes some broad areas of work
. Groundwork (problem statement, use cases, requirements). The chairs
think the core documents are complete, but there may be some further
documents that would be useful (see below)
. Cats framework and architecture. The chairs think this is complete
. Applicability of tools and mechanisms. This seems to be an issue
that a lot of people want to talk about. The chairs have tried to keep a
separation between new protocol definitions (don't belong in CATS) and
applicability and gap analysis (do belong in CATS - see below).
There are some additional groundwork I-Ds on security, OAM, data models.
a. draft-wang-cats-security-considerations
b. draft-fu-cats-oam-fw
c. draft-yl-cats-data-model

[Jing] Do we need to specify a YANG model for the northbound interface here?

The chairs believe these are good candidates for adoption by the working
group, but we have seen very little discussion of them on the list. So we
would ask:
. The authors to reintroduce there work, and explain what the status
is and where they need help
. The working group to actively review the drafts and make concrete
suggestions for changes.
If the mailing list shows good progress, we could move straight towards
adoption. Otherwise we will ask the authors to present in Vienna with the
intention of understanding from the room whether there is any interest in
the work.
The chairs also think that two protocol applicability documents are maturing
well.
d. draft-yxl-cats-protocols-applicability
e. draft-dunbar-cats-5g-metadata-applicability

[Jing] Do we need to include an applicability description for the YANG model here?

Again, the level of discussion on the list has not been good, so we would
also ask:
. The authors to reintroduce there work, and explain what the status
is and where they need help
. The working group to actively review the drafts and make concrete
suggestions for changes.
People also seem to be interested in discussing "stretch use cases", but the
chairs think that we need to see CATS working before we get too excited
about specialist applicability.

[Jing] CATS supports potential extended use cases, and we would appreciate your attention to this area.

As usual, the priorities for the agenda in Vienna will be:
. Working group drafts
. Documents the chairs consider in scope and close to ready for
adoption
. I-Ds that have been discussed on the list.
We'd like to remind you that sending a three-line email to the list does not
equate to "discussion," so please try to engage the working group, and
please review each other's drafts.
Thanks,
Peng and Adrian