[Dyncast] Information on use of compute information in L7 vs L3/L3.5 solutions

Dirk Trossen <dirk.trossen@huawei.com> Mon, 31 October 2022 09:12 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 1743EC14CF14; Mon, 31 Oct 2022 02:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNmN9zUxWMpR; Mon, 31 Oct 2022 02:12:39 -0700 (PDT)
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 B60F3C14CE33; Mon, 31 Oct 2022 02:12:28 -0700 (PDT)
Received: from frapeml100008.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4N16l91X7bz67lD7; Mon, 31 Oct 2022 17:08:37 +0800 (CST)
Received: from lhrpeml100002.china.huawei.com (7.191.160.241) by frapeml100008.china.huawei.com (7.182.85.131) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Mon, 31 Oct 2022 10:12:26 +0100
Received: from lhrpeml500003.china.huawei.com (7.191.162.67) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Mon, 31 Oct 2022 09:12:25 +0000
Received: from lhrpeml500003.china.huawei.com ([7.191.162.67]) by lhrpeml500003.china.huawei.com ([7.191.162.67]) with mapi id 15.01.2375.031; Mon, 31 Oct 2022 09:12:25 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: can <can@ietf.org>, dyncast <dyncast@ietf.org>
Thread-Topic: Information on use of compute information in L7 vs L3/L3.5 solutions
Thread-Index: AdjtBO1URXQ/QbtMTfKSqCjmLjEtqA==
Date: Mon, 31 Oct 2022 09:12:25 +0000
Message-ID: <ccb5076644334bb79b09fa3e238c8c00@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.128.29]
Content-Type: multipart/alternative; boundary="_000_ccb5076644334bb79b09fa3e238c8c00huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/gnROYG1TfkJO6GEWH-4JsPFMkPY>
Subject: [Dyncast] Information on use of compute information in L7 vs L3/L3.5 solutions
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Anycast <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, 31 Oct 2022 09:12:44 -0000

Dear all,

As additional information to the CAN gap analysis and requirements draft (https://www.ietf.org/archive/id/draft-liu-can-gap-reqs-00.html), our paper at the recent ACM SIGCOMM workshop on Future of Internet Routing & Addressing (FIRA) (available at https://dl.acm.org/doi/abs/10.1145/3527974.3545721) may provide some insights into the use of a compute aware traffic steering solution in architectures relying on an indirection approach (e.g., DNS, GSLB, ALTO) vs those provide in-band discovery capabilities (such as those advocated by CAN).

The paper illustrates the two systems-at-test and compare performance for crucial aspects in service delivery, such as initial request latency, as well as performs a use case driven comparison to shed light on latency as well as latency variance reduction but also resilience. The finding of this paper may be useful for this community.

The paper will also be presented in a planned sidemeeting at the IETF on Wednesday the 9th of November, starting at around 6.15pm; see https://wiki.ietf.org/meeting/115/sidemeetings for more info and the announcements on a few IETF lists.

Best,

Dirk