PROPOSED METRIC SECTION ***STAFF USE ONLY: PLEASE DO NOT EDIT*** | ||||||
1 | Metric Description: | % Uptime for Registrar services such as WHOIS, contact info, and complaints. | ||||
2 | Notes/Comments: | Assuming that SLAs are established for these measures in the new RAA. | ||||
3 | AoC Category: | Consumer Trust (CT) | ||||
4 | SO/AC Originator: | GNSO | ||||
STAFF INFORMATION/ANALYSIS SECTION | ||||||
5 | Staff Team: | Registrar | ||||
6 | Metric Currently Measured? | No | ||||
7
| Computation: (e.g., data elements, formula, numerator, denominator, ratio/percent, periodicity/frequency) | There are two types of up-time that could be measured. ICANN Ops (IT) has a Network Operations Center ("NOC"). Can track registry/registrar SLAs minute to minute in the NOC, and a tool/probes are being built. Alternatively, ICANN Compliance will be tracking the data at a high-level on a per month basis. time that could be measured. | ||||
8 | Data Owner: (i.e., party responsible for collecting and publishing metric) | |||||
9 | Data Reference Source: (i.e., how/where is the data collected, tracked, managed, and published/produced?) | |||||
10 | Targets: |
| ||||
11 | Implementation Considerations: (e.g., what new or additional resources, tasks, activities, systems, et al., whether internal or external, would be needed to develop, capture, and report this metric?) | Re: Registrar Whois, this is not monitored currently but this capability is expected to be built out in FY15. Re: contact info and complaints, 2013 RAA requires Rr's to put description of customer service offerings on their sites. Could do review of sites at a point in time. Could also track compliance complaints about customer service unavailability or no response from registrar. This would require manual analysis as it is not its own complaint category. | ||||
12 | Degree of Difficulty/Impact: (i.e., net impact on existing ICANN resources, systems, and capabilities) | Significant | ||||
13 | Estimated Development Cost ($M): |
| ||||
14 | Estimated Ongoing Production Costs: (i.e., incremental to existing funded/budgeted expenditures) |
| ||||
15 | Estimated Net Incremental Staff (FTE): (Express as a fraction and/or range, e.g., .25 - .50) | |||||
16 | Itemization of Staff Work Effort: | |||||
17 | Rough Implementation Timeframe: (e.g., indicate major steps and months/years to complete each one) |
| ||||
18 | Critical Dependencies: | |||||
19 | Anticipated Challenges/Risks: | |||||
METRIC EFFECTIVENESS AND UTILITY SECTION | ||||||
20 | Explanation of Metric Effectiveness: (i.e., how will success/failure enable conclusions to be drawn concerning the relevant AoC definition?) | |||||
21 | Metric Effectiveness Assessment: (i.e., vis a vis AoC definition) | |||||
22 | Overall Feasibility Assessment: LEGEND Poor: Low Effectiveness - High Cost | |||||
======================================= |
DETAILED ITEMIZATION & TRACKING OF ISSUES
Category A: | Metric Questions & Issues |
---|
No. | Issue Description | Originator | Status | Comments |
---|---|---|---|---|
|
|
|
Category B: | Metric Effectiveness & Utility |
---|
No. | Issue Description | Originator | Status | Comments |
---|---|---|---|---|
|
|
|
Category C: | Technical/Implementation |
---|
No. | Issue Description | Originator | Status | Comments |
---|---|---|---|---|
|
|
|
Category D: | Financial/Cost/Budgetary |
---|
No. | Issue Description | Originator | Status | Comments |
---|---|---|---|---|
|
|
|
Category E: | Other |
---|
No. | Issue Description | Originator | Status | Comments |
---|---|---|---|---|
|
|
|