Architecture for Routing on Service Addresses
draft-trossen-rtgwg-rosa-arch-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dirk Trossen , Luis M. Contreras , Jens Finkhäuser , Paulo Mendes | ||
| Last updated | 2024-01-10 (Latest revision 2023-07-09) | ||
| Replaces | draft-trossen-rtgwg-rosa | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The term 'service-based routing' (SBR) captures the set of mechanisms for the steering of traffic in an application-level service scenario. As in the related use case and gap analysis drafts, we position this steering as an anycast problem, requiring the selection of one of the possibly many choices for service execution at the very start of a service transaction. This document outlines a possible architecture for realizing SBR so as to address the issues identified in the use case and gap analysis companion documents, specifically aiming at the realization of the requirements in the latter document. We outline the architecture, with pointers to possible realizations of the interactions, while also outlining possible extensions to a base SBR capability through a ROSA system as an outlook to possible richer capabilities.
Authors
Dirk Trossen
Luis M. Contreras
Jens Finkhäuser
Paulo Mendes
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)