![]() |
|
|||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
This week, the Internet Corporation for Assigned names and Numbers or ICANN is holding its Annual General Meeting in Sao Paulo, the largest commercial hub in South America, where incidentally it has been raining almost continually for the past ten days or so. ICANN is the body that coordinates addresses on the internet. Paul Twomey, CEO of ICANN always goes to great lengths to explain that the organisation does not control or manage the Internet. He likes to compare his sophisticated set up to a snail mail postal service, where ICANN coordinates the postal address system - but does not deliver the letters, does not set prices and does not say what people can put in the envelopes. Twomey says that ICANN does not deal with e-commerce nor does it set any rules regarding hate speech or pornography ? in fact it has nothing to do with content at all. Now we know what ICANN does NOT do ? so what does it do and what is the Sao Paulo meeting all about? First of all, although the organisation is headquartered in California where it was originally incorporated, the council makes an effort to be inclusive by holding meetings in various parts of the globe.
It's also a great way to see the world. In 2004 the final meeting of the year was held in Cape Town. One of the most important topics of discussion here at the Sao Paulo meeting concerns Internationalised Domain Names or IDNs. When the Internet was initially set up, addresses could only use the 26 letters of our Latin alphabet; the numbers from zero to nine and a hyphen - the system is known as LDH - or Letters, Digits and Hyphen. This is very problematic for people in countries where English is not a common language - and it can create a lot of confusion. Here in Brazil where Portuguese is the spoken language, people need to write addresses with a C cedilha - the C with a little tail - and a number of letters with accents. The LDH system ignores character sets used by billions of people in countries such as China, Ethiopia, Japan, Egypt and Russia. There is also a serious risk of confusion when an individual letter is pronounced differently in diverse languages. For example the letter that looks like a "P" in English is in fact an "R" in Russian. Our letter "Y" has the value of a "U" in Russian. You might have noticed that Russian language web sites use the country code of dot RU - which is fine if you are using the Latin alphabet and thinking in English. But if you would prefer the Cyrillic alphabet ? as most Russians do - and thought in Russian - then logically all Russian addresses should end with dot "PY". The problem is that Paraguay has already secured the dot "PY" country code top level domain. This is only a small example of problems created by Internationalised Domain Names. If you add the characters of all the major languages of the world ? the useable character set would have to increase from the existing 37 of the LDH system to more than fifty thousand. So while you ponder the enormity of that problem, I'll go back to the conference. |
|
||||
|
>>BRUCE TONKIN: ...THE OUTCOME OF THE DISCUSSION WE HAD TODAY WAS TRYING TO IDENTIFY A TIME LINE OR A TARGET FOR WHEN IDNS COULD POTENTIALLY BE INTRODUCED. AND THIS TIME LINE NEEDS TO INCORPORATE THE WORK ITEMS OF WHAT'S HAPPENING WITH THE IETF WITH RESPECT TO UPDATING THE PROTOCOL, WHAT'S HAPPENING WITH RESPECT TO THE TESTS THAT ICANN IS RUNNING, A BOARD DECISION TO ALLOW IDNS FROM A TECHNICAL PERSPECTIVE. THEN WE NEED TO LOOK AT THE ADVICE AND THE TIME LINE OF THAT ADVICE FROM THE GAC, THE CCNSO POLICY DEVELOPMENT PROCESS AND THE GNSO NEW GTLD POLICY DEVELOPMENT PROCESS.
THERE IS A LOT OF INTERCONNECTING EVENTS HERE AND WE FEEL THAT WE NEED TO TAKE A PROJECT MANAGEMENT APPROACH WHERE WE IDENTIFY ALL THESE EVENTS, IDENTIFY THE DEPENDENCIES BUT HAVE A CLEAR TARGET TO TRY TO INTRODUCE THESE IDNS, ASSUMING THAT THE TECHNICAL TESTS ARE SUCCESSFUL... Looks like a job for Alphamale!
__________________
Yours RD. Sales threads older than 30 days are void unless stated otherwise. |
|
||||
|
....I THINK A GENERAL COMMENT I WOULD MAKE WITH RESPECT TO REFORMING THE GNSO AND I THINK IT IS THE SAME COMMENT AS REFORMING ICANN IS THAT WE EFFECTIVELY HAVE -- AND I WILL USE AIRLINE ANALOGY. WE HAVE THREE FLIGHTS THAT ARE CURRENTLY FLYING IN THE AIR AT THE MOMENT. AND THEY ARE ALL PRETTY IMPORTANT. THEY RELATE TO NEW GTLDS, THEY RELATE TO IDNS AND THEY RELATE TO WHOIS. EACH OF THOSE FLIGHTS ARE CURRENTLY FLYING.
WE ACTUALLY WANT TO LAND THOSE FLIGHTS AT SOME TIME AND WE RECOGNIZE THAT IT IS ALWAYS VERY ENTERTAINING TO START FIDDLING AROUND THE WITH SYSTEMS WHILE THEY ARE IN FLIGHT, BUT LET'S MAKE SURE THAT WE KEEP THE PLANES FLYING AND IN PARTICULAR WE HAVE A CLEAR TIMETABLE FOR LANDING THOSE PLANES AND DON'T END UP WITH THOSE PLANES IN A HOLDING PATTERN AROUND THE AIRPORTS SO WE DO WANT TO LAND THEM... I am beginning to warm to this guy!
__________________
Yours RD. Sales threads older than 30 days are void unless stated otherwise. |
|
|||
|
Quote:
errrr, if they havent already been doing that for the last few years, what approach have they been taking? The old i'll engage head in sand and hope the shoe fairies fix it ?
__________________
Theres a storm coming...
|
|
||||
|
Quote:
Hell, what's the point? You were right the first time!
__________________
Yours RD. Sales threads older than 30 days are void unless stated otherwise. |
|
|||
|
Looks like no IDN decisions made by the ICANN Board this round, just a resounding "you're all doing very well". Mrs Slocombe would be proud.
__________________
Blame Edwin. |
|
||||
|
Quote:
__________________
Yours RD. Sales threads older than 30 days are void unless stated otherwise. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|