November 2017 - UA-discuss

Domainers
by Andre Schappo Dec. 5, 2017

Dec. 5, 2017

Would IDNs even exist today if it was not for Domainers? I suspect that IDNs would have been abandoned long ago if it was not for Domainers. I believe that Domainers are the majority holders of IDNs. The dependency on Domainers is well emphasised in the thread http://www.idnforums.com/forums/35654-number-of-%E3%82%B3%E3%83%A0-registra…<http://www.idnforums.com/forums/35654-number-of-コム-registrations-takes-a-no…> I think the international community should be acknowledging and thanking Domainers for their significant contribution to IDNs. André Schappo

6 7

Re: [UA-discuss] Domainers
by Michele Neylon - Blacknight Dec. 1, 2017

Dec. 1, 2017

The .ie ccTLD introduced IDN in .ie recently so that our local ccTLD could finally support the Irish language. You can now register a .ie domain using a fada (the accent) See http://fada.ie/ (disclosure: we run it) Domainers had absolutely nothing to do with that decision. Zero. Nada. While the takeup of IDNs in .ie hasn’t been exactly “huge” it has allowed companies and other organisations whose names included fadas to register their “real” name. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ https://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845 From: UA-discuss <ua-discuss-bounces(a)icann.org> on behalf of Andre Schappo <A.Schappo(a)lboro.ac.uk> Date: Thursday 23 November 2017 at 10:07 To: Universal Acceptance <UA-discuss(a)icann.org> Subject: [UA-discuss] Domainers Would IDNs even exist today if it was not for Domainers? I suspect that IDNs would have been abandoned long ago if it was not for Domainers. I believe that Domainers are the majority holders of IDNs. The dependency on Domainers is well emphasised in the thread http://www.idnforums.com/forums/35654-number-of-%E3%82%B3%E3%83%A0-registra…<http://www.idnforums.com/forums/35654-number-of-コム-registrations-takes-a-no…> I think the international community should be acknowledging and thanking Domainers for their significant contribution to IDNs. André Schappo

4 3

Co-Coordinator - EAI Working Group
by Don Hollander Nov. 29, 2017

Nov. 29, 2017

Dear all: We recently received notice from Mark Svancarek that he would like to withdraw from the co-convener role of the EAI Working group but will retain his other role as Vice-Chair of the UASG. Mark takes pain to note that he is not reducing his overall commitment to the UASG nor the EAI Working Group. He is seeking to broaden the participation in the UA Coordination Group. We are now looking for a replacement co-convener (Jiankang Yao is the other co-convener) for the EAI Project group of the UASG. The EAI project group is one of two project groups within the UASG (the other is Community Outreach). From the UASG Charter: Each Project Group will be led by one to two Coordinators, an appointed role by the Steering Group Chair without specific term. Each group will develop budgets (resource, staffing and money) necessary to complete specific projects and develop sourcing strategies. … Project Group leaders should submit a Statement of Interest that is publicly accessible, and lists their affiliations and interests. Project Groups can spawn additional smaller working parties…. If you’re interested in this role, would you please send an email with your expression of interest and explanation why you should be chosen for this role to don.hollander(a)icann.org <mailto:don.hollander@icann.org> by the 30th of November 2017. Interviews will be conducted and a decision is expected shortly after this deadline. The decision is up to the Chair of the UASG. If you have any questions, please don't hesitate to ask. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

3 3

"Universal Acceptance of non-Latin email addresses and domain names: how does your framework rate?" (IUC41 presentation)
by Jim DeLaHunt Nov. 27, 2017

Nov. 27, 2017

UA Colleagues: Last month I got to present UASG0018 and UA, at the 41st Internationalization and Unicode Conference (IUC41) in Santa Clara, California. The talk was, "Universal Acceptance of non-Latin email addresses and domain names: how does your framework rate?". It explains UA, and the library evaluation method of UASG0018. It urges app developers to use UASG0018 to guide their own evaluation of their own libraries for Universal Acceptance. Description of the content: <http://blog.jdlh.com/en/2017/10/31/universal-acceptance-eval-iuc41/> (as blog post) Direct link to the slides: <http://go.jdlh.com/iuc41s10t2> (PDF, 6.3MB). Comments welcome, either direct to me or on this list or on the blog post. I had meant to send this earlier, sorry. I also gave a tutorial introducing Universal Acceptance, and I'll send a link to that in a separate email thread. Best regards, —Jim DeLaHunt, Vancouver, Canada -- --Jim DeLaHunt, jdlh(a)jdlh.com http://blog.jdlh.com/ (http://jdlh.com/) multilingual websites consultant 355-1027 Davie St, Vancouver BC V6E 4L2, Canada Canada mobile +1-604-376-8953

1 0

UA in News
by Dr Ajay Data Nov. 27, 2017

Nov. 27, 2017

Dr. Ajay DATA | Founder &amp CEO Get email id like अजय(a)xn--c2bd1gb.xn--h2brj9c in your own language,visit www.xgenplus.com Do not Remove: [HID]20171126113310622[-HID]

3 2

Re: [UA-discuss] Update to UASG006 - Relevant RFCs
by Tan Tanaka, Dennis Nov. 21, 2017

Nov. 21, 2017

I think it is appropriate. But I suggest using this link instead https://tools.ietf.org/html/rfc3492 because it has the links to errata, other references, etc. -Dennis From: UA-discuss <ua-discuss-bounces(a)icann.org> on behalf of Don Hollander <don.hollander(a)icann.org> Date: Tuesday, November 21, 2017 at 2:42 PM To: "UA-discuss(a)icann.org" <ua-discuss(a)icann.org> Subject: [EXTERNAL] [UA-discuss] Update to UASG006 - Relevant RFCs I would like to add https://www.ietf.org/rfc/rfc3492.txt to this (https://uasg.tech/wp-content/uploads/2017/06/UA006-Relevant-RFCs.pdf) document. Any comments? Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

