- UA-discuss - lists.iana.org

Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt
by nalini.elkins＠insidethestack.com March 13, 2017

March 13, 2017

> It's worth noting that, to some extent, there is literally nothing we > can do about this. The overarching problem of confusables is a > problem of character repertoire, typography, human-computer > interfaces, and psychodynamics. In the right context, "corn" and > "com" look pretty similar. I wonder. So, if the problem is hard, then we give up? One relatively easy suggestion might be that registries, ALL registries, attempt to detect such names. Don't let the perfect be the enemy of the good. I think I have heard you, actually, quote that in some presentation. Nalini

2 1

Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt
by nalini.elkins＠insidethestack.com March 13, 2017

March 13, 2017

>Are these all single-script creations? No. > I fear your algorithm is rather more expansive than is reasonable. We will see if it is. Let's see what combinations of scripts are actually being registered. > This is hardly the first time the issue has been studied. The combinatorial explosion problem is a well-known and well-discussed one. The ICANN Variant Issues > Project explored an awful lot of this. Whatever they did or didn't do, what is going on in reality is that people are doing this and no one is stopping them. Nalini -------------------------------------------- On Mon, 3/13/17, Andrew Sullivan <ajs(a)anvilwalrusden.com> wrote: Subject: Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt To: ua-discuss(a)icann.org Date: Monday, March 13, 2017, 8:14 AM On Mon, Mar 13, 2017 at 02:46:42PM +0000, nalini.elkins(a)insidethestack.com wrote: > Of course, it is not just the "decoration" that is of interest. > There are quite a few other characters from other scripts that are > confusable possibilities. In general, cross-script registration is a bad idea. We have known this since at least 2003. The LGR work points out that script-language definitions is generally a good idea for multi-language scripts. > It is an interesting problem. For example, we took one 6 character > name of a business which is trademarked & ran it through my > algorithm, we came up with over 1 million possible permutations. > This is because you can use more than one character look-alike. Are these all single-script creations? I fear your algorithm is rather more expansive than is reasonable. This is hardly the first time the issue has been studied. The combinatorial explosion problem is a well-known and well-discussed one. The ICANN Variant Issues Project explored an awful lot of this. > Lest you think that this doesn't happen, we have already found names registered which use more than one confusable. Of course it happens. That's actually what all proposals for restrictions are about. > I call them "miscreants" because it is difficult for me to believe that someone who registers a variation of "mybank.com" or "apple.com" has something good on their mind. > It doesn't help us to think clearly about the issues to start trying to do psycological analysis and intention-attribution of the people doing these things. _Regardless_ of the intention, it's an attack vector, and I think that is part of what we need to take into consideration. Best regards, A -- Andrew Sullivan ajs(a)anvilwalrusden.com

1 0

Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt
by nalini.elkins＠insidethestack.com March 13, 2017

March 13, 2017

On Mon, Mar 13, 2017 at 01:22:52PM +0000, Mark Svancarek via UA-discuss wrote: >> >> "Your requested domain name Q has been identified as one likely to cause user confusions due to its mix of >> characters and character sets. (See our Confusables Policy, here). As a result, ownership of this >> domain name must be bundled with the following additional domain names: >> X >> Y >> Z >> This bundle of domain names is available for the low price of $$. >> Unfortunately, we are not able to offer the domain name Q separately from this bundle. If you are not interested in >> this bundle, might we suggest the following alternatives: >> H >> J >> K > I think most registries doing any kind of variants mostly do this sort of thing. Andrew, from personal experience, I would beg to differ with you. Registries most definitely are not doing any such thing. As far as I can see, very few, if any, policies are in effect. I have seen and been able to buy domains (with the full knowledge and consent of the trademark holder) that one would not believe possible. I have seen, from my monitoring that many others have bought domains which I suspect are NOT with the full knowledge and consent of the trademark holder or as a part of a bundle. Nalini

2 1

Presentations: UASG Workshop @ ICANN58
by Don Hollander March 13, 2017

March 13, 2017

