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

Carsten Bormann <cabo@tzi.org> Mon, 22 February 2021 22:28 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: dyncast@ietfa.amsl.com
Delivered-To: dyncast@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD3863A210C for <dyncast@ietfa.amsl.com>; Mon, 22 Feb 2021 14:28:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KMos7s6q2Qjp for <dyncast@ietfa.amsl.com>; Mon, 22 Feb 2021 14:28:22 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E5E63A2104 for <dyncast@ietf.org>; Mon, 22 Feb 2021 14:28:21 -0800 (PST)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DkxfC3k7kzyVf; Mon, 22 Feb 2021 23:28:19 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 22 Feb 2021 23:28:19 +0100
X-Mao-Original-Outgoing-Id: 635725699.026517-e1cba2caf047d1f66a269a6c3028943d
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3F5A2A1-1CAD-4F3D-8822-A29769B5F661@tzi.org>
References: <161401620630.26161.6573331426093772450@ietfa.amsl.com>
To: dyncast@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/R6xaykg3bJr_OFBnvTTm3xDGN2c>
Subject: [Dyncast] Instance Affinity (draft-bormann-dyncast-affinity-00.txt)
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dyncast.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dyncast>, <mailto:dyncast-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dyncast/>
List-Post: <mailto:dyncast@ietf.org>
List-Help: <mailto:dyncast-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dyncast>, <mailto:dyncast-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2021 22:28:25 -0000

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.