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 Procedures and Consultation on gTLD Delegation and Redelegation User Instructions and Source of Policy and ProceduresDraftingCheryl Langdon-Orr (APRALO)TBCTBCTBCTBCTBCTBCTBCMichelle Cotton
michelle.cotton@icann.org

TBC

 

 

Consultation on ccTLD Delegation and Redelegation User Instructions and Source of Policy and Procedures

Comment / Reply Periods (*)
Comment Open Date: 
9 September 2013
Comment Close Date: 
30 September 2013 - 23:59 UTC
Reply Open Date: 
1 October 2013
Reply Close Date: 
21 October 2013 - 23:59 UTC
Important Information Links
Public Comment Announcement
To Submit Your Comments (Forum)
View Comments Submitted
Brief Overview
Originating Organization: 
ICANN
Categories/Tags: 
  • Top-Level Domains
Purpose (Brief): 
A consultation on User Instructions and Source of Policy for Delegation and Redelegation of a Country-Code Top Level Domain (ccTLD).
Current Status: 
Initial public consultation
Next Steps: 
Review comments received
Staff Contact: 
Michelle Cotton
Email Staff Contact
Detailed Information
Section I: Description, Explanation, and Purpose: 

The Internet Assigned Numbers Authority (IANA) functions contract (SA1301-12-CN-0035) between ICANNand 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:

C.2.6 Transparency and Accountability — [No later than 1 October 2013], the Contractor shall develop performance standards, in collaboration with all interested and affected parties as enumerated in Section C.1.3, develop user instructions including technical requirements for each corresponding IANA function and post via a website.

C.2.7 Responsibility and Respect for Stakeholders – [No later than 1 October 2013], the contractor shall, in collaboration with all interested and affected parties as enumerated in Section C.1.C, develop for each of the IANA functions a process for documenting the source of the policies and procedures and how it will apply the relevant policies and procedures for the corresponding IANA function and post via a website.

This consultation involves the operation of the Delegations and Redelegations of Country Code Top Level Domains (ccTLDs) described in the IANA functions contract as the following:

C.2.9.2.c Delegation and Redelegation of a Country Code Top Level Domain (ccTLD) ‑ The Contractor shall apply existing policy frameworks in processing requests related to the delegation and redelegation of a ccTLD, such as RFC 1591 Domain Name System Structure and Delegation, the Governmental Advisory Committee (GAC) Principles And Guidelines For The Delegation AND Administration Of Country Code Top Level Domains, and any further clarification of these policies by interested and affected parties as enumerated in Section C.1.3. If a policy framework does not exist to cover a specific instance, the Contractor will consult with the interested and affected parties, as enumerated in Section C.1.3; relevant public authorities and governments on any recommendation that is not within or consistent with an existing policy framework. In making its recommendations, the Contractor shall also take into account the relevant national frameworks and applicable laws of the jurisdiction that the TLD registry serves. 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 user instructions and source of policy for the delivery of theIANA functions, as described in contract SA1301-12-CN-0035.
Section III: Document and Resource Links: 
Section IV: Additional Information: 
None

Specific Questions to be addressed=> 

1. Do the DRAFT User Instructions clearly provide instructions on how to request a ccTLD delegation or redelegation?
2. Do the User Instructions clearly describe the steps for processing a ccTLD delegation and redelegation?
3. Do you have additional suggestions as to what may be missing from the User Instructions?
4. By what process should ICANN notify the community when there are revisions made to the User Instructions?
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?

Consultation on gTLD Delegation and Redelegation User Instructions and Source of Policy and Procedures

Comment / Reply Periods (*)
Comment Open Date: 
10 September 2013
Comment Close Date: 
1 October 2013 - 23:59 UTC
Reply Open Date: 
2 October 2013
Reply Close Date: 
22 October 2013 - 23:59 UTC
Important Information Links
Public Comment Announcement
To Submit Your Comments (Forum)
View Comments Submitted
Brief Overview
Originating Organization: 
ICANN
Categories/Tags: 
  • Top-Level Domains
Purpose (Brief): 

A consultation on User Instructions and Source of Policy 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 Staff Contact
Detailed Information
Section I: Description, Explanation, and Purpose: 

The Internet Assigned Numbers Authority (IANA) functions contract (SA1301-12-CN-0035) between ICANNand 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:

C.2.6 Transparency and Accountability — [No later than 1 October 2013], the Contractor shall develop performance standards, in collaboration with all interested and affected parties as enumerated in Section C.1.3, develop user instructions including technical requirements for each corresponding IANA function and post via a website.

C.2.7 Responsibility and Respect for Stakeholders – [No later than 1 October 2013], the contractor shall, in collaboration with all interested and affected parties as enumerated in Section C.1.C, develop for each of the IANA functions a process for documenting the source of the policies and procedures and how it will apply the relevant policies and procedures for the corresponding IANA function and post via a website.

This consultation involves the operation of the Delegations and Redelegations of Generic Top Level Domains (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 user instructions and source of policy for the delivery of theIANA functions, as described in contract SA1301-12-CN-0035.

Section III: Document and Resource Links: 
Section IV: Additional Information: 

None

(*) 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

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 final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.

FIRST DRAFT SUBMITTED

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