Please see https://uasg.tech/ua-presentations/ <https://uasg.tech/ua-presentations/> for copies of the presentations used in yesterday’s workshop. Notes should be out in the next 24 hours. Don Don Hollander Universal Acceptance Steering Group Skype: don_hollander

1 0

Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt
by nalini.elkins＠insidethestack.com March 13, 2017

March 13, 2017

>Pretty much all of the concerns regarding the character repertoire can be resolved and the registrar level if the registrars would ensure that they did not allow registrations of multiple domain variations that >might confuse their users. Or if they bundled those registrations. There is a potential conflict of interest here. Registries want to sell as many domains as they can as that is how they make money. Thanks, Nalini Elkins Inside Products, Inc. www.insidethestack.com (831) 659-8360 From: Shawn Steele Sent: ‎3/‎12/‎2017 7:33 PM To: Richard Merdinger; Edmon Chung; Mark Svancarek; UA-discuss(a)icann.org Subject: RE: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt My concern is John’s emphasis on creating very restrictive character rule sets. The most restrictive rules created by IDNA2008 have been ignored because of user demand and backwards compatibility. Eg: no-emoji in labels. People want emoji, but IDNA2008 doesn’t permit it. Part of that is compatibility with the permitted IDNA2003 emoji, however there has also been demand for emoji characters newly added to Unicode. I think that it is appropriate to remind registrars that they are responsible for creating sane rules for their spaces, but it is clear that users do not want to be tied to the most restrictive demands of IDNA2008. Implementations appear to be settling on the Unicode provided idna data and I would much prefer to see the IETF standards point to the IDNA character sets provided by Unicode (while still encouraging registrars to do sane things that make sense for their domains). A good example of something a registrar might want to consider could be something like ü. Some spaces may allow ü without much restriction, however for .de, .ch, .at, etc. it might make sense to recognize that ü has an alternate ue spelling and to provide bundling or blocking of domains like müller.ch and mueller.ch. That kind of rule is very domain/language specific. Though it is not called out as some of the bidi rules are, the RFCs allow registrars to implement such a policy if it fits their purposes. Of course many other behaviors are called out by the IDNA2008 rules. Pretty much all of the concerns regarding the character repertoire can be resolved and the registrar level if the registrars would ensure that they did not allow registrations of multiple domain variations that might confuse their users. Or if they bundled those registrations. -Shawn From: Richard Merdinger [mailto:rmerdinger@godaddy.com] Sent: Saturday, March 11, 2017 11:35 PM To: Edmon Chung <edmon(a)registry.asia>; Mark Svancarek <marksv(a)microsoft.com>; UA-discuss(a)icann.org Cc: Shawn Steele <Shawn.Steele(a)microsoft.com> Subject: Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt Agree, thanks for forwarding Mark This was a very cogent statement of affairs relative to the closing out of known IDN issues (or our current inability to do so). I agree with Edmon in that I think the UA effort should strive to be a catalyst here. --Rich From: <ua-discuss-bounces(a)icann.org> on behalf of Edmon Chung <edmon(a)registry.asia> Date: Sunday, March 12, 2017 at 7:11 AM To: 'Mark Svancarek' <marksv(a)microsoft.com>, "UA-discuss(a)icann.org" <UA-discuss(a)icann.org> Cc: 'Shawn Steele' <Shawn.Steele(a)microsoft.com> Subject: Re: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt Thanks for forwarding this Mark, This seems to be something useful for UA, perhaps we should work with the IDN team at ICANN (along with the communities networked from the LGR work) to see where we can best support. Edmon -----Original Message----- From: ua-discuss-bounces(a)icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Mark Svancarek via UA-discuss Sent: Sunday, 12 March 2017 12:58 PM To: UA-discuss(a)icann.org Cc: Shawn Steele <Shawn.Steele(a)microsoft.com> Subject: [UA-discuss] FW: I-D Action: draft-klensin-idna-rfc5891bis-00.txt FYI, too much stuff from John for me to dig into this a.m. -----Original Message----- From: Idna-update [mailto:idna-update-bounces@alvestrand.no] On Behalf Of John C Klensin Sent: Saturday, March 11, 2017 8:25 AM To: idna-update(a)alvestrand.no Subject: FWD: I-D Action: draft-klensin-idna-rfc5891bis-00.txt Hi. For the information of those who may be watching this list but not the IETF announcement one... Asmus Freytag and I have started to put together a draft that addresses a problem with the IDNA2008 specs, specifically that we failed to make the responsibility of registries to define code point and label acceptability rules that were considerably more narrow (and better understood by them) than the full set of labels allowed by RFC 5891-5893. It doesn't actually change anything because that requirement is in the existing specs; it just makes (or tries to make) the requirements painfully clear to those who have been missing or misreading them. It also provides an explicit link between IDNA2008 requirements and ICANN work on repertoires and label generation rules without endorsing that work as more than one thoughtful approach that might be examined for either reference or inspiration. Comments (obviously) welcome. For anyone who might wonder, this document avoids the more controversial IDNA2008 issues including: * Multiple suggestions that we should add emoji, a subset of code points with General Category "So", to the list of code points allowed by IDNA. There are many reasons to not do that but it seems clear that, at some point, the IETF will need to either document those reasons or make the change. Volunteers to put together or work on a document would be welcome. * The non-decomposing code point problem, formerly (and incorrectly) known as the Hamza problem. There has been no discernable activity on this since the IAB Statement and LUCID BOF almost exactly two years ago. I've further updated the working copy of draft-klensin-idna-5892upd- unicode70 to cover additional cases and issues, but, in part because it is clearly inappropriate for a quick-patch individual submission, have been advised to not post it until we have a plan to make progress. So far, there is no such plan. * The (IMO, growing) problem of multiple and inconsistent specifications for IDNs and IDN handling, with different ones being used in different higher-level protocols and areas of the Internet. The use of different specifications and definitions creates opportunities for user and implementer confusion, interoperability difficulties, domain names that cannot be resolved under some circumstances, and various sorts of attacks. The specifications involved include IDNA2008, IDNA2003, assorted local "updates" to IDNA2003 that use versions of Stringprep locally updated to assorted versions of Unicode, and the various versions of UTR#46. The latest version of the latter explicitly allows emoji along with other symbols. A few months ago, I suggested to the IAB I18N program that a document be produced that at least pointed out the problems associated with multiple divergent specifications, but the idea got no traction. It appears to me that, although almost everyone agrees that IDNs, and well- and clearly-functional IDNs, are important, virtually no one is willing to do the hard work, at least unless they are being supported by ICANN (disclosure: I am not) or organizations whose interests lie in selling names, preferably as many of them as possible (I have no support from any of them either). Until and unless that changes, I don't see much prospect for getting those other issues addressed in a way that might lead to consensus documents. john ---------- Forwarded Message ---------- Date: Saturday, March 11, 2017 07:22 -0800 From: internet-drafts(a)ietf.org To: i-d-announce(a)ietf.org Subject: I-D Action: draft-klensin-idna-rfc5891bis-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Internationalized Domain Names in Applications (IDNA): Registry Restrictions and Recommendations Authors : John C Klensin Asmus Freytag Filename : draft-klensin-idna-rfc5891bis-00.txt Pages : 10 Date : 2017-03-11 Abstract: The IDNA specifications for internationalized domain names combine rules that determine the labels that are allowed in the DNS without violating the protocol itself and an assignment of responsibility, consistent with earlier specifications, for determining the labels that are allowed in particular zones. Conformance to IDNA by registries and other implementations requires both parts. Experience strongly suggests that the language describing those responsibility was insufficiently clear to promote safe and interoperable use of the specifications and that more details and some specific examples would have been helpful. This specification updates the earlier ones to provide that guidance and to correct some technical errors in the descriptions. It does not alter the protocols and rules themselves in any way. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-klensin-idna-rfc5891bis/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-klensin-idna-rfc5891bis-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce(a)ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt ---------- End Forwarded Message ---------- _______________________________________________ Idna-update mailing list Idna-update(a)alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update

