[ippm] Fwd: New Version Notification for draft-mhmcsfh-ippm-pam-01.txt

Greg Mirsky <gregimirsky@gmail.com> Sun, 19 June 2022 20:17 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 927EBC14F74C; Sun, 19 Jun 2022 13:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xceg05ScYyRC; Sun, 19 Jun 2022 13:17:43 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 C99DDC14F749; Sun, 19 Jun 2022 13:17:43 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id s10so9828921ljh.12; Sun, 19 Jun 2022 13:17:43 -0700 (PDT)
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; bh=43jaY9Osa4y+FFUGt/qoXJIB4c4qIfz5IqjJbBkUDrw=; b=guO9KOh/OuFOVMG0AQa1+HqAiME1vOTvQX1BU7++Doo1VUVoUs5MwA0mKN93VvfsNn d9EUAPTkS2PiQxGQ76GQFJb1pHhXT4pP4xYDCPxvlLkgxFSVQ1+52iw7Z4C2XeBretwk k6GJovxWlBx2zum0NbhJ/4v7qBcP3bpyn6ir5CBqPTL+jNfyTyRDJfsQPA0lS0bcd++u nqldTOaZW4dMe+Xby+S1ZMTeEZjwhD8Ejnpz/lrl1OY975OYMZQdxv1izZ3PhARFyLKe XqrOT926gHSpMcD36WI+OU3QrDghXWEMQsLrmuGLyBcLOfUVO23h+VwWRGRuPu4tXSr7 /Kgw==
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; bh=43jaY9Osa4y+FFUGt/qoXJIB4c4qIfz5IqjJbBkUDrw=; b=qM1pVdX5K5cCYUnXQqOjnJzscOcorkOCKVSfqNsyTIf6mBfqbDyARezpJBYXAzAkNl LDa0MxI2UKhEL9q1ULpMEnnoGN1GCuSH31VPAzu9ge+4uym3j7QU+zwjG/btdiUjfTyE vOONZPqKXy72/f2QKjt8Uya6v8oGyFlQ/pl7AJ5Mslw9DhtF4qwhBelQ1BN3jFZkS77w pDTW1/RMxCfbSAkgd6VOyDgtOQKlyPKs5tnyY0aJgPdOcix0vB5vRoQArcCcCOqeigQu hA4qJ9BWrteVpXtjDMPk03bVYemTMnM8qw6/WjGLcGY2UPsCaEgmdgkqPe0y9fm9V+8q afQQ==
X-Gm-Message-State: AJIora/bYoaTR62dn2FMkZo6xIWIDsLNEOiBUirZLoBvsWA6kXDn/FsD MiKzGEV+g2rlzj8ko/dZAv7wPV6J67neiaZ8mal2Ot/J
X-Google-Smtp-Source: AGRyM1sSGf0BOpvHMydTGai5lq435cB1AUrsNtjOy48/Nz4RhzeiM5mTVw9awpnG+YLfQ1KDSzFQU24S93HA/+UHKvE=
X-Received: by 2002:a05:651c:b1f:b0:25a:29ee:fcce with SMTP id b31-20020a05651c0b1f00b0025a29eefccemr10457333ljr.113.1655669861443; Sun, 19 Jun 2022 13:17:41 -0700 (PDT)
MIME-Version: 1.0
References: <165560163820.3459.7700811621251217416@ietfa.amsl.com>
In-Reply-To: <165560163820.3459.7700811621251217416@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sun, 19 Jun 2022 13:17:30 -0700
Message-ID: <CA+RyBmUBGirTmXEFOOnSbU9U7w7HvLk39bC8uoYWDnq76CZ3MA@mail.gmail.com>
To: IETF IPPM WG <ippm@ietf.org>, TEAS WG <teas@ietf.org>, Med Boucadair <mohamed.boucadair@orange.com>
Content-Type: multipart/alternative; boundary="000000000000f4eb7005e1d2ade5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/FDA9C_VFpKo0LoyJeVpEfWE_Ocw>
Subject: [ippm] Fwd: New Version Notification for draft-mhmcsfh-ippm-pam-01.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 19 Jun 2022 20:17:47 -0000

Dear All,
the authors of the draft took time to address the thoughtful comments from
Med. Also, we've discussed the use of terminology and agreed to settle on
"violated interval" vs. "errored interval". Furthermore, clarified that the
definitions of SLA and SLO used in this document are as defined in Section
4.1 draft-ietf-teas-ietf-network-slices
<https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slices/>.
And then several other clarifications and editorial updates in the new
version.
We welcome your comments, suggestions, and questions. Looking forward to
discussing PAM at IETF-114.

Regards,
Greg (on behalf of the authors and contributors)

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Sat, Jun 18, 2022 at 6:20 PM
Subject: New Version Notification for draft-mhmcsfh-ippm-pam-01.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>, Xiao Min <
xiao.min2@zte.com.cn>



A new version of I-D, draft-mhmcsfh-ippm-pam-01.txt
has been successfully submitted by Greg Mirsky and posted to the
IETF repository.

Name:           draft-mhmcsfh-ippm-pam
Revision:       01
Title:          Precision Availability Metrics for SLO-Governed End-to-End
Services
Document date:  2022-06-18
Group:          Individual Submission
Pages:          12
URL:
https://www.ietf.org/archive/id/draft-mhmcsfh-ippm-pam-01.txt
Status:         https://datatracker.ietf.org/doc/draft-mhmcsfh-ippm-pam/
Html:
https://www.ietf.org/archive/id/draft-mhmcsfh-ippm-pam-01.html
Htmlized:       https://datatracker.ietf.org/doc/html/draft-mhmcsfh-ippm-pam
Diff:           https://www.ietf.org/rfcdiff?url2=draft-mhmcsfh-ippm-pam-01

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 assess whether a service is provided
   in compliance with its specified quality, i.e., in accordance with
   its defined SLOs.




The IETF Secretariat