RE: New Version Notification for draft-mendes-rtgwg-rosa-use-cases-00.txt

Dirk Trossen <dirk.trossen@huawei.com> Tue, 27 June 2023 07:33 UTC

Return-Path: <dirk.trossen@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27D23C15152D; Tue, 27 Jun 2023 00:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.894
X-Spam-Level:
X-Spam-Status: No, score=-6.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
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 DYPSc4DF0uPo; Tue, 27 Jun 2023 00:33:25 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77E1CC153CBB; Tue, 27 Jun 2023 00:33:25 -0700 (PDT)
Received: from lhrpeml500005.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4QqxFm69PJz6DBSY; Tue, 27 Jun 2023 15:30:36 +0800 (CST)
Received: from lhrpeml500003.china.huawei.com (7.191.162.67) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Tue, 27 Jun 2023 08:33:23 +0100
Received: from lhrpeml500003.china.huawei.com ([7.191.162.67]) by lhrpeml500003.china.huawei.com ([7.191.162.67]) with mapi id 15.01.2507.027; Tue, 27 Jun 2023 08:33:23 +0100
From: Dirk Trossen <dirk.trossen@huawei.com>
To: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, RTGWG <rtgwg@ietf.org>
CC: "rosa@ietf.org" <rosa@ietf.org>
Subject: RE: New Version Notification for draft-mendes-rtgwg-rosa-use-cases-00.txt
Thread-Topic: New Version Notification for draft-mendes-rtgwg-rosa-use-cases-00.txt
Thread-Index: AQHZqDWQ5D12P3gXtUWvVy1EFgXWiK+dHjSwgAA8m4CAAOcKAA==
Date: Tue, 27 Jun 2023 07:33:22 +0000
Message-ID: <ea768bbeb4d84cf2b22e8b7534bd1561@huawei.com>
References: <168778758099.56770.5134833507424431177@ietfa.amsl.com> <596f390455b44df2bdc8943275ef0373@huawei.com> <44C638E5-E211-4039-8688-ACA197D11BB5@cisco.com>
In-Reply-To: <44C638E5-E211-4039-8688-ACA197D11BB5@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.221.98.120]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/Xkjg7j2NEr6k3K0fHnaSorBu8hk>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jun 2023 07:33:30 -0000

Dear all,

This is to announce (to the dedicated ROSA list and the wider RTG WG list) that we have now submitted the gap analysis and requirements as well as the arch draft for ROSA as companion documents to the already submitted use cases and problem statement draft. 

The gap analysis draft includes a more comprehensive analysis of other works compared to the previous standalone draft, including the question that Eric raised in CATS. The drafts are available at

https://datatracker.ietf.org/doc/draft-contreras-rtgwg-rosa-gaar/ 
https://datatracker.ietf.org/doc/draft-trossen-rtgwg-rosa-arch/ 

Any comments and thoughts are welcome on either mailing list; for a wider discussion, using the ROSA list may help limiting traffic on the RTG WG list.

Thanks, 

Dirk (on behalf on the co-authors)

-----Original Message-----
From: Eric Vyncke (evyncke) <evyncke=40cisco.com@dmarc.ietf.org> 
Sent: 26 June 2023 17:43
To: Dirk Trossen <dirk.trossen@huawei.com>; RTGWG <rtgwg@ietf.org>
Subject: Re: New Version Notification for draft-mendes-rtgwg-rosa-use-cases-00.txt

Hello Dirk,

Obviously writing this email without any hat, I did not find any reference to the CATS WG [1] in the ROSA draft. While CATS has already a good direction on what to do, it seems to me that ROSA and CATS are addressing very similar problems.

Do you intend to work within the CATS WG ? Else, what are the big differences ? 

Regards and thanks for educating me,

-éric

[1] https://datatracker.ietf.org/wg/cats/about/


On 26/06/2023, 16:08, "rtgwg on behalf of Dirk Trossen" <rtgwg-bounces@ietf.org <mailto:rtgwg-bounces@ietf.org> on behalf of dirk.trossen=40huawei.com@dmarc.ietf.org <mailto:40huawei.com@dmarc.ietf.org>> wrote:


