- UA-discuss - lists.iana.org

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

Sieve protocol internationalization
by Vittorio Bertola Nov. 15, 2017

Nov. 15, 2017

Hello, I just wanted to note that I am at the IETF in the Extra WG, and after consulting with the people in my company that work on the evolution of IMAP etc, we brought up the need to update the Sieve protocol specification to make it fully EAI-ready (it still is not). The WG generally agreed that this is an issue that they need to pick up and asked us to submit an initial Internet draft for consideration. So, perhaps it would be useful if the UASG got in touch with the WG chair, if you are not already - I just talked to him explaining him briefly what the UASG is, I can provide pointers / make introductions if necessary. 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.

3 2

Re: [UA-discuss] UA-discuss Digest, Vol 35, Issue 8
by Harish Chowdhary Nov. 13, 2017

Nov. 13, 2017

Great Job.Thanks,Harish Chowdhary,ISOC IETF FELLOWinSIG 2017 FELLOWwww.nixi.in | www.indiaig.in From: ua-discuss-request(a)icann.orgSent: Sun, 12 Nov 2017 17:30:09 GMT+0530To: ua-discuss(a)icann.orgSubject: UA-discuss Digest, Vol 35, Issue 8Send UA-discuss mailing list submissions to   ua-discuss(a)icann.orgTo subscribe or unsubscribe via the World Wide Web, visit   https://mm.icann.org/mailman/listinfo/ua-discussor, via email, send a message with subject or body 'help' to   ua-discuss-request(a)icann.orgYou can reach the person managing the list at   ua-discuss-owner(a)icann.orgWhen replying, please edit your Subject line so it is more specificthan "Re: Contents of UA-discuss digest..."Today's Topics:  1. Progress on HTML and email... (Chaals McCathie Nevile)  2. Re: Progress on HTML and email... (Jiankang Yao)  3. Re: Progress on HTML and email... (Don Hollander)  4. Re: Progress on HTM L and email... (Satish Babu)  5. Re: Progress on HTML and email... (Abdalmonem Tharwat Galila)----------------------------------------------------------------------Message: 1Date: Sun, 12 Nov 2017 04:13:54 +0100From: "Chaals McCathie Nevile" <chaals(a)yandex.ru>To: "ua-discuss(a)icann.org" <ua-discuss(a)icann.org>Subject: [UA-discuss] Progress on HTML and email...Message-ID:   <op.y9klpusbftbnq3@desktop-kurf4r9.daskysfot1.sfo.wayport.net>Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yesHi,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.cheerschaals--Chaals is Charles McCathie Nevilefind more at http:// yandex.com------------------------------Message: 2Date: Sun, 12 Nov 2017 11:18:13 +0800 (GMT+08:00)From: "Jiankang Yao" <yaojk(a)cnnic.cn>To: "Chaals McCathie Nevile" <chaals(a)yandex.ru>Cc: "ua-discuss(a)icann.org" <ua-discuss(a)icann.org>Subject: Re: [UA-discuss] Progress on HTML and email...Message-ID: <64c7904d.21f4.15fae3c139a.Coremail.yaojk(a)cnnic.cn>Content-Type: text/plain; charset=UTF-8Dear chaals, A very good news! That is a great job done. Thanks for your great contribution!Jiankang Yao> -----????-----> ???: "Chaals McCathie Nevile" <chaals(a)yandex.ru>> ????: 2017-11-12 11:13:54 (???)> ???: "ua-discuss(a)icann.org" <ua-discuss(a)icann.org>> ??:> ??: [UA-discuss] Progress on HTML and email...>> 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 &nb sp;> "@" 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------------------------------Message: 3Date: Sun, 12 Nov 2017 03:54:29 +0000From: Don Hollander <don.hollander(a)icann.org>To: Chaals McCathie Nevile <chaals(a)yandex.ru>Cc: Universal Acceptance <ua-discuss(a)icann.org>Subject: Re: [UA-discuss] Progress on HTML and email...Message-ID: <0D37433C-FB93-41C3-9310-C037A5ADB94F(a)icann.org>Content-Type: text/plain; charset="utf-8"That is indeed good news.Are there other constraints to the email input type?  Does it allow unicode on the other side of the ?@??   Does it include any validation?   And field length constraints?D> On 12/11/2017, at 4:13 PM, 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>> --> Chaals is Charles McCathie Nevile> find more at http://yandex.comDon HollanderUniversal Acceptance Steering GroupSkype: don_hollander-------------- next part --------------A non-text attachment was scrubbed...Name: smime.p7sType: application/pkcs7-signatureSize: 3869 bytesDesc: not availableURL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20171112/5e8d846b/smime-0001.p7s>------------------------------Message: 4Date: Sun, 12 Nov 2017 09:34:15 +0530From: Satish Babu <sb.inapp(a)gmail.com>To: Don Hollander <don .hollander(a)icann.org>Cc: ua-discuss <UA-discuss(a)icann.org>Subject: Re: [UA-discuss] Progress on HTML and email...Message-ID:   <CAA8UJvCQNmprxZn0k6OZ+fdb_SK6xV9QGNdHd4T6iyJODEAp0Q@mail.gmail.com>Content-Type: text/plain; charset="utf-8"This is a great step.Is there a document that sets out the context for this spec and providesthe full details ? It would be useful for outreach.satishOn Nov 12, 2017 9:24 AM, "Don Hollander" <don.hollander(a)icann.org> wrote:That is indeed good news.Are there other constraints to the email input type?  Does it allow unicodeon the other side of the ?@??   Does it include any validation?   And fieldlength constraints?D> On 12/11/2017, at 4:13 PM, Chaals McCathie Nevile <chaals@yandex.ru>wrote:>> Hi,>> just to note that this week we reached a provisional agreement to changethe HTML email input type, and make it accept a unicode value before the"@" instead of the current restriction to ASCII. Once we get this changemade and published - hopefully in a few weeks - we would appreciate helpencouraging browsers to implement it fast.>> cheers>> chaals>> --> Chaals is Charles McCathie Nevile> find more at http://yandex.comDon HollanderUniversal Acceptance Steering GroupSkype: don_hollander-------------- next part --------------An HTML attachment was scrubbed...URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20171112/01580226/attachment-0001.html>------------------------------Message: 5Date: Sun, 12 Nov 2017 10:38:09 +0000From: Abdalmonem Tharwat Galila <agalila(a)mcit.gov.eg>To: Chaals McCathie Nevile <chaals(a)yandex.ru>, "ua-discuss@icann.org"   <ua-discuss@icann.org>Subject: Re: [UA-discuss] Progress on HTML and email...Message-ID:   <147aacd99c03465885fc3ced08199524@MCIT-B1MBBK-02.mcit.core.local>Content-Type: text/plain; charset="ut f-8"Greet news , Appreciate itIf there will be a test pilot for that , I am happy to see it.-----Original Message-----From: UA-discuss [mailto:ua-discuss-bounces@icann.org] On Behalf Of Chaals McCathie NevileSent: Sunday, November 12, 2017 5:14 AMTo: ua-discuss(a)icann.orgSubject: [UA-discuss] Progress on HTML and email...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.cheerschaals--Chaals is Charles McCathie Nevilefind more at http://yandex.com------------------------------Subject: Digest Footer_______________________________________________UA-discuss mailing listUA-discuss@icann.orghttps://mm.icann.org/mailman/listinfo/ua-discuss------------------------------End of UA-discus s Digest, Vol 35, Issue 8***************************************** ------------------------------------------------------------------------------------------------------------------------------- [NIXI is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/nixiindia & Twitter: @inregistry ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. -------------------------------------------------------------------------------------------------

