[teas-3272bis-design-team] SLO in 3272bis
Loa Andersson <loa@pi.nu> Thu, 12 March 2020 10:35 UTC
Return-Path: <loa@pi.nu>
X-Original-To: teas-3272bis-design-team@ietfa.amsl.com
Delivered-To: teas-3272bis-design-team@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72EB53A09D6 for <teas-3272bis-design-team@ietfa.amsl.com>; Thu, 12 Mar 2020 03:35:34 -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, SPF_HELO_NONE=0.001, SPF_NONE=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 RepDqcEiUYBT for <teas-3272bis-design-team@ietfa.amsl.com>; Thu, 12 Mar 2020 03:35:32 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0F263A09CD for <teas-3272bis-design-team@ietf.org>; Thu, 12 Mar 2020 03:35:32 -0700 (PDT)
Received: from [192.168.1.6] (unknown [119.94.165.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id E56B8364BCB for <teas-3272bis-design-team@ietf.org>; Thu, 12 Mar 2020 11:35:29 +0100 (CET)
From: Loa Andersson <loa@pi.nu>
To: "teas-3272bis-design-team@ietf.org" <teas-3272bis-design-team@ietf.org>
Message-ID: <cdd0d630-24c8-833e-3434-bfbbcff62bfd@pi.nu>
Date: Thu, 12 Mar 2020 18:34:53 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-3272bis-design-team/HErxks_0bERUlrAPCiHHg36UPXs>
Subject: [teas-3272bis-design-team] SLO in 3272bis
X-BeenThere: teas-3272bis-design-team@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <teas-3272bis-design-team.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas-3272bis-design-team>, <mailto:teas-3272bis-design-team-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas-3272bis-design-team/>
List-Post: <mailto:teas-3272bis-design-team@ietf.org>
List-Help: <mailto:teas-3272bis-design-team-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas-3272bis-design-team>, <mailto:teas-3272bis-design-team-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2020 10:35:35 -0000
Folks, I'm working what we have to say from a model point of view (chap 2) based on the development since the document was firsst posted, but sometimes I get side-tracked. The terminology section in 3272bis says: "Service Level Objective(SLO) A service-level objective (SLO) is a key element of a SLA between a provider and a customer. SLOs are agreed upon as a means of measuring the performance of the Service Provider and are outlined as a way of avoiding disputes between the two parties based on misunderstanding." It was a bit hard to understand the workings of this, but after reading around a bit I think I get it, at least in someway the SLOs are the measurable atom of an SLA. But then I look at our document, and it looks like the only place where SLO (the abbreviation) is used is in the terminology list. Service Level objective (without the abbreviation) is used in one other place. I'd like to do the following change. In the terminology section: OLD Service Level Objective(SLO) A service-level objective (SLO) is a key element of a SLA between a provider and a customer. SLOs are agreed upon as a means of measuring the performance of the Service Provider and are outlined as a way of avoiding disputes between the two parties based on misunderstanding. NEW Service Level Objective - A service level objective is a key element of a SLA between a provider and a customer. Service level objectives are agreed upon as a means of measuring the performance of the Service Provider and are outlined as a way of avoiding disputes between the two parties based on misunderstanding. END And then keep the last paragraph of section 5.5 as is. Alternatively we could push the abbreviation in at all places. I can write that up if you want to go that way. We could also remove service level objective altogether. /Loa -- Loa Andersson email: loa@pi.nu Senior MPLS Expert Bronze Dragon Consulting phone: +46 739 81 21 64
- [teas-3272bis-design-team] SLO in 3272bis Loa Andersson
- Re: [teas-3272bis-design-team] SLO in 3272bis Acee Lindem (acee)