IETF Logo Mail Archive

Re: [Dyncast] edge capability feedback

Carsten Bormann <cabo@tzi.org> Sat, 13 March 2021 12:48 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 D88F63A0C81 for <dyncast@ietfa.amsl.com>; Sat, 13 Mar 2021 04:48:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 p5lwkLyJ4H6f for <dyncast@ietfa.amsl.com>; Sat, 13 Mar 2021 04:48:33 -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 D74643A0C82 for <dyncast@ietf.org>; Sat, 13 Mar 2021 04:48:32 -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 4DyMtQ4GGJzySB; Sat, 13 Mar 2021 13:48:30 +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>
In-Reply-To: <9f5b7f65b27c46d49f7a75253b56f7de@huawei.com>
Date: Sat, 13 Mar 2021 13:48:30 +0100
Cc: Dirk Trossen <dirk.trossen@huawei.com>, Dirk Kutscher <ietf@dkutscher.net>, dyncast <dyncast@ietf.org>, Joel Halpern Direct <jmh.direct@joelhalpern.com>, "Milheiro Mendes, Paulo Jorge" <paulo.mendes@airbus.com>
X-Mao-Original-Outgoing-Id: 637332510.1100121-e0b9dd4db20be19409614377e57f3745
Content-Transfer-Encoding: quoted-printable
Message-Id: <91571256-FA3B-46C0-9A6D-AEAAF3AD4758@tzi.org>
References: <20210311102435132657878@chinamobile.com> <9A6BA68B-3916-413E-BD29-62D4096DF1D3@senki.org> <00CCE76F-D3F8-49DD-8E11-29E7DBB956E1@huawei.com> <5EEEA7D8-D4E7-42AE-9D40-2DF6DF744567@chinamobile.com> <ea129e08-d5b2-5edb-a5ee-8362b12dc2b5@joelhalpern.com> <B930F50D-4A0C-4DAB-A3E5-0CD308CEB67F@tzi.org> <CAD6RcJZ-vSxzEEDBDHwwqQuMWQ9Ws=vs8j4W=cAS12m+cAMj7w@mail.gmail.com> <d85e3f5e-bbbf-757e-bd92-fac861166961@joelhalpern.com> <7dda62f741ce49cdba9892a2e7ce7077@huawei.com> <2FAAE3BE-BEC8-4534-8DFB-EC2A3FD27D24@dkutscher.net> <0423e80157724ac4975d0b987a2ce813@huawei.com> <9f5b7f65b27c46d49f7a75253b56f7de@huawei.com>
To: Luigi IANNONE <luigi.iannone@huawei.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/XTMkELYhkphAQMYzubL_ee3Jz9c>
Subject: Re: [Dyncast] edge capability feedback
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: Sat, 13 Mar 2021 12:48:36 -0000

On 2021-03-13, at 09:38, Luigi IANNONE <luigi.iannone@huawei.com> wrote:
> 
> Obviously we touch topic like “metrics” but it is not about which one to use. 

We do have some requirements, though.

I think the most important requirement on the application-side metric is that it can be combined with a network-side metric in a way that allows to make routing decisions in a d-router.

So, indeed, it cannot encode information that would need application-level knowledge (“business logic”) to combine and compare.  

As I said in the meeting, the obvious metric will be based on latency and its dispersion (variability).  Anything that is compatible with this metric will do, too (so there is space for adding secret sauce, too).

Grüße, Carsten

v2.23.0 | Report a Bug | By Email