Terminology aside, I don’t think we are in a position to dismiss the IDN Implementation Guidelines. But we can address the process concern by recommending the GNSO Council to develop a change management process for future versions of the document. Version 4 has some items that, in my opinion, need to be reconcile with the RA. So on this matter I find it acceptable that the CPH and ICANN work in good faith to settle those differences. Best, Dennis From: gnso-council-IDN-scoping <gnso-council-idn-scoping-bounces@icann.org> on behalf of Maxim Alzoba via gnso-council-IDN-scoping <gnso-council-idn-scoping@icann.org> Reply-To: Maxim Alzoba <m.alzoba@gmail.com> Date: Friday, December 13, 2019 at 4:13 AM To: Edmon Chung <edmon@registry.asia> Cc: "gnso-council-idn-scoping@icann.org" <gnso-council-idn-scoping@icann.org> Subject: [EXTERNAL] Re: [GNSO-Council-IDN-Scoping] [Ext] Re: Actions & Notes: GNSO IDN Scoping Team Meeting on 5 December at 3:00 UTC Hello Edmon, there is an issue of the legal nature, with the "the acceptance of the Guidelines as Consensus Policy" only the items, which followed policy development process from GNSO Operating Procedures can be recognized as Consensus Policy (after all steps are properly finished). And IDN Guidelines do not fit it so far. P.s: An Applicant is not a Registry (please check the text of RA, it has nothing to do with the contents of the Application.) Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID Current UTC offset: +3.00 (.Moscow) On 13 Dec 2019, at 11:55, Edmon via gnso-council-IDN-scoping <gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org>> wrote: On the issue of IDN Variants allocated to the same entity, I can appreciate that it has operational impact, but to say that does not come from GNSO policy is simply not correct. The IDN Outcomes report produced within the new gTLD PDP back in 2007 specifically describes the matter regarding 2LD registrations and IDN Variants. The report is incorporated into the new gTLD recommendations. That must be considered GNSO Policy. https://gnso.icann.org/en/drafts/idn-wg-fr-22mar07.htm ================ 4.1.6. Limit Confusingly Similar Strings: Agreement that measures be taken to ensure that an IDN gTLD string with variants (see 4.1.4 and 4.1.5 above) be treated in analogy with current practice for IDN SLD labels, i.e. strings that only differ from an IDN gTLD string by variants (see above) are not available for registration by others. ================ I can understand if there may be questions raised to reconsider it, but there is clear GNSO Policy produced by a GNSO PDP on the matter. Likewise the acceptance of the ICANN IDN Implementation Guidelines. Included in Recommendation 18: If an applicant offers an IDN service, then ICANN's IDN guidelines must be followed. https://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm So the acceptance of the Guidelines as Consensus Policy into the RA is not an issue in my mind. The Policy issue to be considered is only its update process which was what was raised. And FWIW, the original IDN Working Group that was formed was a representative group selected from different constituencies. If my memory serves me right, I was elected from the Registrars Constituency at that time to participate in that IDN WG which produced the first IDN Implementation Guidelines. Subsequent revisions were less representative and mostly through Expert groups. Edmon From: Maxim Alzoba [mailto:m.alzoba@gmail.com] Sent: Friday, December 13, 2019 5:38 AM To: Tan Tanaka, Dennis <dtantanaka@verisign.com<mailto:dtantanaka@verisign.com>> Cc: edmon@registry.asia<mailto:edmon@registry.asia> Subject: Re: [GNSO-Council-IDN-Scoping] [Ext] Re: Actions & Notes: GNSO IDN Scoping Team Meeting on 5 December at 3:00 UTC I will add my comments below Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID Current UTC offset: +3.00 (.Moscow) On 13 Dec 2019, at 00:14, Tan Tanaka, Dennis <dtantanaka@verisign.com<mailto:dtantanaka@verisign.com>> wrote: From: Maxim Alzoba <m.alzoba@gmail.com<mailto:m.alzoba@gmail.com>> Speaking of the process , when ICANN / PTI (IANA) processes new IDN tables (which are brought by Applicants or Registries ) is an internal process of ICANN/ PTI and I am not saying that the process (where ICANN and Registries discuss this to understand the way do it) can be handled separately. (The same might be for the existing tables updates process)
Ok. Good to know. So I do not see things preventing us from helping it to start in Feb 2020.
The "same entity" thing is going to affect the Registrants and since Registrants have nothing to do with the RA and Registries , there might be a need for RAA amendment (which goes through the negotiation with RrSG ExCom). That is why I was referring to CPH when we discussed changes to the contracts.
Agree re: contract implications. Registries might need some kind of policy+technical combo to enforce the same entity on registrars. And registrars will need to do the same for registrants. The PDP will need to be sensible of these relationships and how any potential PDP recommendations impacts to RA and RAA, right? However, this would not be the first time a PDP recommendation triggers a RA/RAA amendment (i.e. RDAP, Clear Display and Labelling) without going through CPH ExCom review/blessing. The policy implementation is handled by the IRT.
The Amendment is triggered, but then it is in the hands of CPH (for RA amendment - RySG, for RAA - RrSG). (I think I might have caused some confusion here about order of things to start and cause other things, sorry for that). We are (CPH ExComs appointed Working Group, which is not split to separate WG of Registries and WG of Registrars yet, because we are discussing the common for ROs and RRs issues at the moment) right now in the middle of the "RDAP changes to the RA/RAA" process, all blessed by ExComs(both CPH), for RA, according to Art. 7.6 (v) of RA, for RAA 2013 - according to Art. 1.32 of RAA. (I am one of the members of the group), and it is not handled via IRT at this stage (RA and RAA prescribe the process to amend those contracts and it is strictly between ICANN and respective part of CPH, with the public comments closer to the end of the process). As I remember CL&D implementation (published text of the first reading of the policy) was troubled the first time (Reconsideration request to the Board went to remove RDAP profile from the policy text, because it was not part of policy, just was added by ICANN staff), then it passed second time as a consensus policy text, which is obligatory for Registries and Registrars without changes to RA / RAA . According to the Charter of the RySG , GNSO Council reps. of RySG are part of RySG ExCom (so I am there too). It was the requirement for the same entity for all variants, which could not be accepted without a proper due policy development process.
That would be one of the issues the PDP would need to deliberate. Not us within the scoping team. That is what I meant.
P.s: for avoidance of doubt - nothing prevents us from sending a clarification letter to Donna (but we should mention that it is sent to RySG, not a personal opinion request). Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID m. +7 916 6761580(+whatsapp) skype oldfrogger Current UTC offset: +3.00 (.Moscow) On 12 Dec 2019, at 23:16, Maxim Alzoba <m.alzoba@gmail.com<mailto:m.alzoba@gmail.com>> wrote: Hi Dennis, I meant that the RA Amendment is a process triggered by RySG ExCom, and RAA - by RrSG ExCom, and that without a proper reason it is not going to happen. I think in avoidance of doubt, the idea of 'we need to do something with it' is supported. GNSO Council decided to review what we have now because RySG ExCom asked for it. I would recommend to re-read the RySG Letter on this issue. Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID m. +7 916 6761580(+whatsapp) skype oldfrogger Current UTC offset: +3.00 (.Moscow) On 12 Dec 2019, at 17:31, Tan Tanaka, Dennis <dtantanaka@verisign.com<mailto:dtantanaka@verisign.com>> wrote: *** Removing Staff*** I sense that there is a disconnect by way of the terms being used e.g. CPH. I’m not knowledgeable about the formal procedures, but the fact is since the RySG raised the issue about how the IDN table review and approval process is being handled, Staff reached out to me (and few others as I understand it) to work on an agreeable process. We are aiming to kick-off this workstream by early Feb 2020. In the last RySG call of Dec 4 I presented a summary of the facts and the approach the RySG should take on this matter (i.e. narrowly on IDN table review and approval process). I bring this up because, as far as I am aware, this is a RySG initiative. RrSG is not involved. To my knowledge, Donna is supportive of RySG pursuing this. But I’m not sure whether that is equivalent to say that the RySG Excom also is. My point is. RySG initiated this work because it thought it was worth doing. To my knowledge, there was no formal CPH ExComs process to start the work. Dennis From: Maxim Alzoba <m.alzoba@gmail.com<mailto:m.alzoba@gmail.com>> Date: Thursday, December 12, 2019 at 5:35 AM To: Edmon Chung <edmon@registry.asia<mailto:edmon@registry.asia>> Cc: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>>, Dennis Tan Tanaka <dtantanaka@verisign.com<mailto:dtantanaka@verisign.com>>, "gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org>" <gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org>> Subject: [EXTERNAL] Re: [GNSO-Council-IDN-Scoping] [Ext] Re: Actions & Notes: GNSO IDN Scoping Team Meeting on 5 December at 3:00 UTC Just for clarity, The history has nothing to do with the legal obligations of parties. CPH ExComs decide what to do basing on the input (in our case not ready yet, and no policy to speak of) and the need to things (not much to speak either), not because we think that it might be a good idea. CPH Team will not be formed before the decision of CPH ExComs to do so. I do not believe that there will be anything to speak of on CPH level prior to the delivery of the policy work. P.s: and the reason for our group to exist is that CPH saw the materials provided by the previous expert group as no basis for the things to be changed yet (it is possible to check the transcripts of the GNSO Council meetings, where the idea was deffered). Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID Current UTC offset: +3.00 (.Moscow) On 12 Dec 2019, at 13:05, Edmon <edmon@registry.asia<mailto:edmon@registry.asia>> wrote: The IDN Implementation Guidelines have been put in place since 2003 for all Contracted Parties… it was referred to and included in the GNSO Policy Recommendations for new gTLDs in 2007 and subsequently in the AGB. So it does form part of the GNSO Policies as I understand it. The IDN Implementation Guidelines have always included the consideration of IDN Variants, albeit in a less robust form than in Version 4.0. Much of the IDN Implementation Guidelines work was informed and motivated by the consideration of potential homograph concerns as well as user experience. I understand that in the future, there is interest to re look at how the IDN Implementation Guidelines should be reviewed and updated and perhaps reformatted, but based on our discussions early on, I believe there was agreement that we should focus on a few specific issues identified that needed execution corrections/clarifications for version 4.0: 1. The issue of IDN Tables and to confirm that existing LGRs can be used as-is 2. The RA/RAA reference to the IDN Implementation Guidelines 3. The acceptable implementation for allocating IDN Variants to the same registrant only These could be taken up by a Contracted Party house team directly with ICANN staff. Edmon From: Maxim Alzoba [mailto:m.alzoba@gmail.com] Sent: Thursday, December 12, 2019 5:19 PM To: Edmon <edmon@registry.asia<mailto:edmon@registry.asia>> Cc: Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>>; Tan Tanaka, Dennis <dtantanaka@verisign.com<mailto:dtantanaka@verisign.com>>; gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org> Subject: Re: [GNSO-Council-IDN-Scoping] [Ext] Re: Actions & Notes: GNSO IDN Scoping Team Meeting on 5 December at 3:00 UTC Hi Edmon, I do not see the way for the 1. until the 2. resulted in a policy (if guidelines extensively refer to variants which is not defined in the policy work). There is a strong reason for this, without due policy work we can not be sure we see all implications. For contracted parties where should be something more than pages of text that an expert group produced, and which did not have review of the legal and operational implications. Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID m. +7 916 6761580(+whatsapp) skype oldfrogger Current UTC offset: +3.00 (.Moscow) On 12 Dec 2019, at 05:01, Edmon via gnso-council-IDN-scoping <gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org>> wrote: On the topic of (i) potential conflicts between RA and IDN Guidelines and (ii) updating and evolving IDN tables Based on discussions earlier in the process, I had in my mind that we would be recommending 2 streams of work overall: 1. A Contracted Party working/negotiation/implementation team that would be focused on IDN Implementation Guidelines 4.0 operational issues (which includes the above and closely related to RA/RRA), to resolve immediate issues and allow for the guidelines 4.0 to be adopted. 2. A PDP/EPDP that would have a scope including both the IDN Variant TLD define, manage, and coordinate issues as well as the related issue of how the IDN Implementation Guidelines should be revised in the future so that it becomes a GNSO policy. Does this reconcile with other’s recollection and does this direction work? Edmon From: Steve Chan [mailto:steve.chan@icann.org] Sent: Thursday, December 12, 2019 6:58 AM To: Tan Tanaka, Dennis <dtantanaka@verisign.com<mailto:dtantanaka@verisign.com>>; edmon@registry.asia<mailto:edmon@registry.asia>; gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org> Subject: Re: [Ext] Re: [GNSO-Council-IDN-Scoping] Actions & Notes: GNSO IDN Scoping Team Meeting on 5 December at 3:00 UTC Hi Dennis, Maxim, all, Dennis great point - if you take a look at the agenda, you’ll see item 3 is about next steps. One of the likely items for discussion here is how the two documents generated by this group fit together. I believe Edmon mentioned that his initial thought is that the options paper, which describes the operational issues you note below, would serve as the main document and then the scoping document recently discussed would serve as more of an Annex, providing evidence of the background materials and issue analysis already conducted and available. Maxim, the things you mention sound more like substantive discussions that would take place during policy development. Based on my understanding and using one of your concerns as an example, the remit of this scoping team would be to identify if the “same entity” recommendations and the impacts on other elements (like RPMs) should be examined during policy development, but not to delve into the substance of the issue nor consider solutions. Best, Steve From: "Tan Tanaka, Dennis" <dtantanaka@verisign.com<mailto:dtantanaka@verisign.com>> Date: Wednesday, December 11, 2019 at 2:32 PM To: "edmon@registry.asia<mailto:edmon@registry.asia>" <edmon@registry.asia<mailto:edmon@registry.asia>>, Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>>, "gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org>" <gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org>> Subject: [Ext] Re: [GNSO-Council-IDN-Scoping] Actions & Notes: GNSO IDN Scoping Team Meeting on 5 December at 3:00 UTC Edmon, Steve, et al I made a few comments in the Issue Scoping doc; mainly about elaborating on the IDN Guidelines issue and incorporating it in the “Objectives of a possible EPDP”. The below email discusses the policy issues but I’d like to see a discussion on the operational issues as well: (i) potential conflicts between RA and IDN Guidelines and (ii) updating and evolving IDN tables. Perhaps this is coming after we wrap up the policy issues? Thanks, Dennis From: gnso-council-IDN-scoping <gnso-council-idn-scoping-bounces@icann.org<mailto:gnso-council-idn-scoping-bounces@icann.org>> on behalf of Edmon via gnso-council-IDN-scoping <gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org>> Reply-To: Edmon Chung <edmon@registry.asia<mailto:edmon@registry.asia>> Date: Tuesday, December 10, 2019 at 6:19 PM To: 'Steve Chan' <steve.chan@icann.org<mailto:steve.chan@icann.org>>, "gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org>" <gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org>> Subject: [EXTERNAL] Re: [GNSO-Council-IDN-Scoping] Actions & Notes: GNSO IDN Scoping Team Meeting on 5 December at 3:00 UTC Thanks Steve. It seems clear at this point we should recommend for the matters to proceed in a separate PDP and not added to existing PDPs. One of the important decisions the group needs to make though, is whether to recommend to the GNSO Council: A) A regular PDP, for which an Issues Report needs to be developed B) An EPDP, for which the only difference from a PDP is a further Issues Report is not required Given the volume of background information already produced for the topic, as well as the rough draft which staff has drawn up, which includes the issues (1) as well as the listing of the background documents (2): 1. https://docs.google.com/document/d/13tO5IP64EAnFebdefRahK3vuhIBzUEdl1oeGFBnQ... [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> 2. https://docs.google.com/document/d/1vhbIIpua9_3s_0G-LMNQ3hdWo8SkIxObUSpfJPk-... [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> It appears that an EPDP is the appropriate approach because there is ample background information on the subject and there does not seem to be any clear gaps requiring an Issues report. I understand that Maxim has raised concerns about EPDP, but that seems to stem from the emotional aftermath of how the EPDP in response to GDPR was created more than the actual requirement (i.e. of the Issues Report). If there are any other concerns or objections to proceeding with EPDP please raise them. If we do move forward to recommend an EPDP approach, the chartering team can determine the structure and membership of the EPDP working group and complete the IDN Variant Issues Scoping (1. Above) which would form essentially an issues report for the working group consideration. Please take a look and we hope to come to conclusion on the matter so we can make the recommendation to the council before its meeting in January. Edmon From: gnso-council-IDN-scoping [mailto:gnso-council-idn-scoping-bounces@icann.org] On Behalf Of Steve Chan via gnso-council-IDN-scoping Sent: Saturday, December 7, 2019 4:02 AM To: gnso-council-idn-scoping@icann.org<mailto:gnso-council-idn-scoping@icann.org> Subject: [GNSO-Council-IDN-Scoping] Actions & Notes: GNSO IDN Scoping Team Meeting on 5 December at 3:00 UTC Dear Team, With apologies for the late delivery, please find below the action items and notes captured during the IDN Scoping Team call on Thursday, 5 December at 3:00 UTC. Staff has posted to the wiki space the action items and notes. Please note that these are high-level notes and are not meant as a substitute for the recording and chat room records, which are posted on the wiki at: https://community.icann.org/x/z5czBw Best, Steve == Action Item - Staff to add SAC060 and SAC052 to the list of documents - Edmon to determine if he feels like he can make an assessment as to which Option the scoping team supports to recommend to the GNSO Council. If he is able, he will provide his assessment to the email list for input. NOTES 1. Welcome and roll call - Edmon may need to leave meeting early - Update on coordination with the SubPro PDP – SubPro leadership does not believe that the IDN work must take place in SubPro. If an IDN variants PDP is launched, it can further the related work done in SubPro and build upon it. - Edmon has review the SubPro draft recs and they indeed seem like they can be built upon rather than needing to be overturned. - SubPro may want to consider the technical utilization paper for the RZ-LGR, currently under Board consideration, but they should be aware that it’s a fluid situation of they indeed review the document now. - GNSO policies can be replaced by policy development taking place at a later date, so a new PDP on IDN variants could in theory develop recommendations that go against the SubPro recommendations on IDN variants. 2. Review of new Issue Scoping Document here: https://docs.google.com/document/d/13tO5IP64EAnFebdefRahK3vuhIBzUEdl1oeGFBnQ... [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen...> - Purpose of this document is to explore whether or not there is sufficient background documentation and analysis to serve as a proxy for an Issue Report, which could make an EPDP make some sense - There is also the existing work on IDN variants taking place in SubPro - Document is structured similarly to the substantive part of an Issue Report and make sure that all of the required elements are present. - First part is about identifying the problems that need to be solved, which in this case come from the Board resolution (e.g., RZ-LGR must be the only source and that policies should be developed to manage IDN variant TLDs for current and future gTLDs). - Also notes that coordination with ccNSO is needed and GNSO concerns about the process by which the IDN Guidelines are updated from version to version. - Second section identifies the list of relevant documentation. There is also, by reference, a comprehensive list of documents related to IDN variants. ACTION – Add SAC060 and SAC052 to the list of documents - The list is not intended to limit what a PDP may consider, in the event something relevant arises later. - Third part of the document is about the issues and questions a PDP should consider and address. Firstly, broken down into the two challenges. Lists out the recommendations from the staff report. - Also lists out questions from the staff report where there may be policy implications. This list is captured verbatim from the staff paper. - The Council did not specifically request a charter from the IDN Scoping team - There was not a specific time frame dictated by the Council, but there is an expectation that the scoping team will provide its recommendations prior to the end of the year. Concerns expressed from Maxim about the time constraint. 3. After discussing agenda item 2, revisiting the options paper:https://docs.google.com/document/d/1o_9bfnkKufrSxiJGxpNcOcfTK2VLWp5XYQvwe5qx... - In light of the previous discussion about what could be in an issue report, based on existing materials and analysis, what option makes the most sense? - Option A is to leverage existing PDPs (i.e., SubPro and RPMs), Option B is to separate new gTLDs versus existing gTLDs, Option C is a PDP or EPDP, Option D is an expert working group. - Maxim indicates that there is not support from the entire group to for an EPDP, suggestion that he should indicate why he oppose, what he prefers, and why. Also indicates that GNSO should not feel obligated to follow pace of ccNSO. ACTION – Edmon to determine if he feels like he can make an assessment as to which Option the scoping team supports to recommend to the GNSO Council. If he is able, he will provide his assessment to the email list for input. - Maxim notes that some believe that the set of documents is not holistic and that further analysis is needed. 4. Possible next steps - None, discussed above 5. AOB - None Steven Chan Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Email: steve.chan@icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group...> _______________________________________________ gnso-council-IDN-scoping mailing list gnso-council-IDN-scoping@icann.org<mailto:gnso-council-IDN-scoping@icann.org> https://mm.icann.org/mailman/listinfo/gnso-council-idn-scoping _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ gnso-council-IDN-scoping mailing list gnso-council-IDN-scoping@icann.org<mailto:gnso-council-IDN-scoping@icann.org> https://mm.icann.org/mailman/listinfo/gnso-council-idn-scoping _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.