ICANN Board transcript posted again Beckstrom confirms existing gtld's route to IDN

[sbe18]

ICANN' s Board transcript is posted.


http://sel.icann.org/meetings/seoul2...30oct09-en.txt


And for all the doubters about existing gTLD's enroute to IDN.IDN status...
...



CEO Rod Beckstrom's Remarks:

ROD BECKSTROM: Thank you, Peter. I'd just like to express my
appreciation to all those across the open Internet ecosystem who have
worked for many, many years to make this possible. And especially
not only to the members of the ICANN community, but to the members of
the Internet Engineering Task Force, the IETF, some of whom have
worked for over a decade on this issue.

And this represents today one small step for ICANN, and the IETF,
but it represents a very important and significant step for half the
world of Internet users. Those who use non-Latin scripts and their
own language.

This helps us live up to our shared goals of: One world, one
Internet, everyone connected.

Now, in people's own script.

And this first step allows them to use their own domain names in
their own languages, but only for the country code domains, so
instead of dot Korea, they can have dot -- the set of Hangul symbols
or, rather, symbols that represent Korea for them -- and this is an
important step. And yet there's many people around the world that
would like to have the equivalents of the Latin TLDs such as dot com,
dot net, dot org, and others in their own native scripts as well.

This is an important next step that we need to continue working on.
We, as a community, have not yet reached consensus on the final
resolution of those other issues, but we have a moral responsibility
in what we do for the public interest to push that forward.



Otherwise, we are prejudicing the global domain name system against
half of the world whose native languages are in those other scripts.
So I hope that to fulfill our obligation to act in the public
interest, which we recently reaffirmed by signing the Affirmation of
Commitments, that we will move forward swiftly and professionally and
with due consideration to bring those issues to a closure, so that
people in Thailand, in Korea, in India, and all over the world can
truly use the Internet in their own script for their domain name
needs. Thank you.

[Wot]

Originally Posted by sbe18

ICANN' s Board transcript is posted.


http://sel.icann.org/meetings/seoul2...30oct09-en.txt


And for all the doubters about existing gTLD's enroute to IDN.IDN status...
...



CEO Rod Beckstrom's Remarks:

ROD BECKSTROM: Thank you, Peter. I'd just like to express my
appreciation to all those across the open Internet ecosystem who have
worked for many, many years to make this possible. And especially
not only to the members of the ICANN community, but to the members of
the Internet Engineering Task Force, the IETF, some of whom have
worked for over a decade on this issue.

And this represents today one small step for ICANN, and the IETF,
but it represents a very important and significant step for half the
world of Internet users. Those who use non-Latin scripts and their
own language.

This helps us live up to our shared goals of: One world, one
Internet, everyone connected.

Now, in people's own script.

And this first step allows them to use their own domain names in
their own languages, but only for the country code domains, so
instead of dot Korea, they can have dot -- the set of Hangul symbols
or, rather, symbols that represent Korea for them -- and this is an
important step. And yet there's many people around the world that
would like to have the equivalents of the Latin TLDs such as dot com,
dot net, dot org, and others in their own native scripts as well.

This is an important next step that we need to continue working on.
We, as a community, have not yet reached consensus on the final
resolution of those other issues, but we have a moral responsibility
in what we do for the public interest to push that forward.



Otherwise, we are prejudicing the global domain name system against
half of the world whose native languages are in those other scripts.
So I hope that to fulfill our obligation to act in the public
interest, which we recently reaffirmed by signing the Affirmation of
Commitments, that we will move forward swiftly and professionally and
with due consideration to bring those issues to a closure, so that
people in Thailand, in Korea, in India, and all over the world can
truly use the Internet in their own script for their domain name
needs. Thank you.

[Explorer]

Originally Posted by sbe18

ICANN' s Board transcript is posted.


http://sel.icann.org/meetings/seoul2...30oct09-en.txt


And for all the doubters about existing gTLD's enroute to IDN.IDN status...
...



