Thread: ICANN Nairobi
View Single Post
  #2 (permalink)  
Old 12th March 2010, 11:14 PM
phio's Avatar
phio phio is offline
Senior Member
 
Join Date: Oct 2007
Location: Arctic Circle
Posts: 1,541
iTrader: (31)
Rep Power: 658
phio is an unknown quantity at this pointphio is an unknown quantity at this pointphio is an unknown quantity at this pointphio is an unknown quantity at this pointphio is an unknown quantity at this point
Re: ICANN Nairobi

Part of Tina's presentation on Wednesday:

icann nairobi

"IDN ccTLD Fast Track Status
Successfully launched 16 November 2010
100% up-time and no technical issues
Total of 19 requests received so far
–4 requests has successfully passed String Evaluation and are now going through String Delegation
–15 requests are actively being processed
–Spam requests are not calculated in stats
Requests span over 11 languages
Requests are kept confidential
–Per the Fast Track Process requirements"

From the meeting ICANN board meeting today:

>>ROD BECKSTROM: Thank you very much, Peter.
...
"Second, IDN ccTLD Fast Track process. We've received four
additional applications for string evaluation, awaiting the DNS
stability panel's report on the most recent submissions, and
expecting to have additional strings successfully complete the string
evaluation process by the end of March.

The first four IDN strings passing string evaluation are still in
the process of delegation request."

...



>>THOMAS NARTEN: Thank you, Mr. Chairman. Whereas, public comment
has indicated that the requirement for gTLD strings to be at least
three characters would limit the utility of IDN gTLDs in some regions
of the world. Whereas, the GNSO IDN working group previously
recommended that applications for fewer than three-character gTLDs
were allowed in the gTLD program based on a case by case evaluation.

Whereas an independent IDN implementation support team was formed as
a result of discussion during the meeting in Sydney, Australia to
assist in implementation of a set of rules that could be employed to
allocate IDN strings of fewer than three characters where appropriate.

Whereas the team completed its work and published a recommendation
for relaxing the three-character requirement in a report for public
comment that included specific requirements for when two-character
gTLDs can be delegated and deferred the notion of one-character gTLDs
pending policy issues.

Whereas, a number of thoughtful public comments have been received.
And whereas a model for implementing the team's recommendation in the
new gTLD program has also been posted for public comment.

Resolved, ICANN shall take into account remaining public comments on
the proposed model and develop a final proposal to be included in
draft version 4 of the Draft Applicant Guidebook.

Whereas, subject to any amendments in response to public comment,
the board supports the substantive content of the model that was
posted on February 15, 2010 for public comment and expects that it
will be included in version 4 of the Draft Applicant Guidebook.

Resolved, ICANN thanks those members of the community who have
devoted their time and energy to advancing this aspect of trademark
rights protection.

>>PETER DENGATE THRUSH: Thank you, Thomas. Is there a seconder
for that? I see Dennis.

Anyone wish to speak to this resolution?

No?

All right. Let's put that to a vote. All those in favor, please
raise your hands.

Thank you.

Rita, are you voting?

>>RITA RODIN JOHNSTON: In favor, please.

>>PETER DENGATE THRUSH: Thank you. Any abstentions -- Any opposed?

Any abstentions? Carried unanimously.

Let's move, then, to item 10 which is in relation to IDN variants,
and we have the ability to call on some technical expertise. I will
ask Dr. Crocker to take us through this one.

>>STEVE CROCKER: Thank you, Mr. Chairman. This is the first of
three related resolutions, 10, 12, and 13 -- not 11 -- related to
IDNs and related topics.

Resolution 10, IDN variants.

Whereas, language communities that use variant characters are
affected by the management and implementation of variants in new TLDs.

Whereas, an implementation IDN -- an independent, excuse me.

Whereas an independent IDN implementation support team was formed as
a result of discussions alt the ICANN meeting in Sydney, Australia,
to make recommendations for managing IDN variants at the top level.

Whereas, the IDN implementation support team has completed its work
and published its recommendations in a report for public comment and
recommends that ICANN is to study the usability of the DNAME resource
record as part of a supported mechanism for managing TLD strings
containing variants.

Whereas, the variant approach used in the IDN ccTLD fast track is
consistent with the team's recommendations.

Whereas a model for implementing the recommendations of the IDN
implementation support team for allocation or reservation of desired
variant TLDs, pending identification of a mechanism for delegation
and management of the variant TLDs in the new gTLD program, has been
posted for comment.

Resolved, ICANN shall take into account remaining public comments on
the proposed model and based on such comments develop a proposal to
be included in version 4 of the Draft Applicant Guidebook.

Resolved, the board tasks the ICANN CEO to undertake a study on the
usability of the DNAME resource record as part of the supported
mechanism for managing TLD strings containing variants.

Resolved, ICANN thanks those members of the community who have
devoted their time and energy to the work on these issues, and urges
the community to collaborate on the ongoing testing of variant
mechanisms."
__________________
.
Reply With Quote