[Dyncast] Instance Affinity (draft-bormann-dyncast-affinity-00.txt)

[Carsten Bormann <[e-mail]>]

You may not see this because of the I-D frenzy, but I thought I might alert you anyway.  I have written a little draft that proposes a way to obtain service instance affinity without building network state that needs to scale with the number of clients/service invocations.  Feedback would be welcome if you like exploring ideas like this.

Grüße, Carsten


> Name:		draft-bormann-dyncast-affinity
> Revision:	00
> Title:		Providing Instance Affinity in Dyncast
> Document date:	2021-02-22
> Group:		Individual Submission
> Pages:		7
> Status:         https://datatracker.ietf.org/doc/draft-bormann-dyncast-affinity/
> Html:           https://www.ietf.org/archive/id/draft-bormann-dyncast-affinity-00.html
> 
> Abstract:
>   Dyncast support in the network provides a client with a fresh optimal
>   path to a service provider instance, where optimality includes both
>   path and service provider characteristics.  As a service invocation
>   usually takes more than one packet, dyncast needs to provide instance
>   affinity for each service invocation.  Naive implementations of
>   instance affinity require per-application, per service-invocation
>   state in the network.
> 
>   The present short document defines a way to provide instance affinity
>   that does not require, but also does not rule out per-application
>   state.