[ICANN-CSC] Minor Correction to the final SLE Working Group Report

Trang Nguyen trang.nguyen at icann.org
Tue Nov 29 20:59:37 UTC 2016


Dear Names SLE Working Group members:

The final SLE Working Group Report on Service Level Expectation for IANA Root Zone Management (https://community.icann.org/display/gnsocwgdtstwrdshp/DT-A+Service+Levels+Expectations?preview=/52891144/62390722/Clean%20-%20IANA%20Service%20Level%20Expectations%20-%20AGREED%20WITH%20SLA%20PROPOSALS%2008Aug16.pdf) contained a table listing metrics and expected threshold measurements. The document also provided definitions for the various headers in the table. One of the table headers is Type and the document provided the following definition:

Type: Whether the target specified is a minimum target (compliance must be less than the target) or a maximum target (compliance must not be more than the target)

During the drafting of the IANA Naming Function Contract (https://www.icann.org/iana_pti_docs/151-iana-naming-function-contract-v-30sep16), a minor edit was made for clarity.

Type: Whether the target specified is a minimum target (compliance must not be less than the target) or a maximum target (compliance must not be more than the target)

On Monday, 28 November, the Customer Standing Committee (CSC) had its fourth meeting and agreed to use the definition contained in the IANA Naming Function Contract moving forward, including in the glossary of the monthly PTI performance report and dashboards. The committee asked that we reach out to the Working Group to inquire about updating the final SLE Working Group Report to reflect the definition contained in the IANA Naming Function Contract. The reason for the request is to ensure that all documents are consistent. I have included the CSC in the cc line of this email so that your response to the request can go directly to the CSC members and liaisons.

Best,

Trang









-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20161129/63cf72bf/attachment.html>


More information about the ICANN-CSC mailing list