FW: New Version Notification for draft-trossen-rtgwg-rosa-01.txt

[Dirk Trossen <[e-mail]>]

All,

After presenting the initial draft on ROSA (routing on service addresses) at the IETF115, we have been working on an update, which you can find below. 

Apart from welcoming additional co-authors (Jens Finkhaeuser, Daniel Huang, and Paulo Mendes), we have been working on several comments we received in discussions with community members (many thanks for those who engaged with us on this topic). 

In more detail, the following changes can be found in the update:
1. Restructured introduction to improve readability and argumentation for this draft
2. Addressing IETF115 comments in various parts of the draft, e.g.,  introduction, analysis (relation to other technologies), traffic steering (relation to anycast) etc
3. Added six new use cases (mobile applications - Section 3.4, chunk  retrieval - Section 3.5, AR/VR - Section 3.6, Cloud-to-Thing - Section 3.7, Metaverse - Section 3.8, and popularity-based services - Section 3.9)
4. Added separate analysis section, as derived from use cases (Section 4)
5. Revised and linked requirements to use cases through additional text (Section 5)
6. Discussed possible benefits from applying ROSA in identified use cases (Section 6)
7. Revised ROSA messages figure (Figure 2) 
8. Added section on possible extended capabilities to 'base' ROSA (Section 8), including multi-homing support, namespace support.
9. Added and maintaining open issues (Section 10)
10.  Added missing sections, like conclusions (Section 11) and privacy  considerations (Section 13)

We would welcome any comments and thoughts on this work, its motivation and argumentation as well as possible ways forward. Any interest for contribution is also very welcome.

We plan on capturing any inputs into a possible update before IETF116 and would very much like to present this work for discussion in the RTGWG when we will meet at IETF116. We are also looking into demonstrating aspects of ROSA at the IETF; happy to receive any interest in such demonstration.

Best,

Dirk

-----Original Message-----
From: [e-mail] <[e-mail]> 
Sent: 02 February 2023 14:27
To: Luis M. Contreras <[e-mail]>; Daniel Huang <[e-mail]>; Dirk Trossen <[e-mail]>; Jens Finkhaeuser <[e-mail]>; Luis Contreras <[e-mail]>; Paulo Mendes <[e-mail]>
Subject: New Version Notification for draft-trossen-rtgwg-rosa-01.txt


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

Name:		draft-trossen-rtgwg-rosa
Revision:	01
Title:		Routing on Service Addresses
Document date:	2023-02-02
Group:		Individual Submission
Pages:		53
URL:            https://www.ietf.org/archive/id/draft-trossen-rtgwg-rosa-01.txt
Status:         https://datatracker.ietf.org/doc/draft-trossen-rtgwg-rosa/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-trossen-rtgwg-rosa
Diff:           https://author-tools.ietf.org/iddiff?url2=draft-trossen-rtgwg-rosa-01

Abstract:
   This document proposes a novel communication approach which reasons
   about WHAT is being communicated (and invoked) instead of WHO is
   communicating.  Such approach is meant to transition away from
   locator-based addressing (and thus routing and forwarding) to an
   addressing scheme where the address semantics relate to services
   being invoked (e.g., for computational processes, and their generated
   information requests and responses).

   The document introduces Routing on Service Addresses (ROSA), as a
   realization of what is referred to as 'service-based routing' (SBR),
   to replace the usual DNS+IP sequence, i.e., the off-path discovery of
   a service name to an IP locator mapping, through an on-path discovery
   with in-band data transfer to a suitable service instance location
   for a selected set of services, not all Internet-based services.

   SBR is designed to be constrained by service-specific parameters that
   go beyond load and latency, as in today's best effort or traffic
   engineering based routing, leading to an approach to steer traffic in
   a service-specific constraint-based manner.

   Particularly, this document outlines sample ROSA use case scenarios,
   requirements for its design, and the ROSA system design itself.

                                                                                  


The IETF Secretariat