Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Comment Close
Date
Statement
Name 

Status

Assignee(s) and
RALO(s)

Call for
Comments
Call for
Comments
Close 
Vote
Announcement 
Vote OpenVote
Reminder
Vote CloseDate of SubmissionStaff Contact and EmailStatement Number
30.09.2013Consultation on ccTLD Delegation and Redelegation User Instructions and Source of Policy and ProceduresCommentingAdopted
13Y, 0N, 0A 
Cheryl Langdon-Orr (APRALO)11.09.201318.09.20132425.09.2013
 
2524.09.2013
 
2928.09.201329

30.09.2013
20:00 

30.09.2013
23:59 
Michelle Cotton
michelle.cotton@icann.org

TBCAL-ALAC-ST-0913-06-01-EN

 

 

Comment / Reply Periods (*)

...

FINAL VERSION TO BE SUBMITTED IF RATIFIED

Please click here to download a copy of the PDF below.

PDF
nameAL-ALAC-ST-0913-06-01-EN.pdf

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

...

 

<INSERT USUAL Preamble for PC's>

...

ALAC thanks ICANN for giving it the opportunity to comment on the User Instructions.

1. Do the DRAFT User Instructions  clearly  clearly provide instructions on how to request a ccTLD delegation or redelegation?

  • Yes, they do, in particular the sections on the . In particular: 
    • The section on the 'Background of the process,'
    that
    • is
    simply
    • written in
    plan language, as well as the clearly identified and outlined stages of the
    • simple, plain English. 
    • The 'Preparing a request'
     and
    • and the 'Submitting the request' sections
    , though it
    • 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,
    such as sample
    • 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
    • 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, 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 as a linked 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 ccTLD's 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 dealing 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 IDNccPDPIDNcc 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 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 ; In addition to use of for local outreach via engagement centres outreach 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 that information which is in alternate formates formats would be most useful with:-

    Focus
    1. Focusing on the ease

  1. of serch
    1. of searching for these Knowledge Base and FAQ resources

  2. .
  3. Also focus
    1. Focusing on other companion tools such as links to video

  4. introduction
    1. introductions to topic (perhaps a Q&A Interview style) and presentation materials;

  5. Consider
    1. Considering video

  6. demonstrating
    1. demonstrations on how to complete the form

  7. .
    1. ; and

    2. Using some

  8. Use of some
    1. sample applications so that requesters get a good idea of the quality of the information that is required.

<INSERT USUAL ENDING for PC's>

 

...

FIRST DRAFT SUBMITTED

The first draft submitted will be placed here before the call for comments begins.

...