Skip to main content

Routing on Service Addresses

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Dirk Trossen , Luis M. Contreras , Jens Finkhäuser , Paulo Mendes
Last updated 2023-02-03
Replaced by draft-mendes-rtgwg-rosa-use-cases, draft-trossen-rtgwg-rosa-arch, draft-contreras-rtgwg-rosa-gaar
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-mendes-rtgwg-rosa-use-cases, draft-contreras-rtgwg-rosa-gaar, draft-trossen-rtgwg-rosa-arch
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:


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.


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.)