[ippm] High-Precision Service Metrics draft

Alexander L Clemm <ludwig@clemm.org> Wed, 20 October 2021 20:39 UTC

Return-Path: <ludwig@clemm.org>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE1B3A1047 for <ippm@ietfa.amsl.com>; Wed, 20 Oct 2021 13:39:19 -0700 (PDT)
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_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=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 oGCzXaTPHATG for <ippm@ietfa.amsl.com>; Wed, 20 Oct 2021 13:39:15 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9CBD3A103C for <ippm@ietf.org>; Wed, 20 Oct 2021 13:39:13 -0700 (PDT)
Received: from [172.16.0.44] ([73.189.160.186]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0Lfl9w-1n27SJ1mvq-00pLd8; Wed, 20 Oct 2021 22:39:09 +0200
Message-ID: <010dd135-4efd-f2e5-6eec-cdc64cafd375@clemm.org>
Date: Wed, 20 Oct 2021 13:39:07 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0
Content-Language: en-US
From: Alexander L Clemm <ludwig@clemm.org>
To: ippm@ietf.org
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K1:nJZLRBwRJf5AtcBRKTmfpz2fAVQtWDqZyn0oOMpmxVSdmjy5cV7 yHhAi3sYpzxXk1+/W+U0yVZrPhYqSeZxQ3XCBSvL0OQzvl8VQrQg6LiVI1ED79k8/9rseSA 6AiSEFgAJWQLeBvyEb9Z6JanVfn+txqAlmEre9IRYHGrLaIK8YlZaF22v7uVK6BgvYa4F7A giVcDG5lYawzFlLMoC0cg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:6XNBDb1X4UQ=:aJ2ekeKQELcSe5C92NQNEO lcndgqgtOT3pTyCSF/KWKNq0I94jobCxTBH22Gpw+DTN7Uf8lnsQrdeKPFAG0XfsnD8bI/2Aj KpKQA1nVJ/sPtSRfuji8KRZFPGl88CLjxOfhOX0MUQL8IdL/AEA4iERTCx25BUgdF3G5M7Wp4 lwwaVK1LHcXkOczYMEAWjCUZWV0sb2N1J/62NqbUuG98CF+/l1884YLGX+qWtxOXuk5z/PJk2 kobnolWxNrv7ndEIWa9HRqVC1Ju6NLfkljTdCBHAVIbIAJUgJzCRXV+o2Kz2UeiD3upUEuvF2 sOjvtLqdNKc/t8Wp4e3NAigQLdCxEya6IVPyHVaZWRburO8/O2qBUPdDaVGZIMFYVTzDU7FAu qu9EfkBMBPrDqtnZjNK7pTnDkPJbkWFf0bekcVk0UrSyauV+AYlM1K/sBkBu09PBQSzAo3PQ4 FJN2ilHjjqk7ncZvfl/h/Rwrw+iXHKxRX5iFjwqUlGla7iZb3TYZUrGFGzqVeyFRv0fIIf1JJ 4oDSJNc3MMqQj4MGKTGKZX1I17FHnO7ws3VIU8b/nWGm3CNcawm2t+P8ShGecHbKI/G9JeqdL jIuKr7KLRWigrIK0Nv8sQqXevuW8sLfalllHTyA+8fMDxAlsDhkFuIpWABbAo60wJWK6sW2D7 6j0aarpmhI+kJyiSi/ZwvObz7Hh1IgF+o/+abvZ+d6FQDTf9bf/K9DBgD+p8abF7haLI=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/Za3wHnKDVGP_qEyDv_TXdRNZnrM>
Subject: [ippm] High-Precision Service Metrics draft
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2021 20:39:20 -0000

Hello IPPM working group,

we have just uploaded a new draft on High-Precision Service Metrics, 
draft-csfx-ippm-hipmetrics-00, which we hope to discuss at IETF 112 and 
which we believe fits well into IPPM.  The abstract is as follows:

"This document defines a set of metrics for high-precision networking 
services. These metrics can be used to assess the service levels that 
are being delivered for a networking flow. Specifically, they can be 
used to determine the degree of compliance with which service levels are 
being delivered relative to service level objectives that were defined 
for the flow. The metrics can be used as part of flow records and/or 
accounting records.  They can also be used to continuously monitor the 
quality with which high-precision networking service are being delivered."

We are looking forward to your feedback and also for collaborators.

--- Alex (also on behalf of co-authors: John, Jerome)