[ICANN-CSC] [Ext] Re: IDN practices submission service

Wed Mar 15 12:10:07 UTC 2017

Thank you Kim for the additional background.
And thank you Elaine for pointing out that it is part of the contract. I'm
on the IDN Guidelines drafting team and I can confirm that the new
guidelines will retain this obligation.

So that leaves us with whether we think it should be monitored?
I think this is broken down further into "Should PTI be responsible?" and
"Is the service critical to naming customers?".

To gTLD operators the answer to the second question is unequivocally 'yes'.

The answer to the first question is less clear. ICANN could host those
practices themselves. Perhaps there's a separation of responsibilities
principle I'm not aware of that might prevent this.

However if PTI do continue to host this service, I think it should be
monitored.

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
<http://www.neustar.biz/>

Follow Neustar:    Facebook <http://www.facebook.com/neustarinc>
LinkedIn <http://www.linkedin.com/company/5349>    Twitter
<http://www.twitter.com/neustarinc>
________________________________________

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.

On 15/3/17, 10:57, "Kim Davies" <kim.davies at iana.org> wrote:

>Hi Elaine,
>
>
>
>Definitely understood. I think when they first started checking it there
>was some confusion about this, but once the issue was identified, our
>business processes were clarified with ICANN Compliance so they
>understood some table posting requests could be pending with IANA.
>
>
>
>kim
>
>
>
>"Elaine Pruis" <elaine at donuts.email> wrote:
>
>
>
>    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 
><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_topi
>cs_idn_implementation-2Dguidelines.htm-5Bicann.org-5D&d=DwIGaQ&c=MOptNlVtI
>ETeDALC_lULrw&r=_-v0M-gLiqWrtaHtP66hjSPyu3ePgw9YIihGxxybjqU&m=dd37xgCsQ4hi
>Q7_9kgtW_MlwhKYv8g-_oybUL2-1nzw&s=dkMtfsiUCfwlGvMLG3-QJT2Qqlag_EGE2A1ArnIx
>H_s&e=  
><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_topi
>cs_idn_implementation-2Dguidelines.htm&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgf
>kbPSS6sJms7xcl4I5cM&r=u-w41jmTz8W-GZ2oW5VPT7IdBzgDrOaE_Xl5v328lnM&m=YOnlyG
>z3gFQ4p2Rk9qvgqME6PkextW8GfbcWdLju7hQ&s=M0J0QC0FtjXgXTomhxV7OU5zJr--Lr-jCB
>qc2znfHDk&e=>>,
>
>     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 Guidelines.
>
>    
>
>    
>
>    
>
>     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 <tel:%2B61%203%209866%203710> /
>
>    kal.feher at neustar.biz /
>
>    www.neustar.biz[neustar.biz]
><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.neustar.biz&d=DwM
>FaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=u-w41jmTz8W-GZ2oW5VPT7
>IdBzgDrOaE_Xl5v328lnM&m=YOnlyGz3gFQ4p2Rk9qvgqME6PkextW8GfbcWdLju7hQ&s=HK6G
>5WCO2XTuHGKyHl2fiP36J-tUbr3WkBv-OQda_Pw&e=>
>
>    
>
>        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://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_
>listinfo_icann-2Dcsc&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=_-v0M-gLiqWrtaHtP
>66hjSPyu3ePgw9YIihGxxybjqU&m=dd37xgCsQ4hiQ7_9kgtW_MlwhKYv8g-_oybUL2-1nzw&s
>=BiXYLTt_1uYJ9M_4RYQ2kmcFZRlTXHlOP2uWYHeiPtk&e=
><https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman
>_listinfo_icann-2Dcsc&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=_-v0M-gLiqWrtaHt
>P66hjSPyu3ePgw9YIihGxxybjqU&m=dd37xgCsQ4hiQ7_9kgtW_MlwhKYv8g-_oybUL2-1nzw&
>s=BiXYLTt_1uYJ9M_4RYQ2kmcFZRlTXHlOP2uWYHeiPtk&e= >
>
>    
>
>    
>
>    
>
>    
>
>        --
>
>        Jay Daley
>
>        Chief Executive
>
>        NZRS Ltd
>
>        desk: +64 4 931 6977 <tel:%2B64%204%20931%206977>
>
>        mobile: +64 21 678840 <tel:%2B64%2021%20678840>
>
>        linkedin:
>
>    
>
>    
>
>        
>
>    www.linkedin.com/in/jaydaley[linkedin.com][linkedin.com]
><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_j
>aydaley-5Blinkedin.com-5D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xc
>l4I5cM&r=u-w41jmTz8W-GZ2oW5VPT7IdBzgDrOaE_Xl5v328lnM&m=YOnlyGz3gFQ4p2Rk9qv
>gqME6PkextW8GfbcWdLju7hQ&s=paWxYCm9novqQru0tfAQsNpto8FYtraTTYj5u8Rwggs&e=>
> 
><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_j
>aydaley&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=pXgd7rUFm
>OGPSaTcf3kROMV5Rt3fTXejagLVImG-D14&m=z5uIhosySxIoiNM_n0xfc2tOYNpE71x05S2Vg
>MCtkx8&s=oxtDBW7h-wT7ER8Pokw-OHqQ-fCxGCCVWv08-IkqN5w&e=>
>
>    
>
>    
>
>    
>
>    
>
>    
>
>    
>
>    
>
>    _______________________________________________
>
>    ICANN-CSC mailing list
>
>    ICANN-CSC at icann.org
>
>    
>https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_
>listinfo_icann-2Dcsc&d=DwIGaQ&c=MOptNlVtIETeDALC_lULrw&r=_-v0M-gLiqWrtaHtP
>66hjSPyu3ePgw9YIihGxxybjqU&m=dd37xgCsQ4hiQ7_9kgtW_MlwhKYv8g-_oybUL2-1nzw&s
>=BiXYLTt_1uYJ9M_4RYQ2kmcFZRlTXHlOP2uWYHeiPtk&e=
>
>    
>
>    
>
>    
>
>    
>
>    
>
>    
>
>    
>
>    
>
>    
>
>    -- 
>
>    
>
>    
>
>    [donuts.domains]
><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.donuts.domains&d=
>DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=u-w41jmTz8W-GZ2oW5V
>PT7IdBzgDrOaE_Xl5v328lnM&m=YOnlyGz3gFQ4p2Rk9qvgqME6PkextW8GfbcWdLju7hQ&s=4
>mLhLc_MhW3FBBsxIOnUPWaCbkfqDKjTy_JIHk0FhQs&e=>Elaine Pruis, Vice
>President, Operations
>
>    Donuts
>
>     Inc.[donuts.domains]
><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.donuts.domains&d=
>DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=u-w41jmTz8W-GZ2oW5V
>PT7IdBzgDrOaE_Xl5v328lnM&m=YOnlyGz3gFQ4p2Rk9qvgqME6PkextW8GfbcWdLju7hQ&s=4
>mLhLc_MhW3FBBsxIOnUPWaCbkfqDKjTy_JIHk0FhQs&e=>
>
>    10500 NE 8th Street, Suite 350, Bellevue Washington, 98004, U.S.A. |
>Telephone: 509.899.3161
>
>    [twitter.com] 
><https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_DonutsIn
>c&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=u-w41jmTz8W-GZ2
>oW5VPT7IdBzgDrOaE_Xl5v328lnM&m=YOnlyGz3gFQ4p2Rk9qvgqME6PkextW8GfbcWdLju7hQ
>&s=1g9gvH6m9Ha72w1NLdkKaFXmUTkM0lcOCTThDFieycI&e=>[facebook.com]
><https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_don
>utstlds&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=u-w41jmTz
>8W-GZ2oW5VPT7IdBzgDrOaE_Xl5v328lnM&m=YOnlyGz3gFQ4p2Rk9qvgqME6PkextW8GfbcWd
>Lju7hQ&s=XoR2ePfp-dlOLGO17WelJPnCp8Hn--A5NqtyIs339a4&e=>[linkedin.com]
><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_comp
>any_donuts-2Dinc-2D&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM
>&r=u-w41jmTz8W-GZ2oW5VPT7IdBzgDrOaE_Xl5v328lnM&m=YOnlyGz3gFQ4p2Rk9qvgqME6P
>kextW8GfbcWdLju7hQ&s=wZSLWaGAJ92U87AfoRE2v8RBnfYLIqvEHIE15i41ofY&e=>
>
>    
>
>    
>
>    
>
>     
>
>    
>
>    
>
>    
>
>    
>
>
>