Dear all,


Please find below the link to our submission of the ROSA use cases and problem statement draft. This draft has been split out of the originally single ROSA draft and is now revised in the use cases and includes, as the title suggests, the suggested problem statement for ROSA, replacing thus the longer draft originally submitted and presented to the RTG WG during IETF115 and 116. 


We plan on submitting the separate gap analysis and requirements as well as the architecture drafts tomorrow.


We would welcome any comments from your side on this update, specifically on the use cases, the observed pain points and derived issues as well as the problem statement. For the discussions around ROSA and its related drafts, a non-WG mailing list at rosa@ietf.org <mailto:rosa@ietf.org> has been established. Please use this list for your comments so as to reduce traffic from the wider RTG WG list. In case you have not yet subscribed to this new list, we'd welcome you doing so!


Looking forward to receiving your comments!


Best,


Dirk (on behalf of the co-authors)


-----Original Message-----
From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>> 
Sent: 26 June 2023 15:53
To: Luis M. Contreras <luismiguel.contrerasmurillo@telefonica.com <mailto:luismiguel.contrerasmurillo@telefonica.com>>; Dirk Trossen <dirk.trossen@huawei.com <mailto:dirk.trossen@huawei.com>>; Jens Finkhaeuser <ietf@interpeer.io <mailto:ietf@interpeer.io>>; Luis Contreras <luismiguel.contrerasmurillo@telefonica.com <mailto:luismiguel.contrerasmurillo@telefonica.com>>; Paulo Mendes <paulo.mendes@airbus.com <mailto:paulo.mendes@airbus.com>>
Subject: New Version Notification for draft-mendes-rtgwg-rosa-use-cases-00.txt




A new version of I-D, draft-mendes-rtgwg-rosa-use-cases-00.txt
has been successfully submitted by Dirk Trossen and posted to the IETF repository.


Name: draft-mendes-rtgwg-rosa-use-cases
Revision: 00
Title: Use Cases and Problem Statement for Routing on Service Addresses
Document date: 2023-06-26
Group: Individual Submission
Pages: 33
URL: https://www.ietf.org/archive/id/draft-mendes-rtgwg-rosa-use-cases-00.txt <https://www.ietf.org/archive/id/draft-mendes-rtgwg-rosa-use-cases-00.txt>
Status: https://datatracker.ietf.org/doc/draft-mendes-rtgwg-rosa-use-cases/ <https://datatracker.ietf.org/doc/draft-mendes-rtgwg-rosa-use-cases/>
Htmlized: https://datatracker.ietf.org/doc/html/draft-mendes-rtgwg-rosa-use-cases <https://datatracker.ietf.org/doc/html/draft-mendes-rtgwg-rosa-use-cases>




Abstract:
The proliferation of virtualization, microservices, and serverless
architectures has made the deployment of services possible in more
than one network location, alongside long practised replication
within single network locations, such as within a CDN datacentre.
This necessitates the potential need to coordinate the steering of
(client-initiated) traffic towards different services and their
deployed instances across the network.


The term 'service-based routing' (SBR) captures the set of mechanisms
for said traffic steering, positioned as an anycast problem, in that
it requires the selection of one of the possibly many choices for
service execution at the very start of a service transaction,
followed by the transfer of packets to that chosen service endpoint.


This document provides typical scenarios for service-based routing,
particularly for which a more dynamic and efficient (in terms of both
latency and signalling overhead) selection of suitable service
execution endpoints would not exhibit the overheads and thus latency
penalties experienced with existing explicit discovery methods.
Related drafts introduce the design for an in-band service discovery
method instead, named Routing on Service Addresses (ROSA), based on
the insights from the use case and problem discussion in this draft.








The IETF Secretariat






_______________________________________________
rtgwg mailing list
rtgwg@ietf.org <mailto:rtgwg@ietf.org>
https://www.ietf.org/mailman/listinfo/rtgwg <https://www.ietf.org/mailman/listinfo/rtgwg>