[council] Fwd: Proposed Agenda for the GNSO Council Meeting 12 May 2016 at 12:00 UTC.

[Rubens Kuhl]

Although more of an implementation issue, I though it was worthwhile to bring to the Council information uncovered by a registry that ICANN has known since December 2014 and still have not acted upon, regarding flaws in the Red Cross identifiers list, which is discussion item 7. 
>From a policy management perspective, the question at hand is if the currently available review processes are enough for both registries and RC/RC organizations for signaling implementation mistakes are adequate, or if a more formal process is warranted. 


Rubens



>>> Item 7: DISCUSSION – Next Steps in Resolving the Issue of Permanent Protection of Certain Red Cross Identifiers (15 minutes)
> 
> I found few mistakes in the list of Red Cross names 
> (ICANN is aware of it,  but did nothing)
> thus the real names (without mistakes) are not protected =]
> 
> As I understand it is all because of ICANN blind processing of all incoming info from 
> Red Cross without sanity checks (in the first case they effectively blocked russian word for society , 
> without any kind of right to do so - across all new gTLDs).
> 
> here are the info bits:
> 
>> ICANN provided list of Reserved names (requirement of RA, Spec 5, Art 5 & 6)
>> 
>> https://www.icann.org/sites/default/files/packages/reserved-names/ReservedNames.xml
> 
> 
> This one on mistake caused by someone pushed ENTER in the middle of the name
> (known to ICANN since dec 2014)
> 
>> We have found the generic term which was added, most probably by mistake into 
>> the addition to the last version (2014-12-10) of the list of the Reserved names:
>> International Red Cross and Red Crescent Movement - International Committee of the Red Cross and International Federation of the Red Cross and Red Crescent Societies Names
>> 
>> https://www.icann.org/sites/default/files/packages/reserved-names/ReservedNames.xml
>> 
>> the string:
>> общество    
>> xn--90aci8adqh7c
>> 
>> One of the meanings is a generic term for 'society' in russian language (also 'public' in it's broad meaning … like entire society).
>> 
>> And it would be seen like a cybersquatting from the Red Cross with the help of powerful lobby (the situation which was most feared by IPC) and most probably, will hit news.
>> 
>> The reasons to believe it was typo mistake and that there are two strings (mentioned later in 4.)  fell
>> out of the protection due to this mistake:
>> 
>> 1. The website of the http://www.redcrescent.uz/indexe.html
>> Red Crescent Society of Uzbekistan
>> in English
>> or
>> Ўзбекистон Қизил Ярим Ой жамияти
>> in Uzbek
>> or
>> Общество Красного Полумесяца Узбекистана
>> in Russian
>> 
>> 
>> has reference to full name with 'society' in all 3 languages:
>> (also in documents, laws under which it was established in 1992)
>> 
>> 2. string
>> окпу
>> xn--j1aheq
>> is an abbreviation of Общество Красного Полумесяца Узбекистана
>> with first letter о for Общество (Society in Russian)
>> 
>> 3. If we look at the strings from Tadzhikistan Red Cross Society
>> we can see еру pattern:
>> (2 strings in Russian, Russian abbreviation, 2 strings in Tadzhikistan language)
>> 
>> So we could come to the conclusion that Uzbekistan Red Cross Society might have wanted the set of strings
>> designed the same way.
>> 
>> 4. Thus we come to the conclusion that
>> during the preparation of the document,
>> 'enter' was pressed on the keyboard in the wrong place and
>> the first word from
>> общество-красного-полумесяца-узбекистана
>> &
>> обществокрасногополумесяцаузбекистана
>> became a separate string
>> and as a result we see 
>> 3 wrong strings and missed 2 actual strings meant for protection
>> (also we avoid cybersquatting scandal with involvement of Red Cross)
>> 
>> proposed changes
>> ======
>> Strings a1,a2,a3 from bellow 
>> Should be replaced with strings b1,b2. Strings a1,a2,a3 should be released from the obligatory reserved list.
>> 
>> a1.
>> общество    xn--90aci8adqh7c
>> a2.
>> красного-полумесяца-узбекистана
>> xn-----6kcbbafmtduoqjiqnnfbbvqzkh1aqf1g5n
>> a3.
>> красногополумесяцаузбекистана
>> xn--80aaaadkocqmohhomlfbatpxjgzpe6f0n
>> 
>> should be replaced with
>> b1.
>> общество-красного-полумесяца-узбекистана
>> xn------6cdbbabfenufd2asyjmurncdebb1awzgkhi0ayf5i5dwm
>> and
>> b2.
>> обществокрасногополумесяцаузбекистана
>> xn—80aaaabcejpdcwpuhkrplcddbayuxfjgixwe7h1d7l
>> 
> 
> and this one is Mixed script:
> (known to ICANN since jun 2015)
>> 
>> tчху 
>> (xn--t-cubfh)
>> 
>> instead of first letter to be from cyrillyc script it is from latin 't'
>> 
>> if you check two lines which are right above it
>> 
>> товариство-червоного-хреста-україни
>> xn------5cdcbibbkud6ak2a6bhcedbb9afhejoigp8a0d2cz1b
>> 4 letter abbreviation should be 
>> тчху
>> (xn--r1acfh)
>>