3 2

Update to UASG006 - Relevant RFCs
by Don Hollander Nov. 21, 2017

Nov. 21, 2017

I would like to add https://www.ietf.org/rfc/rfc3492.txt <https://www.ietf.org/rfc/rfc3492.txt> to this (https://uasg.tech/wp-content/uploads/2017/06/UA006-Relevant-RFCs.pdf <https://uasg.tech/wp-content/uploads/2017/06/UA006-Relevant-RFCs.pdf>) document. Any comments? Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

1 0

Progress on HTML and email...
by Chaals McCathie Nevile Nov. 20, 2017

Nov. 20, 2017

Hi, just to note that this week we reached a provisional agreement to change the HTML email input type, and make it accept a unicode value before the "@" instead of the current restriction to ASCII. Once we get this change made and published - hopefully in a few weeks - we would appreciate help encouraging browsers to implement it fast. cheers chaals -- Chaals is Charles McCathie Nevile find more at http://yandex.com

12 23

Re: [UA-discuss] Progress on HTML and email...
by Chaals McCathie Nevile Nov. 15, 2017

Nov. 15, 2017

On Mon, 13 Nov 2017 06:07:44 +0100, Dr. Ajay Data <ajay(a)data.in> wrote: > This is good initiative. I have few queries challs. > > 1. After @ , are you not checking / validating. What's the plan.? > 2. Any specific reason, team decided to consider for before @ only? We split this into two parts in HTML, so I will describe what we did for "after the @" and then what we are planning for "before the @" Please note: 1. We do not put things into an HTML Recommendation without real-world implementation. Help from this group to identify concrete implementations would be very useful in getting support for changes. 2. We aim to publish an HTML version about every year. 3. We are only discussing here the "email" input type for HTML forms, specified at <https://w3c.github.io/html/sec-forms.html#email-state-typeemail> ==After the @ In HTML 5.2, which we have effectively finalised and hope to publish this year, we tried to deal with some of the issues "after the @". We didn't specify full unicode transfer, due to concerns expressed about how compatible that would be with reality. We did try to encourage user agents (e.g. browsers, or scripts in content) to accept "unicode" domain names - roughly, anything that can be validated as a punycode domain, and handle the conversion invisibly - so the user types and sees e.g. chaals(a)xn--d1acpjx3f.xn--p1ai, but under the hood the representation is punycode which is what gets transferred. It seems that we should consider this issue again. If someone is confident that there is sufficient implementation to justify browsers sending stuff directly in unicode, please contact me and I will raise the issue on the HTML spec - or feel free to do so yourself, as noted elsewhere, at https://github.com/w3c/html/issues ==Before the @ We had a face to face meeting last week which had a short time for HTML and at which we considered one technical issue - the question of what should be allowed before the "@", and whether we should keep the email input type in the first place. Note that if we were starting from the beginning, the email input type would be quite different - we have learned that there are numerous problems with the way it was designed. But it is useful, and its continued existence does not create new problems, so for now we resolved to keep it. We also provisionally agreed that before the "@" we should accept a unicode label, not just ASCII which is what is currently required - and has been for over a decade without change. In practice this means we need to change the specification to remove the current validation, and specify correctly what is allowed. Text for this would be appreciated, but otherwise it will say something like "blablabla NFC unicode string blablabla user agents should convert what they get from users appropriately blablabla" This is currently being tracked in an issue: https://github.com/w3c/html/issues/845 cheers Chaals > > > > > Thanks. > > > AD > > On 12 November 2017 08:43:54 GMT+05:30, Chaals McCathie Nevile > <chaals(a)yandex.ru> wrote: >> >> Hi, >> >> just to note that this week we reached a provisional agreement to >> change the HTML email input type, and make it accept a unicode value >> before the "@" instead of the current restriction to ASCII. Once we get >> this change made and published - hopefully in a few weeks - we would >> appreciate help encouraging browsers to implement it fast. >> >> cheers >> >> chaals > > > -- > Sent from my Android device with XGenPlus. -- Chaals is Charles McCathie Nevile find more at http://yandex.com

1 0

Re: [UA-discuss] Sieve protocol internationalization
by Vittorio Bertola Nov. 15, 2017

Nov. 15, 2017

> Il 15 novembre 2017 alle 4.47 "Dr. Ajay Data" <ajay(a)data.in> ha scritto: > > I would be happy to discuss and work.. please connect. > > However, this much we are doing already on server side with EAI > > Messages from a certain sender address. ...Messages to a certain address. ...The difference between header addresses and envelope addresses. ...Messages from a name...Detecting mailing lists. ... > Did you implement this in Sieve, or does your platform use another language / mechanism for specifying mail filtering rules? Regards, -- Vittorio Bertola Research & Innovation Engineer Cell: +39 348 7015022 Skype: in-skype-ox(a)bertola.eu Email: vittorio.bertola(a)open-xchange.com mailto:vittorio.bertola@open-xchange.com Twitter: @openexchange http://twitter.com/openexchange - Facebook: OpenXchange https://www.facebook.com/OpenXchange - Web: www.open-xchange.com http://www.open-xchange.com Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738 Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein Chairman of the Board: Richard Seibt European Office: Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718 Managing Directors: Frank Hoberg, Martin Kauss US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system.

1 0