great points！ especially for email address part！ From my phone
在 2015年2月19日，8:32，Mark Svancarek <marksv@microsoft.com> 写道：
Here’s how I think of the functionality:
Whenever Internet domain names, URIs, URLs, IRIs and/or file paths are used/expected, the product or service… · Allows entry of international chars into UI input controls · Can correctly render International strings · Can correctly render RTL strings · Can communicate data between apps and services in formats which support Unicode and are convertible to/from UTF-8 · Offers public APIs which support Unicode & UTF-8 · Offers private APIs which support Unicode & UTF-8 (these private APIs apply only to inter-service calls by the same vendor) · Stores user data values as a type which allows Unicode and is convertible to/from UTF-8 (visible only to the product/service owner) · Supports all domain name strings in the Public Suffix List regardless of length
Regarding any email address which includes Unicode characters (whether TLD, n-level domain name, and/or username ), the product or service… · Allows entry of international chars into UI input controls · Can correctly render International strings · Can correctly render RTL strings · Can communicate data between apps and services in formats which support Unicode and are convertible to/from UTF-8 · Offers public APIs which support Unicode & UTF-8 · Offers private APIs which support Unicode & UTF-8 (these private APIs apply only to inter-service calls by the same vendor) · Stores user data values as a type which allows Unicode and is convertible to/from UTF-8 (visible only to the product/service owner) · Can send email to recipients with such email address · Can receive email from senders with such email address · Supports accounts associated with both an ASCII and Unicode email address · Supports all domain name strings in the Public Suffix List regardless of length
From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Tuesday, February 17, 2015 11:51 PM To: Kurt Pritz Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] What are the main things to do in UASG?
Or, we could slice it by functionality:
- Validation on data entry - usually of an e-mail address - Storage & display characteristics of an e-mail address - Storage & display characteristics of a URL - including a name server entry.
Don
On 18/02/2015, at 6:39 pm, Kurt Pritz <kpritz@thedna.org> wrote:
Regarding prioritization of IDNs:
In practice: I think the way that this will play out is that there will mostly independent technical work streams for IDNs, IDN email and ASCII issues. Each will go as fast as it can and will not get in the way of the other. Then, it will become important to match the messaging of each stream with the target audience.
If there are ever contention over resources or messaging we can manage it at the time it occurs. I have seen how passionate people are on each of these streams and believe that they can all be managed in an expedited way.
Kurt
We are all passionate about all three streams. On Feb 18, 2015, at 4:00 PM, "Edmon Chung" <edmon@registry.asia> wrote:
Agree with Rich on taking this as a domain issue irrespective of IDN/cc/g Based on what Rich and Don said, I think it is important that we do not try to isolate IDN too much.
Past experience have told us that what may sound like a good idea to “give special attention to” IDN turns out rendering it into a second class citizen.
I think IDN Readiness should be incorporated into every work stream as a priority item even if it is not the spotlight feature (as for example for messaging in the US).
Edmon
From: ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] On Behalf Of Don Hollander Sent: Wednesday, February 18, 2015 3:50 AM To: Jeffrey Sass Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] What are the main things to do in UASG?
Let me put my CIO’s hat on and contribute.
The expensive part of making a change to a system is the initial touching of it. If I end up touching it twice to deal with length of TLDs in one pass and IDNs in a second pass, I’m not going to be too thrilled. But making clear from the beginning that there are a number of changes to the TLD environment that need to be catered for then I will deal with them all at once. But don’t feed them to me one at a time.
The actual code changes are relatively small parts of the project budget. There’s the scoping, analysis and testing - particularly testing - and documentation and training where the big dollars are spent.
Don
On 18/02/2015, at 7:52 am, Jeffrey Sass <jeff@nic.club> wrote:
Chiming in, I agree with Rich. UA should be for all domain names, as even legacy TLD's (.Travel, due to length, for instance) may have issues in certain systems. I am also hyper-sensitive to make sure we do not send a message that new TLD's are not ready for prime time by highlighting problems specific to them. The goal, as Richard stated, should be to achieve Universal Acceptance of all domain names, regardless of the flavor of the extension, or the language/character set of the string. Thanks all!
Jeffrey Sass, CMO .CLUB Domains, LLC Direct: (+1) 954-256-9334 Mobile: (+1) 970-367-7277 E-Mail: jeff@nic.club Website: www.nic.club Twitter: @sass @getDotClub Skype, Hangouts: jwsass
PLEASE NOTE: I am only checking email 2-3 times per day. If something is time sensitive (really time sensitive) please message me or text me at the mobile number above. Thanks!
From: Anthony Harris (anthonyrharris@gmail.com) Sent: Tuesday, February 17, 2015 12:36 PM To: Ram Mohan (rmohan@afilias.info) Cc: UA-discuss@icann.org (ua-discuss@icann.org) Subject: Re: [UA-discuss] What are the main things to do in UASG? I also agree with this.
Tony Harris
On Tue, Feb 17, 2015 at 2:25 PM, Ram Mohan <rmohan@afilias.info> wrote: +1. This is not an IDN, ngTLD or TLD issue.
-----Original Message----- From: Richard Merdinger [mailto: rmerdinger@godaddy.com] Sent: Tuesday, February 17, 2015 9:21 AM To: Dusan Stojicevic; ua-discuss@icann.org Subject: Re: [UA-discuss] What are the main things to do in UASG?
While I appreciate the fact that IDN issues are, in many ways, a superset of the issues faced by other domains/TLDs that exhibit acceptance issues, I really think that we need to continue to consider this UA effort a "domain" issue and not a new gTLD issue, IDN issue, or even a TLD issue.
My view is that we decompose the UA issue into component issue areas and attack them, irrespective of labels that could inadvertently/inaccurately attach the perception of agendas that could ultimately thwart the effort.
Richard Merdinger VP, Domains e: rmerdinger@godaddy.com s: richard.merdinger m: 319.530.4100
-----Original Message----- From: ua-discuss-bounces@icann.org [mailto: ua-discuss-bounces@icann.org] On Behalf Of Dusan Stojicevic Sent: Tuesday, February 17, 2015 6:14 AM To: ua-discuss@icann.org Subject: Re: [UA-discuss] What are the main things to do in UASG?
Dear all,
Although I think that IDN is a big, maybe major question in UA, I must say that I agree with Mark and Michele. IDN problem is part of UA, but UA is a much broader concept. Those people from the list who had the misfortune to meet me, will be surprised.
Regards, Dušan Serbian ccTLD registry
On 17.2.2015 12:43, Mark McFadden wrote:
Edmon:
While risking agreeing with Michele on this, I'd say that I'm very fond of the "U" in "UA" - that is, I think we should be focusing on Universal Acceptance and not IDN Acceptance. By breaking the problem into two parts, I think we may be heading for a better, crisper problem statement. There are problems in many settings - for instance, problems with acceptance of "long" strings, problems with acceptance of IDN scripts, problems in display, problems in EAI, etc. etc.
It might be better not to focus on IDNs until we had a more precise definition of "how universal" our approach to Universal Acceptance is going to be.
mark
Mark McFadden Principal Consultant, Internet Infrastructure and Governance InterConnect Communications
Mobile: +44 (0) 7792 276 904 Skype: McElmside or +44 (0) 20 7558 8105 Email: MarkMcFadden@icc-uk.com Web: http://www.icc-uk.com
InterConnect Communications Ltd, Merlin House, Station Road, Chepstow, NP16 5PB, United Kingdom. Registered in England and Wales, company registration no. 1828673. ________________________________________ From: ua-discuss-bounces@icann.org [ ua-discuss-bounces@icann.org] On Behalf Of Michele Neylon - Blacknight [ michele@blacknight.com] Sent: Tuesday, February 17, 2015 11:40 AM To: Edmon Chung; 'Mark Svancarek'; 'Nelson, Nick'; 'Christian Dawson'; 'Ram Mohan SMTP' Cc: UA-discuss@icann.org Subject: Re: [UA-discuss] What are the main things to do in UASG?
Edmon
I'm sorry, but I cannot agree with you on this.
If, for example, I was trying to get a bunch of Irish web developers or software engineeers to code better and support ALL tlds then they're not going to be motivated by IDNs.
Telling them that their bad code choices is blocking English speaking users from using their new (Latin script) domains might be a motivator.
I also don't think the IDN banner helps rally people. It would help rally *some* people, but I'm not convinced that they're the ones who need the most rallying.
Regards
Michele
-- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains http://www.blacknight.host/ http://blog.blacknight.com/ http://www.blacknight.press - get our latest news & media coverage http://www.technology.ie Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Social: http://mneylon.social ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845
From: Edmon Chung [mailto: edmon@registry.asia] Sent: 17 February 2015 01:13 To: Michele Neylon - Blacknight; 'Mark Svancarek'; 'Nelson, Nick'; 'Christian Dawson'; 'Ram Mohan SMTP' Cc: UA-discuss@icann.org Subject: RE: [UA-discuss] What are the main things to do in UASG?
I agree with you Michele that this is not an issue limited to IDNs, however, I still believe that if we solve the IDN issue, we will solve the ASCII new TLD issue.
So as a "moral high ground" if you will, for ICANN with this as a community-wide project, I think it is better to have IDN be the "primary" focus so that it gets the support from the whole community. If we had a primary focus on ASCII TLDs, I worry we will lose the support we need from many parts of the community.
That is not to say we only focus on IDN. But the IDN banner I believe helps us rally this as a global effort for the Internet.
Edmon
From: ua-discuss-bounces@icann.org<mailto: ua-discuss-bounces@icann.org> [mailto: ua-discuss-bounces@icann.org] On Behalf Of Michele Neylon - Blacknight Sent: Tuesday, February 17, 2015 9:03 AM To: Mark Svancarek; Nelson, Nick; Christian Dawson; Ram Mohan SMTP Cc: UA-discuss@icann.org<mailto: UA-discuss@icann.org> Subject: Re: [UA-discuss] What are the main things to do in UASG?
Mark
That's good, but that's assuming that Universal Acceptance is limited to IDNs, whereas in reality the issue is much wider. At present a lot of online services and software do not recognise new TLDs - be they ASCII or IDN. So while incorporating that language is excellent, I'd hate to see IDNs as being the primary focus Regards
Michele
-- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains http://www.blacknight.host/ http://blog.blacknight.com/ http://www.blacknight.press - get our latest news & media coverage http://www.technology.ie Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Social: http://mneylon.social ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845 ________________________________ From: Mark Svancarek [ marksv@microsoft.com] Sent: 16 February 2015 21:43 To: Michele Neylon - Blacknight; Nelson, Nick; Christian Dawson; Ram Mohan SMTP Cc: UA-discuss@icann.org<mailto: UA-discuss@icann.org> Subject: RE: [UA-discuss] What are the main things to do in UASG? Yes, I also agree with Michele and Nick.
As a starter:
"International character sets, whether in Unicode or Punycode, are inconsistently managed by existing software products and existing online services. These inconsistencies arise both from non-support of the RFCs or from support for outdated versions of these RFCs.
Software and service providers have historically had little market or regulatory incentive to invest in solutions which would bring true interoperability to platforms or applications. Democratization of computing and greater availability of Internationalized Domain Names are likely to upset this status quo.
A coordinated industry effort is required to ensure a timely and practical resolution to this pending change."
From: ua-discuss-bounces@icann.org<mailto: ua-discuss-bounces@icann.org> [mailto: ua-discuss-bounces@icann.org] On Behalf Of Michele Neylon - Blacknight Sent: Monday, February 16, 2015 9:43 AM To: Nelson, Nick; Christian Dawson; Ram Mohan SMTP Cc: UA-discuss@icann.org<mailto: UA-discuss@icann.org> Subject: Re: [UA-discuss] What are the main things to do in UASG?
I'd agree with Nick
Defining the problem should be key Everything else comes after that
Regards
Michele
-- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains http://www.blacknight.host/ http://blog.blacknight.com/ http://www.blacknight.press - get our latest news & media coverage http://www.technology.ie Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Social: http://mneylon.social ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845
From: ua-discuss-bounces@icann.org<mailto: ua-discuss-bounces@icann.org> [mailto: ua-discuss-bounces@icann.org] On Behalf Of Nelson, Nick Sent: 16 February 2015 17:39 To: Christian Dawson; Ram Mohan SMTP Cc: UA-discuss@icann.org<mailto: UA-discuss@icann.org> Subject: Re: [UA-discuss] What are the main things to do in UASG?
I'm coming in a bit late but that gives me good perspective and I think the total list from Ram is accurate. However, I'd argue that both Christian is right with defining structure and charger, but also first - we should define the Problem space.
The problem space to me is ultimately why we're all here right. "What are we trying to solve for?" and even more so, "How is this group going to benefit the ultimate end-user?" ________________________________ From: ua-discuss-bounces@icann.org<mailto: ua-discuss-bounces@icann.org> [ ua-discuss-bounces@icann.org] on behalf of Christian Dawson [ dawson@i2coalition.com] Sent: Monday, February 16, 2015 9:22 AM To: Ram Mohan SMTP Cc: UA-discuss@icann.org<mailto: UA-discuss@icann.org> Subject: Re: [UA-discuss] What are the main things to do in UASG? Ram,
I think this is a good list with one proposed change. I am 3-4 pages into a draft charter for people to look at, which proposes a structure. I'd say we need an agreed-on structure before we pick leaders to fill defined roles, so I suggest flipping 1 and 2.
I probably can't get far enough along to put my draft charter up for review until tomorrow - chairing a small anti-SPAM working group on SPAM in the Cloud at M3AAWG today. (If anybody else from this group is at M3AAWG come find me and we can chat/complain about timezones together.)
-Christian
On Feb 14, 2015, at 11:21 AM, Ram Mohan < rmohan@afilias.info<mailto: rmohan@afilias.info>> wrote:
Team, Trying to get an inventory of the main tasks in front of the UASG, in chronological order:
1. Group leadership 2. Group structure and charter 3. Definition of problem space 4. Prioritization of problem space 5. Definition of approach to problem spaces 6. Delegation of work 7. Execution of work 8. Follow-through
Appreciate input.
-Ram
---------------------------------------------------------------------- -------- Ram Mohan Executive Vice President & CTO Afilias |Ireland|Canada|USA|India o: +1.215.706.5700 x103; m: +1.215.431.0958; f: +1.215.706.5701 Skype: gliderpilot30
______________________________________________________________________ __ This e-mail has been scanned for all viruses by Star Internet. ______________________________________________________________________ __
______________________________________________________________________ __ This e-mail has been scanned for all viruses by Star Internet. However, InterConnect makes no warranty that this email is virus-free. ______________________________________________________________________ __
--- Ova e-pošta je provjerena na viruse Avast protuvirusnim programom. http://www.avast.com