1 0

Draft Notes - UASG @ ICANN60
by Don Hollander Nov. 12, 2017

Nov. 12, 2017

Draft Notes attached. Comments and corrections most welcome indeed. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

3 2

Re : Draft Notes - UASG @ ICANN60
by Dr Ajay Data Nov. 9, 2017

Nov. 9, 2017

Wonderful Capture of Minutes. Great job done. I have few actionable in my name.. and here is the action and response.. ?Ajay Data &ndash re: business case failures vs system failures - Help define in more detail what a discriminating test would look like (client &ndash vs server errors/validation). Potentially take the error message into a count . Client Validation: Input box for email or domain names 1) accepts the IDN / EAI without throwing or restricting the UTF8 character 2) After entry of IDN / EAI , shifts focus on other input field and do not throw any error 3) On submit / save , it do not through any error. Server Validation: On Submit, 1) user receives the confirmation page / notification for successful save and in almost most cases, 2) user receives the confirmation of entry or for validation of email on EAI addresses.------------#NPC #digitalINdia and #GCCS2018. Dr Data to provide links to these.NPC: sangeeta DigitalIndia - ajay kumar GCCS2018 - ajay kumar + chitrita chatterjee , -----------Ajay Data &ndash spec out the enhancement to the UASG.TECH site regarding the collection of EAI addressed with a price/lotteryPlease connect me with the uasg.tech website tech person, I will discuss and frame the specs. -----------All &ndash register at least one EAI address with Dr. Data&rsquos systems at mail.yesicann.orgPlease send email to me personally with a request for ID, I will be happy to connect you and get the EAI ID created. Dusan took the lead, already got his domain hosted and got his EAI ID activated in Cyrillic script. ----------If anything else is left, please do let me know. Thanks. Dr. Ajay DATA | Founder &amp CEO Get email id like अजय(a)xn--c2bd1gb.xn--h2brj9c in your own language,visit www.xgenplus.com From: Don Hollander MailId : [75398066]To: Universal Acceptance Subject: [UA-discuss] Draft Notes - UASG @ ICANN60Date: 09 Nov 2017 06:06:13 PM Draft Notes attached.Comments and corrections most welcome indeed.DonDon HollanderUniversal Acceptance Steering GroupSkype: don_hollanderHID] Do not Remove: [HID]20171109180613580[-HID]

