AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
Page History
Comment Close Date | Statement Name | Status | Assignee(s) and | Call for Comments | Call for Comments Close | Vote Announcement | Vote Open | Vote Reminder | Vote Close | Date of Submission | Staff Contact and Email | Statement Number |
---|---|---|---|---|---|---|---|---|---|---|---|---|
30.09.2013 | Consultation on ccTLD Delegation and Redelegation User Instructions and Source of Policy and Procedures | CommentingAdopted 13Y, 0N, 0A | Cheryl Langdon-Orr (APRALO) | 11.09.2013 | 18.09.201319 | 25.09.2013 | 2519.09.2013 | 2529.09.201325 | 30.09.2013 | 2730.09.2013 23:59 | Michelle Cotton michelle.cotton@icann.org | TBCAL-ALAC-ST-0913-06-01-EN
|
...
FINAL VERSION TO BE SUBMITTED IF RATIFIED
Please click here to download a copy of the PDF below.
|
The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote.
FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC
...
The ALAC thanks ICANN for giving it the opportunity to comment on the User Instructions.
1. Do the DRAFT User Instructions clearly provide instructions on how to request a ccTLD delegation or redelegation?
- Yes, they do. In particular:
- The section on the 'Background of the process,' is written in simple, plain English.
- The 'Preparing a request' and the 'Submitting the request' sections clearly note identified and outlined stages. However, it was felt that some further examples could be given to aid applicants in this process. For example, forms with examples of pre-filled in fields and the use of some other outreach materials and tools.
- It was also felt that the 'After the request is received' section was clear and understandable.
- The 'Qualifying top-level domain Strings section was also clear, easy to follow and unambiguous but additional text is we feel required as we outlined in our response to Q3. below.
- The 'Preparing an Operational and Technical Plan' section was also clear and particularly useful, but again this could be aided further with the provision of a 'Sample Ops and Tech Plan with pre-filled sample text that shows or expands in context the material from the 'Specific suggestions' section.
2. Do the User Instructions clearly describe the steps for processing a ccTLD delegation and redelegation?
Yes they do. However, some consideration could be given to the section detailing the "Prohibited Networks" on pages 10, 11 & 12 of the documentation. It could also be better to link this section as an appendix rather than in the body of the text.
3. Do you have additional suggestions as to what may be missing from the User Instructions?
- Reference should be now made in this documentation to IDN ccTLDs outside of the Fast Track Process (such as at paragraph 5 and in any other appropriate reference to IDN ccTLDs).
- Making this reference, would allow for the likelihood of the ICANN Board, in a reasonably short time frame, in dealing with the recently received 'ccNSO Member Endorsed Report' from the ccTLD IDN PDP Work Group and the ccNSO Councils Recommendations regarding the report and its identification of feasible policy for the selection and delegation of IDN ccTLDs associated with the territories listed in the ISO 3166-1 (IDNccTLDs) within the framework of the IDNcc PDP.
4. By what process should ICANN notify the community when there are revisions made to the User Instructions?
In addition to the 'usual' ICANN Announcements, Webinars and Fora at appropriate meeting venues (including but not limited to ICANN Meetings) as well as appropriate Press Releases, specific advice and presentations could be made to Key stakeholder groups in ICANN (GAC, ALAC, ccNSO Membership, ISOC and I* Communities, etc.,) and these groups should be provided with materials to encourage and facilitate outreach through their networks to use for local outreach via engagement centers outreach programs etc.,
5. Does the community think it would be useful for ICANN to publish additional documentation such as a Knowledge Base with help articles and/or a list of Frequently Asked Questions as a companion to the User Instructions?
Yes, additional information and some information which is in alternate formats would be most useful with:
Focusing on the ease of searching for these Knowledge Base and FAQ resources;
Focusing on other companion tools such as links to video introductions to topic (perhaps a Q&A Interview style) and presentation materials;
Considering video demonstrations on how to complete the form; and
Using some sample applications so that requesters get a good idea of the quality of the information that is required.
FIRST DRAFT SUBMITTED
The first draft submitted will be placed here before the call for comments begins.
...
- Yes they do, however some consideration should be given to the following:
The section detailing the "Delegation Request Form" on pages 7 & 8 of the documentation 'IANA TLD MODIFICATION TEMPLATE 2010-02-17'. could be better as a linked appendix rather than in the body of the text.- The section detailing the "Prohibited Networks" on pages 10, 11 & 12 of the documentation, could also be better as a linked appendix rather than in the body of the text.
- .... ... ...
...
5. Does the community think it would be useful for ICANN to publish additional documentation such as a Knowledge Base with help articles and/or a list of Frequently Asked Questions as a companion to the User Instructions?
- Yes additional information and some that is in alternate formates would be most useful . Shorter and searchable KB's and FAQ's with:-
- focus on the EASILY SEARCHABLE..KBs and FAQs
- as well as other companion tools such as links to video introduction to topic (perhaps a Q&A style) and presentation materials
...
- perhaps a video demonstrating how to complete the form
- some sample applications so that requesters get a good idea of the quality of the information that is required.
Other Comments: Including any drafting and grammar/text modification suggestions.