3 2

Universal Acceptance at ICANN58 - Final program
by Don Hollander March 13, 2017

March 13, 2017

UASG @ ICANN58 – Copenhagen https://schedule.icann.org/event/9nq6/icann-gdd-uasg-workshop <https://schedule.icann.org/event/9nq6/icann-gdd-uasg-workshop> Sunday March 12, 2017 1:45pm - 6:30pm Hall B3 <https://schedule.icann.org/venue/Hall+B3> Working Group <https://schedule.icann.org/type/working+group>, Open Session <https://schedule.icann.org/type/working+group/open+session> Adobe Connect https://participate.icann.org/cph58-hallb3 <https://participate.icann.org/cph58-hallb3> English Audio (Low Bitrate) http://stream.icann.org:8000/cph58-hallb3-en-lo.m3u <http://stream.icann.org:8000/cph58-hallb3-en-lo.m3u> English Audio http://stream.icann.org:8000/cph58-hallb3-en.m3u <http://stream.icann.org:8000/cph58-hallb3-en.m3u> 13:45 15 Welcome & Introduction Ram Mohan 14:00 10 UASG Update Don Hollander 14:10 20 Programming Language Reviews – Evaluation Criteria Sara Dickson 14:30 30 White Paper Draft Review Michael Kende 15:00 20 Break 15:20 40 Communications Lars Steffan & Andrew Robertson 16:00 15 Issues Logging Michaela Quinzy 16:15 30 UA & Phishing & Spam Lars Steffan & Peter Myer 16:45 15 ICANN IT Sigmund Fidyke 17:00 20 Updates from Communities Thailand Germany Argentina 17:20 40 EAI - Community Update - Quick Guide - Testing - April Meeting Mark Svancarek 18:00 30 General Discussion, Parking Lot - UA & Internet Industry Ram/Don UASG/GAC Sunday March 12, 2017 6:30pm - 7:00pm Hall A2 (GAC) <https://schedule.icann.org/venue/Hall+A2+%28GAC%29> General Session / Plenary <https://schedule.icann.org/type/general+session+%2F+plenary>, Open Session <https://schedule.icann.org/type/general+session+%2F+plenary/open+session> Adobe Connect https://participate.icann.org/cph58-halla2 <https://participate.icann.org/cph58-halla2> English Audio (Low Bitrate) http://stream.icann.org:8000/cph58-halla2-en-lo.m3u <http://stream.icann.org:8000/cph58-halla2-en-lo.m3u> English Audio http://stream.icann.org:8000/cph58-halla2-en.m3u <http://stream.icann.org:8000/cph58-halla2-en.m3u> Arabic Audio (Low Bitrate) http://stream.icann.org:8000/cph58-halla2-ar-lo.m3u <http://stream.icann.org:8000/cph58-halla2-ar-lo.m3u> Portuguese Audio http://stream.icann.org:8000/cph58-halla2-pt.m3u <http://stream.icann.org:8000/cph58-halla2-pt.m3u> Spanish Audio (Low Bitrate) http://stream.icann.org:8000/cph58-halla2-es-lo.m3u <http://stream.icann.org:8000/cph58-halla2-es-lo.m3u> Arabic Audio http://stream.icann.org:8000/cph58-halla2-ar.m3u <http://stream.icann.org:8000/cph58-halla2-ar.m3u> French Audio (Low Bitrate) http://stream.icann.org:8000/cph58-halla2-fr-lo.m3u <http://stream.icann.org:8000/cph58-halla2-fr-lo.m3u> Spanish Audio http://stream.icann.org:8000/cph58-halla2-es.m3u <http://stream.icann.org:8000/cph58-halla2-es.m3u> French Audio http://stream.icann.org:8000/cph58-halla2-fr.m3u <http://stream.icann.org:8000/cph58-halla2-fr.m3u> Russian Audio (Low Bitrate) http://stream.icann.org:8000/cph58-halla2-ru-lo.m3u <http://stream.icann.org:8000/cph58-halla2-ru-lo.m3u> Chinese Audio (Low Bitrate) http://stream.icann.org:8000/cph58-halla2-zh-lo.m3u <http://stream.icann.org:8000/cph58-halla2-zh-lo.m3u> Russian Audio http://stream.icann.org:8000/cph58-halla2-ru.m3u <http://stream.icann.org:8000/cph58-halla2-ru.m3u> Chinese Audio http://stream.icann.org:8000/cph58-halla2-zh.m3u <http://stream.icann.org:8000/cph58-halla2-zh.m3u> Portuguese Audio (Low Bitrate) http://stream.icann.org:8000/cph58-halla2-pt-lo.m3u <http://stream.icann.org:8000/cph58-halla2-pt-lo.m3u> Since its first presentation to the GAC in Dublin, the UASG has continued to deliver on its core mission of providing good content and raising awareness. Universal Acceptance is the idea that all domain names and email addresses work in all systems. With the introduction of IDNccTLDs in 2010 and the greater expansion in new gTLDs in 2013, many applications have not kept up to date and need updating. In this session, the UASG (Universal Acceptance Steering Group) will update the GAC with its activities and provide suggestions of how governments can engage their own departments as well as their local software community to make their system UA Ready. ccNSO Session (Support role) Wednesday, 15 March 2017 13:45 – 15:00 Hall C1.2 13:45 15:00 ccTLD News Session chair: Abdalla Omari (.ke) - The development of IDN .vn domain names: Phan Nguyen Ngoc Anh (.vn) - .africa delegation: Lucky Masilela (.za Central Registry) - Promotion Chinese E-mail Address Internationalisation: Ian Chiang (.tw) - Registries from south-eastern Europe: working together: Barbara Povše (.si) - The registry of the future: Cristian Hesselman (.nl) - Q&A and wrap-up by the session chair UASG Public Forum Wednesday, 15 March 2017 17:00 – 18:30 Hall B3 <https://schedule.icann.org/venue/Hall+B3> General Session / Plenary <https://schedule.icann.org/type/general+session+%2F+plenary>, Open Session <https://schedule.icann.org/type/general+session+%2F+plenary/open+session> Adobe Connect https://participate.icann.org/cph58-hallb3 <https://participate.icann.org/cph58-hallb3> English Audio (Low Bitrate) http://stream.icann.org:8000/cph58-hallb3-en-lo.m3u <http://stream.icann.org:8000/cph58-hallb3-en-lo.m3u> English Audio http://stream.icann.org:8000/cph58-hallb3-en.m3u <http://stream.icann.org:8000/cph58-hallb3-en.m3u> 17:00 15 Introduction & Recent Update Ram 17:15 15 Issues Logging Update Seda & Koray 17:30 15 EAI Issues Mark 17:45 15 Comms Work Christian & Lars 18:00 10 UA @ ICANN IT Sigmund 18:10 20 Q&A and General Ram Don Hollander Universal Acceptance Steering Group Skype: don_hollander

