Date 1 - 1 of 1
Follow-up on SLA #hyperledgertelecom
Joe Ruffles <joe@...>
[ my first attempt to send this seemed to bounce from the mailer -- so following some admin advice, I'm trying again. apologies if anyone receives extra copies ]
Hi All -
Just to follow up on the last call when I promised to get some information on SLAs, I have consulted some colleagues who are in that business and looked for some items on the MEF website.
You can see in the referenced MEF specifications details on performance metrics -- what is measured, how it is quantified, etc.
In MEF parlance, the Service Level Specification (SLS) specifies the quality of the service to be delivered, while the Service Level Agreement (SLA) is more of a legal document which explains the consequences when service quality falls below the level of the SLS (e.g., an SLA might specify the credits which must be paid if the service quality falls below the level specified in the SLS).
A slight but useful simplification is to say that engineers design an SLS, while lawyers negotiate an SLA.
That said, in common usage, the term "SLA" is often applied to both, or the union of both. Those who work in the area, though, draw a distinction.
Finally, some info on the two MEF PoCs that I referenced which explored SLA accounting using blockchain are here: PoC 120 and PoC 127.
===== From the MEF's Wiki ====
A Service Level Agreement (SLA) is a contract between the Subscriber or Operator, on the one hand, and the Service Provider on the other, specifying the agreed to service level commitments and related business agreements.
The technical section in a service provider's Service Level Agreement (SLA) is often referred to as a Service Level Specification (SLS)
The SLS often includes, not exclusively, the following topics:
When MEF 10.3, MEF 23.1 and MEF 26.1 refer to Service Level Specification (SLS), they are referring to the performance metrics included in the SLS, not to the overall SLS.
|1 - 1 of 1|