[ICANN-CSC] IDN practices submission service

Kim Davies kim.davies at iana.org
Wed Mar 15 09:16:02 UTC 2017

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.


"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.
    <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
    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?
    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. 
    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
    Jay Daley
    Chief Executive
    NZRS Ltd
    desk: +64 4 931 6977
    mobile: +64 21 678840
    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=>

More information about the ICANN-CSC mailing list