1 0

Re: [UA-discuss] Draft Notes - UASG @ ICANN60
by Tan Tanaka, Dennis Nov. 9, 2017

Nov. 9, 2017

Looks pretty accurate to me. Thanks Don and Rich for the notes. -Dennis On 11/9/17, 7:35 AM, "Don Hollander" <ua-discuss-bounces(a)icann.org on behalf of don.hollander(a)icann.org> wrote: Draft Notes attached. Comments and corrections most welcome indeed. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

1 0

The Open Dot as a label delimiter in Chinese and Japanese
by Don Hollander Nov. 7, 2017

Nov. 7, 2017

G’day: The UASG has in the past indicated that good practice is to treat the Open Dot as a label delimiter, just like the traditional full-stop. The ideographic full stop (U+3002 [。]) is used in languages such as Chinese or Japanese to mark the end of a sentence. UASG004 states “We expect software to transform the ‘open dot’ to a standard ASCII dot “.”, thus making use of the already registered domain name.” We found that some browsers do this. As we go through the Linkification review, we’re not seeing this happen for social media communications apps. Does anyone have reference or even perception to how widely used the Open Dot is in Chinese, Japanese and/or other script? Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

10 17

Contacts at Social Media Organisations
by Don Hollander Nov. 7, 2017

Nov. 7, 2017

The UASG is currently reviewing the UA Readiness of a 23 different social media applications. If you work for one of these or know someone who works for one of these, would you please let me know? We want to give them an opportunity to review the results before publication to make sure that we’ve not missed anything. Thanks. Don PS: We have Skype and LinkedIn covered. Facebook What'sApp Facebook Messenger QQ WeChat Qzone Tumblr Instagram Twitter Baidu Tieba Skype Sina Weibo Viber RenRen Line Snapchat YY LinkedIn Vkontake Pinetrest BBM Telegram Kakao Don Hollander Universal Acceptance Steering Group Skype: don_hollander

3 2