CEO Rod Beckstrom's Remarks:

ROD BECKSTROM: Thank you, Peter. I'd just like to express my
appreciation to all those across the open Internet ecosystem who have
worked for many, many years to make this possible. And especially
not only to the members of the ICANN community, but to the members of
the Internet Engineering Task Force, the IETF, some of whom have
worked for over a decade on this issue.

And this represents today one small step for ICANN, and the IETF,
but it represents a very important and significant step for half the
world of Internet users. Those who use non-Latin scripts and their
own language.

This helps us live up to our shared goals of: One world, one
Internet, everyone connected.

Now, in people's own script.

And this first step allows them to use their own domain names in
their own languages, but only for the country code domains, so
instead of dot Korea, they can have dot -- the set of Hangul symbols
or, rather, symbols that represent Korea for them -- and this is an
important step. And yet there's many people around the world that
would like to have the equivalents of the Latin TLDs such as dot com,
dot net, dot org, and others in their own native scripts as well.

This is an important next step that we need to continue working on.
We, as a community, have not yet reached consensus on the final
resolution of those other issues, but we have a moral responsibility
in what we do for the public interest to push that forward.



Otherwise, we are prejudicing the global domain name system against
half of the world whose native languages are in those other scripts.
So I hope that to fulfill our obligation to act in the public
interest, which we recently reaffirmed by signing the Affirmation of
Commitments, that we will move forward swiftly and professionally and
with due consideration to bring those issues to a closure, so that
people in Thailand, in Korea, in India, and all over the world can
truly use the Internet in their own script for their domain name
needs. Thank you.

Great find!

[Rubber Duck]

He is not particularly intuitive, but he is clever enough to know when he has run out of options. Those that pay the Piper are getting impatient.

[sarcle]

that we will move forward swiftly

First, this is a nice find and very encouraging.

I just have my doubts over what Icann thinks or understands as to what "swiftly" means. How many years have we been waiting for a .IDN? We still don't see it live. I know we are going into a critical and an important period in the Internet's history. This is after all why we have invested.

Now we are finally on track to get the first .IDNs rolling out. But what does "swiftly" mean to an organization that has stalled out on this project; that in all reality should have only taken a couple years.

We're almost there guys.

I'm still wondering how much bureaucracy, red tape, and drama we going to see coming out of the gTLD .IDN process?

[bwhhisc]

Originally Posted by sarcle

First, this is a nice find and very encouraging.

I just have my doubts over what Icann thinks or understands as to what "swiftly" means. How many years have we been waiting for a .IDN? We still don't see it live. I know we are going into a critical and an important period in the Internet's history. This is after all why we have invested.

Now we are finally on track to get the first .IDNs rolling out. But what does "swiftly" mean to an organization that has stalled out on this project; that in all reality should have only taken a couple years.

I'm still wondering how much bureaucracy, red tape, and drama we going to see coming out of the gTLD .IDN process?

The deal was made long ago and its all about timing coordinated timing of idn.com and idn.cctld's aliasing "so as not to disadvantage one another". ICANN has also answered a lot of questions by saying the decisions will be made by each registry...and no doubt Verisign has a johnny on every spot there.

The GNSO Council, in response to ccNSO-GAC report on IDN issues (http://gnso.icann.org/drafts/ccnso-g...se-20feb08.pdf), as well as in its comments on the IDNC WG Final Report (http://gnso.icann.org/issues/idn-tld...rt-14aug08.pdf) expressed that “the introduction of IDN gTLDs or IDN ccTLDs should not be delayed because of lack of readiness of one category, but if they are not introduced at the same time, steps should be taken so that neither category is advantaged or disadvantaged, and procedures should be developed to avoid possible conflicts.”

Further, the GNSO Council made a resolution in January 2009 to assert that “the GNSO Council strongly believes that neither the New gTLD or ccTLD fast track process should result in IDN TLDs in the root before the other unless both the GNSO and ccNSO so agree.”