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

Dirk Trossen <dirk.trossen@huawei.com> Tue, 23 February 2021 09:13 UTC

Return-Path: <dirk.trossen@huawei.com>
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 C780B3A28E8 for <dyncast@ietfa.amsl.com>; Tue, 23 Feb 2021 01:13:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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 rCurGFzya9yb for <dyncast@ietfa.amsl.com>; Tue, 23 Feb 2021 01:13:41 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB3C33A28E9 for <dyncast@ietf.org>; Tue, 23 Feb 2021 01:13:40 -0800 (PST)
Received: from fraeml737-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DlCtB7434z67qqq; Tue, 23 Feb 2021 17:09:38 +0800 (CST)
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Tue, 23 Feb 2021 10:13:39 +0100
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Tue, 23 Feb 2021 09:13:38 +0000
Received: from lhreml701-chm.china.huawei.com ([10.201.68.196]) by lhreml701-chm.china.huawei.com ([10.201.68.196]) with mapi id 15.01.2106.006; Tue, 23 Feb 2021 09:13:38 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: Carsten Bormann <cabo@tzi.org>, "dyncast@ietf.org" <dyncast@ietf.org>
Thread-Topic: [Dyncast] Instance Affinity (draft-bormann-dyncast-affinity-00.txt)
Thread-Index: AQHXCWoWU85veum6RkC4JZahG5ZjiKplc9wg
Date: Tue, 23 Feb 2021 09:13:38 +0000
Message-ID: <2900f75d03714f2495edf0c28653b297@huawei.com>
References: <161401620630.26161.6573331426093772450@ietfa.amsl.com> <B3F5A2A1-1CAD-4F3D-8822-A29769B5F661@tzi.org>
In-Reply-To: <B3F5A2A1-1CAD-4F3D-8822-A29769B5F661@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.219.60]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/JncGWeN0o_HaIfWjUVQUictJJKo>
Subject: Re: [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: Tue, 23 Feb 2021 09:13:43 -0000

Hi Carsten,

Thanks for this pointer since the I-D frenzy indeed makes things easily 'disappear'. 

This is an interesting approach, effectively addressing at invocation level. 

What is striking is that you see this being done in a DNS-based resolution (requiring short TTLs, possibly VERY short, and no client caching). Do you see your approach being reconcilable with the dyncast architecture, as proposed in the draft? 

Best,

Dirk

-----Original Message-----
From: Dyncast [mailto:dyncast-bounces@ietf.org] On Behalf Of Carsten Bormann
Sent: 22 February 2021 23:28
To: dyncast@ietf.org
Subject: [Dyncast] Instance Affinity (draft-bormann-dyncast-affinity-00.txt)

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.


-- 
Dyncast mailing list
Dyncast@ietf.org
https://www.ietf.org/mailman/listinfo/dyncast