Linda, Indeed, both words, "almost" and "DNS", are correct: As for "DNS, the initial service request is akin to a DNS query, resulting in a locator of the service instance being provided in the service response.
As for "almost", the differences lie: 1. in the obvious 'place' where this is done, i.e., at L3.5, which is motivated by the following items 2. the in-band nature of the resolution, i.e., the service request already carries data payload (since we are using an L3.5) of transport and above, thus the service response may also carry suitable response data - this cuts latency even further 3. the decision logic to map service address to service instance, either by - a converged routing state based decision (using, e.g., Sobrinho's multi-optimality routing, you can do service-specific partial linear order based decisions, using a simple overlay DV protocol) - a runtime scheduling decision, where the service request is distributed according to a secondary forwarding decision, selecting one of the possibly several possible instances (that decision may be random, which may suffice in scenarios where instances are of equal capability, round robin or others) Item 3 aims at the dynamicity of the decision that the draft outlines as one of the motivations. I hope this explains. Best, Dirk -----Original Message----- From: rtgwg <[email protected]> On Behalf Of Linda Dunbar Sent: 02 February 2023 21:14 To: Dirk Trossen <[email protected]>; [email protected] Subject: RE: New Version Notification for draft-trossen-rtgwg-rosa-01.txt Dirk, Your proposed ROSA is almost like distributed DNS. - the initial IP packet sent to Shim Overlay routers by the client is like DNS query to the distributed mini DNS servers - the Shim Overlay routers (or the mini DNS servers) sent back the actual destination address for the chosen service - .. Did I understand your Rosa correctly? Linda -----Original Message----- From: rtgwg <[email protected]> On Behalf Of Dirk Trossen Sent: Thursday, February 2, 2023 7:35 AM To: [email protected] Subject: FW: New Version Notification for draft-trossen-rtgwg-rosa-01.txt 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: [email protected] <[email protected]> Sent: 02 February 2023 14:27 To: Luis M. Contreras <[email protected]>; Daniel Huang <[email protected]>; Dirk Trossen <[email protected]>; Jens Finkhaeuser <[email protected]>; Luis Contreras <[email protected]>; Paulo Mendes <[email protected]> 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-trossen-rtgwg-rosa-01.txt&data=05%7C01%7Clinda.dunbar%40futurewei.com%7C3b82001c29e24b64f3b708db052246fa%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638109417031511229%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uL107dO4eLNaQ10%2F6C2nec62Z1YTHvwVazJEny4Lmow%3D&reserved=0 Status: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-trossen-rtgwg-rosa%2F&data=05%7C01%7Clinda.dunbar%40futurewei.com%7C3b82001c29e24b64f3b708db052246fa%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638109417031511229%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7jkDb1DToDqkaNG9TNuaF85t6XmuGMZ01GBJmJcHK84%3D&reserved=0 Htmlized: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-trossen-rtgwg-rosa&data=05%7C01%7Clinda.dunbar%40futurewei.com%7C3b82001c29e24b64f3b708db052246fa%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638109417031511229%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=IfFjL6gih2VkJahaU0VBrwok%2F%2B9qg6slAwoexWQzGTg%3D&reserved=0 Diff: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-trossen-rtgwg-rosa-01&data=05%7C01%7Clinda.dunbar%40futurewei.com%7C3b82001c29e24b64f3b708db052246fa%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638109417031511229%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TlGFjoDfvwGKJwQjG7hCo35rdaZhe7fMWv6XdhjzCqE%3D&reserved=0 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 _______________________________________________ rtgwg mailing list [email protected] https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Frtgwg&data=05%7C01%7Clinda.dunbar%40futurewei.com%7C3b82001c29e24b64f3b708db052246fa%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638109417031666884%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=v%2BsvMqKrrZIF%2BDfqp%2Fa92AnbmX4S31YM0ILWs4Y%2BLAw%3D&reserved=0 _______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg _______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
