Sure. I will cover that... -- Dr. Andrzej Bartosiewicz, CEO & President, Yonita Inc. phone (US): +1 650 2493707 phone (Poland): +48 518 235209 Jothan Frakes <jothan@gmail.com> wrote:
Nice work, Andrzej-
You might want to expose the tæst1234.pl (xn--tst1234-mxa.pl) and taest1234.pl homograph potential in this which is something that has occurred since.
https://bugzilla.mozilla.org/show_bug.cgi?id=618051#c12
-Jothan
Jothan Frakes +1.206-355-0230 tel +1.206-201-6881 fax
On Sun, Jul 24, 2011 at 1:43 PM, Andrzej Bartosiewicz <andrzej@yonita.com> wrote:
Dear Steve,
Here are my draft slides for webinar: http://yonita.com/ICANN-IDN-Variants-Bartosiewicz.pdf http://yonita.com/ICANN-IDN-Variants-Bartosiewicz.pptx
Best, Andrzej
On 7/15/2011 7:53 PM, Steve Sheng wrote:
Dear all, the IDN variant project team appreciates your contribution. Based on the request, we will organize a webinar.
Here is a draft agenda:
1. An overview of existing TLD programs related to variants by ICANN staff [15 minutes]
2. Experience of variant handling in ccTLDs [50 minutes]
Five presentations, 7 mins each + 15 mins Q&A
Fahd Batayneh, Iftikhar H. Shah, Behnam Esfahbod, Andrzej Bartosiewicz, Vladimir Shadrunov
4: Overview of DNS mechanisms and status from IETF standards. [7 mins]
5: Outline of RFC discussions about variant handling. [15 mins]
6. 3 min wrap up.
Before we close the queue, are there any others willing to share their experiences?
We will also proceed to arrange a time that speakers can make and announce the dates shortly. Given the global nature of our audience, we may have to run two exact webinars.
Warm regards, IDN Variant Project Team
At 09:40 25/07/2011, Andrzej Bartosiewicz wrote:
Sure. I will cover that...
Dear Andrzeij, I am not sure this introduction covers the IDNA2008 context? We reach the IDNA2008 consensus due to the RFC 5895 draft, that was further on published for information only as it exemplifies one of the many possible ways to address many different real life problems including mapping, variants, etc. Also, you seem to consider variants only in the TLD and domain name context (without indicating the DNS options). However the problem also affects many other Internet protocols. The WG/PRECIS is chartered to help a solution to replace stringprep in these protocols. Don't you think it would be advisable to present all these issues together? This might help a lot? RFC 1958 states: "If there are several ways of doing the same thing, choose one. If a previous design, in the Internet context or elsewhere, has successfully solved the same problem, choose the same solution unless there is a good technical reason not to. Duplication of the same protocol functionality should be avoided as far as possible, without of course using this argument to reject improvements." So, whatever the technical solution, is there is one, should be the same. Or do you think the variant/homograph problem should only be addressed as a general digital ecosystem scripting issue outside of the Internet context ? An Unicode extension as a script table able to cleanly support any entry without any risk of variant and homograph problem because it would be a graphcode only based upon the geometric graphic form. This would be really sympathetic to me as I think this is the only solution on the long range and that ccTLDs could easily contribute in sending a copy of every symbol they accept in a given script, based upon a common fount. I suppose people like ABBY could also help? This field is very wide, isn't it? Lot of consideration ahead, I am afraid. jfc
participants (2)
-
Andrzej Bartosiewicz -
JFC Morfin