3 2

UA at IUC? [or: Call for Participation Announced! - 41st Internationalization & Unicode Conference, Santa Clara, CA - October 16-18, 2017]
by Jim DeLaHunt March 13, 2017

March 13, 2017

Hello, colleagues: I'm a big fan of, and regular participant in, the annual Internationalization and Unicode Conference (IUC), brought to us by the people who brought us Unicode. I imagine that people who are interested in Universal Acceptance are likely to be interested in this conference, and may well have important contributions they could make to it. So, #1, I'd like to make everyone in UASG aware that the IUC has a call for participation. The deadline for proposals is Friday, 24. March, 2017. Please consider proposing a talk if you have something that the IUC audience would benefit from. And, #2, I don't recall there being a proper presentation of the UASG activity at the IUC conference. (Dave Crocker gave a 5-minute "lightning talk" about Universal Acceptance and the UASG, but that was barely enough time to say that it existed.) I would like to see a proposal about the Universal Acceptance Initiative submitted to the conference this year. If someone is already working on this, I would like to talk to you off-list and see if it makes sense to work together. If there is no existing effort, I would like to start one. I welcome collaboration. I will see to it that a proposal gets submitted. Best regards, --Jim DeLaHunt - - --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 -------- Forwarded Message -------- Subject: Call for Participation Announced! - 41st Internationalization & Unicode Conference, Santa Clara, CA - October 16-18, 2017 Date: Thu, 23 Feb 2017 11:34:19 -0500 From: Unicode Conference <programs(a)unicodeconference.org> To: from.unicodeconf(a)jdlh.com IUC 41 Conference To see this message in your browser click *here <http://www.unicodeconference.org/e-marketing/IUC41-CfP-022217.htm>* Internationalization & Unicode Conference 40. October 16-18, 2017 - Santa Clara, CA U.S.A. *Call for Participation Announced!* The Internationalization and Unicode® Conference (IUC) is the annual conference of the Unicode Consortium where experts and industry leaders gather to map the future of internationalization, ignite new ideas and present the latest in technologies and best practices for creation, management, and testing of global, web, and multilingual software solutions. Join in with other industry leaders to present your ideas and solutions at the 41st Internationalization & Unicode Conference (IUC 41) in Santa Clara, California, October 16-18, 2017. Please submit your proposals for presentations or tutorials by Friday, March 24, 2017. Topics can include case studies, best practices, and innovative technology within the following: /APPLICATION AREAS/ /GENERAL TECHNIQUES/ /EVOLVING STANDARDS AND RELATED PRACTICES/ /MANAGING GLOBAL SOFTWARE DEVELOPMENT AND GEOGRAPHICALLY DISTRIBUTED TEAMS/ *ABSTRACTS DUE BY MARCH 24TH!* Please *submit* <http://www.unicodeconference.org/call-for-participation.htm> a brief abstract by the deadline of Friday, March 24, 2017 to be considered as a presenter for the conference. Submit Now! <http://www.unicodeconference.org/call-for-participation.htm> * *The Program Committee will notify authors by April 28, 2017. Speaker agreements and materials such as photos, bios and final presentation abstracts will be required from selected presenters by Friday, May 19, 2017. Tutorial Presenters receive complimentary conference registration, and two nights lodging, while Session Presenters receive a fifty percent conference discount and two nights lodging. We welcome your proposals for papers and tutorials. View examples of content from *past conferences* <http://www.unicodeconference.org/past-conferences.htm>**on the IUC 41 website. GOLD SPONSOR: Adobe <http://www.unicodeconference.org/adobe-banner> MEDIA SPONSOR: Multilingual <http://www.unicodeconference.org/ml-banner/> *About The Unicode Consortium* The Unicode Consortium is a non-profit organization founded to develop, extend and promote use of the Unicode Standard and related globalization standards. The membership of the consortium represents a broad spectrum of corporations and organizations in the computer and information processing industry. Members are: Adobe Systems, Apple, Google, Government of Bangladesh, Government of India, IBM, Microsoft, Monotype Imaging, Oracle, SAP, The Society for Natural Language Technology Research, The University of California (Berkeley), The University of California (Santa Cruz), Yahoo!, plus well over a hundred Associate, Liaison, and Individual members. For more information, please contact the Unicode Consortium <http://www.unicode.org/contacts.html>. *About the Event Producer* OMG <http://www.omg.org>® is the Event Producer for the Internationalization & Unicode Conferences. OMG is an international, open membership, not-for-profit computer industry standards consortium. OMG Task Forces develop enterprise integration standards for a wide range of technologies and an even wider range of industries. OMG's modeling standards, including the Unified Modeling Language™ (UML®) and Model Driven Architecture® (MDA®), enable powerful visual design, execution and maintenance of software and other processes, including IT Systems Modeling and Business Process Management. OMG's middleware standards and profiles are based on the Common Object Request Broker Architecture (CORBA®) and support a wide variety of industries. OMG has offices at 109 Highland Avenue, Needham, MA 02494 USA. This email may be considered to be commercial email, an advertisement or a solicitation. For more information about OMG, visit us online at http://www.omg.org. By accepting this email and not responding with an unsubscribe request, you have consented or "opted in" to receive additional correspondence and promotions from OMG and its associated partners and sponsors. Should you wish to opt-out in the future please visit http://www.omg.org/cgi-bin/unsubscribe.cgi.

