[ippm] Fwd: New Version Notification for draft-mhmcsfh-ippm-pam-00.txt
Greg Mirsky <gregimirsky@gmail.com> Fri, 04 March 2022 18:27 UTC
Return-Path: <gregimirsky@gmail.com>
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 EF6A03A0D9A for <ippm@ietfa.amsl.com>; Fri, 4 Mar 2022 10:27:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qYAIwqL-OGUq for <ippm@ietfa.amsl.com>; Fri, 4 Mar 2022 10:27:37 -0800 (PST)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9FB03A0D53 for <ippm@ietf.org>; Fri, 4 Mar 2022 10:27:36 -0800 (PST)
Received: by mail-ej1-x62a.google.com with SMTP id d10so19163983eje.10; Fri, 04 Mar 2022 10:27:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XNQihDcOUaNmp1oWHn9VxOID4lcdTDoDO4dtGPmeAWU=; b=qtwMU44hzKyo+hrQdxq/Qyb09RpJIdoa7vCzsI1i6hq7SVOliCpk9CeM4ZelOYEjfo 9Js119DiLrn5MLoaOeZqllg0mXjtDawHWz1mMYeuZ00hYYXukjNvdbXdfirdZ/SCs/xv kXmrDq6vo4y7z5MxiBVCc7fO/dXijRiOBt6CLGu87gHux4wBMjWJcHUh3VnT54A6oXNN vDtDC6WhIJjV5MTucO82WD/3TBsT8JwEm3qluEa6Eqe4RYvG6ea84GUoEsxcw1MZ2vp9 6iqr69llPTdN4dnsvtMIfTZGjHQC39HNIxIqonyxtUWhQ1nSr/8zNr+CjmaOoKtWYqwn Wg8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XNQihDcOUaNmp1oWHn9VxOID4lcdTDoDO4dtGPmeAWU=; b=2IdEDNsJoM7a4yqZSRYuJPfxgzsURkkVsTMTLyEHuX+IFpnH6ejq2z1nxafi4d4N7A DWJZUVO5Zh1q21k15EsGmUceYjQb/55FAeQjpvVSXOsYopTTNs13qKWNTl0hZ+BbLAlj dYsuIoxxLNB8vZJiDcXnzuo8aOMhwI6OOOY1O79SF+qDaU8vK6cOlM1Sd2+cQjlMtoRM SoM3z1xNuMGCHV7dVLZ4I78WXVcPkKey5D8nF31yxabmDYVgsfm7lGW3uzaf8kL3VZ3I 9wI9dFN3mLHoYUc/t54zaZknMfpsAmTZVQWP+S7mKmVA738J4H/h+aNzHYDMKatX0Drh cZUg==
X-Gm-Message-State: AOAM533CeYHijKQPL4H++ppHQLZW88uRodZ9fXJ6VJngrwc59X3l9g+1 /xqHQ/UARQ79pQYfTk8SuV4wlH0pPNA+Dy08/9h7CWzG4oI=
X-Google-Smtp-Source: ABdhPJwbX8aY/x8akViGsiND+Q6zmR+PrtBeRtmWYmUDz/LxvewWmN+h+1ycKmVYU1C+jGXUE6t7nU74NvZ3sgK9N/o=
X-Received: by 2002:a17:906:53d2:b0:6ce:791a:31a0 with SMTP id p18-20020a17090653d200b006ce791a31a0mr9728ejo.59.1646418454480; Fri, 04 Mar 2022 10:27:34 -0800 (PST)
MIME-Version: 1.0
References: <164641778881.28341.3129162684341467426@ietfa.amsl.com>
In-Reply-To: <164641778881.28341.3129162684341467426@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 04 Mar 2022 10:27:23 -0800
Message-ID: <CA+RyBmUM3RT5uZDJ+pdUobPN6odzJDPMmHfD70pmkZybSbjq-A@mail.gmail.com>
To: IETF IPPM WG <ippm@ietf.org>
Cc: draft-mhmcsfh-ippm-pam@ietf.org
Content-Type: multipart/alternative; boundary="000000000000218c1c05d968ab3b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/cJEeuatRJnOJUOTP2xOYeTiNcXE>
Subject: [ippm] Fwd: New Version Notification for draft-mhmcsfh-ippm-pam-00.txt
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: Fri, 04 Mar 2022 18:27:47 -0000
Dear All, after our meeting at IETF-112, the authors of draft-mirsky-ippm-epm and draft-csfx-ippm-hipmetrics worked together. This draft is the result of our efforts to merge documents and combine ideas. We always welcome your comments, questions, and suggestions. Dear IPPM WG Chairs, we appreciate an opportunity to present our work on Precision Availability Metrics in multi-SLO environments. We hope you'll grant us a full slot as this work replaces an earlier draft that had received substantial discussion on our mailing list. draft-mhmcsfh-ippm-pam Presenter: Greg Mirsky Time: 10 - 15 min Regards, Greg (on behalf of the authors) ---------- Forwarded message --------- From: <internet-drafts@ietf.org> Date: Fri, Mar 4, 2022 at 10:16 AM Subject: New Version Notification for draft-mhmcsfh-ippm-pam-00.txt To: Alexander Clemm <ludwig@clemm.org>, Greg Mirsky <gregimirsky@gmail.com>, Jerome Francois <jerome.francois@inria.fr>, Joel Halpern < joel.halpern@ericsson.com>, John Strassner <strazpdj@gmail.com>, Liuyan Han <hanliuyan@chinamobile.com>, Xiao Min <xiao.min2@zte.com.cn> A new version of I-D, draft-mhmcsfh-ippm-pam-00.txt has been successfully submitted by Greg Mirsky and posted to the IETF repository. Name: draft-mhmcsfh-ippm-pam Revision: 00 Title: Precision Availability Metrics for SLO-Governed End-to-End Services Document date: 2022-03-04 Group: Individual Submission Pages: 13 URL: https://www.ietf.org/archive/id/draft-mhmcsfh-ippm-pam-00.txt Status: https://datatracker.ietf.org/doc/draft-mhmcsfh-ippm-pam/ Html: https://www.ietf.org/archive/id/draft-mhmcsfh-ippm-pam-00.html Htmlized: https://datatracker.ietf.org/doc/html/draft-mhmcsfh-ippm-pam Abstract: This document defines a set of metrics for networking services with performance requirements expressed as Service Level Objectives (SLO). These metrics, referred to as Precision Availability Metrics (PAM), can be used to assess the service levels that are being delivered. Specifically, PAM can be used to determine the degree of compliance with which service levels are being delivered relative to pre-defined SLOs. PAM can be used to provide a service according to its SLO as part of accounting records, to account for the actual quality with which services were delivered and whether or not any SLO violations occurred. Also, PAM can be used to continuously monitor the quality with which the service is delivered. The IETF Secretariat