[Idngwg] Suggestions for items for discussion

[Wael Nasr]

Dear All
I think another very important issue also is the contention rules in IDN
such as Arabic . Not 100% sure if this belongs to this group . there is a
serious concern regarding the answer to the question :

will icann allow "hotel" "hotels" and thehotel and myhotel to be applied
for and operated as separate TLDs.

I am prepared to spend time with the right subgroup to develop suggested
rules particularly when this is not a trivial issue in Arabic...there could
be 10 or more strings that are confusingly similar in Arabic with
confusingly similar meaning etc .

This might belong to the language rather than a guidelines group.

Please advise ?
wael

On Tue, Nov 24, 2015 at 2:36 PM, Sarmad Hussain via Idngwg <idngwg at icann.org
> wrote:

> Dear All,
>
> Here are more items which may be considered for further discussion.  As
> discussed, I am suggesting a liberal list.
>
> 1.      Transition and Terminology
>
> a.      Any (residual) issues/items from IDNA2003 to IDNA2008 transition?
>
> b.      Glossary of terms around LGRs and variants from the IDN TLD
> project and other work
>
> 2.      Language table format and managing consistency of end-user
> experience
>
> a.      IDN Table format in XML, based on new LGR specifications being
> developed
>
> b.      Role of reference second level tables in managing consistency and differences
> across TLDs for a predictable end-user experience
>
> c.      Relationship between language tables and script tables? Other
> categories (some languages but not entire script)?
>
> d.      Managing consistence across levels;  relationship of Root Zone
> LGR and the second level IDN tables?
>
> 3.      Variants
>
> a.      Variant states (number and nomenclature) and state-change
> mechanisms (e.g. blocked, allocatable, allocated, reserved, etc.)
>
> b.      Primary vs. secondary variants in Chinese language (other scripts
> or languages?)
>
> c.      Policy for activating variants
>
> i.      Automatic or registrant requested allocation
>
> 1.      Automatic activation of variant labels at second level for
> Chinese language domain names
>
> ii.     Minimum and Maximum number of allocated variants/Ceiling value?
>
> iii.    Choosing which variants may be activated
>
> d.      Variants at second level must(?) be allocated to the same
> registrant?
>
> e.      Implication of second level variants on TMCH
>
> 4.      Similarity/Confusability of labels
>
> a.      Homographic issues within script
>
> i.      General homographic issues within a script
>
> ii.     Scope of confusability: upper to lower case mapping
>
> b.      Cross-script homoglyphs management to prevent phishing
> possibilities– cox.com, where “cox” can be in Latin or Greek or Cyrillic
>
> i.      Script mixing within a second level label
>
> ii.     Script mixing across levels
>
> iii.    Scope of confusability: upper to lower case mapping
>
> iv.     Is ASCII a special case for mixing?
>
> 5.      Registration data
>
> a.      Registration data for IDNs
>
> b.      Registration data of variants – information regarding variant
> sets and variant label disposition(s)
>
>
> Regards,
> Sarmad
>
>
> _______________________________________________
> Idngwg mailing list
> Idngwg at icann.org
> https://mm.icann.org/mailman/listinfo/idngwg
>
>


-- 
---------------------------
Wael Nasr
SVP - TLDVIilla LLC
http://icannwiki.com/Wael_Nasr
http://www.linkedin.com/in/nasrwael
US Office : +1 209 682 5144.
Bahrain mobile :+973 393 16891
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20151124/dbfca534/attachment.html>