[IDN-WG] [ALAC] The Problem of IDNs
edmon at isoc.hk
Mon May 12 05:26:37 UTC 2014
I think it is very important for ICANN to take the issue of "Universal Acceptance of IDN" seriously and take a central role in the coordination and facilitation of bringing together the stakeholders so that the issue can be addressed.
The issue in my mind is 2 fold, including 1. a technical side and 2. an advocacy side
After many years of discussion, I strongly believe ICANN is the right forum and place for this coordination and gathering of stakeholders to take place, even as ICANN itself nor its immediate community can "solve" the issue.
Following from the JIG Final Report on the issue, of which of course I was very much involved, I hope that ICANN could make this a strategic item, at the level (at least) of advocating for IPv6 and DNSSEC.
Also, we must start with our own community, the registries and registrars and make sure we have those systems for which ICANN policies can directly influence to be fully IDN aware so that users can not only register IDNs but use them at least to setup nameservers, dns hosting, web hosting and emails.
In my mind, the ideal approach ICANN could take would be to convene a community wide steering group that would include participants from all organs of ICANN, including ALAC, GAC, ccNSO, GNSO, SSAC, RSSAC in fact ASO as well, but not stop there, ICANN should also help invite participants from other parts of the Internet community including application level organizations e.g. WITSA, as well as W3C, IETF, etc.
The group should work with an ICANN staff team to produce:
1. A set of best practices for IDN Acceptance in systems (based on and consolidating from the experience already in the community)
2. Set of measurements of IDN Acceptance (so we can continue to track and measure our progress)
3. Continued study measuring IDN Acceptance on the internet (including domain registries and registrars)
The group does not need to meet all the time like GNSO working groups, we just need to meet maybe 2-3 times a year and keep track of the progress and to make sure we move forward methodically. Such meetings could ideally coincide with ICANN meetings, again where we would invite other parts of the internet community to join.
Well... the above is my wish :-D
ICANN board seems have not considered the JIG report yet and am not sure what their schedule or priority level is on the issue... Though, here at the APTLD meetings, I heard encouraging presentation from Ed Lewis of ICANN that finally there is a change in the attitude of ICANN staff that ICANN has a role to play in this.
In any case, as mentioned briefly in Singapore, I think maybe ALAC can take the lead on forming that community wide steering group...
> -----Original Message-----
> From: idn-wg-bounces at atlarge-lists.icann.org [mailto:idn-wg-bounces at atlarge-
> lists.icann.org] On Behalf Of Rinalia Abdul Rahim
> Sent: Monday, May 12, 2014 8:36 AM
> To: León Felipe Sánchez Ambía
> Cc: Carlton Samuels; No name; ALAC Working List; Don Hollander; apralo
> Subject: Re: [IDN-WG] [ALAC] The Problem of IDNs
> Hi, Leon.
> A cross-RALO collaboration would be excellent if there is interest in the respective
> RALOs to take on this issue. In the past, RALOs have had different prioritization
> for IDN related issues. I think some awareness-raising is needed among RALOs
> to help them understand the nature of the problem. It is a problem of relevance to
> users worldwide.
> A webinar before ATLAS II in London and / or discussion during ATLAS II in
> London would be a good opportunity to do it. Would you be willing to help
> shepherd process (i.e., make sure a discussion happens on the topic)?
> Best regards,
> On Mon, May 12, 2014 at 1:12 AM, León Felipe Sánchez Ambía <
> leonfelipe at sanchez.mx> wrote:
> > Good information. Thanks Rinalia!
> > I might be stating the obvious, however, this is not a problem that is
> > exclusive to the AP region but to the rest of the regions as well. I
> > see it as a chance to advance in a cross-regional effort in order to
> > create awareness and engage different users and technical communities
> > towards addressing the issue.
> > Could we think of ways in which we could collaborate across RALOs to
> > help solve the problem? Maybe a cross-regional workshop at some forum?
> > What are your thoughts?
> > Best regards,
> > León
> > El 09/05/2014, a las 10:07, Carlton Samuels
> > <carlton.samuels at gmail.com>
> > escribió:
> > > On Thu, May 8, 2014 at 11:09 PM, Rinalia Abdul Rahim <
> > > rinalia.abdulrahim at gmail.com> wrote:
> > >
> > >> The challenge for ICANN is that it doesn't deal with application
> > >> level problems. Nevertheless, the successful adoption of IDN TLDs
> > >> is
> > arguably a
> > >> success measure for ICANN's TLD programme, so ICANN has a stake in
> > seeing
> > >> IDNs succeed.
> > >>
> > >
> > > Maybe. But if ICANN were to understand that the application issues
> > impacts
> > > not just the health but a 'stable, secure.....' ecosystem then ICANN
> > would
> > > be well-advised to find a corner and get to working.
> > >
> > > In this era of roiled sensibilities and sensitivities ICANN no
> > > longer has the luxury of being Potiphar's wife; make a claim to be above
> > >
> > > Thanks for sharing, Rinalia. Much obliged.
> > >
> > > -Carlton
> > >
> > >
> > >
> > > ==============================
> > > Carlton A Samuels
> > > Mobile: 876-818-1799
> > > *Strategy, Planning, Governance, Assessment & Turnaround*
> > > =============================
> > > _______________________________________________
> > > ALAC mailing list
> > > ALAC at atlarge-lists.icann.org
> > > https://atlarge-lists.icann.org/mailman/listinfo/alac
> > >
> > > At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki:
> > https://community.icann.org/display/atlarge/At-Large+Advisory+Committe
> > e+(ALAC)
> IDN-WG mailing list
> IDN-WG at atlarge-lists.icann.org
> IDN WG Wiki: https://community.icann.org/display/atlarge/At-Large+IDN+Policy
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4570 / Virus Database: 3931/7441 - Release Date: 05/05/14
More information about the IDN-WG