7 7

mixi.jp
by Andre Schappo March 12, 2017

March 12, 2017

http://mixi.jp are using google mail 苹果电脑 ~: host mixi.jp<http://mixi.jp> mixi.jp<http://mixi.jp> has address 54.92.71.226 mixi.jp<http://mixi.jp> has address 52.198.59.66 mixi.jp<http://mixi.jp> has address 52.198.89.90 mixi.jp<http://mixi.jp> mail is handled by 20 alt1.aspmx.l.google.com<http://alt1.aspmx.l.google.com>. mixi.jp<http://mixi.jp> mail is handled by 20 alt2.aspmx.l.google.com<http://alt2.aspmx.l.google.com>. mixi.jp<http://mixi.jp> mail is handled by 30 aspmx2.googlemail.com<http://aspmx2.googlemail.com>. mixi.jp<http://mixi.jp> mail is handled by 30 aspmx3.googlemail.com<http://aspmx3.googlemail.com>. mixi.jp<http://mixi.jp> mail is handled by 10 aspmx.l.google.com<http://aspmx.l.google.com>. André Schappo

2 1

twitter
by Andre Schappo March 12, 2017

March 12, 2017

Just looked at twitter and they are using google mail so they are ready to go with EAI 苹果电脑 ~: host twitter.com twitter.com has address 104.244.42.1 twitter.com has address 104.244.42.193 twitter.com mail is handled by 30 ASPMX3.GOOGLEMAIL.COM. twitter.com mail is handled by 10 aspmx.l.google.com. twitter.com mail is handled by 20 alt2.aspmx.l.google.com. twitter.com mail is handled by 30 ASPMX2.GOOGLEMAIL.COM. twitter.com mail is handled by 20 alt1.aspmx.l.google.com. André Schappo

