|Vote Open||Vote |
|Vote Close||Date of Submission||Staff Contact and Email||Statement Number|
|28.02.2013||At-Large Consultation on gTLD Delegation and Redelegation Performance Standards Workspace||Adopted|
11Y, 0N, 0A
|Comment/Reply Periods (*)||Important Information Links|
|Comment Open:||15 January 2013|
|Comment Close:||28 February 2013|
|Close Time (UTC):||23:59 UTC||Public Comment Announcement|
|Reply Open:||1 March 2013||To Submit Your Comments (Forum)|
|Reply Close:||21 March 2013||View Comments Submitted|
|Close Time (UTC):||23:59 UTC||Report of Public Comments|
|Purpose (Brief):||A consultation on developing performance standards for Delegation and Redelegation of a Generic Top Level Domain (gTLD)|
|Current Status:||Initial public consultation|
|Next Steps:||Review comments received|
|Staff Contact:||Michelle Cotton||Email:||firstname.lastname@example.org|
|Section I: Description, Explanation, and Purpose|
The Internet Assigned Numbers Authority (IANA) functions contract
(SA1301-12-CN-0035) between ICANN and the United States Department of Commerce, National Telecommunications Information Administration (NTIA) to maintain the continuity and stability of services related to certain interdependent Internet technical management functions, known collectively as the Internet Assigned Numbers Authority calls for a public consultation from all interested and affected parties to help satisfy the following objective:
This consultation involves the operation of the Delegations and Redelegations of Generic Top Level Doamins (gTLDs) described in the IANA functions contract as the following:
C.2.9.2.d Delegation and Redelegation of a Generic Top Level Domain (gTLD) ‑ The Contractor shall verify that all requests related to the delegation and redelegation of gTLDs are consistent with the procedures developed by ICANN. In making a delegation or redelegation recommendation, the Contractor must provide documentation verifying that ICANN followed its own policy framework including specific documentation demonstrating how the process provided the opportunity for input from relevant stakeholders and was supportive of the global public interest. The Contractor shall submit its recommendations to the COR via a Delegation and Redelegation Report.
|Section II: Background|
|This is one of a series of consultations to establish performance standards for the delivery of the IANA functions, as described in contract SA1301-12-CN-0035.|
|Section III: Document and Resource Links|
|Section IV: Additional Information|
(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.
FINAL VERSION TO BE SUBMITTED IF RATIFIED
FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC
The ALAC recognises and understands why this consultation is occurring now, but we do note that it is, to some extent, unfortunate timing with regard to redelegations.
ccTLD: The ccNSO Working Group on the review of the Framework of Interpretation (FOI-WG) aims to establish a community agreed consensus of the understanding of terms, meanings, usage, limitations and the intentions of RFC 1591, ICP-1 and the relevant GAC Advice (2000 and 2005) relating to the rare relatively occurrence of the ccTLD redelegation (see FOI-WG -http://ccnso.icann.org/workinggroups/foiwg.htm). The WG has not completed its work, but it will report to the ccNSO Council and as stated in its Charter “... advise whether it should launch a Policy Development Process to recommend changes to the current policies for delegation, re‐delegation and retirement of country code Top Level Domains …”.
gTLD: Redelegations are virtually unknown at the moment. With the advent of the New gTLDs program, they may well become far more common, but it is not at all clear how this new process will play out.
1. What are the key performance standards that would be meaningful for delivering the ccTLD/gTLD Delegation and Redelegation service?
Timing and accuracy are reasonable standards.
To be meaningful, they must be fully documented and publicly available to the extent allowed by legal or confidentiality constraints.
For ccTLD redelegations, which can at times be tortuous processes and often include “false starts”, end-to-end timing may not be sufficient. There may need to be measures not only of the overall end-to-end time, but the time from the initiation of the “successful” redelegation request, with a particular focus on the effectiveness, efficiency as well as accountability and transparency of the involvement of the ‘Local Internet Community” and ‘Significantly Interested Parties’.
Once the work of the FOI-WG and any recommended ccNSO PDP process has been completed, there may be a need to redefine the performance standards.
2. What do you consider KPIs for successful performance of the ccTLD/gTLD Delegation and Redelegation service?
With one exception, the KPIs identified in the Consultation documents are reasonable. The exception is for ccTLD redelegations. ccTLD/gTLD delegations, and gTLD relegations are, or are expected to be, reasonably standardized processes. ccTLD redelegations particularly contested redelegations, are rare occurrences and often “one-of-a-kind” and the reporting may need to be tailored particularly to reflect the more convoluted process. Moreover, the possibly necessary elongated ccTLD processes should to the extent possible, not skew the overall reporting.
For any process that will not be concluded within one reporting cycle (presumably not longer than one month), processes that are in progress should be displayed to allow all stakeholders and interested parties to be able to follow the progress.
For accuracy, the rate should not only be reported, but for cases where the transaction was not 100% accurate initially, information on the time-to-discover the error and the time-to-recover should be made available.
3. In what formats would you like the results reported to the community?
Some sort of a dashboard should be used to present the overall statistics, with the ability to drill down to specific delegations and redelegations. Moreover the underlying data should be readily exportable.
Stakeholders should be able to subscribe to alerts to keep them informed of delegation and redelegations requests and the ensuing milestones throughout the following process.
As the rate of new gTLD delegations ramp up, statistics on these should updated regularly, probably weekly, to ensure that the community is well aware of the details of the namespace expansion and most particularly, any problems experienced in the ramp-up and steady-state period, where root changes are expected to occur at an unprecedented rate.
4. Do you have additional input on suitable performance standards for the ccTLD/gTLD Delegation and Redelegation service?