Thanks for your interest, Satoru. In service segmentation use-cases, Cats-mup enables mobile systems such as 5G to route a service request to an optimal combination of service subtasks determined by CATS via SRv6 underlay infrastructure. For example, AR service is segmented into a sequence of Render and Decode subtasks. CATS determines optimal Render instance at Site A, and optimal Decode instance at Site B. CATS-MUP can send this route to PE and convert it to a corresponding routing segment list that goes through A then B then back to UE,
Best regards, Minh-Ngoc On Thu, Mar 27, 2025 at 9:30 PM Satoru Matsushima < [email protected]> wrote: > No problem Minh-Ngoc, FWIW can you explain a little bit about how your > cats-mup connect to? > > Cheers, > --satoru > > On Tue, Mar 25, 2025 at 12:17 PM Minh Ngoc Tran < > [email protected]> wrote: > >> I'm Sorry for sending to the wrong WG mailing list. This is supposed to >> send to CATS WG. >> Please ignore the email. >> >> Thank you, >> Minh-Ngoc >> >> On Tue, Mar 25, 2025 at 8:14 PM Minh Ngoc Tran < >> [email protected]> wrote: >> >>> Hi CATS WG, >>> >>> Following the comments about the presentation from the IETF 122 meeting, >>> This is the updated version of the document "Additional CATS requirements >>> for Service Segmentation-related use cases". >>> https://datatracker.ietf.org/doc/draft-dcn-cats-req-service-segmentation/ >>> In short, this updated version discuss: >>> >>> *1. Service Segmentation characteristics:* >>> - Service is segmented into multiple smaller subtasks. >>> - Subtasks also have multiple instances. >>> - Subtasks are transparent to users. Suppose users request the >>> original service via its service ID. Traffic steering to subtasks is >>> handled by CATS system >>> >>> *2. Differences that Service Segmentation cause to the CATS system >>> (Detailed in Section 3)* >>> - Normal CATS: Request is served by a single optimal service instance >>> - Service Segmentation CATS: Request is served by the result combination >>> of these subtasks. An optimal subtask combination includes one optimal >>> instance of each subtask >>> >>> *3. Possible CATS requirements caused by these differences: (Detailed in >>> Section 4)* >>> - R1: A CATS system should provide a method to distinguish different >>> CATS candidate paths >>> corresponding to different service subtask instance combinations. >>> - R2: A CATS system should provide a method to deliver the service >>> request to the determined >>> optimal service subtask instance combination in correct order and >>> correct composition. >>> - R3: A CATS system should provide a method to map the service request >>> to corresponding >>> segmented subtasks if the original service is not existed, only subtask >>> instance endpoints are >>> available. >>> >>> *These Differences and Requirements are explained by 2 examples in >>> Section 5 where Service Segmentation is applied in 2 CATS use cases: AR and >>> Federated Learning model training* >>> >>> We're looking forward to your feedback! >>> >>> Best regards, >>> Minh-Ngoc >>> >>> ---------- Forwarded message --------- >>> From: <[email protected]> >>> Date: Tue, Mar 25, 2025 at 8:11 PM >>> Subject: New Version Notification for >>> draft-dcn-cats-req-service-segmentation-01.txt >>> To: Minh-Ngoc Tran <[email protected]>, Younghan Kim < >>> [email protected]> >>> >>> >>> A new version of Internet-Draft >>> draft-dcn-cats-req-service-segmentation-01.txt >>> has been successfully submitted by Minh-Ngoc Tran and posted to the >>> IETF repository. >>> >>> Name: draft-dcn-cats-req-service-segmentation >>> Revision: 01 >>> Title: Additional CATS requirements consideration for Service >>> Segmentation-related use cases >>> Date: 2025-03-25 >>> Group: Individual Submission >>> Pages: 12 >>> URL: >>> https://www.ietf.org/archive/id/draft-dcn-cats-req-service-segmentation-01.txt >>> Status: >>> https://datatracker.ietf.org/doc/draft-dcn-cats-req-service-segmentation/ >>> HTML: >>> https://www.ietf.org/archive/id/draft-dcn-cats-req-service-segmentation-01.html >>> HTMLized: >>> https://datatracker.ietf.org/doc/html/draft-dcn-cats-req-service-segmentation >>> Diff: >>> https://author-tools.ietf.org/iddiff?url2=draft-dcn-cats-req-service-segmentation-01 >>> >>> Abstract: >>> >>> This document discusses possible additional CATS requirements when >>> considering service segmentation in related CATS use cases such as >>> AR-VR and Distributed AI Training >>> >>> >>> >>> The IETF Secretariat >>> >>> >>> >>> >>> -- >>> >>> __________________________________ >>> >>> *Minh-Ngoc Tran* >>> >>> IISTRC - Internet Infra System Technology Research Center >>> >>> 369, Sangdo-ro, Dongjak-gu, Seoul, Republic of Korea, 06978 >>> Tel : +82-2-820-0841 >>> >>> Email: [email protected] >>> >>> __________________________________ >>> >> >> >> -- >> >> __________________________________ >> >> *Minh-Ngoc Tran* >> >> IISTRC - Internet Infra System Technology Research Center >> >> 369, Sangdo-ro, Dongjak-gu, Seoul, Republic of Korea, 06978 >> Tel : +82-2-820-0841 >> >> Email: [email protected] >> >> __________________________________ >> _______________________________________________ >> dmm mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> > -- __________________________________ *Minh-Ngoc Tran* IISTRC - Internet Infra System Technology Research Center 369, Sangdo-ro, Dongjak-gu, Seoul, Republic of Korea, 06978 Tel : +82-2-820-0841 Email: [email protected] __________________________________
_______________________________________________ dmm mailing list -- [email protected] To unsubscribe send an email to [email protected]