1 0

APrIGF Workshop: "Universal Acceptance: An Elixir to Inclusive and Multilingual Internet" - Invitation to participate as speaker in APrIGF 2017
by Harish Chowdhary March 12, 2017

March 12, 2017

Dear,I have proposed a workshop titled "Universal Acceptance: An Elixir to Inclusive and Multilingual Internet" to present at APrIGF scheduled on 26-29 July 2017 in Bangkok, Thailand.2.            Our open discussions/workshop  will primarily focus the issues of Implementation of Universal Acceptance via Multilingual Internet through IDN's (Internationalized Domain Names) and E-mail Address Internationalization so that we may connect remaining 57% population of the world to the internet in their local/Native language.3.            Many communities are actively and independently working to realize various components of multilingual internet viz. Support for local languages on various browsers and operating systems, partial support on email clients and servers, availability of software keypads and fonts for local languages, availability of some web content in loca l languages (though not significant), translation option from English to some of the local languages etc. However, there are still many challenges that need to be addressed.4.            We anticipate the open forum to be organized with the experts discussing the following issues "Interoperability issues of internationalized e-mail addresses viz.e-mail Addresses in local Languages". Universal acceptance of Internationalized Domain Names (IDNs) Another most important issues is lack of Awareness, about the availability of IDNs and EAI (E-mail Address internationalization), many language tools, like fonts and virtual keypads, lack of standardization.5.         It is an effort to bring all the stakeholders to a forum to solve issues related to Universal acceptance.6.         The Internet community in the Asia Pacific needs to play an important role to help in this multi-stakeholder effort given that over 50% of all languages of the world are spoken and used in the region. Establishing a platform and/or forum might be a suitable first step to develop awareness and collect information to deal with all the issues each community has in relation to using and accessing IEAs (Internationalized e-mail addresses) and IDNs.7.         I kindly request you to confirm your availability as speaker for the proposed workshop by 14th March 2017.8.         Awaiting your confirmation at the earliest.You may send the confirmation mail to harish(a)nixi.in9.        Please suggest more speakers who are going to attend APrIGF and want to contribute in the workshop as confirmed speaker. Thanks,Harish Chowdhary,National Internet Exchange of Indiaharish(a)nixi.in  ------------------------------------------------------------------------------------------------------------------------------- [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