[Cats] More on "Service Aware Network"

Adrian Farrel <adrian@olddog.co.uk> Sun, 26 March 2023 05:18 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: cats@ietfa.amsl.com
Delivered-To: cats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FFDBC151B20; Sat, 25 Mar 2023 22:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=olddog.co.uk
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWdfxhlioA2d; Sat, 25 Mar 2023 22:18:33 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C632C15152C; Sat, 25 Mar 2023 22:18:29 -0700 (PDT)
Received: from vs4.iomartmail.com (vs4.iomartmail.com [10.12.10.122]) by mta7.iomartmail.com (8.14.7/8.14.7) with ESMTP id 32Q5II5S021585; Sun, 26 Mar 2023 06:18:18 +0100
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9B4884604A; Sun, 26 Mar 2023 06:18:18 +0100 (BST)
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7A4B946043; Sun, 26 Mar 2023 06:18:18 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs4.iomartmail.com (Postfix) with ESMTPS; Sun, 26 Mar 2023 06:18:18 +0100 (BST)
Received: from LAPTOPK7AS653V (dhcp-8a91.meeting.ietf.org [31.133.138.145]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 32Q5IChT003652 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 26 Mar 2023 06:18:15 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: cats@ietf.org, draft-zhou-intarea-aware-route-san-database@ietf.org
Cc: int-area@ietf.org, 'John Scudder' <jgs@juniper.net>, 'Erik Kline' <ek.ietf@gmail.com>, 'Alvaro Retana' <aretana.ietf@gmail.com>, 'Andrew Alston' <andrew-ietf@liquid.tech>, 'James Guichard' <james.n.guichard@futurewei.com>, "'Eric Vyncke (evyncke)'" <evyncke=40cisco.com@dmarc.ietf.org>
References: <BYAPR15MB23277564F2347BA144996832998A9@BYAPR15MB2327.namprd15.prod.outlook.com> <D3AA531D-D7E2-4E4A-A98C-8EA0DF717BE5@cisco.com> <020601d95f9f$7855ada0$690108e0$@olddog.co.uk>
In-Reply-To: <020601d95f9f$7855ada0$690108e0$@olddog.co.uk>
Date: Sun, 26 Mar 2023 06:18:12 +0100
Organization: Old Dog Consulting
Message-ID: <022501d95fa2$600d3800$2027a800$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0226_01D95FAA.C1D1A000"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdlfolrUAUfTplEcSq+FSqBTQsCeXg==
Content-Language: en-gb
X-Originating-IP: 31.133.138.145
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=Ad2qGNss3MVfI9/KDBWCT wJrKrFKPKivgVMs2wTNUfk=; b=Eey8dA7Uuefs4qP0tO1rs+7ChQBoe9J4A5qBo xod4WkhczUG2hypfryCLv1GPbaDC93swESVQoHWn40VABzOPb/x5a7fbZEI3VjNX l/JAwyiGt/z2XltuJqss2xFRvDUGv6U/ks7sdEWyTRF7MXjMbSbHreBzq9IxWBmq VvCQ2tI+pdlU7alYIltwhnWATVIb6LmYoV2/lKH8Z8JWm0ebou9/6LZsH9cRdAZu UhkqSLST+VToIaNBx4Zu47dsTRgqy+m648hcyPtnNlhcNNk4AxBi4TuPhUa0wkGV fKAWv1gSPjOoj5JDjJKOlP/Uj8jOuR+WPoPVx48OYaloofpTw==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27526.005
X-TM-AS-Result: No--33.216-10.0-31-10
X-imss-scan-details: No--33.216-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27526.005
X-TMASE-Result: 10--33.215600-10.000000
X-TMASE-MatchedRID: A977YP1bixMZnuop9luYIIOlbll4OMtkcNUoZUO46iIR34ro7k23nbEO oitFQVcI4x+3thRT1QYqOIfspaReuE+OlgVjF47vh2VzUlo4HVO2SlZsf8SKLqFIbih0s/42RKL a632yXzQyMp4NsfIcrz/5J8lUk0WLXuSc18ZT1KNM+xVFI1xtY688H8Y4FXgtggrVGi5LBfAn4J kU8L63QdjDEUIxF5uH3cXVpJpf3niAJmQRSVHSt0zs4u81P77p1jd10P+8LE/EU6ZTpNSs1kIjI p4EpSqCabJXSybwaOTmLIcSLXvnl2FojGDB/KT3f2dTnBlY9espA2ExuipmWi196sn93sBvbW/H haSRCatlGOUYHLZgLaSgRjggedCjizpvVZ4uM0y4V0/u9pqUzRtPDNiPbNC65bCHz6fdt0lc3De +KAH8CeD5CIcLwXN69ElewkZ1UERMO/auBcHzXu9VsdrlGzy3Q6/DFZugyt1bYv6Kt+uF2PU72n YVxvYN4D6lW82JZVEb8xI2OD3Z7eyDy8V8lTWUZBiPr4EU8TBRpObkR9DMwkekR3VSvOYV2jgVm hKlDxiqH12uH+NHwvvZiwgq9df702uOaQCpma1sCltwTmzMU5kShYcLpGH95qOldExPCaP6rA5s DO02DFTXEHlJoVbT6JBhFChuHBI4c5PfPWZTthlLm7Fc/E3pBaExZeqJZbLDv5dDcuT2ebvOg8y Bml4YZipMsTQzH+IUAF4uBmvRkR8TzIzimOwPgxsfzkNRlfJoFT3KzpHqE7BnpSKHUIjKn9SenJ q/hy3iRhduhvElsucjNHNZLY/T
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/jTK3y04JUmg9OU3A6-QvxhivrJI>
Subject: [Cats] More on "Service Aware Network"
X-BeenThere: cats@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Computing-Aware Traffic Steering \(CATS\)" <cats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cats>, <mailto:cats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cats/>
List-Post: <mailto:cats@ietf.org>
List-Help: <mailto:cats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cats>, <mailto:cats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Mar 2023 05:18:39 -0000

Further to my previous, I’ve now had a chance to skim https://datatracker.ietf.org/doc/draft-zhou-intarea-aware-route-san-database/

 

It seems to me that this draft is “routing related”, and highly related to CATS. In particular, the overlay of “service routing” with edges and relay nodes is leveraged through knowledge of “compute resource status” injected into the routing overlay network nodes.

 

Many of the issues addressed here seem to be directly overlapping with CATS in terms of what problem is being solved, what metrics need to be advertised, and how the overlay is built. While (obviously) this draft intends to leverage the solution set developed as “SAN”, it would be worthwhile synchronising the use case and problem statement with that in CATS. 

 

One of the jobs of CATS, in the medium term, is to evaluate existing tools and mechanisms to see what can address the CATS problems and where the gaps are. So we would certainly welcome learning more about SAN and the use cases that the authors hope to address.

 

Thanks,

Adrian

 

From: Cats <cats-bounces@ietf.org> On Behalf Of Adrian Farrel
Sent: 26 March 2023 05:57
To: 'Eric Vyncke (evyncke)' <evyncke=40cisco.com@dmarc.ietf.org>; cats@ietf.org
Cc: int-area@ietf.org; 'John Scudder' <jgs@juniper.net>; 'Erik Kline' <ek.ietf@gmail.com>; 'Alvaro Retana' <aretana.ietf@gmail.com>; 'Andrew Alston' <andrew-ietf@liquid.tech>; 'James Guichard' <james.n.guichard@futurewei.com>
Subject: Re: [Cats] FW: [Int-area] Intarea WG agenda

 

Thanks Eric, that’s helpful.

 

The agenda slot is:

Tuesday, March 28, 2023
17:00-18:00 Tuesday Afternoon Session IV 

 

The agenda item and related drafts are as shown below.

 

4. Service aware network (SAN) framework and data plane solutions  - Daniel Huang

draft-huang-intarea-san-framework-00

draft-ma-intarea-identification-header-of-san-00

draft-ma-intarea-encapsulation-of-san-header-00

draft-zhou-intarea-aware-route-san-database-00

draft-zhou-intarea-computing-segment-san-01

    20 mins

 

The work certainly seems related, but a quick reading suggests that the approach chosen is to mark the traffic according to the service and then route according to that marker. This seems (to me) to be closer to APNET proposals (https://datatracker.ietf.org/wg/apn/about/) where a charter is currently being developed and discussed with the IESG.

 

I would certainly encourage the authors with their work, but also I would invite them to try to contribute to existing work efforts and not create new ones where there is overlap.

 

Cheers,

Adrian

 

 

From: Cats <cats-bounces@ietf.org> On Behalf Of Eric Vyncke (evyncke)
Sent: 26 March 2023 05:35
To: cats@ietf.org
Cc: int-area@ietf.org; John Scudder <jgs@juniper.net>; Erik Kline <ek.ietf@gmail.com>; Alvaro Retana <aretana.ietf@gmail.com>; Andrew Alston <andrew-ietf@liquid.tech>; James Guichard <james.n.guichard@futurewei.com>
Subject: [Cats] FW: [Int-area] Intarea WG agenda

 

For information to the CATS WG as the INTAREA WG agenda includes individual drafts about "service aware network" (SAN). At first sight, those SAN drafts look pretty close to the CATS charter.

 

So, feel free to join us in INTAREA WG meeting (or on the mailing list).

 

Regards

 

-éric

 

From: Int-area <int-area-bounces@ietf.org <mailto:int-area-bounces@ietf.org> > on behalf of Wassim Haddad <wassim.haddad=40ericsson.com@dmarc.ietf.org <mailto:wassim.haddad=40ericsson.com@dmarc.ietf.org> >
Date: Sunday, 26 March 2023 at 13:07
To: Internet Area <int-area@ietf.org <mailto:int-area@ietf.org> >
Cc: "intarea-chairs@ietf.org <mailto:intarea-chairs@ietf.org> " <intarea-chairs@ietf.org <mailto:intarea-chairs@ietf.org> >
Subject: [Int-area] Intarea WG agenda

 

Hi,

 

The Intarea WG meeting agenda is available at: https://datatracker.ietf.org/meeting/116/materials/agenda-116-intarea-01

 

Presenters, please upload your slides or send a copy to the chairs.

 

 

Thanks,

Wassim H.