Re: [Dyncast] How to expose "Computing Capability"?

Jens Finkhaeuser <jens@interpeer.io> Fri, 13 May 2022 06:32 UTC

Return-Path: <jens@interpeer.io>
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 67688C159A2E for <dyncast@ietfa.amsl.com>; Thu, 12 May 2022 23:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=interpeer.io
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 4NvYVKo31K0w for <dyncast@ietfa.amsl.com>; Thu, 12 May 2022 23:32:06 -0700 (PDT)
Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82C6FC15E41C for <dyncast@ietf.org>; Thu, 12 May 2022 23:32:05 -0700 (PDT)
Date: Fri, 13 May 2022 06:31:57 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interpeer.io; s=protonmail; t=1652423522; bh=iePcsuD+5xlE+BPIO4hMC5s54QXkqvvPLiHIHbcyzGU=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=prp9OGc4YtgbQAzJ6BNjcrMR3R1xEvukjBiOmfwN8JEU/FekHsfBEzupQ9iXyhFfM WBhRCSYwZtKuyRrpQhGMWvraiObI7uzpNCVHQJG0lTd+QryorPBJC2OtKSE6/9lBmG RGblwD6gmTOB/EDYReO0mWYGr7OPYvjoq+FGnCow=
To: Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>
From: Jens Finkhaeuser <jens@interpeer.io>
Cc: Linda Dunbar <linda.dunbar@futurewei.com>, "dyncast@ietf.org" <dyncast@ietf.org>
Reply-To: Jens Finkhaeuser <jens@interpeer.io>
Message-ID: <oQfMkYgoGRN0CleHUbPQf0cA2SzZRh-5pd5Ab375MfBlYp42xq9-0sx0WVDsHeExkBGCeg_-GAOkf2yka_G_aAz_gpGdExGdhILNY1C8lTk=@interpeer.io>
In-Reply-To: <a2583f12d6cd4387b28ad701d9e7e638@huawei.com>
References: <CO1PR13MB4920E1DF2F12914C8F39173D85C89@CO1PR13MB4920.namprd13.prod.outlook.com> <a2583f12d6cd4387b28ad701d9e7e638@huawei.com>
Feedback-ID: 18725731:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------8d7f9ae2ac37d17109ed9aa29d7fb3f6a2f8854c70d7306b1b5bffb7949863c6"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/T2SoHGhb7Tuk1M16LmD5-CdCMwo>
Subject: Re: [Dyncast] How to expose "Computing Capability"?
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.34
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: Fri, 13 May 2022 06:32:11 -0000

Hi all,
maybe a tad off-topic, but I still think that "compute capability" is best application defined, and CAN should just offer a function for publishing an application specific value, where routers pick the best (aka highest/lowest; and/or maybe combine that with path awareness). That requires the least protocol engineering, the least computation on the router, and gives applications every flexibility in defining how to come by this value. Plus, it leaks the least amount of data one might not want to expose.


I say off-topic because I don't know what's in that paper!

Jens
------- Original Message -------
On Thursday, May 12th, 2022 at 09:00, Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org> wrote:


> Hi Linda,
> 

> Apologies for that. I had hoped the links are coming online quicker but they’re not yet there. I don’t want to send the PDF on the list directly but can provide it for anybody who drops me an email. Once I have the link, I’ll add it to the github issue.
> 

> Best,
> 

> Dirk
> 

> From: Dyncast [mailto:dyncast-bounces@ietf.org] On Behalf Of Linda Dunbar
> Sent: 11 May 2022 20:33
> To: dyncast@ietf.org
> Subject: [Dyncast] How to expose "Computing Capability"?
> 

> The answer to the CAN issue #10 (Is computing resource measurable? https://github.com/CAN-IETF/CAN-BoF-ietf113/issues/10 ) states:
> 

> o   See IFIP Networking 2022 paper on how to simply expose “computing capability” and achieve better steering with such simple measure.
> 

> Does anyone have the link to the IFIP Network 2022 paper on how to simply expose “Computing Capability”?
> 

> Thank you
> 

> Linda