Reserved Names wg charter 2

Reserved Names Working Group (RN-wg)

Draft Statement of Work for 30-Day Extension of RN-WG

Original RN-WG Statement of Work will apply as applicable with the following added.

General Tasks

1. Define reserved names per direction provided during meetings in Lisbon

2. Reorganize the RN-WG report so that recommendations are grouped in the following categories:

a. Reserved name recommendations ready for input into the New gTLD PDP report

b. Recommendations for possible use in the New gTLD evaluation process, not as reserved names

i. Geographical and geopolitical names

ii. Controversial names

c. Categories of names deemed to be out of scope for the RN-WG

i. Three character names at the third level

ii. Registry specific names at the second level

iii. Other reserved names at the second level



3. Review GAC Principles for New gTLDs



4. Review IDN-WG Report



5. Add the GAC Principles for New gTLDs to the RN-WG report and reference them in applicable name categories



6. Request that the SSAC identify any possible security or stability issues with regard to RN-WG recommendations as well as suggestions as to how any such issues might be mitigated



7. Create an annex as feasible (with no explanations) which is simply the full proposed list of reserved names listed alphanumerically



8. Use format specifications to be provided by Liz Williams

Tasks regarding Recommendations

1. ICANN/IANA reserved names


a. Attempt to complete the work needed to make a final recommendation regarding whether or not the existing ASCII reserved name requirement should be continued at all levels of domain names registered by a registry.

b. State recommendations in the RN-WG report so that they can be readily transferred into the New gTLD PDP report

i. If unable to complete the work described in item a above, maintain status quo for now regarding ASCII names

ii. Confirm that these names are already reserved at the third level for .name and .pro and edit the document accordingly

iii. Reword recommendation for “example” at all levels for ASCII and IDN names

1. Provide examples

2. Incorporate any relevant comments from the IDN-WG report

iv. Provide a brief rationale in support of the recommendations, referring to the role of the category as applicable

c. Finalize guidelines for additional work if needed

2. Use of symbols in Reserved Names

a. Restate recommendations in RN-WG report so that they can be readily transferred into the New gTLD PDP, including fine-tuning of language

i. Provide examples as possible

ii. Maintain status quo for now regarding ASCII names

b. Provide a brief rationale in support of the recommendations, referring to the role of the category as applicable



3. Single & two-character reserved names



a. Consult further with IDN experts regarding single and two-character IDN names including definition of the term ‘character’ as it relates to non-roman scripts

b. Consult further with experts in the technical community regarding single letter ASCII names, single-number ASCII names and two-character ASCII names involving at least one number.

c. Consult with the GAC as possible regarding single and two-character IDN names

d. Restate recommendations in RN-WG report so that they can be readily transferred into the New gTLD PDP report

i. Provide examples as possible for both the top and second levels, ASCII and IDN, single and two-character

ii. Incorporate any relevant comments from the IDN-WG report

e. Provide a brief rationale in support of the recommendations, referring to the role of the category as applicable

f. Finalize guidelines for additional work for ASCII single character names at all levels

g. As necessary, finalize guidelines for additional work for IDN single and two-character names at all levels



4. Tagged names



a. Restate recommendations in RN-WG report so that they can be readily transferred into the New gTLD PDP report

i. To ensure clarity, change all occurrences of ‘in the third and fourth character positions’ to ‘in both the third and fourth character positions’

ii. Move recommendation 2 for IDN gTLDs from ASCII, top level to IDN top level

iii. In recommendation 2 for IDN gTLDs, change wording to use the terms ‘ASCII compatible encoding’ and ‘Unicode display form’

iv. Provide examples, including an example of what new applicants for an IDN gTLD would have to provide

v. Incorporate any relevant comments from the IDN-WG report

b. Provide a brief rationale in support of the recommendations, referring to the role of the category as applicable



5. NIC, Whois and www



a. Restate recommendations in RN-WG report so that they can be readily transferred into the New gTLD PDP report

i. Provide examples

ii. Incorporate any relevant comments from the IDN-WG report

b. Provide a brief rationale in support of the recommendations, referring to the role of the category as applicable



6. Geographical & geopolitical names



a. Review the GAC Principles for New gTLDs with regard to geographical and geopolitical names

b. Consult with WIPO experts regarding geographical and geopolitical names and IGO names

c. Consult with the GAC as possible

d. Reference the treaty instead of the Guidelines and identify underlying laws if different than a treaty

e. Consider restricting the second and third level recommendations to unsponsored gTLDs only

f. Restate recommendations in RN-WG report for possible use in the New gTLD evaluation process, not as reserved names

i. Describe process flow

ii. Provide examples as possible

iii. Incorporate any relevant comments from the IDN-WG report

g. Provide a brief rationale in support of the recommendations, referring to the role of the category as applicable

h. Edit other text of the individual subgroup report as applicable to conform with the fact that geographical and geopolitical names will not be considered reserved names

i. Finalize guidelines for additional work as necessary



7. Third level names

a. Replace recommendations with a statement about the direction by the Council that this category is not in the scope of the RN-WG

b. Edit other text of the individual subgroup report as applicable with the statement regarding scope



8. gTLD names at the 2nd (or 3rd level if applicable)



a. Complete consultation with gTLD registries and incorporate final results in the RN-WG report

b. Determine whether final recommendations can be made

c. State recommendations in RN-WG report so that they can be readily transferred into the New gTLD PDP report

i. Provide examples

ii. Incorporate any relevant comments from the IDN-WG report

d. Provide a brief rationale in support of the recommendations, referring to the role of the category as applicable

e. If additional work is needed, finalize guidelines for that work



9. Other names at the second level



a. Replace recommendations with a statement about the direction by the Council that this category is not in the scope of the RN-WG

b. Edit other text of the individual subgroup report as applicable with the statement regarding scope



10. Controversial names



a. Review the GAC Principles for New gTLDs with regard to controversial names

b. Consult with the GAC as possible

c. Consider the possibility of creating a disputed name list (not a reserved name list) that would be updated whenever controversial names are rejected and would be used for guideline purposes only

d. Restate recommendations in RN-WG report for possible use in the New gTLD evaluation process, not as reserved names

i. Describe process flow

ii. Provide examples as possible

iii. Incorporate any relevant comments from the IDN-WG report

e. Provide a brief rationale in support of the recommendations, referring to the role of the category as applicable

f. Edit other text of the individual subgroup report as applicable to conform with the fact that controversial names will not be considered reserved names

g. Finalize guidelines for additional work as necessary

Schedule

1. Restart date: Wednesday, 11 April

2. Completion date: Monday, 10 May