[ICANN-CSC] IDN practices submission service

Elaine Pruis elaine at donuts.email
Wed Mar 15 09:35:32 UTC 2017

Thanks Kim,
It is a contractual obligation on new TLD operators to have their IDN
tables published by IANA,
>From Spec 6:
1.4.         IDN.  If the Registry Operator offers Internationalized Domain
Names (“IDNs”), it shall comply with RFCs 5890, 5891, 5892, 5893 and their
successors.  Registry Operator shall comply with the ICANN IDN Guidelines
at <http://www.icann.org/en/topics/idn/implementation-guidelines.htm>, as
they may be amended, modified, or superseded from time to time.  Registry
Operator shall publish and keep updated its IDN Tables and IDN Registration
Rules in the IANA Repository of IDN Practices as specified in the ICANN IDN

 and that is why there is concern that it takes so long to get them
published. ICANN compliance has in the past issued "notices" that we're out
of compliance with our contract because not all of our tables are yet
published. I don't know if they are still pursuing it, given it is not in
the operator's power to actually post them there (we do provide proof that
they've been submitted).

On Wed, Mar 15, 2017 at 10:16 AM, Kim Davies <kim.davies at iana.org> wrote:

> Hi folks,
> I believe as the IDN table repository was not part of the IANA functions,
> and is not part of root zone management, that it was considered out of
> scope for performance monitoring.
> For background, we provide an IDN table repository that allows TLD
> managers to share their IDN registration policies (aka LGRs). This was set
> up on staff initiative quite some time ago as a project to promote IDN
> adoption — so TLD managers could learn from one another about the policies
> of other registries and re-use them if they wished.
> kim
> "icann-csc-bounces at icann.org on behalf of Elise Gerich" <
> icann-csc-bounces at icann.org on behalf of elise.gerich at iana.org> wrote:
>     Hi Jay,
>     Like you, I do not remember the discussion about IDN tables.  Kim was
> actively involved in the discussions about the service level definitions
> and perhaps he remembers the discussion that
>      the design team had on this topic. Or perhaps there is something in
> the Design Team’s email archives.
>     --Elise
>     From:
>     <icann-csc-bounces at icann.org> on behalf of Jay Daley <jay at nzrs.net.nz>
>     Date: Tuesday, March 14, 2017 at 4:41 PM
>     To: "Feher, Kal" <Kalman.Feher at neustar.biz>
>     Cc: "ICANN-CSC at icann.org" <ICANN-CSC at icann.org>
>     Subject: Re: [ICANN-CSC] IDN practices submission service
>     Kal
>     During the SLE drafting process we did propose service levels around
> IDN tables (see attached screenshot) but for reasons I cannot remember
> these got dropped.
>     Elaine/EliseG - Can you (or Kim) remember the reasoning?
>     Jay
>     On 14/03/2017, at 4:16 PM, Feher, Kal <Kalman.Feher at neustar.biz>
> wrote:
>     During our Q&A with the RySG today, it was raised to us by Rubens Kuhl
> that IDN practices submission and publication falls within the CSC's
> responsibilities. My immediate reaction was that this should be a protocol
> assignment metric, but I'm assured it falls
>      under our remit.
>     Does anyone with more history or context knowledge than me have
> additional information on this?
>     Since we don't have an SLE for it, should a new SLE be created? I'm
> assuming the process would be similar to having one modified.
>     Or
>     Is it appropriate to add IDN practice submission/publication under an
> existing SLE such as "Other changes"? Noting that the target measurement
> would have been developed without awareness of such additional scope.
>     Kal Feher
>     Neustar Inc. / Enterprise Architect
>     Level 8, 10 Queens Road, Melbourne, Australia VIC 3004
>     Office +61 3 9866 3710 / kal.feher at neustar.biz / www.neustar.biz
>     Follow Neustar:   <54033593-3099-4D83-8140-0D8157811442[25].png>
> Facebook   <CD6E1201-C37D-47D2-B2EA-486E58552390[25].png> LinkedIn
>  <A61F1170-9103-40BB-BDCE-E545DF2935F7[25].png> Twitter
>     The information contained in this e-mail message is intended only for
> the use of the recipient(s) named above and may contain confidential and/or
> privileged information. If you are not the intended recipient you have
> received this e-mail message in error and
>      any review, dissemination, distribution, or copying of this message
> is strictly prohibited. If you have received this communication in error,
> please notify us immediately and delete the original message.
>     _______________________________________________
>     ICANN-CSC mailing list
>     ICANN-CSC at icann.org
>     https://mm.icann.org/mailman/listinfo/icann-csc
>     --
>     Jay Daley
>     Chief Executive
>     NZRS Ltd
>     desk: +64 4 931 6977
>     mobile: +64 21 678840
>     linkedin:
>     www.linkedin.com/in/jaydaley[linkedin.com] <https://urldefense.
> proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_jaydaley&d=DwMFAg&c=
> FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=
> pXgd7rUFmOGPSaTcf3kROMV5Rt3fTXejagLVImG-D14&m=z5uIhosySxIoiNM_
> n0xfc2tOYNpE71x05S2VgMCtkx8&s=oxtDBW7h-wT7ER8Pokw-OHqQ-
> fCxGCCVWv08-IkqN5w&e=>
> _______________________________________________
> ICANN-CSC mailing list
> ICANN-CSC at icann.org
> https://mm.icann.org/mailman/listinfo/icann-csc


[image: Donuts Inc.] <http://www.donuts.domains>
*Elaine Pruis*, Vice President, Operations
*Donuts Inc. <http://www.donuts.domains>*
10500 NE 8th Street, Suite 350, Bellevue Washington, 98004, U.S.A. |
Telephone: 509.899.3161
[image: Twitter] <https://twitter.com/DonutsInc>[image: Facebook]
<https://www.facebook.com/donutstlds>[image: Linked In]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20170315/5dd7d844/attachment.html>

More information about the ICANN-CSC mailing list