From manju at nii.org.tw Fri Apr 1 04:32:57 2022 From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=) Date: Fri, 1 Apr 2022 09:32:57 +0800 Subject: [NCSG-PC] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> Message-ID: Hi Kathy, The Council has formed a small team and charged it with the task of coming up with suggestions for the next step. I guess you can think of this small team as having the responsibility of requesting input from their respective groups? The members of the small team are Paul McGrady, Kurt Pritz, Jeff Neuman, Justine Chew, and me. So you can see how we really have to hold our fort on this one, and I'm counting on the statement we agreed to put together as a cheat sheet so I deliver our points loud and clear. The small team is scheduled to meet next week. I'll listen to our policy call again to note down our points. In the meantime, I'd really appreciate more insights from those of you who have extensive knowledge of closed generics and GAC/GNSO dialogue on Red Cross. Best, Manju On Thu, Mar 31, 2022 at 20:39 Kathy Kleiman wrote: > Hi Tomslin, > > I thought the Council was going to go through a period of requesting some > input. Has that changed? > > Best, Kathy > On 3/30/2022 9:08 PM, Tomslin Samme-Nlar wrote: > > Hi team, > > I just wanted to call your attention to this response we promised to put > together on the board proposed dialogue between GAC and Council on closed > generics. The Council small team is about to be activated to start > deliberations and I believe @??? Manju Chen who is > representing us there hopes to rely on the response we pen down to guide > her contribution to that team. > > In this regard, can I request that we find some time to please put our > ideas down on the Google form > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > Looking forward to your help with this. In the meantime, i'll review my > meeting notes and put down some feedback we got during our policy call on > the document. > > Warmly, > Tomslin > > On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, > wrote: > >> Hi all, >> >> As a follow-up to my previous email regarding the board's proposed >> facilitated dialogue between GAC and GNSO council, I have created this >> Google doc [ >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> ] to capture our response to this proposal in the form of a letter to the >> council small team on Closed Generics. >> >> Inputs to the document are welcomed and for your convenience, attached >> again is the letter from the board and the accompanying framing paper. >> >> Regards, >> Tomslin >> >> >> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar >> wrote: >> >>> Dear everyone, >>> >>> Here is the framing paper on the board's proposed dialogue between GNSO >>> Council and the GAC on Closed Generics that was promised. >>> >>> Comments are welcomed. I will also be sending a separate email with a >>> link to the Google doc where we intend to draft a letter as a response to >>> this. >>> >>> Regards, >>> Tomslin >>> >>> >>> ---------- Forwarded message --------- >>> From: Wendy Profit via Gnso-chairs >>> Date: Fri, 11 Mar 2022 at 04:33 >>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal >>> Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>> To: manal.ismail at board.icann.org , Manal >>> Ismail , philippe.fouquart at orange.com < >>> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >>> gnso-chairs at icann.org> >>> Cc: Secretary , Correspondence < >>> Correspondence at icann.org>, Board Ops Team , >>> gnso-secs at icann.org , GACSTAFF , >>> Maarten Botterman >>> >>> >>> Dear Manal and Philippe, >>> >>> >>> >>> Pursuant to the letter sent recently (6 March 2022, attached for >>> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >>> Process for a GAC - GNSO Council Dialogue on Closed Generics?, also >>> attached. >>> >>> >>> >>> Thank you and best regards, >>> >>> >>> >>> Wendy Profit >>> >>> ICANN >>> >>> Board Operations Senior Manager >>> >>> 12025 Waterfront Drive, Suite 300 >>> >>> >>> >>> >>> Los Angeles, CA 90094 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> *From: *Wendy Profit >>> *Date: *Sunday, March 6, 2022 at 3:58 PM >>> *To: *"manal.ismail at board.icann.org" , " >>> manal at tra.gov.eg" , "philippe.fouquart at orange.com" < >>> philippe.fouquart at orange.com> >>> *Cc: *Maarten Botterman , " >>> gnso-chairs at icann.org" , GACSTAFF < >>> gac-staff at icann.org>, "gnso-secs at icann.org" , >>> ICANN Board Ops , Correspondence < >>> Correspondence at icann.org>, Secretary >>> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >>> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>> >>> >>> >>> Dear Manal and Philippe, >>> >>> >>> >>> Please find the attached letter from ICANN Chair Maarten Botterman >>> regarding a proposed formal consultation between the GAC and GNSO Council >>> on how to handle the subject of closed generics in gTLD applications. >>> >>> >>> >>> Thank you and best regards, >>> >>> >>> >>> Wendy Profit >>> >>> ICANN >>> >>> Board Operations Senior Manager >>> >>> 12025 Waterfront Drive, Suite 300 >>> >>> >>> >>> >>> Los Angeles, CA 90094 >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Gnso-chairs mailing list >>> Gnso-chairs at icann.org >>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>> _______________________________________________ >>> 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. >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Sun Apr 3 15:36:39 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sun, 3 Apr 2022 22:36:39 +1000 Subject: [NCSG-PC] [Public Comment] For Review - Policy Status Report: Uniform Domain Name Dispute Resolution Policy (UDRP) In-Reply-To: References: Message-ID: Dear everyone, Pedro de Perdig?o Lana has kindly offered a draft comment to this proceeding and it can be found on this link . Your comments and suggestions will be greatly appreciated. https://docs.google.com/document/d/1OkjTnKz7YoXzNeWaZ5L3UDiPclSyVv7q5QBnl67_IQ8/edit?usp=sharing Warmly, Tomslin On Sat, 5 Mar 2022 at 20:28, Tomslin Samme-Nlar wrote: > Dear members, > > The public comment period on the *Policy Status Report: Uniform Domain > Name Dispute Resolution Policy (UDRP)* has just been opened and the > Policy Committee is calling for volunteers to draft an NCSG comment for > this proceeding which is due for consideration on *Monday, 11 April 2022* > to allow time for filling and submitting the new public comment form. > > Please let me know off-list if you'd like to volunteer for the comment > drafting. It'll be nice to have more than one volunteer, including > new-commers who can use this as an opportunity to learn and be familiar > with policy work. > > More information about the policy status report can be found here : > https://www.icann.org/en/public-comment/proceeding/policy-status-report-uniform-domain-name-dispute-resolution-policy-udrp-03-03-2022 > > A draft Google doc for the comment can be found here: > https://docs.google.com/document/d/1OkjTnKz7YoXzNeWaZ5L3UDiPclSyVv7q5QBnl67_IQ8/edit?usp=sharing > > You can find previous NCSG comments here: > https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2021 > > *See below some best practices for the penholder:* > > - > *Provide the first draft on the mailing list in by day 21 of the comment > period * > - *Try to resolve the comments throughout the duration of comment > period * > - *Make sure that the commenter has seen how comment has been resolved > (contact them directly if necessary)* > > Cheers, > Tomslin > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kathy at kathykleiman.com Sun Apr 3 20:00:37 2022 From: kathy at kathykleiman.com (Kathy Kleiman) Date: Sun, 3 Apr 2022 13:00:37 -0400 Subject: [NCSG-PC] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> Message-ID: Hi Manju, Your material is excellent. I've tried to be helpful in adding more references from the GAC Beijing Advice in 2013, and some of the outreach of the more recent outreach of SubPro WG members to the GAC during the PDP. Also some sources/references/letters/CircleID at bottom now. What else can we do to help you? Best, Kathy On 3/31/2022 9:32 PM, ??? Manju Chen wrote: > Hi?Kathy, > > The Council has formed a small team and charged it with the task of > coming up with suggestions for the next step. > I guess you can think of this small team as having the responsibility > of requesting input from their?respective groups? > > The members of the small team are Paul McGrady, Kurt Pritz, Jeff > Neuman, Justine Chew, and me. > > So you can see how we really have to hold our fort on this one, and > I'm counting on the statement we agreed to put together as a > cheat?sheet so I deliver our points loud and clear. > > The small team is scheduled to meet next week. I'll listen to our > policy call again to note down our points. In the meantime, I'd really > appreciate more insights from those of you who have extensive > knowledge of closed generics and GAC/GNSO dialogue on Red Cross. > > Best, > Manju > > > On Thu, Mar 31, 2022 at 20:39 Kathy Kleiman > wrote: > > Hi Tomslin, > > I thought the Council was going to go through a period of > requesting some input. Has that changed? > > Best, Kathy > > On 3/30/2022 9:08 PM, Tomslin Samme-Nlar wrote: >> Hi team, >> >> I just wanted to call your attention to this response we promised >> to put together on the board proposed dialogue between GAC and >> Council on closed generics. The Council small team is about to be >> activated to start deliberations and I believe @??? Manju Chen >> ?who is representing us there hopes to >> rely on the response we pen down to guide her contribution to >> that team. >> >> In this?regard, can I request that we find some time to please >> put our ideas down on the Google >> formhttps://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> Looking forward to your help with this. In the meantime, i'll >> review my meeting notes and put down some feedback we got during >> our policy call on the document. >> >> Warmly, >> Tomslin >> >> On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, >> wrote: >> >> Hi all, >> >> As a follow-up to my previous email regarding the board's >> proposed facilitated dialogue between GAC and GNSO council, I >> have created this Google doc [ >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> ] to capture our response to this proposal in the form of a >> letter to the council small team on Closed Generics. >> >> Inputs to the document are welcomed and for your convenience, >> attached again is the letter from the board and the >> accompanying framing paper. >> >> Regards, >> Tomslin >> >> >> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar >> wrote: >> >> Dear everyone, >> >> Here is the framing paper on the board's proposed >> dialogue between GNSO Council and the GAC on Closed >> Generics that was promised. >> >> Comments are welcomed. I will also be sending a separate >> email with a link to the Google doc where we intend to >> draft a letter as a response to this. >> >> Regards, >> Tomslin >> >> >> ---------- Forwarded message --------- >> From: *Wendy Profit via Gnso-chairs* >> Date: Fri, 11 Mar 2022 at 04:33 >> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman >> to Manal Ismail and Philippe Fouquart - GAC-GNSO >> Consultation on Closed Generics >> To: manal.ismail at board.icann.org >> , Manal Ismail >> , philippe.fouquart at orange.com >> , gnso-chairs at icann.org >> >> Cc: Secretary , Correspondence >> , Board Ops Team >> , gnso-secs at icann.org >> , GACSTAFF , >> Maarten Botterman >> >> >> Dear Manal and Philippe, >> >> Pursuant to the letter sent recently (6 March 2022, >> attached for reference), we are now forwarding the >> associated framework paper entitled ?Board-Facilitated >> Process for a GAC - GNSO Council Dialogue on Closed >> Generics?, also attached. >> >> ** >> >> Thank you and best regards, >> >> Wendy Profit >> >> ICANN >> >> Board Operations Senior Manager >> >> 12025 Waterfront Drive, Suite 300 >> >> >> >> >> >> Los Angeles, CA 90094 >> >> >> *From: *Wendy Profit >> *Date: *Sunday, March 6, 2022 at 3:58 PM >> *To: *"manal.ismail at board.icann.org" >> , "manal at tra.gov.eg" >> , "philippe.fouquart at orange.com" >> >> *Cc: *Maarten Botterman >> , >> "gnso-chairs at icann.org" , GACSTAFF >> , "gnso-secs at icann.org" >> , ICANN Board Ops >> , Correspondence >> , Secretary >> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal >> Ismail and Philippe Fouquart - GAC-GNSO Consultation on >> Closed Generics >> >> Dear Manal and Philippe, >> >> Please find the attached letter from ICANN Chair Maarten >> Botterman regarding a proposed formal consultation >> between the GAC and GNSO Council on how to handle the >> subject of closed generics in gTLD applications. >> >> Thank you and best regards, >> >> Wendy Profit >> >> ICANN >> >> Board Operations Senior Manager >> >> 12025 Waterfront Drive, Suite 300 >> >> >> >> >> >> Los Angeles, CA 90094 >> >> >> _______________________________________________ >> Gnso-chairs mailing list >> Gnso-chairs at icann.org >> https://mm.icann.org/mailman/listinfo/gnso-chairs >> _______________________________________________ >> 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. >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Mon Apr 4 13:57:54 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Mon, 4 Apr 2022 20:57:54 +1000 Subject: [NCSG-PC] IGO WT Update Message-ID: Hi Juan, I understand the IGO WT final report is ready and that there is full consensus. Would you be able to walk us through how that came to be and a few more insights into the report during our policy call on Monday? Tomslin -------------- next part -------------- An HTML attachment was scrubbed... URL: From manju at nii.org.tw Thu Apr 7 01:18:27 2022 From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=) Date: Thu, 7 Apr 2022 06:18:27 +0800 Subject: [NCSG-PC] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> Message-ID: Hi team, Borrowing this thread to report back to you about what happened in the small team. So as you might have guessed, I was the only one saying no to the 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the discussion of how we engage with GAC in this 'facilitated dialogue' but thankfully they still respected our objection. My first point of objection is that the small team is really not representative enough to make the decision of whether the Council should meet with the GAC. For now, we agreed to refer this back to the Council and make the decision at the Council level. I'm afraid though NCSG would be the only one saying no when we're at the Council level. Also when this pops up, we really have to have our statement ready explaining why we're saying no. I've put notes in the document Tomslin created and Kathy has been extremely helpful by providing reference material and edits: https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing We will still need to phrase them into a formal statement, but I think it'd be an easy task now we have all the contents. Best, Manju On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar wrote: > Hi team, > > I just wanted to call your attention to this response we promised to put > together on the board proposed dialogue between GAC and Council on closed > generics. The Council small team is about to be activated to start > deliberations and I believe @??? Manju Chen who is > representing us there hopes to rely on the response we pen down to guide > her contribution to that team. > > In this regard, can I request that we find some time to please put our > ideas down on the Google form > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > Looking forward to your help with this. In the meantime, i'll review my > meeting notes and put down some feedback we got during our policy call on > the document. > > Warmly, > Tomslin > > On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, > wrote: > >> Hi all, >> >> As a follow-up to my previous email regarding the board's proposed >> facilitated dialogue between GAC and GNSO council, I have created this >> Google doc [ >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> ] to capture our response to this proposal in the form of a letter to the >> council small team on Closed Generics. >> >> Inputs to the document are welcomed and for your convenience, attached >> again is the letter from the board and the accompanying framing paper. >> >> Regards, >> Tomslin >> >> >> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar >> wrote: >> >>> Dear everyone, >>> >>> Here is the framing paper on the board's proposed dialogue between GNSO >>> Council and the GAC on Closed Generics that was promised. >>> >>> Comments are welcomed. I will also be sending a separate email with a >>> link to the Google doc where we intend to draft a letter as a response to >>> this. >>> >>> Regards, >>> Tomslin >>> >>> >>> ---------- Forwarded message --------- >>> From: Wendy Profit via Gnso-chairs >>> Date: Fri, 11 Mar 2022 at 04:33 >>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal >>> Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>> To: manal.ismail at board.icann.org , Manal >>> Ismail , philippe.fouquart at orange.com < >>> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >>> gnso-chairs at icann.org> >>> Cc: Secretary , Correspondence < >>> Correspondence at icann.org>, Board Ops Team , >>> gnso-secs at icann.org , GACSTAFF , >>> Maarten Botterman >>> >>> >>> Dear Manal and Philippe, >>> >>> >>> >>> Pursuant to the letter sent recently (6 March 2022, attached for >>> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >>> Process for a GAC - GNSO Council Dialogue on Closed Generics?, also >>> attached. >>> >>> >>> >>> Thank you and best regards, >>> >>> >>> >>> Wendy Profit >>> >>> ICANN >>> >>> Board Operations Senior Manager >>> >>> 12025 Waterfront Drive, Suite 300 >>> >>> Los Angeles, CA 90094 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> *From: *Wendy Profit >>> *Date: *Sunday, March 6, 2022 at 3:58 PM >>> *To: *"manal.ismail at board.icann.org" , " >>> manal at tra.gov.eg" , "philippe.fouquart at orange.com" < >>> philippe.fouquart at orange.com> >>> *Cc: *Maarten Botterman , " >>> gnso-chairs at icann.org" , GACSTAFF < >>> gac-staff at icann.org>, "gnso-secs at icann.org" , >>> ICANN Board Ops , Correspondence < >>> Correspondence at icann.org>, Secretary >>> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >>> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>> >>> >>> >>> Dear Manal and Philippe, >>> >>> >>> >>> Please find the attached letter from ICANN Chair Maarten Botterman >>> regarding a proposed formal consultation between the GAC and GNSO Council >>> on how to handle the subject of closed generics in gTLD applications. >>> >>> >>> >>> Thank you and best regards, >>> >>> >>> >>> Wendy Profit >>> >>> ICANN >>> >>> Board Operations Senior Manager >>> >>> 12025 Waterfront Drive, Suite 300 >>> >>> Los Angeles, CA 90094 >>> >>> >>> >>> >>> _______________________________________________ >>> Gnso-chairs mailing list >>> Gnso-chairs at icann.org >>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>> _______________________________________________ >>> 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. >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Fri Apr 8 03:50:39 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 8 Apr 2022 10:50:39 +1000 Subject: [NCSG-PC] NCSG policy call invite/reminder Message-ID: Hi Brenda, I hope you are well. Would you mind sending a reminder about our policy call next week? I have it in my calendar but many members seem not to have it. The draft Agenda is below: 1. Welcome & Introduction 2. GNSO Council Agenda walk-through 3. Update: EPDP-IGOs Final Report 4. Update: Council SSAD ODA small group report 5. Update: Council DNS abuse small team 6. Update: Closed Generics 7. Administrative updates & any other business a. Uniform Domain Name Dispute Resolution Policy (UDRP) public comment. b. Root Zone Label Generation Rules Version 5 (RZ-LGR-5) Warmly, Tomslin -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Fri Apr 8 04:39:35 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Fri, 8 Apr 2022 03:39:35 +0200 Subject: [NCSG-PC] Fwd: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 In-Reply-To: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> References: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> Message-ID: Hey all, Hope this email finds everyone well! As you know, ICANN74 will be a hybrid meeting hosted in The Hague. For that, we need to submit the councillors and NCSG travellers soon. Therefore, this email is to ask you - councillors - to let me know whether you are planning to attend ICANN74 by Thursday, April 14th. For those who are not able or comfortable to attend meetings yet, we kindly ask that you reply to this email so that we can select a substitute. Best, Bruna ---------- Forwarded message --------- From: Terri Agnew Date: Thu 7. Apr 2022 at 04:39 Subject: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 To: bruna.mrtns at gmail.com , mesumbeslin at gmail.com < mesumbeslin at gmail.com>, Andrea Glandon Cc: gnso-secs at icann.org Dear all, In order to service your travel needs for ICANN74 in The Hauge in a timely fashion, please submit your ICANN74 Meeting database to gnso-secs at icann.org by *Thursday, 14 April 2022 *in order to be submitted by deadline of 15 April 2022. As a reminder, for the AGM meeting only, incoming Councilors get funding, as well as the then-incumbent Councilors. A timely response would be appreciated in view of visa issues and the OFAC review. The deadline for submissions is critical to allow for confirmed reservation numbers as required for visa and travel arrangements. *WHAT IS NEW FOR TRAVELERS* 1. *WAIVER*. Funded Travelers are expected to sign an acknowledgement and waiver for ICANN74. This acknowledgement and waiver is built in the ICANN74 Registration for anyone that is registering for in-person participation. Funded Travelers will need to register using this specific link which will be sent on their ?Travel Funding Confirmation Email.? Funded travelers are expected to comply with the acknowledgement and waiver. If they are unable or unwilling to agree to these terms, they are able to participate in the meeting remotely and their request to have travel funding will be provided to another person. ICANN org will provide more information about the specific support that will be offered to Funded Travelers in the case of emergencies or other non-standard situations. You can read the acknowledgment and waiver text with the attached document that can be shared with funded travelers. *NOTE:* The acknowledgement includes that Funded Travelers have read, understand, and agree to comply with the Community Travel Support Guidelines. https://www.icann.org/en/system/files/files/community-travel-support-guidelines-01jul20-en.pdf 2. *TRAVEL ARRIVAL MEASURES*. As with all international travel, all travelers have a responsibility to understand the entry and exit requirements of their travel and determine if they can meet those requirements before committing to the travel. Travelers may review specific travel requirements by visiting https://apply.joinsherpa.com/map or their local government international traveler websites. - To see travel requirements to enter the Netherlands based on their location, visit https://reizentijdenscorona.rijksoverheid.nl/en. - ICANN is committed to ensuring an inclusive Policy Forum that provides an equal opportunity for all to engage on important policy matters. If funded travelers are not eligible or cannot meet the entry requirements as outlined by the government of the Netherlands, we are confident they will find the virtual participation experience equally as engaging. 3. *CONCUR*. During the pandemic, ICANN org used this opportunity to make some enhancements for our funded travelers experience. We are happy to announce that all funded travelers are now able to book their travel using Concur, an online travel booking tool. Previous booking options with a live person agent with FCM are still available to Funded Travelers. Instructions on how to book travel will be provided to funded travelers who are confirmed and eligible. Reminder: - GNSO supported traveler with a designated hotel accommodation funding, a hotel room is automatically secured for you, please *DO NOT* book your own hotel as it is un-reimbursable. - All personal data provided to ICANN org in for purposes of providing travel support for participants related to ICANN events will be processed in accordance with the ICANN Privacy Policy [icann.org] . Should you have any questions or concerns about this Privacy Policy and our privacy practices, you may contact us at privacy at icann.org. Please note that when requesting travel support, in the interest of fairness and in light of budget restrictions we would like you to take the following into consideration: 1. Respond timely to ICANN Travel regarding your upcoming travel. 2. If you require a visa to enter the country, please make sure to acquire your visa immediately. Please contact the ICANN travel team to let them know you will need a visa. 3. Requests past the deadline will be handled on a case by case basis by ICANN. All additional travelers added after the 90-day deadline are subject to availability, may NOT be placed in the same hotel as their funded traveler groups, and may not be able to attend due to visa issues. 4. If possible please book direct travel requests. Detours and multi-stop trips are unfortunately not guaranteed. 5. Strictly limit your travel from your home to the ICANN meeting venue. 6. Approved date of arrival/departure for this meeting is *ARRIVAL: 12 June 2022 and DEPARTURE: 17 June 2022* 7. If travelers want to extend their stay this must be done at their own expense and should contact the hotel directly once the ICANN hotel confirmation has be sent to them. 8. *Privately Booked Reservations*: ICANN will not refund or take over accommodations directly booked by the funded traveler. If a replacement has an existing hotel reservation, they will need to cancel their reservation and ICANN will not be able to take over their reservation. Many thanks for your cooperation! Thank you. With kind regards, *Terri* * ---* *Terri Agnew* Policy Operations Specialist (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) *Skype ID:* terri.agnew.icann Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Information for Funded Travelers on ICANN74[4].pdf Type: application/pdf Size: 493502 bytes Desc: not available URL: From wisdom.dk at gmail.com Fri Apr 8 07:48:12 2022 From: wisdom.dk at gmail.com (Wisdom Donkor) Date: Fri, 8 Apr 2022 04:48:12 +0000 Subject: [NCSG-PC] NCSG policy call invite/reminder In-Reply-To: References: Message-ID: Hello Tomslin, Thanks very much for the information On Fri, 8 Apr 2022, 12:50 am Tomslin Samme-Nlar, wrote: > Hi Brenda, > > I hope you are well. Would you mind sending a reminder about our policy > call next week? I have it in my calendar but many members seem not to have > it. > > The draft Agenda is below: > > 1. Welcome & Introduction > > > > 2. GNSO Council Agenda walk-through > > > > 3. Update: EPDP-IGOs Final Report > > > 4. Update: Council SSAD ODA small group report > > > 5. Update: Council DNS abuse small team > > > 6. Update: Closed Generics > > 7. Administrative updates & any other business > > > a. Uniform Domain Name Dispute Resolution Policy (UDRP) public comment. > b. Root Zone Label Generation Rules Version 5 (RZ-LGR-5) > > > > Warmly, > Tomslin > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Fri Apr 8 15:40:47 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 8 Apr 2022 22:40:47 +1000 Subject: [NCSG-PC] Fwd: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 In-Reply-To: References: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> Message-ID: I will not be attending in person @Bruna. Warmly, Tomslin On Fri, 8 Apr 2022, 11:39 Bruna Martins dos Santos, wrote: > Hey all, > > Hope this email finds everyone well! > > As you know, ICANN74 will be a hybrid meeting hosted in The Hague. For > that, we need to submit the councillors and NCSG travellers soon. > > Therefore, this email is to ask you - councillors - to let me know whether > you are planning to attend ICANN74 by Thursday, April 14th. For those who > are not able or comfortable to attend meetings yet, we kindly ask that > you reply to this email so that we can select a substitute. > > Best, > Bruna > > > > ---------- Forwarded message --------- > From: Terri Agnew > Date: Thu 7. Apr 2022 at 04:39 > Subject: ICANN74 | The Hague - Supported Travelers/Contractor Travelers > Database Due | Thursday, 14 April 2022 > To: bruna.mrtns at gmail.com , mesumbeslin at gmail.com < > mesumbeslin at gmail.com>, Andrea Glandon > Cc: gnso-secs at icann.org > > > Dear all, > > > > In order to service your travel needs for ICANN74 in The Hauge in a timely > fashion, please submit your ICANN74 Meeting database to > gnso-secs at icann.org by *Thursday, 14 April 2022 *in order to be submitted > by deadline of 15 April 2022. > > > > As a reminder, for the AGM meeting only, incoming Councilors get funding, > as well as the then-incumbent Councilors. > > > > A timely response would be appreciated in view of visa issues and the OFAC > review. The deadline for submissions is critical to allow for confirmed > reservation numbers as required for visa and travel arrangements. > > *WHAT IS NEW FOR TRAVELERS* > > > > > 1. *WAIVER*. Funded Travelers are expected to sign an acknowledgement > and waiver for ICANN74. This acknowledgement and waiver is built in the > ICANN74 Registration for anyone that is registering for in-person > participation. Funded Travelers will need to register using this specific > link which will be sent on their ?Travel Funding Confirmation Email.? > Funded travelers are expected to comply with the acknowledgement and > waiver. If they are unable or unwilling to agree to these terms, they are > able to participate in the meeting remotely and their request to have > travel funding will be provided to another person. ICANN org will provide > more information about the specific support that will be offered to Funded > Travelers in the case of emergencies or other non-standard situations. You > can read the acknowledgment and waiver text with the attached document that > can be shared with funded travelers. > > > > *NOTE:* The acknowledgement includes that Funded Travelers have read, > understand, and agree to comply with the Community Travel Support > Guidelines. > > > https://www.icann.org/en/system/files/files/community-travel-support-guidelines-01jul20-en.pdf > > > > > 2. *TRAVEL ARRIVAL MEASURES*. As with all international > travel, all travelers have a responsibility to understand the entry and > exit requirements of their travel and determine if they can meet those > requirements before committing to the travel. Travelers may review specific > travel requirements by visiting https://apply.joinsherpa.com/map or their > local government international traveler websites. > > - To see travel requirements to enter the Netherlands based on their > location, visit https://reizentijdenscorona.rijksoverheid.nl/en. > - ICANN is committed to ensuring an inclusive Policy Forum that > provides an equal opportunity for all to engage on important policy matters. > If funded travelers are not eligible or cannot meet the entry > requirements as outlined by the government of the Netherlands, we are > confident they will find the virtual participation experience equally as > engaging. > > > > 3. *CONCUR*. During the pandemic, ICANN org used this > opportunity to make some enhancements for our funded travelers experience. > We are happy to announce that all funded travelers are now able to book > their travel using Concur, an online travel booking tool. Previous booking > options with a live person agent with FCM are still available to Funded > Travelers. Instructions on how to book travel will be provided to funded > travelers who are confirmed and eligible. > > > > > > Reminder: > > - GNSO supported traveler with a designated hotel accommodation > funding, a hotel room is automatically secured for you, please *DO NOT* > book your own hotel as it is un-reimbursable. > - All personal data provided to ICANN org in for purposes of providing > travel support for participants related to ICANN events will be processed > in accordance with the ICANN Privacy Policy [icann.org] > . > Should you have any questions or concerns about this Privacy Policy and our > privacy practices, you may contact us at privacy at icann.org. > > > > Please note that when requesting travel support, in the interest of > fairness and in light of budget restrictions we would like you to take the > following into consideration: > > > > 1. Respond timely to ICANN Travel regarding your upcoming > travel. > > 2. If you require a visa to enter the country, please make > sure to acquire your visa immediately. Please contact the ICANN travel > team to let them know you will need a visa. > > 3. Requests past the deadline will be handled on a case by > case basis by ICANN. All additional travelers added after the 90-day > deadline are subject to availability, may NOT be placed in the same hotel > as their funded traveler groups, and may not be able to attend due to visa > issues. > > 4. If possible please book direct travel requests. Detours > and multi-stop trips are unfortunately not guaranteed. > > 5. Strictly limit your travel from your home to the ICANN > meeting venue. > > 6. Approved date of arrival/departure for this meeting is *ARRIVAL: > 12 June 2022 and DEPARTURE: 17 June 2022* > > 7. If travelers want to extend their stay this must be done > at their own expense and should contact the hotel directly once the ICANN > hotel confirmation has be sent to them. > > 8. *Privately Booked Reservations*: ICANN will not refund > or take over accommodations directly booked by the funded traveler. If a > replacement has an existing hotel reservation, they will need to cancel > their reservation and ICANN will not be able to take over their > reservation. > > > > Many thanks for your cooperation! > > Thank you. > > > > With kind regards, > > *Terri* > > * ---* > > *Terri Agnew* > > Policy Operations Specialist (GNSO) > > Internet Corporation for Assigned Names and Numbers (ICANN) > > *Skype ID:* terri.agnew.icann > > > > Find out more about the GNSO by visiting: https://learn.icann.org/ > > > Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO > > > Transcripts and recordings of GNSO Working Group and Council events are > located on the GNSO Master Calendar > > > > > > > > > > > > -- > > *Bruna Martins dos Santos * > > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von > Humboldt Foundation > > Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin > f?r Sozialforschung (WZB) > > Member | Coaliz?o Direitos na Rede > Chair | Non-Commercial Stakeholder Group at ICANN > > Co-Coordinator | Internet Governance Caucus > > Twitter: @boomartins // Skype: > bruna.martinsantos > *bruna.martinsdossantos at wzb.eu * and > bruna.mrtns at gmail.com > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Fri Apr 8 15:41:36 2022 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Fri, 8 Apr 2022 12:41:36 +0000 Subject: [NCSG-PC] REMINDER: NCSG Policy Call | 11 April at 11:30 UTC Message-ID: <9f70e85d172649e0b3030016f22c0f92@icann.org> Please join the NCSG Monthly Policy call on Monday, 11 April at 11:30 UTC. Additional time zone support here. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 WANT US TO CALL YOU? Please send dial-out request and apologies to brenda.brewer at icann.org. One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) PHONE ONLY DETAILS: Find your local number: https://icann.zoom.us/u/ayKmeftWg Meeting ID: 988 7818 9584 Phone only Passcode: 7740925615 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2561 bytes Desc: not available URL: From brenda.brewer at icann.org Fri Apr 8 16:04:52 2022 From: brenda.brewer at icann.org (Brenda Brewer) Date: Fri, 8 Apr 2022 13:04:52 +0000 Subject: [NCSG-PC] REMINDER: NCSG Policy Call | 11 April at 11:30 UTC Message-ID: <7B157450-11B2-410C-8D59-F45CFE9A528A@icann.org> Good day all, lease join the NCSG Monthly Policy call on Monday, 11 April at 11:30 UTC. Additional time zone support here. The join details are attached and noted below for your convenience. Thank you. Draft Agenda: 1. Welcome & Introduction 2. GNSO Council Agenda walk-through 3. Update: EPDP-IGOs Final Report 4. Update: Council SSAD ODA small group report 5. Update: Council DNS abuse small team 6. Update: Closed Generics 7. Administrative updates & any other business * Uniform Domain Name Dispute Resolution Policy (UDRP) public comment. * Root Zone Label Generation Rules Version 5 (RZ-LGR-5) Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) Kind regards, Andrea and Brenda -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: REMINDER- NCSG Policy Call 11 April at 11-30 UTC.ics Type: text/calendar Size: 2573 bytes Desc: REMINDER- NCSG Policy Call 11 April at 11-30 UTC.ics URL: From jumaropi at yahoo.com Fri Apr 8 16:17:24 2022 From: jumaropi at yahoo.com (Juan Manuel Rojas) Date: Fri, 8 Apr 2022 13:17:24 +0000 (UTC) Subject: [NCSG-PC] Fwd: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 In-Reply-To: References: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> Message-ID: <472290961.1770247.1649423844073@mail.yahoo.com> Dear Bruna, I am planning to attend this meeting Best Regards, JUAN MANUEL ROJAS P. Director - MINKA DIGITAL ColombiaGNSO Councilor - ICANNCivil Soc. Rep - CODECTI? (Comit? Departamental de Ciencia Tecnolog?a e Innovaci?n) Master IT candidate, Universidad de los AndesRegistered Linux User No.533108. Cel. +57 301 743 56 00 Instagram/Twitter:?@JmanuRojas ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? El jueves, 7 de abril de 2022, 08:39:58 p.?m. GMT-5, Bruna Martins dos Santos escribi?: Hey all,? Hope this email finds everyone well!? As you know, ICANN74 will be a hybrid meeting hosted in The Hague. For that, we need to submit the councillors and NCSG travellers soon.? Therefore, this email is to ask you - councillors - to let me know whether you are planning to attend ICANN74 by Thursday, April 14th. For those who are not able or comfortable to attend meetings yet, we kindly ask that you reply to this email?so that we can select a substitute. ? Best,?Bruna? ---------- Forwarded message --------- From: Terri Agnew Date: Thu 7. Apr 2022 at 04:39 Subject: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 To: bruna.mrtns at gmail.com , mesumbeslin at gmail.com , Andrea Glandon Cc: gnso-secs at icann.org Dearall, ? In order to service your travel needs for ICANN74 in The Hauge in a timely fashion, please submit your ICANN74Meeting database to gnso-secs at icann.orgby Thursday, 14 April 2022 in order to be submitted by deadline of 15 April 2022. ? As a reminder, for the AGM meeting only, incoming Councilors get funding, as well as the then-incumbent Councilors. ? A timely response would be appreciated in view of visa issues and the OFAC review. The deadline for submissions is critical to allow for confirmed reservation numbers as required for visa and travel arrangements. WHAT IS NEW FOR TRAVELERS - WAIVER. Funded Travelers are expected to sign an acknowledgement and waiver for ICANN74. This acknowledgement and waiver is built in the ICANN74 Registration for anyone that is registering for in-person participation. Funded Travelers will need to register using this specific link which will be sent on their ?Travel Funding Confirmation Email.? Funded travelers are expected to comply with the acknowledgement and waiver. If they are unable or unwilling to agree to these terms, they are able to participate in the meeting remotely and their request to have travel funding will be provided to another person. ICANN org will provide more information about the specific support that will be offered to Funded Travelers in the case of emergencies or other non-standard situations. You can read the acknowledgment and waiver text with the attached document that can be shared with funded travelers. ? NOTE:?The acknowledgement includes that Funded Travelers have read, understand, and agree to comply with the Community Travel Support Guidelines. https://www.icann.org/en/system/files/files/community-travel-support-guidelines-01jul20-en.pdf? ? 2.????????????TRAVEL ARRIVAL MEASURES. As with all international travel, all travelers have a responsibility to understand the entry and exit requirements of their travel and determine if they can meet those requirements before committing to the travel. Travelers may review specific travel requirements by visitinghttps://apply.joinsherpa.com/map?or their local government international traveler websites.? - To see travel requirements to enter the Netherlands based on their location, visit?https://reizentijdenscorona.rijksoverheid.nl/en.? - ICANN is committed to ensuring an inclusive Policy Forum that provides an equal opportunity for all to engage on important policy matters.?If funded travelers are not eligible or cannot meet the entry requirements as outlined by the government of the Netherlands, we are confident they will find the virtual participation experience equally as engaging.? ? 3.????????????CONCUR. During the pandemic, ICANN org used this opportunity to make some enhancements for our funded travelers experience. We are happy to announce that all funded travelers are now able to book their travel using Concur, an online travel booking tool. Previous booking options with a live person agent with FCM are still available to Funded Travelers. Instructions on how to book travel will be provided to funded travelers who are confirmed and eligible.? ? ? Reminder: - GNSO supported traveler with a designated hotel accommodation funding, a hotel room is automatically secured for you, pleaseDO NOT book your own hotel as it is un-reimbursable.?? - All personal data provided to ICANN org in for purposes of providing travel support for participants related to ICANN events will be processed in accordance with the ICANN Privacy Policy [icann.org].? Should you have any questions or concerns about this Privacy Policy and our privacy practices, you may contact us atprivacy at icann.org. ? Please note that when requesting travel support, in the interest of fairness and in light of budget restrictions?we would like you to take the following into consideration: ? 1.??????????????Respond?timely to ICANN Travel regarding your upcoming travel. 2.??????????????If you require a visa to enter the country, please make sure to acquire your visa immediately.?Please contact the ICANN travel team to let them know you will need a visa. 3.??????????????Requests past the deadline will be handled on a case by case basis by ICANN. All additional travelers added after the 90-day deadline are subject to availability, may NOT be placed in the same hotel as their funded traveler groups, and may not be able to attend due to visa issues. 4.??????????????If possible pleasebook?direct travel requests.?Detours and multi-stop trips are unfortunately not guaranteed. 5.??????????????Strictly limit your travel from your home to the ICANN meeting venue.? 6.??????????????Approved date of arrival/departure for this meeting isARRIVAL: 12 June 2022 and DEPARTURE: 17 June 2022 7.??????????????If travelers want to extend their stay this must be done at their own expense and should contact the hotel directly once the ICANN hotel confirmation has be sent to them. 8.??????????????Privately Booked Reservations:?ICANN will not refund or take over accommodations directly booked by the funded traveler. If a replacement has an existing hotel reservation, they will need to cancel their reservation and ICANN will not be able to take over their reservation.? ? ? ?Many thanks for your cooperation! ?Thank you.? ? With kind regards, Terri ????????????--- Terri Agnew Policy Operations Specialist (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID:? terri.agnew.icann ? Find out more about the GNSO by visiting:?https://learn.icann.org/ Follow @GNSO on Twitter:?https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the?GNSO Master Calendar? ? ? ? ? ? -- Bruna Martins dos Santos? German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) |?Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede? Chair?|?Non-Commercial Stakeholder Group at ICANN Co-Coordinator?|?Internet Governance Caucus? Twitter:?@boomartins?//?Skype: bruna.martinsantosbruna.martinsdossantos at wzb.eu?and bruna.mrtns at gmail.com_______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From wisdom.dk at gmail.com Fri Apr 8 20:32:14 2022 From: wisdom.dk at gmail.com (Wisdom Donkor) Date: Fri, 8 Apr 2022 17:32:14 +0000 Subject: [NCSG-PC] Fwd: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 In-Reply-To: References: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> Message-ID: Hello Bruna, I will be attending. On Fri, 8 Apr 2022, 12:41 pm Tomslin Samme-Nlar, wrote: > I will not be attending in person @Bruna. > > Warmly, > Tomslin > > On Fri, 8 Apr 2022, 11:39 Bruna Martins dos Santos, > wrote: > >> Hey all, >> >> Hope this email finds everyone well! >> >> As you know, ICANN74 will be a hybrid meeting hosted in The Hague. For >> that, we need to submit the councillors and NCSG travellers soon. >> >> Therefore, this email is to ask you - councillors - to let me know >> whether you are planning to attend ICANN74 by Thursday, April 14th. For >> those who are not able or comfortable to attend meetings yet, we kindly >> ask that you reply to this email so that we can select a substitute. >> >> Best, >> Bruna >> >> >> >> ---------- Forwarded message --------- >> From: Terri Agnew >> Date: Thu 7. Apr 2022 at 04:39 >> Subject: ICANN74 | The Hague - Supported Travelers/Contractor Travelers >> Database Due | Thursday, 14 April 2022 >> To: bruna.mrtns at gmail.com , mesumbeslin at gmail.com >> , Andrea Glandon >> Cc: gnso-secs at icann.org >> >> >> Dear all, >> >> >> >> In order to service your travel needs for ICANN74 in The Hauge in a >> timely fashion, please submit your ICANN74 Meeting database to >> gnso-secs at icann.org by *Thursday, 14 April 2022 *in order to be >> submitted by deadline of 15 April 2022. >> >> >> >> As a reminder, for the AGM meeting only, incoming Councilors get funding, >> as well as the then-incumbent Councilors. >> >> >> >> A timely response would be appreciated in view of visa issues and the >> OFAC review. The deadline for submissions is critical to allow for >> confirmed reservation numbers as required for visa and travel arrangements. >> >> *WHAT IS NEW FOR TRAVELERS* >> >> >> >> >> 1. *WAIVER*. Funded Travelers are expected to sign an acknowledgement >> and waiver for ICANN74. This acknowledgement and waiver is built in the >> ICANN74 Registration for anyone that is registering for in-person >> participation. Funded Travelers will need to register using this specific >> link which will be sent on their ?Travel Funding Confirmation Email.? >> Funded travelers are expected to comply with the acknowledgement and >> waiver. If they are unable or unwilling to agree to these terms, they are >> able to participate in the meeting remotely and their request to have >> travel funding will be provided to another person. ICANN org will provide >> more information about the specific support that will be offered to Funded >> Travelers in the case of emergencies or other non-standard situations. You >> can read the acknowledgment and waiver text with the attached document that >> can be shared with funded travelers. >> >> >> >> *NOTE:* The acknowledgement includes that Funded Travelers have read, >> understand, and agree to comply with the Community Travel Support >> Guidelines. >> >> >> https://www.icann.org/en/system/files/files/community-travel-support-guidelines-01jul20-en.pdf >> >> >> >> >> 2. *TRAVEL ARRIVAL MEASURES*. As with all international >> travel, all travelers have a responsibility to understand the entry and >> exit requirements of their travel and determine if they can meet those >> requirements before committing to the travel. Travelers may review specific >> travel requirements by visiting https://apply.joinsherpa.com/map or >> their local government international traveler websites. >> >> - To see travel requirements to enter the Netherlands based on their >> location, visit https://reizentijdenscorona.rijksoverheid.nl/en. >> - ICANN is committed to ensuring an inclusive Policy Forum that >> provides an equal opportunity for all to engage on important policy matters. >> If funded travelers are not eligible or cannot meet the entry >> requirements as outlined by the government of the Netherlands, we are >> confident they will find the virtual participation experience equally as >> engaging. >> >> >> >> 3. *CONCUR*. During the pandemic, ICANN org used this >> opportunity to make some enhancements for our funded travelers experience. >> We are happy to announce that all funded travelers are now able to book >> their travel using Concur, an online travel booking tool. Previous booking >> options with a live person agent with FCM are still available to Funded >> Travelers. Instructions on how to book travel will be provided to funded >> travelers who are confirmed and eligible. >> >> >> >> >> >> Reminder: >> >> - GNSO supported traveler with a designated hotel accommodation >> funding, a hotel room is automatically secured for you, please *DO >> NOT* book your own hotel as it is un-reimbursable. >> - All personal data provided to ICANN org in for purposes of >> providing travel support for participants related to ICANN events will be >> processed in accordance with the ICANN Privacy Policy [icann.org] >> . >> Should you have any questions or concerns about this Privacy Policy and our >> privacy practices, you may contact us at privacy at icann.org. >> >> >> >> Please note that when requesting travel support, in the interest of >> fairness and in light of budget restrictions we would like you to take the >> following into consideration: >> >> >> >> 1. Respond timely to ICANN Travel regarding your upcoming >> travel. >> >> 2. If you require a visa to enter the country, please make >> sure to acquire your visa immediately. Please contact the ICANN travel >> team to let them know you will need a visa. >> >> 3. Requests past the deadline will be handled on a case by >> case basis by ICANN. All additional travelers added after the 90-day >> deadline are subject to availability, may NOT be placed in the same hotel >> as their funded traveler groups, and may not be able to attend due to visa >> issues. >> >> 4. If possible please book direct travel requests. Detours >> and multi-stop trips are unfortunately not guaranteed. >> >> 5. Strictly limit your travel from your home to the ICANN >> meeting venue. >> >> 6. Approved date of arrival/departure for this meeting is *ARRIVAL: >> 12 June 2022 and DEPARTURE: 17 June 2022* >> >> 7. If travelers want to extend their stay this must be >> done at their own expense and should contact the hotel directly once the >> ICANN hotel confirmation has be sent to them. >> >> 8. *Privately Booked Reservations*: ICANN will not refund >> or take over accommodations directly booked by the funded traveler. If a >> replacement has an existing hotel reservation, they will need to cancel >> their reservation and ICANN will not be able to take over their >> reservation. >> >> >> >> Many thanks for your cooperation! >> >> Thank you. >> >> >> >> With kind regards, >> >> *Terri* >> >> * ---* >> >> *Terri Agnew* >> >> Policy Operations Specialist (GNSO) >> >> Internet Corporation for Assigned Names and Numbers (ICANN) >> >> *Skype ID:* terri.agnew.icann >> >> >> >> Find out more about the GNSO by visiting: https://learn.icann.org/ >> >> >> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO >> >> >> Transcripts and recordings of GNSO Working Group and Council events are >> located on the GNSO Master Calendar >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> *Bruna Martins dos Santos * >> >> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander >> von Humboldt Foundation >> >> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum >> Berlin f?r Sozialforschung (WZB) >> >> Member | Coaliz?o Direitos na Rede >> Chair | Non-Commercial Stakeholder Group at ICANN >> >> Co-Coordinator | Internet Governance Caucus >> >> Twitter: @boomartins // Skype: >> bruna.martinsantos >> *bruna.martinsdossantos at wzb.eu * and >> bruna.mrtns at gmail.com >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Fri Apr 8 23:08:05 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 9 Apr 2022 06:08:05 +1000 Subject: [NCSG-PC] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> Message-ID: Hi Manju, Thank you so much for the update. Nice strategy there with the small team representation. Do you know when that deferral will be brought to the council's attention? Or maybe I missed it in my hundreds of emails. Thanks again. Tomslin On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: > Hi team, > > Borrowing this thread to report back to you about what happened in the > small team. > > So as you might have guessed, I was the only one saying no to the > 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the > discussion of how we engage with GAC in this 'facilitated dialogue' but > thankfully they still respected our objection. My first point of objection > is that the small team is really not representative enough to make the > decision of whether the Council should meet with the GAC. For now, we > agreed to refer this back to the Council and make the decision at the > Council level. > > I'm afraid though NCSG would be the only one saying no when we're at the > Council level. Also when this pops up, we really have to have our statement > ready explaining why we're saying no. I've put notes in the document > Tomslin created and Kathy has been extremely helpful by providing reference > material and edits: > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > > We will still need to phrase them into a formal statement, but I think > it'd be an easy task now we have all the contents. > > Best, > Manju > > On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar > wrote: > >> Hi team, >> >> I just wanted to call your attention to this response we promised to put >> together on the board proposed dialogue between GAC and Council on closed >> generics. The Council small team is about to be activated to start >> deliberations and I believe @??? Manju Chen who is >> representing us there hopes to rely on the response we pen down to guide >> her contribution to that team. >> >> In this regard, can I request that we find some time to please put our >> ideas down on the Google form >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> Looking forward to your help with this. In the meantime, i'll review my >> meeting notes and put down some feedback we got during our policy call on >> the document. >> >> Warmly, >> Tomslin >> >> On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, >> wrote: >> >>> Hi all, >>> >>> As a follow-up to my previous email regarding the board's proposed >>> facilitated dialogue between GAC and GNSO council, I have created this >>> Google doc [ >>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>> ] to capture our response to this proposal in the form of a letter to the >>> council small team on Closed Generics. >>> >>> Inputs to the document are welcomed and for your convenience, attached >>> again is the letter from the board and the accompanying framing paper. >>> >>> Regards, >>> Tomslin >>> >>> >>> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar >>> wrote: >>> >>>> Dear everyone, >>>> >>>> Here is the framing paper on the board's proposed dialogue between GNSO >>>> Council and the GAC on Closed Generics that was promised. >>>> >>>> Comments are welcomed. I will also be sending a separate email with a >>>> link to the Google doc where we intend to draft a letter as a response to >>>> this. >>>> >>>> Regards, >>>> Tomslin >>>> >>>> >>>> ---------- Forwarded message --------- >>>> From: Wendy Profit via Gnso-chairs >>>> Date: Fri, 11 Mar 2022 at 04:33 >>>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal >>>> Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>> To: manal.ismail at board.icann.org , Manal >>>> Ismail , philippe.fouquart at orange.com < >>>> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >>>> gnso-chairs at icann.org> >>>> Cc: Secretary , Correspondence < >>>> Correspondence at icann.org>, Board Ops Team , >>>> gnso-secs at icann.org , GACSTAFF < >>>> gac-staff at icann.org>, Maarten Botterman < >>>> maarten.botterman at board.icann.org> >>>> >>>> >>>> Dear Manal and Philippe, >>>> >>>> >>>> >>>> Pursuant to the letter sent recently (6 March 2022, attached for >>>> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >>>> Process for a GAC - GNSO Council Dialogue on Closed Generics?, also >>>> attached. >>>> >>>> >>>> >>>> Thank you and best regards, >>>> >>>> >>>> >>>> Wendy Profit >>>> >>>> ICANN >>>> >>>> Board Operations Senior Manager >>>> >>>> 12025 Waterfront Drive, Suite 300 >>>> >>>> Los Angeles, CA 90094 >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> *From: *Wendy Profit >>>> *Date: *Sunday, March 6, 2022 at 3:58 PM >>>> *To: *"manal.ismail at board.icann.org" , " >>>> manal at tra.gov.eg" , "philippe.fouquart at orange.com" < >>>> philippe.fouquart at orange.com> >>>> *Cc: *Maarten Botterman , " >>>> gnso-chairs at icann.org" , GACSTAFF < >>>> gac-staff at icann.org>, "gnso-secs at icann.org" , >>>> ICANN Board Ops , Correspondence < >>>> Correspondence at icann.org>, Secretary >>>> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >>>> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>> >>>> >>>> >>>> Dear Manal and Philippe, >>>> >>>> >>>> >>>> Please find the attached letter from ICANN Chair Maarten Botterman >>>> regarding a proposed formal consultation between the GAC and GNSO Council >>>> on how to handle the subject of closed generics in gTLD applications. >>>> >>>> >>>> >>>> Thank you and best regards, >>>> >>>> >>>> >>>> Wendy Profit >>>> >>>> ICANN >>>> >>>> Board Operations Senior Manager >>>> >>>> 12025 Waterfront Drive, Suite 300 >>>> >>>> Los Angeles, CA 90094 >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Gnso-chairs mailing list >>>> Gnso-chairs at icann.org >>>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>>> _______________________________________________ >>>> 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. >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Mon Apr 11 02:34:58 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Mon, 11 Apr 2022 09:34:58 +1000 Subject: [NCSG-PC] GNSO Council DNS abuse small team Questions Message-ID: Hi everyone, As you must have read from the update Wisdom shared a while back, some questions were asked during an outreach by the small team and though our community didn't provide any feedback to Wisdom's email, I think it will be a good idea for us to provide some sort of official response to those questions back to the small team. N.B: I went to observe the small teams meeting last week and realised that all other SGs have or are planning to provide responses to those questions. I have taken the liberty to draft a few responses, which I hope you all can make changes to it as well to better reflect our position on DNS abuse. The Google doc is here: https://docs.google.com/document/d/1Hg468obYDwylFQ6q-3AX6m7UxZvNY1EXGpBFJ-WVd_0/edit?usp=sharing The Questions again are: What specific problem(s) would policy development in particular be expected to address and why do you believe that policy development is the right mechanism to solve those problems? Proposed Response: The NCSG does not believe there are any problems discussed in the community that require policy development effort. Moreover, a common definition of DNS abuse which is in alignment with ICANN?s bylaws and technical remit first needs to be adopted by the community. What do you believe are the expected outcomes if policy development would be undertaken, taking into account the remit of ICANN and more specifically GNSO policy development in this context? Proposed Response: None, since we do not see any problem requiring policy development. Do you (or your community group) have any expectations with regards to possible next steps the GNSO Council could or should undertake in the context of policy development? Proposed Response: Our expectation of next steps is for a common community definition of DNS abuse which is in alignment with ICANN?s bylaws and technical remit. Tomslin -------------- next part -------------- An HTML attachment was scrubbed... URL: From manju at nii.org.tw Mon Apr 11 05:19:02 2022 From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=) Date: Mon, 11 Apr 2022 10:19:02 +0800 Subject: [NCSG-PC] Fwd: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 In-Reply-To: References: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> Message-ID: Hi Bruna, I plan to attend the meeting in person. Many thanks! Best, Manju On Sat, Apr 9, 2022 at 1:32 AM Wisdom Donkor wrote: > Hello Bruna, > I will be attending. > > On Fri, 8 Apr 2022, 12:41 pm Tomslin Samme-Nlar, > wrote: > >> I will not be attending in person @Bruna. >> >> Warmly, >> Tomslin >> >> On Fri, 8 Apr 2022, 11:39 Bruna Martins dos Santos, < >> bruna.mrtns at gmail.com> wrote: >> >>> Hey all, >>> >>> Hope this email finds everyone well! >>> >>> As you know, ICANN74 will be a hybrid meeting hosted in The Hague. For >>> that, we need to submit the councillors and NCSG travellers soon. >>> >>> Therefore, this email is to ask you - councillors - to let me know >>> whether you are planning to attend ICANN74 by Thursday, April 14th. For >>> those who are not able or comfortable to attend meetings yet, we kindly >>> ask that you reply to this email so that we can select a substitute. >>> >>> Best, >>> Bruna >>> >>> >>> >>> ---------- Forwarded message --------- >>> From: Terri Agnew >>> Date: Thu 7. Apr 2022 at 04:39 >>> Subject: ICANN74 | The Hague - Supported Travelers/Contractor Travelers >>> Database Due | Thursday, 14 April 2022 >>> To: bruna.mrtns at gmail.com , mesumbeslin at gmail.com >>> , Andrea Glandon >>> Cc: gnso-secs at icann.org >>> >>> >>> Dear all, >>> >>> >>> >>> In order to service your travel needs for ICANN74 in The Hauge in a >>> timely fashion, please submit your ICANN74 Meeting database to >>> gnso-secs at icann.org by *Thursday, 14 April 2022 *in order to be >>> submitted by deadline of 15 April 2022. >>> >>> >>> >>> As a reminder, for the AGM meeting only, incoming Councilors get >>> funding, as well as the then-incumbent Councilors. >>> >>> >>> >>> A timely response would be appreciated in view of visa issues and the >>> OFAC review. The deadline for submissions is critical to allow for >>> confirmed reservation numbers as required for visa and travel arrangements. >>> >>> *WHAT IS NEW FOR TRAVELERS* >>> >>> >>> >>> >>> 1. *WAIVER*. Funded Travelers are expected to sign an >>> acknowledgement and waiver for ICANN74. This acknowledgement and waiver is >>> built in the ICANN74 Registration for anyone that is registering for >>> in-person participation. Funded Travelers will need to register using this >>> specific link which will be sent on their ?Travel Funding Confirmation >>> Email.? Funded travelers are expected to comply with the acknowledgement >>> and waiver. If they are unable or unwilling to agree to these terms, they >>> are able to participate in the meeting remotely and their request to have >>> travel funding will be provided to another person. ICANN org will provide >>> more information about the specific support that will be offered to Funded >>> Travelers in the case of emergencies or other non-standard situations. You >>> can read the acknowledgment and waiver text with the attached document that >>> can be shared with funded travelers. >>> >>> >>> >>> *NOTE:* The acknowledgement includes that Funded Travelers have read, >>> understand, and agree to comply with the Community Travel Support >>> Guidelines. >>> >>> >>> https://www.icann.org/en/system/files/files/community-travel-support-guidelines-01jul20-en.pdf >>> >>> >>> >>> >>> 2. *TRAVEL ARRIVAL MEASURES*. As with all international >>> travel, all travelers have a responsibility to understand the entry and >>> exit requirements of their travel and determine if they can meet those >>> requirements before committing to the travel. Travelers may review specific >>> travel requirements by visiting https://apply.joinsherpa.com/map or >>> their local government international traveler websites. >>> >>> - To see travel requirements to enter the Netherlands based on their >>> location, visit https://reizentijdenscorona.rijksoverheid.nl/en. >>> - ICANN is committed to ensuring an inclusive Policy Forum that >>> provides an equal opportunity for all to engage on important policy matters. >>> If funded travelers are not eligible or cannot meet the entry >>> requirements as outlined by the government of the Netherlands, we are >>> confident they will find the virtual participation experience equally as >>> engaging. >>> >>> >>> >>> 3. *CONCUR*. During the pandemic, ICANN org used this >>> opportunity to make some enhancements for our funded travelers experience. >>> We are happy to announce that all funded travelers are now able to book >>> their travel using Concur, an online travel booking tool. Previous booking >>> options with a live person agent with FCM are still available to Funded >>> Travelers. Instructions on how to book travel will be provided to funded >>> travelers who are confirmed and eligible. >>> >>> >>> >>> >>> >>> Reminder: >>> >>> - GNSO supported traveler with a designated hotel accommodation >>> funding, a hotel room is automatically secured for you, please *DO >>> NOT* book your own hotel as it is un-reimbursable. >>> - All personal data provided to ICANN org in for purposes of >>> providing travel support for participants related to ICANN events will be >>> processed in accordance with the ICANN Privacy Policy [icann.org] >>> . >>> Should you have any questions or concerns about this Privacy Policy and our >>> privacy practices, you may contact us at privacy at icann.org. >>> >>> >>> >>> Please note that when requesting travel support, in the interest of >>> fairness and in light of budget restrictions we would like you to take the >>> following into consideration: >>> >>> >>> >>> 1. Respond timely to ICANN Travel regarding your upcoming >>> travel. >>> >>> 2. If you require a visa to enter the country, please >>> make sure to acquire your visa immediately. Please contact the ICANN >>> travel team to let them know you will need a visa. >>> >>> 3. Requests past the deadline will be handled on a case >>> by case basis by ICANN. All additional travelers added after the 90-day >>> deadline are subject to availability, may NOT be placed in the same hotel >>> as their funded traveler groups, and may not be able to attend due to visa >>> issues. >>> >>> 4. If possible please book direct travel >>> requests. Detours and multi-stop trips are unfortunately not guaranteed. >>> >>> 5. Strictly limit your travel from your home to the ICANN >>> meeting venue. >>> >>> 6. Approved date of arrival/departure for this meeting is *ARRIVAL: >>> 12 June 2022 and DEPARTURE: 17 June 2022* >>> >>> 7. If travelers want to extend their stay this must be >>> done at their own expense and should contact the hotel directly once the >>> ICANN hotel confirmation has be sent to them. >>> >>> 8. *Privately Booked Reservations*: ICANN will not refund >>> or take over accommodations directly booked by the funded traveler. If a >>> replacement has an existing hotel reservation, they will need to cancel >>> their reservation and ICANN will not be able to take over their >>> reservation. >>> >>> >>> >>> Many thanks for your cooperation! >>> >>> Thank you. >>> >>> >>> >>> With kind regards, >>> >>> *Terri* >>> >>> * ---* >>> >>> *Terri Agnew* >>> >>> Policy Operations Specialist (GNSO) >>> >>> Internet Corporation for Assigned Names and Numbers (ICANN) >>> >>> *Skype ID:* terri.agnew.icann >>> >>> >>> >>> Find out more about the GNSO by visiting: https://learn.icann.org/ >>> >>> >>> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO >>> >>> >>> Transcripts and recordings of GNSO Working Group and Council events are >>> located on the GNSO Master Calendar >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> *Bruna Martins dos Santos * >>> >>> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander >>> von Humboldt Foundation >>> >>> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum >>> Berlin f?r Sozialforschung (WZB) >>> >>> Member | Coaliz?o Direitos na Rede >>> Chair | Non-Commercial Stakeholder Group at ICANN >>> >>> Co-Coordinator | Internet Governance Caucus >>> >>> Twitter: @boomartins // Skype: >>> bruna.martinsantos >>> *bruna.martinsdossantos at wzb.eu * and >>> bruna.mrtns at gmail.com >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From manju at nii.org.tw Mon Apr 11 05:22:34 2022 From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=) Date: Mon, 11 Apr 2022 10:22:34 +0800 Subject: [NCSG-PC] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> Message-ID: Hi Tomslin and all, Kurt and others obviously wanted it to be discussed in the Council meeting this week. Steve has suggested if that was the intent we could propose a late motion. I think NCSG is not in a hurry about this, so I'll let others handle it if they want to propose the motion. I can share more details and answer questions today later during our policy call. Best, Manju On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar wrote: > Hi Manju, > Thank you so much for the update. Nice strategy there with the small team > representation. Do you know when that deferral will be brought to the > council's attention? Or maybe I missed it in my hundreds of emails. > > Thanks again. > Tomslin > > > On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: > >> Hi team, >> >> Borrowing this thread to report back to you about what happened in the >> small team. >> >> So as you might have guessed, I was the only one saying no to the >> 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the >> discussion of how we engage with GAC in this 'facilitated dialogue' but >> thankfully they still respected our objection. My first point of objection >> is that the small team is really not representative enough to make the >> decision of whether the Council should meet with the GAC. For now, we >> agreed to refer this back to the Council and make the decision at the >> Council level. >> >> I'm afraid though NCSG would be the only one saying no when we're at the >> Council level. Also when this pops up, we really have to have our statement >> ready explaining why we're saying no. I've put notes in the document >> Tomslin created and Kathy has been extremely helpful by providing reference >> material and edits: >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> >> We will still need to phrase them into a formal statement, but I think >> it'd be an easy task now we have all the contents. >> >> Best, >> Manju >> >> On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar >> wrote: >> >>> Hi team, >>> >>> I just wanted to call your attention to this response we promised to put >>> together on the board proposed dialogue between GAC and Council on closed >>> generics. The Council small team is about to be activated to start >>> deliberations and I believe @??? Manju Chen who is >>> representing us there hopes to rely on the response we pen down to guide >>> her contribution to that team. >>> >>> In this regard, can I request that we find some time to please put our >>> ideas down on the Google form >>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>> >>> Looking forward to your help with this. In the meantime, i'll review my >>> meeting notes and put down some feedback we got during our policy call on >>> the document. >>> >>> Warmly, >>> Tomslin >>> >>> On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, >>> wrote: >>> >>>> Hi all, >>>> >>>> As a follow-up to my previous email regarding the board's proposed >>>> facilitated dialogue between GAC and GNSO council, I have created this >>>> Google doc [ >>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>> ] to capture our response to this proposal in the form of a letter to the >>>> council small team on Closed Generics. >>>> >>>> Inputs to the document are welcomed and for your convenience, attached >>>> again is the letter from the board and the accompanying framing paper. >>>> >>>> Regards, >>>> Tomslin >>>> >>>> >>>> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar >>>> wrote: >>>> >>>>> Dear everyone, >>>>> >>>>> Here is the framing paper on the board's proposed dialogue between >>>>> GNSO Council and the GAC on Closed Generics that was promised. >>>>> >>>>> Comments are welcomed. I will also be sending a separate email with a >>>>> link to the Google doc where we intend to draft a letter as a response to >>>>> this. >>>>> >>>>> Regards, >>>>> Tomslin >>>>> >>>>> >>>>> ---------- Forwarded message --------- >>>>> From: Wendy Profit via Gnso-chairs >>>>> Date: Fri, 11 Mar 2022 at 04:33 >>>>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal >>>>> Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>> To: manal.ismail at board.icann.org , >>>>> Manal Ismail , philippe.fouquart at orange.com < >>>>> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >>>>> gnso-chairs at icann.org> >>>>> Cc: Secretary , Correspondence < >>>>> Correspondence at icann.org>, Board Ops Team , >>>>> gnso-secs at icann.org , GACSTAFF < >>>>> gac-staff at icann.org>, Maarten Botterman < >>>>> maarten.botterman at board.icann.org> >>>>> >>>>> >>>>> Dear Manal and Philippe, >>>>> >>>>> >>>>> >>>>> Pursuant to the letter sent recently (6 March 2022, attached for >>>>> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >>>>> Process for a GAC - GNSO Council Dialogue on Closed Generics?, also >>>>> attached. >>>>> >>>>> >>>>> >>>>> Thank you and best regards, >>>>> >>>>> >>>>> >>>>> Wendy Profit >>>>> >>>>> ICANN >>>>> >>>>> Board Operations Senior Manager >>>>> >>>>> 12025 Waterfront Drive, Suite 300 >>>>> >>>>> Los Angeles, CA 90094 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> *From: *Wendy Profit >>>>> *Date: *Sunday, March 6, 2022 at 3:58 PM >>>>> *To: *"manal.ismail at board.icann.org" , " >>>>> manal at tra.gov.eg" , "philippe.fouquart at orange.com" < >>>>> philippe.fouquart at orange.com> >>>>> *Cc: *Maarten Botterman , " >>>>> gnso-chairs at icann.org" , GACSTAFF < >>>>> gac-staff at icann.org>, "gnso-secs at icann.org" , >>>>> ICANN Board Ops , Correspondence < >>>>> Correspondence at icann.org>, Secretary >>>>> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >>>>> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>> >>>>> >>>>> >>>>> Dear Manal and Philippe, >>>>> >>>>> >>>>> >>>>> Please find the attached letter from ICANN Chair Maarten Botterman >>>>> regarding a proposed formal consultation between the GAC and GNSO Council >>>>> on how to handle the subject of closed generics in gTLD applications. >>>>> >>>>> >>>>> >>>>> Thank you and best regards, >>>>> >>>>> >>>>> >>>>> Wendy Profit >>>>> >>>>> ICANN >>>>> >>>>> Board Operations Senior Manager >>>>> >>>>> 12025 Waterfront Drive, Suite 300 >>>>> >>>>> Los Angeles, CA 90094 >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Gnso-chairs mailing list >>>>> Gnso-chairs at icann.org >>>>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>>>> _______________________________________________ >>>>> 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. >>>>> >>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Mon Apr 11 14:11:46 2022 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Mon, 11 Apr 2022 11:11:46 +0000 Subject: [NCSG-PC] 20-minute REMINDER: NCSG Policy Call | 11 April at 11:30 UTC Message-ID: <7f3124f3d38c4275931e137cad093191@icann.org> Please join the NCSG Monthly Policy call on Monday, 11 April at 11:30 UTC. Additional time zone support here. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 WANT US TO CALL YOU? Please send dial-out request and apologies to brenda.brewer at icann.org. One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) PHONE ONLY DETAILS: Find your local number: https://icann.zoom.us/u/ayKmeftWg Meeting ID: 988 7818 9584 Phone only Passcode: 7740925615 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2574 bytes Desc: not available URL: From bruna.mrtns at gmail.com Mon Apr 11 14:17:11 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Mon, 11 Apr 2022 13:17:11 +0200 Subject: [NCSG-PC] 20-minute REMINDER: NCSG Policy Call | 11 April at 11:30 UTC In-Reply-To: <7f3124f3d38c4275931e137cad093191@icann.org> References: <7f3124f3d38c4275931e137cad093191@icann.org> Message-ID: Dear all, Apologies for not being able to join today?s call! I had a meeting at the same time and my agenda did not notify me about the clash. Best, Bruna On Mon 11. Apr 2022 at 13:11, ICANN Policy Calendar < PolicyCalendar at icann.org> wrote: > *Please join the NCSG Monthly Policy call on Monday, 11 April at 11:30 > UTC.* Additional time zone support here > > . > > > > Join Zoom Meeting: *https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 > * > > Meeting ID: 988 7818 9584 > > Passcode: i!y7.qx+11 > > > > *WANT US TO CALL YOU?* Please send dial-out request and apologies to *brenda.brewer at icann.org > **.* > > > > One tap mobile > > +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) > > +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) > > PHONE ONLY DETAILS: > > Find your local number: https://icann.zoom.us/u/ayKmeftWg > > Meeting ID: 988 7818 9584 > > Phone only Passcode: 7740925615 > > > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kathy at KathyKleiman.com Mon Apr 11 17:11:12 2022 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Mon, 11 Apr 2022 10:11:12 -0400 Subject: [NCSG-PC] GNSO Council DNS abuse small team Questions In-Reply-To: References: Message-ID: <5672b6b8-95dd-9bd1-52e7-1f1413713c12@KathyKleiman.com> I support these questions and answers. Best, Kathy On 4/10/2022 7:34 PM, Tomslin Samme-Nlar wrote: > Hi everyone, > > As you must have read from the update Wisdom shared a while back, some > questions were asked during an outreach by the small team and though > our community didn't provide any feedback to Wisdom's email, I think > it will be a good idea for us to provide some sort of official > response to those questions back to the small team. > N.B: I went to observe the small teams meeting last week and realised > that all other SGs have or are planning to provide responses to those > questions. > > I have taken the liberty to draft > > a few responses, which I hope you all can make changes to it as well > to better reflect our position on DNS abuse. The Google doc is here: > https://docs.google.com/document/d/1Hg468obYDwylFQ6q-3AX6m7UxZvNY1EXGpBFJ-WVd_0/edit?usp=sharing > > The Questions again are: > > What specific problem(s) would policy development in particular be > expected to address and why do you believe that policy development is > the right mechanism to solve those problems? > > > Proposed Response: The NCSG does not believe there are any problems > discussed in the community that require policy development effort. > Moreover, a common definition of DNS abuse which is in alignment with > ICANN?s bylaws and technical remit first needs to be adopted by the > community. > > > What do you believe are the expected outcomes if policy development > would be undertaken, taking into account the remit of ICANN and more > specifically GNSO policy development in this context? > > > Proposed Response: None, since we do not see any problem requiring > policy development. > > > Do you (or your community group) have any expectations with regards to > possible next steps the GNSO Council could or should undertake in the > context of policy development? > > > Proposed Response: Our expectation of next steps is for a common > community definition of DNS abuse which is in alignment with ICANN?s > bylaws and technical remit. > > > Tomslin > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From brenda.brewer at icann.org Tue Apr 12 00:22:06 2022 From: brenda.brewer at icann.org (Brenda Brewer) Date: Mon, 11 Apr 2022 21:22:06 +0000 Subject: [NCSG-PC] NCSG Policy Call - attendees, replay, chat - 11 April 2022 Message-ID: <69ACCACE-56D6-4BD6-B25F-54549E1863E9@icann.org> Dear NCSG members, Please find attendees, replay, and chat details for the NCSG Monthly Policy Call held Monday, 11 April 2022 at 11:30 UTC. The transcript will be sent upon completion. Thank you! Kind regards, Andrea and Brenda Attendees: Avri Doria, Benjamin Akinmoyeje, Bruna Martins dos Santos, Daniel Charles, Ephraim Percy Kenyanito, Farell Folly, Juan Manuel Rojas, Kathy Kleiman, Kenneth Herman, Manju Chen, Poncelet Ileleji, Rafik Dammak, Razoana Moslam, Robin Gross, Shah Zahidur Rahman, Stephanie Perrin, Tomslin Samme-Nlar, Wisdom Donkor | ICANN Org: Andrea Glandon, Brenda Brewer, Carlos Reyes Zoom Replay Link: \ https://icann.zoom.us/rec/play/42g_Lvdj3EYNSp1WkLEVFZa6mMv2G2aNpiWw26HIP1423FJE_WXvaI-Vvefy8q5JcKwUZmk6zNWPNiZt.I6c947Laea4NEGPV Zoom Audio Link: https://icann.zoom.us/rec/play/b8siW3Tmi1zsiTHhp-9WFywkqzB26_0jpVzeboR2aZU9Dq0DmEj673xmGNtNoGkrIsLvwOPl7CDQAbTz.H5037eExYDM0TKIh Zoom Chat Link: https://icann.zoom.us/rec/sdownload/uV5-22nkkJ9ACH9QxDOYVjjX6OKMgh4hT8Dxk1lR7jaFS6pJXBFbabfQA1ZviN_RebKvqgM7J-94wjVx.mZH1SMv9kS5igZqt -------------- next part -------------- An HTML attachment was scrubbed... URL: From manju at nii.org.tw Tue Apr 12 06:04:11 2022 From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=) Date: Tue, 12 Apr 2022 11:04:11 +0800 Subject: [NCSG-PC] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> Message-ID: Hi all, As discussed per yesterday's policy call, I've drafted our formal response to be sent to the Council (and the Board?) You can find the statement here: https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing Feedbacks and suggestions are welcome and will be highly appreciated! Best, Manju On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen wrote: > Hi Tomslin and all, > > Kurt and others obviously wanted it to be discussed in the Council meeting > this week. > Steve has suggested if that was the intent we could propose a late motion. > I think NCSG is not in a hurry about this, so I'll let others handle it if > they want to propose the motion. > > I can share more details and answer questions today later during our > policy call. > > Best, > Manju > > > > On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar > wrote: > >> Hi Manju, >> Thank you so much for the update. Nice strategy there with the small team >> representation. Do you know when that deferral will be brought to the >> council's attention? Or maybe I missed it in my hundreds of emails. >> >> Thanks again. >> Tomslin >> >> >> On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: >> >>> Hi team, >>> >>> Borrowing this thread to report back to you about what happened in the >>> small team. >>> >>> So as you might have guessed, I was the only one saying no to the >>> 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the >>> discussion of how we engage with GAC in this 'facilitated dialogue' but >>> thankfully they still respected our objection. My first point of objection >>> is that the small team is really not representative enough to make the >>> decision of whether the Council should meet with the GAC. For now, we >>> agreed to refer this back to the Council and make the decision at the >>> Council level. >>> >>> I'm afraid though NCSG would be the only one saying no when we're at the >>> Council level. Also when this pops up, we really have to have our statement >>> ready explaining why we're saying no. I've put notes in the document >>> Tomslin created and Kathy has been extremely helpful by providing reference >>> material and edits: >>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>> >>> >>> We will still need to phrase them into a formal statement, but I think >>> it'd be an easy task now we have all the contents. >>> >>> Best, >>> Manju >>> >>> On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar < >>> mesumbeslin at gmail.com> wrote: >>> >>>> Hi team, >>>> >>>> I just wanted to call your attention to this response we promised to >>>> put together on the board proposed dialogue between GAC and Council on >>>> closed generics. The Council small team is about to be activated to start >>>> deliberations and I believe @??? Manju Chen who is >>>> representing us there hopes to rely on the response we pen down to guide >>>> her contribution to that team. >>>> >>>> In this regard, can I request that we find some time to please put our >>>> ideas down on the Google form >>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>> >>>> Looking forward to your help with this. In the meantime, i'll review my >>>> meeting notes and put down some feedback we got during our policy call on >>>> the document. >>>> >>>> Warmly, >>>> Tomslin >>>> >>>> On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> As a follow-up to my previous email regarding the board's proposed >>>>> facilitated dialogue between GAC and GNSO council, I have created this >>>>> Google doc [ >>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>> ] to capture our response to this proposal in the form of a letter to the >>>>> council small team on Closed Generics. >>>>> >>>>> Inputs to the document are welcomed and for your convenience, attached >>>>> again is the letter from the board and the accompanying framing paper. >>>>> >>>>> Regards, >>>>> Tomslin >>>>> >>>>> >>>>> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar < >>>>> mesumbeslin at gmail.com> wrote: >>>>> >>>>>> Dear everyone, >>>>>> >>>>>> Here is the framing paper on the board's proposed dialogue between >>>>>> GNSO Council and the GAC on Closed Generics that was promised. >>>>>> >>>>>> Comments are welcomed. I will also be sending a separate email with a >>>>>> link to the Google doc where we intend to draft a letter as a response to >>>>>> this. >>>>>> >>>>>> Regards, >>>>>> Tomslin >>>>>> >>>>>> >>>>>> ---------- Forwarded message --------- >>>>>> From: Wendy Profit via Gnso-chairs >>>>>> Date: Fri, 11 Mar 2022 at 04:33 >>>>>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal >>>>>> Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>> To: manal.ismail at board.icann.org , >>>>>> Manal Ismail , philippe.fouquart at orange.com < >>>>>> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >>>>>> gnso-chairs at icann.org> >>>>>> Cc: Secretary , Correspondence < >>>>>> Correspondence at icann.org>, Board Ops Team , >>>>>> gnso-secs at icann.org , GACSTAFF < >>>>>> gac-staff at icann.org>, Maarten Botterman < >>>>>> maarten.botterman at board.icann.org> >>>>>> >>>>>> >>>>>> Dear Manal and Philippe, >>>>>> >>>>>> >>>>>> >>>>>> Pursuant to the letter sent recently (6 March 2022, attached for >>>>>> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >>>>>> Process for a GAC - GNSO Council Dialogue on Closed Generics?, also >>>>>> attached. >>>>>> >>>>>> >>>>>> >>>>>> Thank you and best regards, >>>>>> >>>>>> >>>>>> >>>>>> Wendy Profit >>>>>> >>>>>> ICANN >>>>>> >>>>>> Board Operations Senior Manager >>>>>> >>>>>> 12025 Waterfront Drive, Suite 300 >>>>>> >>>>>> Los Angeles, CA 90094 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> *From: *Wendy Profit >>>>>> *Date: *Sunday, March 6, 2022 at 3:58 PM >>>>>> *To: *"manal.ismail at board.icann.org" , >>>>>> "manal at tra.gov.eg" , "philippe.fouquart at orange.com" >>>>>> >>>>>> *Cc: *Maarten Botterman , " >>>>>> gnso-chairs at icann.org" , GACSTAFF < >>>>>> gac-staff at icann.org>, "gnso-secs at icann.org" , >>>>>> ICANN Board Ops , Correspondence < >>>>>> Correspondence at icann.org>, Secretary >>>>>> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >>>>>> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>> >>>>>> >>>>>> >>>>>> Dear Manal and Philippe, >>>>>> >>>>>> >>>>>> >>>>>> Please find the attached letter from ICANN Chair Maarten Botterman >>>>>> regarding a proposed formal consultation between the GAC and GNSO Council >>>>>> on how to handle the subject of closed generics in gTLD applications. >>>>>> >>>>>> >>>>>> >>>>>> Thank you and best regards, >>>>>> >>>>>> >>>>>> >>>>>> Wendy Profit >>>>>> >>>>>> ICANN >>>>>> >>>>>> Board Operations Senior Manager >>>>>> >>>>>> 12025 Waterfront Drive, Suite 300 >>>>>> >>>>>> Los Angeles, CA 90094 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Gnso-chairs mailing list >>>>>> Gnso-chairs at icann.org >>>>>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>>>>> _______________________________________________ >>>>>> 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. >>>>>> >>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Tue Apr 12 21:08:39 2022 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Tue, 12 Apr 2022 14:08:39 -0400 Subject: [NCSG-PC] [ncsg-dns-abuse-wg] GNSO Council DNS abuse small team Questions In-Reply-To: References: Message-ID: Hi Tomslin Thanks for this. I think generally it's good but asking for a definition might open doors to other problems. Here is DNSAI response to the council small team letter: https://dnsabuseinstitute.org/dnsai-response-gnso-small-team-dns-abuse/ Basically Graeme is suggesting micro narrowly focused pdps on issues related to ICANN mandate. But I find it a curious suggestion. Does he mean they should have PDPs on each kind of DNS abuse that are in ICANN's registrar agreement? Farzaneh On Sun, Apr 10, 2022 at 7:35 PM Tomslin Samme-Nlar via ncsg-dns-abuse-wg < ncsg-dns-abuse-wg at icann.org> wrote: > Hi everyone, > > As you must have read from the update Wisdom shared a while back, some > questions were asked during an outreach by the small team and though our > community didn't provide any feedback to Wisdom's email, I think it will be > a good idea for us to provide some sort of official response to those > questions back to the small team. > N.B: I went to observe the small teams meeting last week and realised that > all other SGs have or are planning to provide responses to those questions. > > I have taken the liberty to draft > > a few responses, which I hope you all can make changes to it as well to > better reflect our position on DNS abuse. The Google doc is here: > https://docs.google.com/document/d/1Hg468obYDwylFQ6q-3AX6m7UxZvNY1EXGpBFJ-WVd_0/edit?usp=sharing > > The Questions again are: > > What specific problem(s) would policy development in particular be > expected to address and why do you believe that policy development is the > right mechanism to solve those problems? > > Proposed Response: The NCSG does not believe there are any problems > discussed in the community that require policy development effort. > Moreover, a common definition of DNS abuse which is in alignment with > ICANN?s bylaws and technical remit first needs to be adopted by the > community. > > What do you believe are the expected outcomes if policy development would > be undertaken, taking into account the remit of ICANN and more specifically > GNSO policy development in this context? > > Proposed Response: None, since we do not see any problem requiring policy > development. > > Do you (or your community group) have any expectations with regards to > possible next steps the GNSO Council could or should undertake in the > context of policy development? > > Proposed Response: Our expectation of next steps is for a common > community definition of DNS abuse which is in alignment with ICANN?s bylaws > and technical remit. > > Tomslin > > _______________________________________________ > ncsg-dns-abuse-wg mailing list > ncsg-dns-abuse-wg at icann.org > https://mm.icann.org/mailman/listinfo/ncsg-dns-abuse-wg > > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Wed Apr 13 12:17:08 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Wed, 13 Apr 2022 11:17:08 +0200 Subject: [NCSG-PC] Fwd: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 In-Reply-To: References: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> Message-ID: Dear all, So, from our list of councilors, I have the following names confirmed to attend ICANN74 in person: Manju Chen Farell Folly Juan Manuel Rojas Wisdom Donkor The Councilors that will not be attending onsite are: Tomslin Samme-Nlar Stephanie Perrin I will try to issue a process for filling these two slots today but if you think there is anyone involved with our policy work - aka. Kathy, Milton, Rafik, Farzaneh - that should take the two remaining slots please let me know asap. Best, Bruna On Mon, Apr 11, 2022 at 4:19 AM ??? Manju Chen wrote: > Hi Bruna, > > I plan to attend the meeting in person. > Many thanks! > > Best, > Manju > > On Sat, Apr 9, 2022 at 1:32 AM Wisdom Donkor wrote: > >> Hello Bruna, >> I will be attending. >> >> On Fri, 8 Apr 2022, 12:41 pm Tomslin Samme-Nlar, >> wrote: >> >>> I will not be attending in person @Bruna. >>> >>> Warmly, >>> Tomslin >>> >>> On Fri, 8 Apr 2022, 11:39 Bruna Martins dos Santos, < >>> bruna.mrtns at gmail.com> wrote: >>> >>>> Hey all, >>>> >>>> Hope this email finds everyone well! >>>> >>>> As you know, ICANN74 will be a hybrid meeting hosted in The Hague. For >>>> that, we need to submit the councillors and NCSG travellers soon. >>>> >>>> Therefore, this email is to ask you - councillors - to let me know >>>> whether you are planning to attend ICANN74 by Thursday, April 14th. For >>>> those who are not able or comfortable to attend meetings yet, we >>>> kindly ask that you reply to this email so that we can select a >>>> substitute. >>>> >>>> Best, >>>> Bruna >>>> >>>> >>>> >>>> ---------- Forwarded message --------- >>>> From: Terri Agnew >>>> Date: Thu 7. Apr 2022 at 04:39 >>>> Subject: ICANN74 | The Hague - Supported Travelers/Contractor Travelers >>>> Database Due | Thursday, 14 April 2022 >>>> To: bruna.mrtns at gmail.com , >>>> mesumbeslin at gmail.com , Andrea Glandon < >>>> andrea.glandon at icann.org> >>>> Cc: gnso-secs at icann.org >>>> >>>> >>>> Dear all, >>>> >>>> >>>> >>>> In order to service your travel needs for ICANN74 in The Hauge in a >>>> timely fashion, please submit your ICANN74 Meeting database to >>>> gnso-secs at icann.org by *Thursday, 14 April 2022 *in order to be >>>> submitted by deadline of 15 April 2022. >>>> >>>> >>>> >>>> As a reminder, for the AGM meeting only, incoming Councilors get >>>> funding, as well as the then-incumbent Councilors. >>>> >>>> >>>> >>>> A timely response would be appreciated in view of visa issues and the >>>> OFAC review. The deadline for submissions is critical to allow for >>>> confirmed reservation numbers as required for visa and travel arrangements. >>>> >>>> *WHAT IS NEW FOR TRAVELERS* >>>> >>>> >>>> >>>> >>>> 1. *WAIVER*. Funded Travelers are expected to sign an >>>> acknowledgement and waiver for ICANN74. This acknowledgement and waiver is >>>> built in the ICANN74 Registration for anyone that is registering for >>>> in-person participation. Funded Travelers will need to register using this >>>> specific link which will be sent on their ?Travel Funding Confirmation >>>> Email.? Funded travelers are expected to comply with the acknowledgement >>>> and waiver. If they are unable or unwilling to agree to these terms, they >>>> are able to participate in the meeting remotely and their request to have >>>> travel funding will be provided to another person. ICANN org will provide >>>> more information about the specific support that will be offered to Funded >>>> Travelers in the case of emergencies or other non-standard situations. You >>>> can read the acknowledgment and waiver text with the attached document that >>>> can be shared with funded travelers. >>>> >>>> >>>> >>>> *NOTE:* The acknowledgement includes that Funded Travelers have read, >>>> understand, and agree to comply with the Community Travel Support >>>> Guidelines. >>>> >>>> >>>> https://www.icann.org/en/system/files/files/community-travel-support-guidelines-01jul20-en.pdf >>>> >>>> >>>> >>>> >>>> 2. *TRAVEL ARRIVAL MEASURES*. As with all international >>>> travel, all travelers have a responsibility to understand the entry and >>>> exit requirements of their travel and determine if they can meet those >>>> requirements before committing to the travel. Travelers may review specific >>>> travel requirements by visiting https://apply.joinsherpa.com/map or >>>> their local government international traveler websites. >>>> >>>> - To see travel requirements to enter the Netherlands based on >>>> their location, visit >>>> https://reizentijdenscorona.rijksoverheid.nl/en. >>>> - ICANN is committed to ensuring an inclusive Policy Forum that >>>> provides an equal opportunity for all to engage on important policy matters. >>>> If funded travelers are not eligible or cannot meet the entry >>>> requirements as outlined by the government of the Netherlands, we are >>>> confident they will find the virtual participation experience equally as >>>> engaging. >>>> >>>> >>>> >>>> 3. *CONCUR*. During the pandemic, ICANN org used this >>>> opportunity to make some enhancements for our funded travelers experience. >>>> We are happy to announce that all funded travelers are now able to book >>>> their travel using Concur, an online travel booking tool. Previous booking >>>> options with a live person agent with FCM are still available to Funded >>>> Travelers. Instructions on how to book travel will be provided to funded >>>> travelers who are confirmed and eligible. >>>> >>>> >>>> >>>> >>>> >>>> Reminder: >>>> >>>> - GNSO supported traveler with a designated hotel accommodation >>>> funding, a hotel room is automatically secured for you, please *DO >>>> NOT* book your own hotel as it is un-reimbursable. >>>> - All personal data provided to ICANN org in for purposes of >>>> providing travel support for participants related to ICANN events will be >>>> processed in accordance with the ICANN Privacy Policy [icann.org] >>>> . >>>> Should you have any questions or concerns about this Privacy Policy and our >>>> privacy practices, you may contact us at privacy at icann.org. >>>> >>>> >>>> >>>> Please note that when requesting travel support, in the interest of >>>> fairness and in light of budget restrictions we would like you to take the >>>> following into consideration: >>>> >>>> >>>> >>>> 1. Respond timely to ICANN Travel regarding your >>>> upcoming travel. >>>> >>>> 2. If you require a visa to enter the country, please >>>> make sure to acquire your visa immediately. Please contact the ICANN >>>> travel team to let them know you will need a visa. >>>> >>>> 3. Requests past the deadline will be handled on a case >>>> by case basis by ICANN. All additional travelers added after the 90-day >>>> deadline are subject to availability, may NOT be placed in the same hotel >>>> as their funded traveler groups, and may not be able to attend due to visa >>>> issues. >>>> >>>> 4. If possible please book direct travel >>>> requests. Detours and multi-stop trips are unfortunately not guaranteed. >>>> >>>> 5. Strictly limit your travel from your home to the >>>> ICANN meeting venue. >>>> >>>> 6. Approved date of arrival/departure for this meeting >>>> is *ARRIVAL: 12 June 2022 and DEPARTURE: 17 June 2022* >>>> >>>> 7. If travelers want to extend their stay this must be >>>> done at their own expense and should contact the hotel directly once the >>>> ICANN hotel confirmation has be sent to them. >>>> >>>> 8. *Privately Booked Reservations*: ICANN will not >>>> refund or take over accommodations directly booked by the funded traveler. >>>> If a replacement has an existing hotel reservation, they will need to >>>> cancel their reservation and ICANN will not be able to take over their >>>> reservation. >>>> >>>> >>>> >>>> Many thanks for your cooperation! >>>> >>>> Thank you. >>>> >>>> >>>> >>>> With kind regards, >>>> >>>> *Terri* >>>> >>>> * ---* >>>> >>>> *Terri Agnew* >>>> >>>> Policy Operations Specialist (GNSO) >>>> >>>> Internet Corporation for Assigned Names and Numbers (ICANN) >>>> >>>> *Skype ID:* terri.agnew.icann >>>> >>>> >>>> >>>> Find out more about the GNSO by visiting: https://learn.icann.org/ >>>> >>>> >>>> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO >>>> >>>> >>>> Transcripts and recordings of GNSO Working Group and Council events are >>>> located on the GNSO Master Calendar >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> *Bruna Martins dos Santos * >>>> >>>> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander >>>> von Humboldt Foundation >>>> >>>> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum >>>> Berlin f?r Sozialforschung (WZB) >>>> >>>> Member | Coaliz?o Direitos na Rede >>>> Chair | Non-Commercial Stakeholder Group at ICANN >>>> >>>> Co-Coordinator | Internet Governance Caucus >>>> >>>> Twitter: @boomartins // Skype: >>>> bruna.martinsantos >>>> *bruna.martinsdossantos at wzb.eu * and >>>> bruna.mrtns at gmail.com >>>> _______________________________________________ >>>> NCSG-PC mailing list >>>> NCSG-PC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>>> >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Wed Apr 13 18:08:30 2022 From: stephanie.perrin at mail.utoronto.ca (Stephanie E Perrin) Date: Wed, 13 Apr 2022 11:08:30 -0400 Subject: [NCSG-PC] Fwd: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 In-Reply-To: References: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> Message-ID: I said i was coming, what do I have to do to claim my own slot? Stephanie PErrin On 2022-04-13 5:17 a.m., Bruna Martins dos Santos wrote: > Dear all, > > So, from our list of councilors, I have the following names confirmed > to attend ICANN74 in person: > > Manju Chen > Farell Folly > Juan Manuel Rojas > Wisdom Donkor > > The Councilors that will not be attending onsite are: > Tomslin Samme-Nlar > Stephanie Perrin > > I will try to issue a process for filling these two slots today but if > you think there is anyone involved with our policy work - aka. Kathy, > Milton, Rafik, Farzaneh - that should take the two remaining slots > please let me know asap. > > Best, > Bruna > > On Mon, Apr 11, 2022 at 4:19 AM ??? Manju Chen > wrote: > > Hi Bruna, > > I plan to attend the meeting in person. > Many?thanks! > > Best, > Manju > > On Sat, Apr 9, 2022 at 1:32 AM Wisdom Donkor > wrote: > > Hello Bruna, > I will be?attending. > > On Fri, 8 Apr 2022, 12:41 pm Tomslin Samme-Nlar, > wrote: > > I will not be attending in person @Bruna. > > Warmly, > Tomslin > > On Fri, 8 Apr 2022, 11:39 Bruna Martins dos Santos, > wrote: > > Hey all, > > Hope this email finds everyone well! > > As you know, ICANN74 will be a hybrid meeting hosted > in The Hague. For that, we need to submit the > councillors and NCSG travellers soon. > > Therefore, this email is to ask you - councillors - to > let me know whether you are planning to attend ICANN74 > by Thursday, April 14th. For those who are not able or > comfortable to attend meetings yet, we kindly ask that > you reply to this email?so that we can select a > substitute. > > Best, > Bruna > > > > ---------- Forwarded message --------- > From: *Terri Agnew* > Date: Thu 7. Apr 2022 at 04:39 > Subject: ICANN74 | The Hague - Supported > Travelers/Contractor Travelers Database Due | > Thursday, 14 April 2022 > To: bruna.mrtns at gmail.com , > mesumbeslin at gmail.com , Andrea > Glandon > Cc: gnso-secs at icann.org > > > Dear all, > > In order to service your travel needs for ICANN74 in > The Hauge in a timely fashion, please submit your > ICANN74 Meeting database to gnso-secs at icann.orgby > *Thursday, 14 April 2022 *in order to be submitted by > deadline of 15 April 2022. > > As a reminder, for the AGM meeting only, incoming > Councilors get funding, as well as the then-incumbent > Councilors. > > A timely response would be appreciated in view of visa > issues and the OFAC review. The deadline for > submissions is critical to allow for confirmed > reservation numbers as required for visa and travel > arrangements. > > *_WHAT IS NEW FOR TRAVELERS_* > > > > 1. *WAIVER*. Funded Travelers are expected to sign an > acknowledgement and waiver for ICANN74. This > acknowledgement and waiver is built in the ICANN74 > Registration for anyone that is registering for > in-person participation. Funded Travelers will > need to register using this specific link which > will be sent on their ?Travel Funding Confirmation > Email.? Funded travelers are expected to comply > with the acknowledgement and waiver. If they are > unable or unwilling to agree to these terms, they > are able to participate in the meeting remotely > and their request to have travel funding will be > provided to another person. ICANN org will provide > more information about the specific support that > will be offered to Funded Travelers in the case of > emergencies or other non-standard situations. You > can read the acknowledgment and waiver text with > the attached document that can be shared with > funded travelers. > > *NOTE:*The acknowledgement includes that Funded > Travelers have read, understand, and agree to comply > with the Community Travel Support Guidelines. > > https://www.icann.org/en/system/files/files/community-travel-support-guidelines-01jul20-en.pdf > > > > 2. *TRAVEL ARRIVAL MEASURES*. As with all > international travel, all travelers have a > responsibility to understand the entry and exit > requirements of their travel and determine if they can > meet those requirements before committing to the > travel. Travelers may review specific travel > requirements by visiting > https://apply.joinsherpa.com/mapor their local > government international traveler websites. > > * To see travel requirements to enter the > Netherlands based on their location, > visithttps://reizentijdenscorona.rijksoverheid.nl/en > . > * ICANN is committed to ensuring an inclusive Policy > Forum that provides an equal opportunity for all > to engage on important policy matters.If funded > travelers are not eligible or cannot meet the > entry requirements as outlined by the government > of the Netherlands, we are confident they will > find the virtual participation experience equally > as engaging. > > 3. *CONCUR*. During the pandemic, ICANN org used this > opportunity to make some enhancements for our funded > travelers experience. We are happy to announce that > all funded travelers are now able to book their travel > using Concur, an online travel booking tool. Previous > booking options with a live person agent with FCM are > still available to Funded Travelers. Instructions on > how to book travel will be provided to funded > travelers who are confirmed and eligible. > > Reminder: > > * GNSO supported traveler with a designated hotel > accommodation funding, a hotel room is > automatically secured for you, please *DO NOT* > book your own hotel as it is un-reimbursable. > * All personal data provided to ICANN org in for > purposes of providing travel support for > participants related to ICANN events will be > processed in accordance with the ICANN Privacy > Policy [icann.org] > .? > Should you have any questions or concerns about > this Privacy Policy and our privacy practices, you > may contact us at privacy at icann.org. > > Please note that when requesting travel support, in > the interest of fairness and in light of budget > restrictions?we would like you to take the following > into consideration: > > 1.Respond?timely to ICANN Travel regarding your > upcoming travel. > > 2.If you require a visa to enter the country, please > make sure to acquire your visa immediately.?Please > contact the ICANN travel team to let them know you > will need a visa. > > 3.Requests past the deadline will be handled on a case > by case basis by ICANN. All additional travelers added > after the 90-day deadline are subject to availability, > may NOT be placed in the same hotel as their funded > traveler groups, and may not be able to attend due to > visa issues. > > 4.If possible please book?direct travel > requests.?Detours and multi-stop trips are > unfortunately not guaranteed. > > 5.Strictly limit your travel from your home to the > ICANN meeting venue. > > 6.Approved date of arrival/departure for this meeting > is *ARRIVAL: 12 June 2022 and DEPARTURE: 17 June 2022* > > 7.If travelers want to extend their stay this must be > done at their own expense and should contact the hotel > directly once the ICANN hotel confirmation has be sent > to them. > > 8./Privately Booked Reservations/:?ICANN will not > refund or take over accommodations directly booked by > the funded traveler. If a replacement has an existing > hotel reservation, they will need to cancel their > reservation and ICANN will not be able to take over > their reservation. > > ?Many thanks for your cooperation! > > Thank you. > > With kind regards, > > *Terri* > > *????????????---* > > *Terri Agnew* > > Policy Operations Specialist (GNSO) > > Internet Corporation for Assigned Names and Numbers > (ICANN) > > *Skype ID:*terri.agnew.icann > > Find out more about the GNSO by visiting: > https://learn.icann.org/ > > > Follow @GNSO on Twitter: > https://twitter.com/ICANN_GNSO > > > Transcripts and recordings of GNSO Working Group and > Council events are located on the GNSO Master > Calendar > > -- > */Bruna Martins dos Santos > /* > > German Chancellor Fellow 21' > (Bundeskanzler-Stipendiatin) | Alexander von Humboldt > Foundation > > Visiting Researcher (Gastwissenschaftlerin) | > Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) > > > Member | Coaliz?o Direitos na Rede > > Chair?| Non-Commercial Stakeholder Group at ICANN > > Co-Coordinator?| Internet Governance Caucus > > > Twitter: @boomartins > ?// Skype: > bruna.martinsantos > _bruna.martinsdossantos at wzb.eu_?and bruna.mrtns at gmail.com > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > > > -- > */Bruna Martins dos Santos > /* > > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander > von Humboldt Foundation > > Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum > Berlin f?r Sozialforschung (WZB) > > Member | Coaliz?o Direitos na Rede > Chair?| Non-Commercial Stakeholder Group at ICANN > > Co-Coordinator?| Internet Governance Caucus > > Twitter: @boomartins ?// Skype: > bruna.martinsantos > _bruna.martinsdossantos at wzb.eu_?and bruna.mrtns at gmail.com > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kathy at KathyKleiman.com Wed Apr 13 18:59:51 2022 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Wed, 13 Apr 2022 11:59:51 -0400 Subject: [NCSG-PC] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> Message-ID: <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> Hi Manju, Great letter and great edits by Bruna.? I edited a few small things and then pulled out and expanded our "ask" - that we would like the GNSO Council to hold a comment period to provide input and guidance to this small group of individuals appointed to talk to the GAC (should our excellent and well-founded objections to the process be overruled).? This will provide a way for the GNSO Council to know the issues/concerns/hopes o the GNSO Community on this matter - and to provide clear input? and guidance to the the small Committee for the negotiations that may lie ahead. Here's the paragraph - building on opening sentences of Manju and edits of Bruna: We strongly support as the first step that the GNSO Council seek public comment from the community on how to proceed with Closed Generics, as opposed to having a ?closed dialogue? with the GAC where the scope and interlocutors of such dialogue is dictated by the ICANN Board.? This input will provide the Council with issues and concerns of the GNSO Community.? The Council, in turn, can provide guidance to the members of the Council who will be leading this discussion - should it occur despite our deep concerns for Multistakeholder process and precedent. How else will this small team - some with very, very long-held personal views on the subject - be bound to a discussion on behalf of the entire GNSO Community? I recommend putting the paragraph in bold for those who tend to scan their email. Best, Kathy On 4/11/2022 11:04 PM, ??? Manju Chen wrote: > Hi all, > > As discussed per yesterday's policy call, I've drafted our formal > response to be sent to the Council (and the Board?) > > You can find the statement here: > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > Feedbacks and suggestions are welcome and will be highly appreciated! > > > Best, > Manju > > On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen > wrote: > > Hi Tomslin and all, > > Kurt and others obviously wanted it to be discussed in the Council > meeting this week. > Steve has suggested if that was the intent we could propose a late > motion. I think?NCSG is not in a hurry about this, so I'll let > others handle it if they want to propose the motion. > > I can share more details and answer questions today later during > our policy call. > > Best, > Manju > > > > On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar > wrote: > > Hi Manju, > Thank you so much for the update. Nice strategy there with the > small team representation. Do you know when that deferral will > be brought to the council's attention? Or maybe I missed it in > my hundreds of emails. > > Thanks again. > Tomslin > > > On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen > wrote: > > Hi team, > > Borrowing this thread to report back to you about what > happened in the small team. > > So as you might have guessed, I was the only one saying no > to the 'facilitated dialogue'. Jeff, Paul, and Kurt were > eager to dive into the discussion of how we engage with > GAC in this 'facilitated dialogue' but thankfully they > still respected our objection. My first point of objection > is that the small team is really not representative enough > to make the decision of whether the Council should meet > with the GAC. For now, we agreed to refer this back to the > Council and make the decision at the Council level. > > I'm afraid though NCSG would be the only one saying no > when we're at the Council level. Also when this pops up, > we really have to have our statement ready?explaining why > we're saying no. I've put notes in the document Tomslin > created and Kathy has been extremely helpful by providing > reference material and edits: > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > > We will still need to phrase them into a formal statement, > but I think it'd be an easy task now we have all the > contents. > > Best, > Manju > > On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar > wrote: > > Hi team, > > I just wanted to call your attention to this response > we promised to put together on the board proposed > dialogue between GAC and Council on closed generics. > The Council small team is about to be activated to > start deliberations and I believe @??? Manju Chen > ?who is representing us there > hopes to rely on the response we pen down to guide her > contribution to that team. > > In this?regard, can I request that we find some time > to please put our ideas down on the Google > formhttps://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > Looking forward to your help with this. In the > meantime, i'll review my meeting notes and put down > some feedback we got during our policy call on the > document. > > Warmly, > Tomslin > > On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, > wrote: > > Hi all, > > As a follow-up to my previous email regarding the > board's proposed facilitated dialogue between GAC > and GNSO council, I have created this Google doc [ > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > ] to capture our response to this proposal in the > form of a letter to the council small team on > Closed Generics. > > Inputs to the document are welcomed and for your > convenience, attached again is the letter from the > board and the accompanying framing paper. > > Regards, > Tomslin > > > On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar > wrote: > > Dear everyone, > > Here is the framing paper on the board's > proposed dialogue between GNSO Council and the > GAC on Closed Generics that was promised. > > Comments are welcomed. I will also be sending > a separate email with a link to the Google doc > where we intend to draft a letter as a > response to this. > > Regards, > Tomslin > > > ---------- Forwarded message --------- > From: *Wendy Profit via Gnso-chairs* > > Date: Fri, 11 Mar 2022 at 04:33 > Subject: [gnso-chairs] [CORRESPONDENCE] > Maarten Botterman to Manal Ismail and Philippe > Fouquart - GAC-GNSO Consultation on Closed > Generics > To: manal.ismail at board.icann.org > , Manal Ismail > , > philippe.fouquart at orange.com > , > gnso-chairs at icann.org > Cc: Secretary , > Correspondence , > Board Ops Team , > gnso-secs at icann.org , > GACSTAFF , Maarten > Botterman > > > Dear Manal and Philippe, > > Pursuant to the letter sent recently (6 March > 2022, attached for reference), we are now > forwarding the associated framework paper > entitled ?Board-Facilitated Process for a GAC > - GNSO Council Dialogue on Closed Generics?, > also attached. > > ** > > Thank you and best regards, > > Wendy Profit > > ICANN > > Board Operations Senior Manager > > 12025 Waterfront Drive, Suite 300 > > Los Angeles, CA 90094 > > *From: *Wendy Profit > *Date: *Sunday, March 6, 2022 at 3:58 PM > *To: *"manal.ismail at board.icann.org" > , > "manal at tra.gov.eg" , > "philippe.fouquart at orange.com" > > *Cc: *Maarten Botterman > , > "gnso-chairs at icann.org" > , GACSTAFF > , "gnso-secs at icann.org" > , ICANN Board Ops > , Correspondence > , Secretary > > *Subject: *[CORRESPONDENCE] Maarten Botterman > to Manal Ismail and Philippe Fouquart - > GAC-GNSO Consultation on Closed Generics > > Dear Manal and Philippe, > > Please find the attached letter from ICANN > Chair Maarten Botterman regarding a proposed > formal consultation between the GAC and GNSO > Council on how to handle the subject of closed > generics in gTLD applications. > > Thank you and best regards, > > Wendy Profit > > ICANN > > Board Operations Senior Manager > > 12025 Waterfront Drive, Suite 300 > > Los Angeles, CA 90094 > > _______________________________________________ > Gnso-chairs mailing list > Gnso-chairs at icann.org > https://mm.icann.org/mailman/listinfo/gnso-chairs > _______________________________________________ > 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Wed Apr 13 19:51:37 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Wed, 13 Apr 2022 18:51:37 +0200 Subject: [NCSG-PC] Fwd: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 In-Reply-To: References: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> Message-ID: Hey Steph! I sent this email before you confirmed it to me! Your slot is secured, I will send the list to staff tomorrow and you shall receive an email afterwards. Best, B On Wed 13. Apr 2022 at 17:08, Stephanie E Perrin < stephanie.perrin at mail.utoronto.ca> wrote: > I said i was coming, what do I have to do to claim my own slot? > > Stephanie PErrin > On 2022-04-13 5:17 a.m., Bruna Martins dos Santos wrote: > > Dear all, > > So, from our list of councilors, I have the following names confirmed to > attend ICANN74 in person: > > Manju Chen > Farell Folly > Juan Manuel Rojas > Wisdom Donkor > > The Councilors that will not be attending onsite are: > Tomslin Samme-Nlar > Stephanie Perrin > > I will try to issue a process for filling these two slots today but if you > think there is anyone involved with our policy work - aka. Kathy, Milton, > Rafik, Farzaneh - that should take the two remaining slots please let me > know asap. > > Best, > Bruna > > On Mon, Apr 11, 2022 at 4:19 AM ??? Manju Chen wrote: > >> Hi Bruna, >> >> I plan to attend the meeting in person. >> Many thanks! >> >> Best, >> Manju >> >> On Sat, Apr 9, 2022 at 1:32 AM Wisdom Donkor wrote: >> >>> Hello Bruna, >>> I will be attending. >>> >>> On Fri, 8 Apr 2022, 12:41 pm Tomslin Samme-Nlar, >>> wrote: >>> >>>> I will not be attending in person @Bruna. >>>> >>>> Warmly, >>>> Tomslin >>>> >>>> On Fri, 8 Apr 2022, 11:39 Bruna Martins dos Santos, < >>>> bruna.mrtns at gmail.com> wrote: >>>> >>>>> Hey all, >>>>> >>>>> Hope this email finds everyone well! >>>>> >>>>> As you know, ICANN74 will be a hybrid meeting hosted in The Hague. For >>>>> that, we need to submit the councillors and NCSG travellers soon. >>>>> >>>>> Therefore, this email is to ask you - councillors - to let me know >>>>> whether you are planning to attend ICANN74 by Thursday, April 14th. For >>>>> those who are not able or comfortable to attend meetings yet, we >>>>> kindly ask that you reply to this email so that we can select a >>>>> substitute. >>>>> >>>>> Best, >>>>> Bruna >>>>> >>>>> >>>>> >>>>> ---------- Forwarded message --------- >>>>> From: Terri Agnew >>>>> Date: Thu 7. Apr 2022 at 04:39 >>>>> Subject: ICANN74 | The Hague - Supported Travelers/Contractor >>>>> Travelers Database Due | Thursday, 14 April 2022 >>>>> To: bruna.mrtns at gmail.com , >>>>> mesumbeslin at gmail.com , Andrea Glandon < >>>>> andrea.glandon at icann.org> >>>>> Cc: gnso-secs at icann.org >>>>> >>>>> >>>>> Dear all, >>>>> >>>>> >>>>> >>>>> In order to service your travel needs for ICANN74 in The Hauge in a >>>>> timely fashion, please submit your ICANN74 Meeting database to >>>>> gnso-secs at icann.org by *Thursday, 14 April 2022 *in order to be >>>>> submitted by deadline of 15 April 2022. >>>>> >>>>> >>>>> >>>>> As a reminder, for the AGM meeting only, incoming Councilors get >>>>> funding, as well as the then-incumbent Councilors. >>>>> >>>>> >>>>> >>>>> A timely response would be appreciated in view of visa issues and the >>>>> OFAC review. The deadline for submissions is critical to allow for >>>>> confirmed reservation numbers as required for visa and travel arrangements. >>>>> >>>>> *WHAT IS NEW FOR TRAVELERS* >>>>> >>>>> >>>>> >>>>> >>>>> 1. *WAIVER*. Funded Travelers are expected to sign an >>>>> acknowledgement and waiver for ICANN74. This acknowledgement and waiver is >>>>> built in the ICANN74 Registration for anyone that is registering for >>>>> in-person participation. Funded Travelers will need to register using this >>>>> specific link which will be sent on their ?Travel Funding Confirmation >>>>> Email.? Funded travelers are expected to comply with the acknowledgement >>>>> and waiver. If they are unable or unwilling to agree to these terms, they >>>>> are able to participate in the meeting remotely and their request to have >>>>> travel funding will be provided to another person. ICANN org will provide >>>>> more information about the specific support that will be offered to Funded >>>>> Travelers in the case of emergencies or other non-standard situations. You >>>>> can read the acknowledgment and waiver text with the attached document that >>>>> can be shared with funded travelers. >>>>> >>>>> >>>>> >>>>> *NOTE:* The acknowledgement includes that Funded Travelers have read, >>>>> understand, and agree to comply with the Community Travel Support >>>>> Guidelines. >>>>> >>>>> >>>>> https://www.icann.org/en/system/files/files/community-travel-support-guidelines-01jul20-en.pdf >>>>> >>>>> >>>>> >>>>> >>>>> 2. *TRAVEL ARRIVAL MEASURES*. As with all international >>>>> travel, all travelers have a responsibility to understand the entry and >>>>> exit requirements of their travel and determine if they can meet those >>>>> requirements before committing to the travel. Travelers may review specific >>>>> travel requirements by visiting https://apply.joinsherpa.com/map or >>>>> their local government international traveler websites. >>>>> >>>>> - To see travel requirements to enter the Netherlands based on >>>>> their location, visit >>>>> https://reizentijdenscorona.rijksoverheid.nl/en. >>>>> - ICANN is committed to ensuring an inclusive Policy Forum that >>>>> provides an equal opportunity for all to engage on important policy matters. >>>>> If funded travelers are not eligible or cannot meet the entry >>>>> requirements as outlined by the government of the Netherlands, we are >>>>> confident they will find the virtual participation experience equally as >>>>> engaging. >>>>> >>>>> >>>>> >>>>> 3. *CONCUR*. During the pandemic, ICANN org used this >>>>> opportunity to make some enhancements for our funded travelers experience. >>>>> We are happy to announce that all funded travelers are now able to book >>>>> their travel using Concur, an online travel booking tool. Previous booking >>>>> options with a live person agent with FCM are still available to Funded >>>>> Travelers. Instructions on how to book travel will be provided to funded >>>>> travelers who are confirmed and eligible. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Reminder: >>>>> >>>>> - GNSO supported traveler with a designated hotel accommodation >>>>> funding, a hotel room is automatically secured for you, please *DO >>>>> NOT* book your own hotel as it is un-reimbursable. >>>>> - All personal data provided to ICANN org in for purposes of >>>>> providing travel support for participants related to ICANN events will be >>>>> processed in accordance with the ICANN Privacy Policy [icann.org] >>>>> . >>>>> Should you have any questions or concerns about this Privacy Policy and our >>>>> privacy practices, you may contact us at privacy at icann.org. >>>>> >>>>> >>>>> >>>>> Please note that when requesting travel support, in the interest of >>>>> fairness and in light of budget restrictions we would like you to take the >>>>> following into consideration: >>>>> >>>>> >>>>> >>>>> 1. Respond timely to ICANN Travel regarding your >>>>> upcoming travel. >>>>> >>>>> 2. If you require a visa to enter the country, please >>>>> make sure to acquire your visa immediately. Please contact the ICANN >>>>> travel team to let them know you will need a visa. >>>>> >>>>> 3. Requests past the deadline will be handled on a case >>>>> by case basis by ICANN. All additional travelers added after the 90-day >>>>> deadline are subject to availability, may NOT be placed in the same hotel >>>>> as their funded traveler groups, and may not be able to attend due to visa >>>>> issues. >>>>> >>>>> 4. If possible please book direct travel >>>>> requests. Detours and multi-stop trips are unfortunately not guaranteed. >>>>> >>>>> 5. Strictly limit your travel from your home to the >>>>> ICANN meeting venue. >>>>> >>>>> 6. Approved date of arrival/departure for this meeting >>>>> is *ARRIVAL: 12 June 2022 and DEPARTURE: 17 June 2022* >>>>> >>>>> 7. If travelers want to extend their stay this must be >>>>> done at their own expense and should contact the hotel directly once the >>>>> ICANN hotel confirmation has be sent to them. >>>>> >>>>> 8. *Privately Booked Reservations*: ICANN will not >>>>> refund or take over accommodations directly booked by the funded traveler. >>>>> If a replacement has an existing hotel reservation, they will need to >>>>> cancel their reservation and ICANN will not be able to take over their >>>>> reservation. >>>>> >>>>> >>>>> >>>>> Many thanks for your cooperation! >>>>> >>>>> Thank you. >>>>> >>>>> >>>>> >>>>> With kind regards, >>>>> >>>>> *Terri* >>>>> >>>>> * ---* >>>>> >>>>> *Terri Agnew* >>>>> >>>>> Policy Operations Specialist (GNSO) >>>>> >>>>> Internet Corporation for Assigned Names and Numbers (ICANN) >>>>> >>>>> *Skype ID:* terri.agnew.icann >>>>> >>>>> >>>>> >>>>> Find out more about the GNSO by visiting: https://learn.icann.org/ >>>>> >>>>> >>>>> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO >>>>> >>>>> >>>>> Transcripts and recordings of GNSO Working Group and Council events >>>>> are located on the GNSO Master Calendar >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Bruna Martins dos Santos * >>>>> >>>>> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander >>>>> von Humboldt Foundation >>>>> >>>>> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum >>>>> Berlin f?r Sozialforschung (WZB) >>>>> >>>>> Member | Coaliz?o Direitos na Rede >>>>> Chair | Non-Commercial Stakeholder Group at ICANN >>>>> >>>>> Co-Coordinator | Internet Governance Caucus >>>>> >>>>> Twitter: @boomartins // Skype: >>>>> bruna.martinsantos >>>>> *bruna.martinsdossantos at wzb.eu * and >>>>> bruna.mrtns at gmail.com >>>>> _______________________________________________ >>>>> NCSG-PC mailing list >>>>> NCSG-PC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>>>> >>>> _______________________________________________ >>>> NCSG-PC mailing list >>>> NCSG-PC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>>> >>> _______________________________________________ >>> NCSG-PC mailing list >>> NCSG-PC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >>> >> > > -- > > *Bruna Martins dos Santos * > > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von > Humboldt Foundation > > Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin > f?r Sozialforschung (WZB) > > Member | Coaliz?o Direitos na Rede > Chair | Non-Commercial Stakeholder Group at ICANN > > Co-Coordinator | Internet Governance Caucus > > Twitter: @boomartins // Skype: > bruna.martinsantos > *bruna.martinsdossantos at wzb.eu * and > bruna.mrtns at gmail.com > > _______________________________________________ > NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Thu Apr 14 01:02:35 2022 From: stephanie.perrin at mail.utoronto.ca (Stephanie E Perrin) Date: Wed, 13 Apr 2022 18:02:35 -0400 Subject: [NCSG-PC] Fwd: ICANN74 | The Hague - Supported Travelers/Contractor Travelers Database Due | Thursday, 14 April 2022 In-Reply-To: References: <824CD91B-E40E-41D2-8972-1B9C7D5C3D93@icann.org> Message-ID: Sorry, I am having email send problems.? I guess you did not receive anything from me other than my skype message. Hopefully fixed soon On 2022-04-13 12:51 p.m., Bruna Martins dos Santos wrote: > Hey Steph! I sent this email before you confirmed it to me! > > Your slot is secured, I will send the list to staff tomorrow and you > shall receive an email afterwards. > > Best, > B > > On Wed 13. Apr 2022 at 17:08, Stephanie E Perrin > wrote: > > I said i was coming, what do I have to do to claim my own slot? > > Stephanie PErrin > > On 2022-04-13 5:17 a.m., Bruna Martins dos Santos wrote: >> Dear all, >> >> So, from our list of councilors, I have the following names >> confirmed to attend ICANN74 in person: >> >> Manju Chen >> Farell Folly >> Juan Manuel Rojas >> Wisdom Donkor >> >> The Councilors that will not be attending onsite are: >> Tomslin Samme-Nlar >> Stephanie Perrin >> >> I will try to issue a process for filling these two slots today >> but if you think there is anyone involved with our policy work - >> aka. Kathy, Milton, Rafik, Farzaneh - that should take the two >> remaining slots please let me know asap. >> >> Best, >> Bruna >> >> On Mon, Apr 11, 2022 at 4:19 AM ??? Manju Chen >> wrote: >> >> Hi Bruna, >> >> I plan to attend the meeting in person. >> Many?thanks! >> >> Best, >> Manju >> >> On Sat, Apr 9, 2022 at 1:32 AM Wisdom Donkor >> wrote: >> >> Hello Bruna, >> I will be?attending. >> >> On Fri, 8 Apr 2022, 12:41 pm Tomslin Samme-Nlar, >> wrote: >> >> I will not be attending in person @Bruna. >> >> Warmly, >> Tomslin >> >> On Fri, 8 Apr 2022, 11:39 Bruna Martins dos Santos, >> wrote: >> >> Hey all, >> >> Hope this email finds everyone well! >> >> As you know, ICANN74 will be a hybrid meeting >> hosted in The Hague. For that, we need to submit >> the councillors and NCSG travellers soon. >> >> Therefore, this email is to ask you - councillors >> - to let me know whether you are planning to >> attend ICANN74 by Thursday, April 14th. For those >> who are not able or comfortable to attend >> meetings yet, we kindly ask that you reply to >> this email?so that we can select a substitute. >> >> Best, >> Bruna >> >> >> >> ---------- Forwarded message --------- >> From: *Terri Agnew* >> Date: Thu 7. Apr 2022 at 04:39 >> Subject: ICANN74 | The Hague - Supported >> Travelers/Contractor Travelers Database Due | >> Thursday, 14 April 2022 >> To: bruna.mrtns at gmail.com >> , mesumbeslin at gmail.com >> , Andrea Glandon >> >> Cc: gnso-secs at icann.org >> >> >> Dear all, >> >> In order to service your travel needs for ICANN74 >> in The Hauge in a timely fashion, please submit >> your ICANN74 Meeting database to >> gnso-secs at icann.orgby *Thursday, 14 April 2022 >> *in order to be submitted by deadline of 15 April >> 2022. >> >> As a reminder, for the AGM meeting only, incoming >> Councilors get funding, as well as the >> then-incumbent Councilors. >> >> A timely response would be appreciated in view of >> visa issues and the OFAC review. The deadline for >> submissions is critical to allow for confirmed >> reservation numbers as required for visa and >> travel arrangements. >> >> *_WHAT IS NEW FOR TRAVELERS_* >> >> >> >> 1. *WAIVER*. Funded Travelers are expected to >> sign an acknowledgement and waiver for >> ICANN74. This acknowledgement and waiver is >> built in the ICANN74 Registration for anyone >> that is registering for in-person >> participation. Funded Travelers will need to >> register using this specific link which will >> be sent on their ?Travel Funding Confirmation >> Email.? Funded travelers are expected to >> comply with the acknowledgement and waiver. >> If they are unable or unwilling to agree to >> these terms, they are able to participate in >> the meeting remotely and their request to >> have travel funding will be provided to >> another person. ICANN org will provide more >> information about the specific support that >> will be offered to Funded Travelers in the >> case of emergencies or other non-standard >> situations. You can read the acknowledgment >> and waiver text with the attached document >> that can be shared with funded travelers. >> >> *NOTE:*The acknowledgement includes that Funded >> Travelers have read, understand, and agree to >> comply with the Community Travel Support Guidelines. >> >> https://www.icann.org/en/system/files/files/community-travel-support-guidelines-01jul20-en.pdf >> >> >> >> 2. *TRAVEL ARRIVAL MEASURES*. As with all >> international travel, all travelers have a >> responsibility to understand the entry and exit >> requirements of their travel and determine if >> they can meet those requirements before >> committing to the travel. Travelers may review >> specific travel requirements by visiting >> https://apply.joinsherpa.com/mapor their local >> government international traveler websites. >> >> * To see travel requirements to enter the >> Netherlands based on their location, >> visithttps://reizentijdenscorona.rijksoverheid.nl/en >> . >> >> * ICANN is committed to ensuring an inclusive >> Policy Forum that provides an equal >> opportunity for all to engage on important >> policy matters.If funded travelers are not >> eligible or cannot meet the entry >> requirements as outlined by the government of >> the Netherlands, we are confident they will >> find the virtual participation experience >> equally as engaging. >> >> 3. *CONCUR*. During the pandemic, ICANN org used >> this opportunity to make some enhancements for >> our funded travelers experience. We are happy to >> announce that all funded travelers are now able >> to book their travel using Concur, an online >> travel booking tool. Previous booking options >> with a live person agent with FCM are still >> available to Funded Travelers. Instructions on >> how to book travel will be provided to funded >> travelers who are confirmed and eligible. >> >> Reminder: >> >> * GNSO supported traveler with a designated >> hotel accommodation funding, a hotel room is >> automatically secured for you, please *DO >> NOT* book your own hotel as it is >> un-reimbursable. >> * All personal data provided to ICANN org in >> for purposes of providing travel support for >> participants related to ICANN events will be >> processed in accordance with the ICANN >> Privacy Policy [icann.org] >> . >> Should you have any questions or concerns >> about this Privacy Policy and our privacy >> practices, you may contact us at >> privacy at icann.org. >> >> Please note that when requesting travel support, >> in the interest of fairness and in light of >> budget restrictions?we would like you to take the >> following into consideration: >> >> 1.Respond?timely to ICANN Travel regarding your >> upcoming travel. >> >> 2.If you require a visa to enter the country, >> please make sure to acquire your visa >> immediately.?Please contact the ICANN travel team >> to let them know you will need a visa. >> >> 3.Requests past the deadline will be handled on a >> case by case basis by ICANN. All additional >> travelers added after the 90-day deadline are >> subject to availability, may NOT be placed in the >> same hotel as their funded traveler groups, and >> may not be able to attend due to visa issues. >> >> 4.If possible please book?direct travel >> requests.?Detours and multi-stop trips are >> unfortunately not guaranteed. >> >> 5.Strictly limit your travel from your home to >> the ICANN meeting venue. >> >> 6.Approved date of arrival/departure for this >> meeting is *ARRIVAL: 12 June 2022 and DEPARTURE: >> 17 June 2022* >> >> 7.If travelers want to extend their stay this >> must be done at their own expense and should >> contact the hotel directly once the ICANN hotel >> confirmation has be sent to them. >> >> 8./Privately Booked Reservations/:?ICANN will not >> refund or take over accommodations directly >> booked by the funded traveler. If a replacement >> has an existing hotel reservation, they will need >> to cancel their reservation and ICANN will not be >> able to take over their reservation. >> >> ?Many thanks for your cooperation! >> >> Thank you. >> >> With kind regards, >> >> *Terri* >> >> *????????????---* >> >> *Terri Agnew* >> >> Policy Operations Specialist (GNSO) >> >> Internet Corporation for Assigned Names and >> Numbers (ICANN) >> >> *Skype ID:*terri.agnew.icann >> >> Find out more about the GNSO by visiting: >> https://learn.icann.org/ >> >> >> Follow @GNSO on Twitter: >> https://twitter.com/ICANN_GNSO >> >> >> Transcripts and recordings of GNSO Working Group >> and Council events are located on the GNSO Master >> Calendar >> >> -- >> */Bruna Martins dos Santos >> /* >> >> German Chancellor Fellow 21' >> (Bundeskanzler-Stipendiatin) | Alexander von >> Humboldt Foundation >> >> >> Visiting Researcher (Gastwissenschaftlerin) | >> Wissenschaftszentrum Berlin f?r Sozialforschung >> (WZB) >> >> Member | Coaliz?o Direitos na Rede >> >> Chair?| Non-Commercial Stakeholder Group at ICANN >> >> Co-Coordinator?| Internet Governance Caucus >> >> >> Twitter: @boomartins >> ?// Skype: >> bruna.martinsantos >> _bruna.martinsdossantos at wzb.eu_?and >> bruna.mrtns at gmail.com >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> >> >> -- >> */Bruna Martins dos Santos >> /* >> >> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | >> Alexander von Humboldt Foundation >> >> >> Visiting Researcher (Gastwissenschaftlerin) | >> Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) >> >> >> Member | Coaliz?o Direitos na Rede >> Chair?| Non-Commercial Stakeholder Group at ICANN >> >> Co-Coordinator?| Internet Governance Caucus >> >> Twitter: @boomartins ?// Skype: >> bruna.martinsantos >> _bruna.martinsdossantos at wzb.eu_?and bruna.mrtns at gmail.com >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > -- > */Bruna Martins dos Santos > /* > > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander > von Humboldt Foundation > > Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum > Berlin f?r Sozialforschung (WZB) > > Member | Coaliz?o Direitos na Rede > Chair?| Non-Commercial Stakeholder Group at ICANN > > Co-Coordinator?| Internet Governance Caucus > > Twitter: @boomartins ?// Skype: > bruna.martinsantos > _bruna.martinsdossantos at wzb.eu_?and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Thu Apr 14 02:27:07 2022 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 14 Apr 2022 08:27:07 +0900 Subject: [NCSG-PC] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> Message-ID: Hi Manju. Thanks for this, I understand that letter will be sent to council and leadership but I think it should be shared with wider NCSG list to inform them too while acknowledging the timing. Best, Rafik On Tue, Apr 12, 2022, 12:04 ??? Manju Chen wrote: > Hi all, > > As discussed per yesterday's policy call, I've drafted our formal response > to be sent to the Council (and the Board?) > > You can find the statement here: > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > Feedbacks and suggestions are welcome and will be highly appreciated! > > > Best, > Manju > > On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen wrote: > >> Hi Tomslin and all, >> >> Kurt and others obviously wanted it to be discussed in the Council >> meeting this week. >> Steve has suggested if that was the intent we could propose a late >> motion. I think NCSG is not in a hurry about this, so I'll let others >> handle it if they want to propose the motion. >> >> I can share more details and answer questions today later during our >> policy call. >> >> Best, >> Manju >> >> >> >> On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar >> wrote: >> >>> Hi Manju, >>> Thank you so much for the update. Nice strategy there with the small >>> team representation. Do you know when that deferral will be brought to the >>> council's attention? Or maybe I missed it in my hundreds of emails. >>> >>> Thanks again. >>> Tomslin >>> >>> >>> On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: >>> >>>> Hi team, >>>> >>>> Borrowing this thread to report back to you about what happened in the >>>> small team. >>>> >>>> So as you might have guessed, I was the only one saying no to the >>>> 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the >>>> discussion of how we engage with GAC in this 'facilitated dialogue' but >>>> thankfully they still respected our objection. My first point of objection >>>> is that the small team is really not representative enough to make the >>>> decision of whether the Council should meet with the GAC. For now, we >>>> agreed to refer this back to the Council and make the decision at the >>>> Council level. >>>> >>>> I'm afraid though NCSG would be the only one saying no when we're at >>>> the Council level. Also when this pops up, we really have to have our >>>> statement ready explaining why we're saying no. I've put notes in the >>>> document Tomslin created and Kathy has been extremely helpful by providing >>>> reference material and edits: >>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>> >>>> >>>> We will still need to phrase them into a formal statement, but I think >>>> it'd be an easy task now we have all the contents. >>>> >>>> Best, >>>> Manju >>>> >>>> On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar < >>>> mesumbeslin at gmail.com> wrote: >>>> >>>>> Hi team, >>>>> >>>>> I just wanted to call your attention to this response we promised to >>>>> put together on the board proposed dialogue between GAC and Council on >>>>> closed generics. The Council small team is about to be activated to start >>>>> deliberations and I believe @??? Manju Chen who is >>>>> representing us there hopes to rely on the response we pen down to guide >>>>> her contribution to that team. >>>>> >>>>> In this regard, can I request that we find some time to please put our >>>>> ideas down on the Google form >>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>> >>>>> Looking forward to your help with this. In the meantime, i'll review >>>>> my meeting notes and put down some feedback we got during our policy call >>>>> on the document. >>>>> >>>>> Warmly, >>>>> Tomslin >>>>> >>>>> On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, >>>>> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> As a follow-up to my previous email regarding the board's proposed >>>>>> facilitated dialogue between GAC and GNSO council, I have created this >>>>>> Google doc [ >>>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>>> ] to capture our response to this proposal in the form of a letter to the >>>>>> council small team on Closed Generics. >>>>>> >>>>>> Inputs to the document are welcomed and for your convenience, >>>>>> attached again is the letter from the board and the accompanying framing >>>>>> paper. >>>>>> >>>>>> Regards, >>>>>> Tomslin >>>>>> >>>>>> >>>>>> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar < >>>>>> mesumbeslin at gmail.com> wrote: >>>>>> >>>>>>> Dear everyone, >>>>>>> >>>>>>> Here is the framing paper on the board's proposed dialogue between >>>>>>> GNSO Council and the GAC on Closed Generics that was promised. >>>>>>> >>>>>>> Comments are welcomed. I will also be sending a separate email with >>>>>>> a link to the Google doc where we intend to draft a letter as a response to >>>>>>> this. >>>>>>> >>>>>>> Regards, >>>>>>> Tomslin >>>>>>> >>>>>>> >>>>>>> ---------- Forwarded message --------- >>>>>>> From: Wendy Profit via Gnso-chairs >>>>>>> Date: Fri, 11 Mar 2022 at 04:33 >>>>>>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal >>>>>>> Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>>> To: manal.ismail at board.icann.org , >>>>>>> Manal Ismail , philippe.fouquart at orange.com < >>>>>>> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >>>>>>> gnso-chairs at icann.org> >>>>>>> Cc: Secretary , Correspondence < >>>>>>> Correspondence at icann.org>, Board Ops Team , >>>>>>> gnso-secs at icann.org , GACSTAFF < >>>>>>> gac-staff at icann.org>, Maarten Botterman < >>>>>>> maarten.botterman at board.icann.org> >>>>>>> >>>>>>> >>>>>>> Dear Manal and Philippe, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Pursuant to the letter sent recently (6 March 2022, attached for >>>>>>> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >>>>>>> Process for a GAC - GNSO Council Dialogue on Closed Generics?, also >>>>>>> attached. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thank you and best regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Wendy Profit >>>>>>> >>>>>>> ICANN >>>>>>> >>>>>>> Board Operations Senior Manager >>>>>>> >>>>>>> 12025 Waterfront Drive, Suite 300 >>>>>>> >>>>>>> Los Angeles, CA 90094 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> *From: *Wendy Profit >>>>>>> *Date: *Sunday, March 6, 2022 at 3:58 PM >>>>>>> *To: *"manal.ismail at board.icann.org" , >>>>>>> "manal at tra.gov.eg" , "philippe.fouquart at orange.com" >>>>>>> >>>>>>> *Cc: *Maarten Botterman , " >>>>>>> gnso-chairs at icann.org" , GACSTAFF < >>>>>>> gac-staff at icann.org>, "gnso-secs at icann.org" , >>>>>>> ICANN Board Ops , Correspondence < >>>>>>> Correspondence at icann.org>, Secretary >>>>>>> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >>>>>>> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>>> >>>>>>> >>>>>>> >>>>>>> Dear Manal and Philippe, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Please find the attached letter from ICANN Chair Maarten Botterman >>>>>>> regarding a proposed formal consultation between the GAC and GNSO Council >>>>>>> on how to handle the subject of closed generics in gTLD applications. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thank you and best regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Wendy Profit >>>>>>> >>>>>>> ICANN >>>>>>> >>>>>>> Board Operations Senior Manager >>>>>>> >>>>>>> 12025 Waterfront Drive, Suite 300 >>>>>>> >>>>>>> Los Angeles, CA 90094 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Gnso-chairs mailing list >>>>>>> Gnso-chairs at icann.org >>>>>>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>>>>>> _______________________________________________ >>>>>>> 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. >>>>>>> >>>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Thu Apr 14 02:38:37 2022 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Thu, 14 Apr 2022 08:38:37 +0900 Subject: [NCSG-PC] [NCSG-SubPro] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> Message-ID: Hi, I think the argument that will be used to respond to the idea of public comment is : councillors are representing their SG/C and are supposed to bring their input. Moreover in more practical matter, we are raising issues about discussing this issue with GAC but public comment means another group like ALAC would be involved. Any wider discussion should be then done within PDP and not through ad-hoc approach. I can see there might be some possible alignment with ALAC in the topic (just an assumption) but I would object to open the door just for tactical gain. If we fail to stop the process, the next step would be to discuss the rules of engagement and scope for any discussion. Best. Rafik On Thu, Apr 14, 2022, 00:59 Kathy Kleiman via NCSG-SubPro < ncsg-subpro at lists.ncsg.is> wrote: > Hi Manju, > > Great letter and great edits by Bruna. I edited a few small things and > then pulled out and expanded our "ask" - that we would like the GNSO > Council to hold a comment period to provide input and guidance to this > small group of individuals appointed to talk to the GAC (should our > excellent and well-founded objections to the process be overruled). This > will provide a way for the GNSO Council to know the issues/concerns/hopes o > the GNSO Community on this matter - and to provide clear input and > guidance to the the small Committee for the negotiations that may lie > ahead. > > Here's the paragraph - building on opening sentences of Manju and edits of > Bruna: > > We strongly support as the first step that the GNSO Council seek public > comment from the community on how to proceed with Closed Generics, as > opposed to having a ?closed dialogue? with the GAC where the scope and > interlocutors of such dialogue is dictated by the ICANN Board. This input > will provide the Council with issues and concerns of the GNSO Community. > The Council, in turn, can provide guidance to the members of the Council > who will be leading this discussion - should it occur despite our deep > concerns for Multistakeholder process and precedent. How else will this > small team - some with very, very long-held personal views on the subject - > be bound to a discussion on behalf of the entire GNSO Community? > > I recommend putting the paragraph in bold for those who tend to scan their > email. > > Best, Kathy > > On 4/11/2022 11:04 PM, ??? Manju Chen wrote: > > Hi all, > > As discussed per yesterday's policy call, I've drafted our formal response > to be sent to the Council (and the Board?) > > You can find the statement here: > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > Feedbacks and suggestions are welcome and will be highly appreciated! > > > Best, > Manju > > On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen wrote: > >> Hi Tomslin and all, >> >> Kurt and others obviously wanted it to be discussed in the Council >> meeting this week. >> Steve has suggested if that was the intent we could propose a late >> motion. I think NCSG is not in a hurry about this, so I'll let others >> handle it if they want to propose the motion. >> >> I can share more details and answer questions today later during our >> policy call. >> >> Best, >> Manju >> >> >> >> On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar >> wrote: >> >>> Hi Manju, >>> Thank you so much for the update. Nice strategy there with the small >>> team representation. Do you know when that deferral will be brought to the >>> council's attention? Or maybe I missed it in my hundreds of emails. >>> >>> Thanks again. >>> Tomslin >>> >>> >>> On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: >>> >>>> Hi team, >>>> >>>> Borrowing this thread to report back to you about what happened in the >>>> small team. >>>> >>>> So as you might have guessed, I was the only one saying no to the >>>> 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the >>>> discussion of how we engage with GAC in this 'facilitated dialogue' but >>>> thankfully they still respected our objection. My first point of objection >>>> is that the small team is really not representative enough to make the >>>> decision of whether the Council should meet with the GAC. For now, we >>>> agreed to refer this back to the Council and make the decision at the >>>> Council level. >>>> >>>> I'm afraid though NCSG would be the only one saying no when we're at >>>> the Council level. Also when this pops up, we really have to have our >>>> statement ready explaining why we're saying no. I've put notes in the >>>> document Tomslin created and Kathy has been extremely helpful by providing >>>> reference material and edits: >>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>> >>>> >>>> We will still need to phrase them into a formal statement, but I think >>>> it'd be an easy task now we have all the contents. >>>> >>>> Best, >>>> Manju >>>> >>>> On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar < >>>> mesumbeslin at gmail.com> wrote: >>>> >>>>> Hi team, >>>>> >>>>> I just wanted to call your attention to this response we promised to >>>>> put together on the board proposed dialogue between GAC and Council on >>>>> closed generics. The Council small team is about to be activated to start >>>>> deliberations and I believe @??? Manju Chen who is >>>>> representing us there hopes to rely on the response we pen down to guide >>>>> her contribution to that team. >>>>> >>>>> In this regard, can I request that we find some time to please put our >>>>> ideas down on the Google form >>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>> >>>>> Looking forward to your help with this. In the meantime, i'll review >>>>> my meeting notes and put down some feedback we got during our policy call >>>>> on the document. >>>>> >>>>> Warmly, >>>>> Tomslin >>>>> >>>>> On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, >>>>> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> As a follow-up to my previous email regarding the board's proposed >>>>>> facilitated dialogue between GAC and GNSO council, I have created this >>>>>> Google doc [ >>>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>>> ] to capture our response to this proposal in the form of a letter to the >>>>>> council small team on Closed Generics. >>>>>> >>>>>> Inputs to the document are welcomed and for your convenience, >>>>>> attached again is the letter from the board and the accompanying framing >>>>>> paper. >>>>>> >>>>>> Regards, >>>>>> Tomslin >>>>>> >>>>>> >>>>>> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar < >>>>>> mesumbeslin at gmail.com> wrote: >>>>>> >>>>>>> Dear everyone, >>>>>>> >>>>>>> Here is the framing paper on the board's proposed dialogue between >>>>>>> GNSO Council and the GAC on Closed Generics that was promised. >>>>>>> >>>>>>> Comments are welcomed. I will also be sending a separate email with >>>>>>> a link to the Google doc where we intend to draft a letter as a response to >>>>>>> this. >>>>>>> >>>>>>> Regards, >>>>>>> Tomslin >>>>>>> >>>>>>> >>>>>>> ---------- Forwarded message --------- >>>>>>> From: Wendy Profit via Gnso-chairs >>>>>>> Date: Fri, 11 Mar 2022 at 04:33 >>>>>>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal >>>>>>> Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>>> To: manal.ismail at board.icann.org , >>>>>>> Manal Ismail , philippe.fouquart at orange.com < >>>>>>> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >>>>>>> gnso-chairs at icann.org> >>>>>>> Cc: Secretary , Correspondence < >>>>>>> Correspondence at icann.org>, Board Ops Team , >>>>>>> gnso-secs at icann.org , GACSTAFF < >>>>>>> gac-staff at icann.org>, Maarten Botterman < >>>>>>> maarten.botterman at board.icann.org> >>>>>>> >>>>>>> >>>>>>> Dear Manal and Philippe, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Pursuant to the letter sent recently (6 March 2022, attached for >>>>>>> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >>>>>>> Process for a GAC - GNSO Council Dialogue on Closed Generics?, also >>>>>>> attached. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thank you and best regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Wendy Profit >>>>>>> >>>>>>> ICANN >>>>>>> >>>>>>> Board Operations Senior Manager >>>>>>> >>>>>>> 12025 Waterfront Drive, Suite 300 >>>>>>> >>>>>>> Los Angeles, CA 90094 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> *From: *Wendy Profit >>>>>>> *Date: *Sunday, March 6, 2022 at 3:58 PM >>>>>>> *To: *"manal.ismail at board.icann.org" , >>>>>>> "manal at tra.gov.eg" , "philippe.fouquart at orange.com" >>>>>>> >>>>>>> *Cc: *Maarten Botterman , " >>>>>>> gnso-chairs at icann.org" , GACSTAFF < >>>>>>> gac-staff at icann.org>, "gnso-secs at icann.org" , >>>>>>> ICANN Board Ops , Correspondence < >>>>>>> Correspondence at icann.org>, Secretary >>>>>>> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >>>>>>> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>>> >>>>>>> >>>>>>> >>>>>>> Dear Manal and Philippe, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Please find the attached letter from ICANN Chair Maarten Botterman >>>>>>> regarding a proposed formal consultation between the GAC and GNSO Council >>>>>>> on how to handle the subject of closed generics in gTLD applications. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thank you and best regards, >>>>>>> >>>>>>> >>>>>>> >>>>>>> Wendy Profit >>>>>>> >>>>>>> ICANN >>>>>>> >>>>>>> Board Operations Senior Manager >>>>>>> >>>>>>> 12025 Waterfront Drive, Suite 300 >>>>>>> >>>>>>> Los Angeles, CA 90094 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Gnso-chairs mailing list >>>>>>> Gnso-chairs at icann.org >>>>>>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>>>>>> _______________________________________________ >>>>>>> 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. >>>>>>> >>>>>> -- > NCSG-SubPro mailing list > NCSG-SubPro at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-subpro > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Thu Apr 14 02:39:01 2022 From: stephanie.perrin at mail.utoronto.ca (Stephanie E Perrin) Date: Wed, 13 Apr 2022 19:39:01 -0400 Subject: [NCSG-PC] Fwd: Article on Small Team Proposal to the GNSO Council In-Reply-To: <082101d84f54$a049ade0$e0dd09a0$@palage.com> References: <082101d84f54$a049ade0$e0dd09a0$@palage.com> Message-ID: <6283cf33-3a61-7cbd-0d69-3fb9ea66662d@mail.utoronto.ca> Here is Palage's missive.? I go bonkers when I see these unsigned, untitled, undated documents circulating.....having tried to do a dissertation by going through all the documentation on 20 years of arguments, let me assure you this is not the first time a badly attributed documented roamed into our GNSO corral. cheers SP. PS don't be surprised if tomorrow's meeting goes longer than it should...... -------- Forwarded Message -------- Subject: Article on Small Team Proposal to the GNSO Council Date: Wed, 13 Apr 2022 12:36:26 -0400 From: Michael Palage Reply-To: michael at palage.com To: 'Alan Greenberg' , 'Stephanie E Perrin' , john.mcelwaine at nelsonmullins.com, pmcgrady at taftlaw.com, Sebastien at registry.godaddy, 'Kapin, Laureen' , 'Olga Cavalli' , 'Thomas Rickert | rickert.law' , 'Sarah Wyld' , 'Steve DelBianco' , 'Becky Burr' , 'Steve Crocker' CC: 'Marika Konings' Hello All, Attached is a document which comments on the proposed Small Team recommendations to the GNSO Council. Over the last week we have presented our reference implementation of an SSAD Sandbox to the BC and IPC. ?In fact, both Steve and Paul participated in those sessions. ?We believe this reference implementation addresses ALL of the original EPDP Phase 2 recommendations as adopted by the GNSO Council. ?It would really be nice if the Small Team and ICANN Org could make fact based policy decisions on what is technically and cost efficiently possible before prematurely scaling back EPDP Phase 2 recommendations based upon flawed financial assumptions. To be clear we are just asking the Small Team or ICANN Org to invite ALL interested parties to show what is possible, before suspending/disregarding a Super Majority vote of the GNSO Council on the EPDP Phase 2 recommendations. Best regards, Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: GNSO-Communication-12-April-2022.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 42265 bytes Desc: not available URL: From bruna.mrtns at gmail.com Thu Apr 14 14:04:54 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Thu, 14 Apr 2022 13:04:54 +0200 Subject: [NCSG-PC] Letter from Bruna Santos to Philippe Fouquart - NCSG Response to the Board's Proposal for a Council-GAC dialogue on Closed Generics Message-ID: Dear Philippe, Sebastien and Tomslin, I hope this email finds you well. Please find attached NCSGs letter in *response to the Board's Proposal for a GNSO Council & GAC dialogue on Closed Generics, *to yours and GNSO council appreciation. We trust that this communication will provide the council with the current concerns shared by our part of the community and represents some of the internal discussions hosted at NCSG about the Board's recommendation of a dialogue with the GAC. We look forward to continuing our conversations with the GNSO Council and the ICANN Board regarding the Closed Generics. -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Letter from Bruna Santos to Philippe Fo...logue on Closed Generics - Google Docs.png Type: image/png Size: 586270 bytes Desc: not available URL: From bruna.mrtns at gmail.com Thu Apr 14 14:27:38 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Thu, 14 Apr 2022 13:27:38 +0200 Subject: [NCSG-PC] Letter from Bruna Santos to Philippe Fouquart - NCSG Response to the Board's Proposal for a Council-GAC dialogue on Closed Generics In-Reply-To: References: Message-ID: Resending the version of the letter in PDF format. Best, Bruna Santos On Thu, Apr 14, 2022 at 1:04 PM Bruna Martins dos Santos < bruna.mrtns at gmail.com> wrote: > Dear Philippe, Sebastien and Tomslin, > > I hope this email finds you well. > > Please find attached NCSGs letter in *response to the Board's Proposal > for a GNSO Council & GAC dialogue on Closed Generics, *to yours and GNSO > council appreciation. > > We trust that this communication will provide the council with the current > concerns shared by our part of the community and represents some of the > internal discussions hosted at NCSG about the Board's recommendation of a > dialogue with the GAC. > > We look forward to continuing our conversations with the GNSO Council and > the ICANN Board regarding the Closed Generics. > > -- > > *Bruna Martins dos Santos * > > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von > Humboldt Foundation > > Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin > f?r Sozialforschung (WZB) > > Member | Coaliz?o Direitos na Rede > Chair | Non-Commercial Stakeholder Group at ICANN > > Co-Coordinator | Internet Governance Caucus > > Twitter: @boomartins // Skype: > bruna.martinsantos > *bruna.martinsdossantos at wzb.eu * and > bruna.mrtns at gmail.com > -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Letter from Bruna Santos to Philippe Fo...logue on Closed Generics - 14.04.2022.png Type: image/png Size: 586270 bytes Desc: not available URL: From bruna.mrtns at gmail.com Thu Apr 14 15:36:59 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Thu, 14 Apr 2022 14:36:59 +0200 Subject: [NCSG-PC] Letter from Bruna Santos to Philippe Fouquart - NCSG Response to the Board's Proposal for a Council-GAC dialogue on Closed Generics In-Reply-To: References: Message-ID: Dear all, Apologies but there seems to be a problem at my end while saving the document. I?m trying to submit - once again - a PDF version of the letter attached. I?m sorry for overburdening you with emails! Best, Bruna On Thu 14. Apr 2022 at 13:27, Bruna Martins dos Santos < bruna.mrtns at gmail.com> wrote: > Resending the version of the letter in PDF format. > > Best, > Bruna Santos > > On Thu, Apr 14, 2022 at 1:04 PM Bruna Martins dos Santos < > bruna.mrtns at gmail.com> wrote: > >> Dear Philippe, Sebastien and Tomslin, >> >> I hope this email finds you well. >> >> Please find attached NCSGs letter in *response to the Board's Proposal >> for a GNSO Council & GAC dialogue on Closed Generics, *to yours and GNSO >> council appreciation. >> >> We trust that this communication will provide the council with the >> current concerns shared by our part of the community and represents some of >> the internal discussions hosted at NCSG about the Board's recommendation of >> a dialogue with the GAC. >> >> We look forward to continuing our conversations with the GNSO Council and >> the ICANN Board regarding the Closed Generics. >> >> -- >> >> *Bruna Martins dos Santos * >> >> German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander >> von Humboldt Foundation >> >> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum >> Berlin f?r Sozialforschung (WZB) >> >> Member | Coaliz?o Direitos na Rede >> Chair | Non-Commercial Stakeholder Group at ICANN >> >> Co-Coordinator | Internet Governance Caucus >> >> Twitter: @boomartins // Skype: >> bruna.martinsantos >> *bruna.martinsdossantos at wzb.eu * and >> bruna.mrtns at gmail.com >> > > > -- > > *Bruna Martins dos Santos * > > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von > Humboldt Foundation > > Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin > f?r Sozialforschung (WZB) > > Member | Coaliz?o Direitos na Rede > Chair | Non-Commercial Stakeholder Group at ICANN > > Co-Coordinator | Internet Governance Caucus > > Twitter: @boomartins // Skype: > bruna.martinsantos > *bruna.martinsdossantos at wzb.eu * and > bruna.mrtns at gmail.com > -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Letter%20from%20Bruna%20Santos%20to%20Philippe%20Fouquart%20-%20NCSG%20Response%.pdf Type: application/pdf Size: 148863 bytes Desc: not available URL: From brenda.brewer at icann.org Mon Apr 18 19:30:38 2022 From: brenda.brewer at icann.org (Brenda Brewer) Date: Mon, 18 Apr 2022 16:30:38 +0000 Subject: [NCSG-PC] FW: NCSG Policy Call - attendees, replay, chat - 11 April 2022 In-Reply-To: <69ACCACE-56D6-4BD6-B25F-54549E1863E9@icann.org> References: <69ACCACE-56D6-4BD6-B25F-54549E1863E9@icann.org> Message-ID: <19C79064-1867-42A3-820A-24E651940CEE@icann.org> Good day NCSG Members, Please see attached the transcript for the NCSG Monthly Policy Call held Monday, 11 April 2022 at 11:30 UTC. Thank you. Best, Andrea & Brenda From: Brenda Brewer Date: Monday, April 11, 2022 at 4:22 PM To: "ncsg-pc at lists.ncsg.is" , NCSG-Discuss Cc: Andrea Glandon , Brenda Brewer Subject: NCSG Policy Call - attendees, replay, chat - 11 April 2022 Dear NCSG members, Please find attendees, replay, and chat details for the NCSG Monthly Policy Call held Monday, 11 April 2022 at 11:30 UTC. The transcript will be sent upon completion. Thank you! Kind regards, Andrea and Brenda Attendees: Avri Doria, Benjamin Akinmoyeje, Bruna Martins dos Santos, Daniel Charles, Ephraim Percy Kenyanito, Farell Folly, Juan Manuel Rojas, Kathy Kleiman, Kenneth Herman, Manju Chen, Poncelet Ileleji, Rafik Dammak, Razoana Moslam, Robin Gross, Shah Zahidur Rahman, Stephanie Perrin, Tomslin Samme-Nlar, Wisdom Donkor | ICANN Org: Andrea Glandon, Brenda Brewer, Carlos Reyes Zoom Replay Link: \ https://icann.zoom.us/rec/play/42g_Lvdj3EYNSp1WkLEVFZa6mMv2G2aNpiWw26HIP1423FJE_WXvaI-Vvefy8q5JcKwUZmk6zNWPNiZt.I6c947Laea4NEGPV Zoom Audio Link: https://icann.zoom.us/rec/play/b8siW3Tmi1zsiTHhp-9WFywkqzB26_0jpVzeboR2aZU9Dq0DmEj673xmGNtNoGkrIsLvwOPl7CDQAbTz.H5037eExYDM0TKIh Zoom Chat Link: https://icann.zoom.us/rec/sdownload/uV5-22nkkJ9ACH9QxDOYVjjX6OKMgh4hT8Dxk1lR7jaFS6pJXBFbabfQA1ZviN_RebKvqgM7J-94wjVx.mZH1SMv9kS5igZqt -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Transcript_NCSG Policy_11April2022.pdf Type: application/pdf Size: 296525 bytes Desc: Transcript_NCSG Policy_11April2022.pdf URL: From manju at nii.org.tw Fri Apr 22 05:30:06 2022 From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=) Date: Fri, 22 Apr 2022 10:30:06 +0800 Subject: [NCSG-PC] [NCSG-SubPro] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> Message-ID: Hi all, Thought it's worth it to report back to you that our objection to the dialogue was acknowledged but brushed aside by the Council chair. I would be optimistic and say that we still have many chances to voice our opinions during the latter process, the first step being broadening the dialogue to include more stakeholders within the GNSO, not limited to Councilors. Attached is the Council's draft response to the Board. There are discussions going on about whether the NCSG's letter of objection should be included in the response. My personal opinion is opt-out of being included in the Council's response and send our letter to the Board ourselves. But I'd like to know what you think. Council plans to send out the response by the Board Workshop next week so we'll have to respond before April 27th 1200 UTC (Wednesday). Any suggestions are welcome! Best, Manju On Thu, Apr 14, 2022 at 7:38 AM Rafik Dammak wrote: > Hi, > > > I think the argument that will be used to respond to the idea of public > comment is : councillors are representing their SG/C and are supposed to > bring their input. > > Moreover in more practical matter, we are raising issues about discussing > this issue with GAC but public comment means another group like ALAC would > be involved. Any wider discussion should be then done within PDP and not > through ad-hoc approach. I can see there might be some possible alignment > with ALAC in the topic (just an assumption) but I would object to open the > door just for tactical gain. > > If we fail to stop the process, the next step would be to discuss the > rules of engagement and scope for any discussion. > > Best. > > Rafik > > On Thu, Apr 14, 2022, 00:59 Kathy Kleiman via NCSG-SubPro < > ncsg-subpro at lists.ncsg.is> wrote: > >> Hi Manju, >> >> Great letter and great edits by Bruna. I edited a few small things and >> then pulled out and expanded our "ask" - that we would like the GNSO >> Council to hold a comment period to provide input and guidance to this >> small group of individuals appointed to talk to the GAC (should our >> excellent and well-founded objections to the process be overruled). This >> will provide a way for the GNSO Council to know the issues/concerns/hopes o >> the GNSO Community on this matter - and to provide clear input and >> guidance to the the small Committee for the negotiations that may lie >> ahead. >> >> Here's the paragraph - building on opening sentences of Manju and edits >> of Bruna: >> >> We strongly support as the first step that the GNSO Council seek public >> comment from the community on how to proceed with Closed Generics, as >> opposed to having a ?closed dialogue? with the GAC where the scope and >> interlocutors of such dialogue is dictated by the ICANN Board. This input >> will provide the Council with issues and concerns of the GNSO Community. >> The Council, in turn, can provide guidance to the members of the Council >> who will be leading this discussion - should it occur despite our deep >> concerns for Multistakeholder process and precedent. How else will this >> small team - some with very, very long-held personal views on the subject - >> be bound to a discussion on behalf of the entire GNSO Community? >> >> I recommend putting the paragraph in bold for those who tend to scan >> their email. >> >> Best, Kathy >> >> On 4/11/2022 11:04 PM, ??? Manju Chen wrote: >> >> Hi all, >> >> As discussed per yesterday's policy call, I've drafted our formal >> response to be sent to the Council (and the Board?) >> >> You can find the statement here: >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> Feedbacks and suggestions are welcome and will be highly appreciated! >> >> >> Best, >> Manju >> >> On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen wrote: >> >>> Hi Tomslin and all, >>> >>> Kurt and others obviously wanted it to be discussed in the Council >>> meeting this week. >>> Steve has suggested if that was the intent we could propose a late >>> motion. I think NCSG is not in a hurry about this, so I'll let others >>> handle it if they want to propose the motion. >>> >>> I can share more details and answer questions today later during our >>> policy call. >>> >>> Best, >>> Manju >>> >>> >>> >>> On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar >>> wrote: >>> >>>> Hi Manju, >>>> Thank you so much for the update. Nice strategy there with the small >>>> team representation. Do you know when that deferral will be brought to the >>>> council's attention? Or maybe I missed it in my hundreds of emails. >>>> >>>> Thanks again. >>>> Tomslin >>>> >>>> >>>> On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: >>>> >>>>> Hi team, >>>>> >>>>> Borrowing this thread to report back to you about what happened in the >>>>> small team. >>>>> >>>>> So as you might have guessed, I was the only one saying no to the >>>>> 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the >>>>> discussion of how we engage with GAC in this 'facilitated dialogue' but >>>>> thankfully they still respected our objection. My first point of objection >>>>> is that the small team is really not representative enough to make the >>>>> decision of whether the Council should meet with the GAC. For now, we >>>>> agreed to refer this back to the Council and make the decision at the >>>>> Council level. >>>>> >>>>> I'm afraid though NCSG would be the only one saying no when we're at >>>>> the Council level. Also when this pops up, we really have to have our >>>>> statement ready explaining why we're saying no. I've put notes in the >>>>> document Tomslin created and Kathy has been extremely helpful by providing >>>>> reference material and edits: >>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>> >>>>> >>>>> We will still need to phrase them into a formal statement, but I think >>>>> it'd be an easy task now we have all the contents. >>>>> >>>>> Best, >>>>> Manju >>>>> >>>>> On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar < >>>>> mesumbeslin at gmail.com> wrote: >>>>> >>>>>> Hi team, >>>>>> >>>>>> I just wanted to call your attention to this response we promised to >>>>>> put together on the board proposed dialogue between GAC and Council on >>>>>> closed generics. The Council small team is about to be activated to start >>>>>> deliberations and I believe @??? Manju Chen who >>>>>> is representing us there hopes to rely on the response we pen down to guide >>>>>> her contribution to that team. >>>>>> >>>>>> In this regard, can I request that we find some time to please put >>>>>> our ideas down on the Google form >>>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>>> >>>>>> Looking forward to your help with this. In the meantime, i'll review >>>>>> my meeting notes and put down some feedback we got during our policy call >>>>>> on the document. >>>>>> >>>>>> Warmly, >>>>>> Tomslin >>>>>> >>>>>> On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, >>>>>> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> As a follow-up to my previous email regarding the board's proposed >>>>>>> facilitated dialogue between GAC and GNSO council, I have created this >>>>>>> Google doc [ >>>>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>>>> ] to capture our response to this proposal in the form of a letter to the >>>>>>> council small team on Closed Generics. >>>>>>> >>>>>>> Inputs to the document are welcomed and for your convenience, >>>>>>> attached again is the letter from the board and the accompanying framing >>>>>>> paper. >>>>>>> >>>>>>> Regards, >>>>>>> Tomslin >>>>>>> >>>>>>> >>>>>>> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar < >>>>>>> mesumbeslin at gmail.com> wrote: >>>>>>> >>>>>>>> Dear everyone, >>>>>>>> >>>>>>>> Here is the framing paper on the board's proposed dialogue between >>>>>>>> GNSO Council and the GAC on Closed Generics that was promised. >>>>>>>> >>>>>>>> Comments are welcomed. I will also be sending a separate email with >>>>>>>> a link to the Google doc where we intend to draft a letter as a response to >>>>>>>> this. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Tomslin >>>>>>>> >>>>>>>> >>>>>>>> ---------- Forwarded message --------- >>>>>>>> From: Wendy Profit via Gnso-chairs >>>>>>>> Date: Fri, 11 Mar 2022 at 04:33 >>>>>>>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal >>>>>>>> Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>>>> To: manal.ismail at board.icann.org , >>>>>>>> Manal Ismail , philippe.fouquart at orange.com < >>>>>>>> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >>>>>>>> gnso-chairs at icann.org> >>>>>>>> Cc: Secretary , Correspondence < >>>>>>>> Correspondence at icann.org>, Board Ops Team , >>>>>>>> gnso-secs at icann.org , GACSTAFF < >>>>>>>> gac-staff at icann.org>, Maarten Botterman < >>>>>>>> maarten.botterman at board.icann.org> >>>>>>>> >>>>>>>> >>>>>>>> Dear Manal and Philippe, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Pursuant to the letter sent recently (6 March 2022, attached for >>>>>>>> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >>>>>>>> Process for a GAC - GNSO Council Dialogue on Closed Generics?, >>>>>>>> also attached. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Thank you and best regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Wendy Profit >>>>>>>> >>>>>>>> ICANN >>>>>>>> >>>>>>>> Board Operations Senior Manager >>>>>>>> >>>>>>>> 12025 Waterfront Drive, Suite 300 >>>>>>>> >>>>>>>> Los Angeles, CA 90094 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> *From: *Wendy Profit >>>>>>>> *Date: *Sunday, March 6, 2022 at 3:58 PM >>>>>>>> *To: *"manal.ismail at board.icann.org" , >>>>>>>> "manal at tra.gov.eg" , " >>>>>>>> philippe.fouquart at orange.com" >>>>>>>> *Cc: *Maarten Botterman , " >>>>>>>> gnso-chairs at icann.org" , GACSTAFF < >>>>>>>> gac-staff at icann.org>, "gnso-secs at icann.org" , >>>>>>>> ICANN Board Ops , Correspondence < >>>>>>>> Correspondence at icann.org>, Secretary >>>>>>>> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >>>>>>>> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Dear Manal and Philippe, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Please find the attached letter from ICANN Chair Maarten Botterman >>>>>>>> regarding a proposed formal consultation between the GAC and GNSO Council >>>>>>>> on how to handle the subject of closed generics in gTLD applications. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Thank you and best regards, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Wendy Profit >>>>>>>> >>>>>>>> ICANN >>>>>>>> >>>>>>>> Board Operations Senior Manager >>>>>>>> >>>>>>>> 12025 Waterfront Drive, Suite 300 >>>>>>>> >>>>>>>> Los Angeles, CA 90094 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Gnso-chairs mailing list >>>>>>>> Gnso-chairs at icann.org >>>>>>>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>>>>>>> _______________________________________________ >>>>>>>> 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. >>>>>>>> >>>>>>> -- >> NCSG-SubPro mailing list >> NCSG-SubPro at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-subpro >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Closed Generics_Council to ICANN Board - 20 April 2022.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 7074 bytes Desc: not available URL: From Kathy at KathyKleiman.com Fri Apr 22 19:49:19 2022 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Fri, 22 Apr 2022 12:49:19 -0400 Subject: [NCSG-PC] [NCSG-SubPro] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> Message-ID: <34eec13d-0d2f-1172-ecbb-7159174e82ec@KathyKleiman.com> Hi Manju, This is disappointing, but not surprising. Tx to you and our other Councilors for the trying to hold a fair and balanced line here. / / /Can I ask whether the Council will include our entire NCSG letter of objection to their response - or do they want to select parts of it? / If Council is willing to including our NCSG objection - whatever terms /we//would like to include in the Council letter /- with a clear and prominent reference to our NCSG letter of objection as an appendix-? then would it make it easier for the Board to see our concerns??? One place, one document to read (?) Of course, if the Council wants to edit our letter, then sending it separately makes sense.? Also perhaps there are advantages to sending it separately that I may not be seeing. But the overall issue - that sending a few well-known, very-opinionated, and frankly extreme (on this issue) Councilors to the GAC (not including Manju, of course!) without guidance from the GNSO Community is a distortion and misuse of the policy development process. Best, Kathy On 4/21/2022 10:30 PM, ??? Manju Chen wrote: > Hi all, > > Thought it's worth it to report back to you that our objection to the > dialogue was acknowledged but brushed aside by the Council chair. > I would be optimistic and say that we still have many chances to voice > our opinions during the latter process, the?first step being > broadening the dialogue to include more stakeholders within the GNSO, > not limited to Councilors. > > Attached is the Council's draft response to the Board. There are > discussions going on about whether the NCSG's letter of objection > should be included in the response. > > My personal opinion is opt-out of being included in the Council's > response and send our letter to the?Board ourselves. But I'd like to > know what you think. > > Council plans to send out the response by the Board Workshop next week > so we'll have to respond before April 27th 1200 UTC (Wednesday). > > Any suggestions are welcome! > > > Best, > Manju > > > On Thu, Apr 14, 2022 at 7:38 AM Rafik Dammak > wrote: > > Hi, > > > I think the argument that will be used to respond to the idea of > public comment is : councillors are representing their SG/C and > are supposed to bring their input. > > Moreover in more practical matter, we are raising issues about > discussing this issue with GAC but public comment means another > group like ALAC would be involved.? Any wider discussion should be > then done within PDP and not through ad-hoc approach. I can see > there might be some possible alignment with ALAC in the topic > (just an assumption) but I would object to open the door just for > tactical gain. > > If we fail to stop the process, the next step would be to discuss > the rules of engagement and scope for any discussion. > > Best. > > Rafik > > On Thu, Apr 14, 2022, 00:59 Kathy Kleiman via NCSG-SubPro > wrote: > > Hi Manju, > > Great letter and great edits by Bruna.? I edited a few small > things and then pulled out and expanded our "ask" - that we > would like the GNSO Council to hold a comment period to > provide input and guidance to this small group of individuals > appointed to talk to the GAC (should our excellent and > well-founded objections to the process be overruled).? This > will provide a way for the GNSO Council to know the > issues/concerns/hopes o the GNSO Community on this matter - > and to provide clear input? and guidance to the the small > Committee for the negotiations that may lie ahead. > > Here's the paragraph - building on opening sentences of Manju > and edits of Bruna: > > We strongly support as the first step that the GNSO Council > seek public comment from the community on how to proceed with > Closed Generics, as opposed to having a ?closed dialogue? with > the GAC where the scope and interlocutors of such dialogue is > dictated by the ICANN Board.? This input will provide the > Council with issues and concerns of the GNSO Community.? The > Council, in turn, can provide guidance to the members of the > Council who will be leading this discussion - should it occur > despite our deep concerns for Multistakeholder process and > precedent. How else will this small team - some with very, > very long-held personal views on the subject - be bound to a > discussion on behalf of the entire GNSO Community? > > I recommend putting the paragraph in bold for those who tend > to scan their email. > > Best, Kathy > > On 4/11/2022 11:04 PM, ??? Manju Chen wrote: > >> Hi all, >> >> As discussed per yesterday's policy call, I've drafted our >> formal response to be sent to the Council (and the Board?) >> >> You can find the statement here: >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> Feedbacks and suggestions are welcome and will be highly >> appreciated! >> >> >> Best, >> Manju >> >> On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen >> wrote: >> >> Hi Tomslin and all, >> >> Kurt and others obviously wanted it to be discussed in >> the Council meeting this week. >> Steve has suggested if that was the intent we could >> propose a late motion. I think?NCSG is not in a hurry >> about this, so I'll let others handle it if they want to >> propose the motion. >> >> I can share more details and answer questions today later >> during our policy call. >> >> Best, >> Manju >> >> >> >> On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar >> wrote: >> >> Hi Manju, >> Thank you so much for the update. Nice strategy there >> with the small team representation. Do you know when >> that deferral will be brought to the council's >> attention? Or maybe I missed it in my hundreds of emails. >> >> Thanks again. >> Tomslin >> >> >> On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen >> wrote: >> >> Hi team, >> >> Borrowing this thread to report back to you about >> what happened in the small team. >> >> So as you might have guessed, I was the only one >> saying no to the 'facilitated dialogue'. Jeff, >> Paul, and Kurt were eager to dive into the >> discussion of how we engage with GAC in this >> 'facilitated dialogue' but thankfully they still >> respected our objection. My first point of >> objection is that the small team is really not >> representative enough to make the decision of >> whether the Council should meet with the GAC. For >> now, we agreed to refer this back to the Council >> and make the decision at the Council level. >> >> I'm afraid though NCSG would be the only one >> saying no when we're at the Council level. Also >> when this pops up, we really have to have our >> statement ready?explaining why we're saying no. >> I've put notes in the document Tomslin created >> and Kathy has been extremely helpful by providing >> reference material and edits: >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> >> We will still need to phrase them into a formal >> statement, but I think it'd be an easy task now >> we have all the contents. >> >> Best, >> Manju >> >> On Thu, Mar 31, 2022 at 9:08 AM Tomslin >> Samme-Nlar wrote: >> >> Hi team, >> >> I just wanted to call your attention to this >> response we promised to put together on the >> board proposed dialogue between GAC and >> Council on closed generics. The Council small >> team is about to be activated to start >> deliberations and I believe @??? Manju Chen >> ?who is representing >> us there hopes to rely on the response we pen >> down to guide her contribution to that team. >> >> In this?regard, can I request that we find >> some time to please put our ideas down on the >> Google >> formhttps://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> Looking forward to your help with this. In >> the meantime, i'll review my meeting notes >> and put down some feedback we got during our >> policy call on the document. >> >> Warmly, >> Tomslin >> >> On Wed, 16 Mar 2022, 22:25 Tomslin >> Samme-Nlar, wrote: >> >> Hi all, >> >> As a follow-up to my previous email >> regarding the board's proposed >> facilitated dialogue between GAC and GNSO >> council, I have created this Google doc [ >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> ] to capture our response to this >> proposal in the form of a letter to the >> council small team on Closed Generics. >> >> Inputs to the document are welcomed and >> for your convenience, attached again is >> the letter from the board and the >> accompanying framing paper. >> >> Regards, >> Tomslin >> >> >> On Tue, 15 Mar 2022 at 08:12, Tomslin >> Samme-Nlar wrote: >> >> Dear everyone, >> >> Here is the framing paper on the >> board's proposed dialogue between >> GNSO Council and the GAC on Closed >> Generics that was promised. >> >> Comments are welcomed. I will also be >> sending a separate email with a link >> to the Google doc where we intend to >> draft a letter as a response to this. >> >> Regards, >> Tomslin >> >> >> ---------- Forwarded message --------- >> From: *Wendy Profit via Gnso-chairs* >> >> Date: Fri, 11 Mar 2022 at 04:33 >> Subject: [gnso-chairs] >> [CORRESPONDENCE] Maarten Botterman to >> Manal Ismail and Philippe Fouquart - >> GAC-GNSO Consultation on Closed Generics >> To: manal.ismail at board.icann.org >> , Manal >> Ismail , >> philippe.fouquart at orange.com >> , >> gnso-chairs at icann.org >> >> Cc: Secretary , >> Correspondence >> , Board Ops >> Team , >> gnso-secs at icann.org >> , GACSTAFF >> , Maarten >> Botterman >> >> >> >> Dear Manal and Philippe, >> >> Pursuant to the letter sent recently >> (6 March 2022, attached for >> reference), we are now forwarding the >> associated framework paper entitled >> ?Board-Facilitated Process for a GAC >> - GNSO Council Dialogue on Closed >> Generics?, also attached. >> >> ** >> >> Thank you and best regards, >> >> Wendy Profit >> >> ICANN >> >> Board Operations Senior Manager >> >> 12025 Waterfront Drive, Suite 300 >> >> Los Angeles, CA 90094 >> >> *From: *Wendy Profit >> >> *Date: *Sunday, March 6, 2022 at 3:58 PM >> *To: *"manal.ismail at board.icann.org" >> , >> "manal at tra.gov.eg" >> , >> "philippe.fouquart at orange.com" >> >> *Cc: *Maarten Botterman >> , >> "gnso-chairs at icann.org" >> , GACSTAFF >> , >> "gnso-secs at icann.org" >> , ICANN Board >> Ops , >> Correspondence >> , Secretary >> >> *Subject: *[CORRESPONDENCE] Maarten >> Botterman to Manal Ismail and >> Philippe Fouquart - GAC-GNSO >> Consultation on Closed Generics >> >> Dear Manal and Philippe, >> >> Please find the attached letter from >> ICANN Chair Maarten Botterman >> regarding a proposed formal >> consultation between the GAC and GNSO >> Council on how to handle the subject >> of closed generics in gTLD applications. >> >> Thank you and best regards, >> >> Wendy Profit >> >> ICANN >> >> Board Operations Senior Manager >> >> 12025 Waterfront Drive, Suite 300 >> >> Los Angeles, CA 90094 >> >> _______________________________________________ >> Gnso-chairs mailing list >> Gnso-chairs at icann.org >> https://mm.icann.org/mailman/listinfo/gnso-chairs >> _______________________________________________ >> 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. >> > -- > NCSG-SubPro mailing list > NCSG-SubPro at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-subpro > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Sat Apr 23 00:16:08 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 23 Apr 2022 07:16:08 +1000 Subject: [NCSG-PC] [NCSG-SubPro] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: <34eec13d-0d2f-1172-ecbb-7159174e82ec@KathyKleiman.com> References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> <34eec13d-0d2f-1172-ecbb-7159174e82ec@KathyKleiman.com> Message-ID: Hi all, I think the council has now decided not to include the letter. So I guess that leaves us to send it to the board ourselves? Tomslin On Sat, 23 Apr 2022 at 02:49, Kathy Kleiman wrote: > Hi Manju, > > This is disappointing, but not surprising. Tx to you and our other > Councilors for the trying to hold a fair and balanced line here. > > *Can I ask whether the Council will include our entire NCSG letter of > objection to their response - or do they want to select parts of it? * > > If Council is willing to including our NCSG objection - whatever terms > *we** would like to include in the Council letter *- with a clear and > prominent reference to our NCSG letter of objection as an appendix- then > would it make it easier for the Board to see our concerns? One place, one > document to read (?) > > Of course, if the Council wants to edit our letter, then sending it > separately makes sense. Also perhaps there are advantages to sending it > separately that I may not be seeing. > > But the overall issue - that sending a few well-known, very-opinionated, > and frankly extreme (on this issue) Councilors to the GAC (not including > Manju, of course!) without guidance from the GNSO Community is a distortion > and misuse of the policy development process. > > Best, Kathy > On 4/21/2022 10:30 PM, ??? Manju Chen wrote: > > Hi all, > > Thought it's worth it to report back to you that our objection to the > dialogue was acknowledged but brushed aside by the Council chair. > I would be optimistic and say that we still have many chances to voice our > opinions during the latter process, the first step being broadening the > dialogue to include more stakeholders within the GNSO, not limited to > Councilors. > > Attached is the Council's draft response to the Board. There are > discussions going on about whether the NCSG's letter of objection should be > included in the response. > > My personal opinion is opt-out of being included in the Council's response > and send our letter to the Board ourselves. But I'd like to know what you > think. > > Council plans to send out the response by the Board Workshop next week so > we'll have to respond before April 27th 1200 UTC (Wednesday). > > Any suggestions are welcome! > > > Best, > Manju > > > On Thu, Apr 14, 2022 at 7:38 AM Rafik Dammak > wrote: > >> Hi, >> >> >> I think the argument that will be used to respond to the idea of public >> comment is : councillors are representing their SG/C and are supposed to >> bring their input. >> >> Moreover in more practical matter, we are raising issues about discussing >> this issue with GAC but public comment means another group like ALAC would >> be involved. Any wider discussion should be then done within PDP and not >> through ad-hoc approach. I can see there might be some possible alignment >> with ALAC in the topic (just an assumption) but I would object to open the >> door just for tactical gain. >> >> If we fail to stop the process, the next step would be to discuss the >> rules of engagement and scope for any discussion. >> >> Best. >> >> Rafik >> >> On Thu, Apr 14, 2022, 00:59 Kathy Kleiman via NCSG-SubPro < >> ncsg-subpro at lists.ncsg.is> wrote: >> >>> Hi Manju, >>> >>> Great letter and great edits by Bruna. I edited a few small things and >>> then pulled out and expanded our "ask" - that we would like the GNSO >>> Council to hold a comment period to provide input and guidance to this >>> small group of individuals appointed to talk to the GAC (should our >>> excellent and well-founded objections to the process be overruled). This >>> will provide a way for the GNSO Council to know the issues/concerns/hopes o >>> the GNSO Community on this matter - and to provide clear input and >>> guidance to the the small Committee for the negotiations that may lie >>> ahead. >>> >>> Here's the paragraph - building on opening sentences of Manju and edits >>> of Bruna: >>> >>> We strongly support as the first step that the GNSO Council seek public >>> comment from the community on how to proceed with Closed Generics, as >>> opposed to having a ?closed dialogue? with the GAC where the scope and >>> interlocutors of such dialogue is dictated by the ICANN Board. This input >>> will provide the Council with issues and concerns of the GNSO Community. >>> The Council, in turn, can provide guidance to the members of the Council >>> who will be leading this discussion - should it occur despite our deep >>> concerns for Multistakeholder process and precedent. How else will this >>> small team - some with very, very long-held personal views on the subject - >>> be bound to a discussion on behalf of the entire GNSO Community? >>> >>> I recommend putting the paragraph in bold for those who tend to scan >>> their email. >>> >>> Best, Kathy >>> >>> On 4/11/2022 11:04 PM, ??? Manju Chen wrote: >>> >>> Hi all, >>> >>> As discussed per yesterday's policy call, I've drafted our formal >>> response to be sent to the Council (and the Board?) >>> >>> You can find the statement here: >>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>> >>> Feedbacks and suggestions are welcome and will be highly appreciated! >>> >>> >>> Best, >>> Manju >>> >>> On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen >>> wrote: >>> >>>> Hi Tomslin and all, >>>> >>>> Kurt and others obviously wanted it to be discussed in the Council >>>> meeting this week. >>>> Steve has suggested if that was the intent we could propose a late >>>> motion. I think NCSG is not in a hurry about this, so I'll let others >>>> handle it if they want to propose the motion. >>>> >>>> I can share more details and answer questions today later during our >>>> policy call. >>>> >>>> Best, >>>> Manju >>>> >>>> >>>> >>>> On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar < >>>> mesumbeslin at gmail.com> wrote: >>>> >>>>> Hi Manju, >>>>> Thank you so much for the update. Nice strategy there with the small >>>>> team representation. Do you know when that deferral will be brought to the >>>>> council's attention? Or maybe I missed it in my hundreds of emails. >>>>> >>>>> Thanks again. >>>>> Tomslin >>>>> >>>>> >>>>> On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: >>>>> >>>>>> Hi team, >>>>>> >>>>>> Borrowing this thread to report back to you about what happened in >>>>>> the small team. >>>>>> >>>>>> So as you might have guessed, I was the only one saying no to the >>>>>> 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the >>>>>> discussion of how we engage with GAC in this 'facilitated dialogue' but >>>>>> thankfully they still respected our objection. My first point of objection >>>>>> is that the small team is really not representative enough to make the >>>>>> decision of whether the Council should meet with the GAC. For now, we >>>>>> agreed to refer this back to the Council and make the decision at the >>>>>> Council level. >>>>>> >>>>>> I'm afraid though NCSG would be the only one saying no when we're at >>>>>> the Council level. Also when this pops up, we really have to have our >>>>>> statement ready explaining why we're saying no. I've put notes in the >>>>>> document Tomslin created and Kathy has been extremely helpful by providing >>>>>> reference material and edits: >>>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>>> >>>>>> >>>>>> We will still need to phrase them into a formal statement, but I >>>>>> think it'd be an easy task now we have all the contents. >>>>>> >>>>>> Best, >>>>>> Manju >>>>>> >>>>>> On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar < >>>>>> mesumbeslin at gmail.com> wrote: >>>>>> >>>>>>> Hi team, >>>>>>> >>>>>>> I just wanted to call your attention to this response we promised to >>>>>>> put together on the board proposed dialogue between GAC and Council on >>>>>>> closed generics. The Council small team is about to be activated to start >>>>>>> deliberations and I believe @??? Manju Chen who >>>>>>> is representing us there hopes to rely on the response we pen down to guide >>>>>>> her contribution to that team. >>>>>>> >>>>>>> In this regard, can I request that we find some time to please put >>>>>>> our ideas down on the Google form >>>>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>>>> >>>>>>> Looking forward to your help with this. In the meantime, i'll review >>>>>>> my meeting notes and put down some feedback we got during our policy call >>>>>>> on the document. >>>>>>> >>>>>>> Warmly, >>>>>>> Tomslin >>>>>>> >>>>>>> On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, < >>>>>>> mesumbeslin at gmail.com> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> As a follow-up to my previous email regarding the board's proposed >>>>>>>> facilitated dialogue between GAC and GNSO council, I have created this >>>>>>>> Google doc [ >>>>>>>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>>>>>>> ] to capture our response to this proposal in the form of a letter to the >>>>>>>> council small team on Closed Generics. >>>>>>>> >>>>>>>> Inputs to the document are welcomed and for your convenience, >>>>>>>> attached again is the letter from the board and the accompanying framing >>>>>>>> paper. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Tomslin >>>>>>>> >>>>>>>> >>>>>>>> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar < >>>>>>>> mesumbeslin at gmail.com> wrote: >>>>>>>> >>>>>>>>> Dear everyone, >>>>>>>>> >>>>>>>>> Here is the framing paper on the board's proposed dialogue between >>>>>>>>> GNSO Council and the GAC on Closed Generics that was promised. >>>>>>>>> >>>>>>>>> Comments are welcomed. I will also be sending a separate email >>>>>>>>> with a link to the Google doc where we intend to draft a letter as a >>>>>>>>> response to this. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Tomslin >>>>>>>>> >>>>>>>>> >>>>>>>>> ---------- Forwarded message --------- >>>>>>>>> From: Wendy Profit via Gnso-chairs >>>>>>>>> Date: Fri, 11 Mar 2022 at 04:33 >>>>>>>>> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal >>>>>>>>> Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>>>>> To: manal.ismail at board.icann.org , >>>>>>>>> Manal Ismail , philippe.fouquart at orange.com < >>>>>>>>> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >>>>>>>>> gnso-chairs at icann.org> >>>>>>>>> Cc: Secretary , Correspondence < >>>>>>>>> Correspondence at icann.org>, Board Ops Team < >>>>>>>>> board-ops-team at icann.org>, gnso-secs at icann.org < >>>>>>>>> gnso-secs at icann.org>, GACSTAFF , Maarten >>>>>>>>> Botterman >>>>>>>>> >>>>>>>>> >>>>>>>>> Dear Manal and Philippe, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Pursuant to the letter sent recently (6 March 2022, attached for >>>>>>>>> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >>>>>>>>> Process for a GAC - GNSO Council Dialogue on Closed Generics?, >>>>>>>>> also attached. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Thank you and best regards, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Wendy Profit >>>>>>>>> >>>>>>>>> ICANN >>>>>>>>> >>>>>>>>> Board Operations Senior Manager >>>>>>>>> >>>>>>>>> 12025 Waterfront Drive, Suite 300 >>>>>>>>> >>>>>>>>> Los Angeles, CA 90094 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *From: *Wendy Profit >>>>>>>>> *Date: *Sunday, March 6, 2022 at 3:58 PM >>>>>>>>> *To: *"manal.ismail at board.icann.org" , >>>>>>>>> "manal at tra.gov.eg" , " >>>>>>>>> philippe.fouquart at orange.com" >>>>>>>>> *Cc: *Maarten Botterman , " >>>>>>>>> gnso-chairs at icann.org" , GACSTAFF < >>>>>>>>> gac-staff at icann.org>, "gnso-secs at icann.org" , >>>>>>>>> ICANN Board Ops , Correspondence < >>>>>>>>> Correspondence at icann.org>, Secretary >>>>>>>>> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >>>>>>>>> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Dear Manal and Philippe, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Please find the attached letter from ICANN Chair Maarten Botterman >>>>>>>>> regarding a proposed formal consultation between the GAC and GNSO Council >>>>>>>>> on how to handle the subject of closed generics in gTLD applications. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Thank you and best regards, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Wendy Profit >>>>>>>>> >>>>>>>>> ICANN >>>>>>>>> >>>>>>>>> Board Operations Senior Manager >>>>>>>>> >>>>>>>>> 12025 Waterfront Drive, Suite 300 >>>>>>>>> >>>>>>>>> Los Angeles, CA 90094 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Gnso-chairs mailing list >>>>>>>>> Gnso-chairs at icann.org >>>>>>>>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>>>>>>>> _______________________________________________ >>>>>>>>> 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. >>>>>>>>> >>>>>>>> -- >>> NCSG-SubPro mailing list >>> NCSG-SubPro at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-subpro >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Sat Apr 23 00:21:05 2022 From: stephanie.perrin at mail.utoronto.ca (Stephanie E Perrin) Date: Fri, 22 Apr 2022 17:21:05 -0400 Subject: [NCSG-PC] [NCSG-SubPro] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> <34eec13d-0d2f-1172-ecbb-7159174e82ec@KathyKleiman.com> Message-ID: <84ab7236-8415-1368-242d-331e37eb59b6@mail.utoronto.ca> I think we should. Stephanie On 2022-04-22 5:16 p.m., Tomslin Samme-Nlar wrote: > Hi all, > > I think the council has now decided not to include the letter. So I > guess that leaves us to send it to the board ourselves? > > Tomslin > > > On Sat, 23 Apr 2022 at 02:49, Kathy Kleiman > wrote: > > Hi Manju, > > This is disappointing, but not surprising. Tx to you and our other > Councilors for the trying to hold a fair and balanced line here. / > / > > /Can I ask whether the Council will include our entire NCSG letter > of objection to their response - or do they want to select parts > of it? / > > If Council is willing to including our NCSG objection - whatever > terms /we//would like to include in the Council letter /- with a > clear and prominent reference to our NCSG letter of objection as > an appendix- then would it make it easier for the Board to see our > concerns??? One place, one document to read (?) > > Of course, if the Council wants to edit our letter, then sending > it separately makes sense.? Also perhaps there are advantages to > sending it separately that I may not be seeing. > > But the overall issue - that sending a few well-known, > very-opinionated, and frankly extreme (on this issue) Councilors > to the GAC (not including Manju, of course!) without guidance from > the GNSO Community is a distortion and misuse of the policy > development process. > > Best, Kathy > > On 4/21/2022 10:30 PM, ??? Manju Chen wrote: >> Hi all, >> >> Thought it's worth it to report back to you that our objection to >> the dialogue was acknowledged but brushed aside by the Council >> chair. >> I would be optimistic and say that we still have many chances to >> voice our opinions during the latter process, the?first step >> being broadening the dialogue to include more stakeholders within >> the GNSO, not limited to Councilors. >> >> Attached is the Council's draft response to the Board. There are >> discussions going on about whether the NCSG's letter of objection >> should be included in the response. >> >> My personal opinion is opt-out of being included in the Council's >> response and send our letter to the?Board ourselves. But I'd like >> to know what you think. >> >> Council plans to send out the response by the Board Workshop next >> week so we'll have to respond before April 27th 1200 UTC (Wednesday). >> >> Any suggestions are welcome! >> >> >> Best, >> Manju >> >> >> On Thu, Apr 14, 2022 at 7:38 AM Rafik Dammak >> wrote: >> >> Hi, >> >> >> I think the argument that will be used to respond to the idea >> of public comment is : councillors are representing their >> SG/C and are supposed to bring their input. >> >> Moreover in more practical matter, we are raising issues >> about discussing this issue with GAC but public comment means >> another group like ALAC would be involved.? Any wider >> discussion should be then done within PDP and not through >> ad-hoc approach. I can see there might be some possible >> alignment with ALAC in the topic (just an assumption) but I >> would object to open the door just for tactical gain. >> >> If we fail to stop the process, the next step would be to >> discuss the rules of engagement and scope for any discussion. >> >> Best. >> >> Rafik >> >> On Thu, Apr 14, 2022, 00:59 Kathy Kleiman via NCSG-SubPro >> wrote: >> >> Hi Manju, >> >> Great letter and great edits by Bruna.? I edited a few >> small things and then pulled out and expanded our "ask" - >> that we would like the GNSO Council to hold a comment >> period to provide input and guidance to this small group >> of individuals appointed to talk to the GAC (should our >> excellent and well-founded objections to the process be >> overruled).? This will provide a way for the GNSO Council >> to know the issues/concerns/hopes o the GNSO Community on >> this matter - and to provide clear input? and guidance to >> the the small Committee for the negotiations that may lie >> ahead. >> >> Here's the paragraph - building on opening sentences of >> Manju and edits of Bruna: >> >> We strongly support as the first step that the GNSO >> Council seek public comment from the community on how to >> proceed with Closed Generics, as opposed to having a >> ?closed dialogue? with the GAC where the scope and >> interlocutors of such dialogue is dictated by the ICANN >> Board.? This input will provide the Council with issues >> and concerns of the GNSO Community.? The Council, in >> turn, can provide guidance to the members of the Council >> who will be leading this discussion - should it occur >> despite our deep concerns for Multistakeholder process >> and precedent. How else will this small team - some with >> very, very long-held personal views on the subject - be >> bound to a discussion on behalf of the entire GNSO >> Community? >> >> I recommend putting the paragraph in bold for those who >> tend to scan their email. >> >> Best, Kathy >> >> On 4/11/2022 11:04 PM, ??? Manju Chen wrote: >> >>> Hi all, >>> >>> As discussed per yesterday's policy call, I've drafted >>> our formal response to be sent to the Council (and the >>> Board?) >>> >>> You can find the statement here: >>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>> >>> Feedbacks and suggestions are welcome and will be highly >>> appreciated! >>> >>> >>> Best, >>> Manju >>> >>> On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen >>> wrote: >>> >>> Hi Tomslin and all, >>> >>> Kurt and others obviously wanted it to be discussed >>> in the Council meeting this week. >>> Steve has suggested if that was the intent we could >>> propose a late motion. I think?NCSG is not in a >>> hurry about this, so I'll let others handle it if >>> they want to propose the motion. >>> >>> I can share more details and answer questions today >>> later during our policy call. >>> >>> Best, >>> Manju >>> >>> >>> >>> On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar >>> wrote: >>> >>> Hi Manju, >>> Thank you so much for the update. Nice strategy >>> there with the small team representation. Do you >>> know when that deferral will be brought to the >>> council's attention? Or maybe I missed it in my >>> hundreds of emails. >>> >>> Thanks again. >>> Tomslin >>> >>> >>> On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen >>> wrote: >>> >>> Hi team, >>> >>> Borrowing this thread to report back to you >>> about what happened in the small team. >>> >>> So as you might have guessed, I was the only >>> one saying no to the 'facilitated dialogue'. >>> Jeff, Paul, and Kurt were eager to dive into >>> the discussion of how we engage with GAC in >>> this 'facilitated dialogue' but thankfully >>> they still respected our objection. My first >>> point of objection is that the small team is >>> really not representative enough to make the >>> decision of whether the Council should meet >>> with the GAC. For now, we agreed to refer >>> this back to the Council and make the >>> decision at the Council level. >>> >>> I'm afraid though NCSG would be the only one >>> saying no when we're at the Council level. >>> Also when this pops up, we really have to >>> have our statement ready?explaining why >>> we're saying no. I've put notes in the >>> document Tomslin created and Kathy has been >>> extremely helpful by providing reference >>> material and edits: >>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>> >>> >>> We will still need to phrase them into a >>> formal statement, but I think it'd be an >>> easy task now we have all the contents. >>> >>> Best, >>> Manju >>> >>> On Thu, Mar 31, 2022 at 9:08 AM Tomslin >>> Samme-Nlar wrote: >>> >>> Hi team, >>> >>> I just wanted to call your attention to >>> this response we promised to put >>> together on the board proposed dialogue >>> between GAC and Council on closed >>> generics. The Council small team is >>> about to be activated to start >>> deliberations and I believe @??? Manju >>> Chen ?who is >>> representing us there hopes to rely on >>> the response we pen down to guide her >>> contribution to that team. >>> >>> In this?regard, can I request that we >>> find some time to please put our ideas >>> down on the Google >>> formhttps://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>> >>> Looking forward to your help with this. >>> In the meantime, i'll review my meeting >>> notes and put down some feedback we got >>> during our policy call on the document. >>> >>> Warmly, >>> Tomslin >>> >>> On Wed, 16 Mar 2022, 22:25 Tomslin >>> Samme-Nlar, wrote: >>> >>> Hi all, >>> >>> As a follow-up to my previous email >>> regarding the board's proposed >>> facilitated dialogue between GAC and >>> GNSO council, I have created this >>> Google doc [ >>> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >>> ] to capture our response to this >>> proposal in the form of a letter to >>> the council small team on Closed >>> Generics. >>> >>> Inputs to the document are welcomed >>> and for your convenience, attached >>> again is the letter from the board >>> and the accompanying framing paper. >>> >>> Regards, >>> Tomslin >>> >>> >>> On Tue, 15 Mar 2022 at 08:12, >>> Tomslin Samme-Nlar >>> wrote: >>> >>> Dear everyone, >>> >>> Here is the framing paper on the >>> board's proposed dialogue >>> between GNSO Council and the GAC >>> on Closed Generics that was >>> promised. >>> >>> Comments are welcomed. I will >>> also be sending a separate email >>> with a link to the Google doc >>> where we intend to draft a >>> letter as a response to this. >>> >>> Regards, >>> Tomslin >>> >>> >>> ---------- Forwarded message >>> --------- >>> From: *Wendy Profit via >>> Gnso-chairs* >>> Date: Fri, 11 Mar 2022 at 04:33 >>> Subject: [gnso-chairs] >>> [CORRESPONDENCE] Maarten >>> Botterman to Manal Ismail and >>> Philippe Fouquart - GAC-GNSO >>> Consultation on Closed Generics >>> To: manal.ismail at board.icann.org >>> , >>> Manal Ismail , >>> philippe.fouquart at orange.com >>> , >>> gnso-chairs at icann.org >>> >>> Cc: Secretary >>> , >>> Correspondence >>> , >>> Board Ops Team >>> , >>> gnso-secs at icann.org >>> , GACSTAFF >>> , Maarten >>> Botterman >>> >>> >>> >>> Dear Manal and Philippe, >>> >>> Pursuant to the letter sent >>> recently (6 March 2022, attached >>> for reference), we are now >>> forwarding the associated >>> framework paper entitled >>> ?Board-Facilitated Process for a >>> GAC - GNSO Council Dialogue on >>> Closed Generics?, also attached. >>> >>> ** >>> >>> Thank you and best regards, >>> >>> Wendy Profit >>> >>> ICANN >>> >>> Board Operations Senior Manager >>> >>> 12025 Waterfront Drive, Suite 300 >>> >>> Los Angeles, CA 90094 >>> >>> *From: *Wendy Profit >>> >>> *Date: *Sunday, March 6, 2022 at >>> 3:58 PM >>> *To: >>> *"manal.ismail at board.icann.org" >>> , >>> "manal at tra.gov.eg" >>> , >>> "philippe.fouquart at orange.com" >>> >>> *Cc: *Maarten Botterman >>> , >>> "gnso-chairs at icann.org" >>> , >>> GACSTAFF , >>> "gnso-secs at icann.org" >>> , ICANN >>> Board Ops >>> , >>> Correspondence >>> , >>> Secretary >>> *Subject: *[CORRESPONDENCE] >>> Maarten Botterman to Manal >>> Ismail and Philippe Fouquart - >>> GAC-GNSO Consultation on Closed >>> Generics >>> >>> Dear Manal and Philippe, >>> >>> Please find the attached letter >>> from ICANN Chair Maarten >>> Botterman regarding a proposed >>> formal consultation between the >>> GAC and GNSO Council on how to >>> handle the subject of closed >>> generics in gTLD applications. >>> >>> Thank you and best regards, >>> >>> Wendy Profit >>> >>> ICANN >>> >>> Board Operations Senior Manager >>> >>> 12025 Waterfront Drive, Suite 300 >>> >>> Los Angeles, CA 90094 >>> >>> _______________________________________________ >>> Gnso-chairs mailing list >>> Gnso-chairs at icann.org >>> https://mm.icann.org/mailman/listinfo/gnso-chairs >>> _______________________________________________ >>> 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. >>> >> -- >> NCSG-SubPro mailing list >> NCSG-SubPro at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-subpro >> > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From jumaropi at yahoo.com Sat Apr 23 03:10:24 2022 From: jumaropi at yahoo.com (Juan Manuel Rojas) Date: Sat, 23 Apr 2022 00:10:24 +0000 (UTC) Subject: [NCSG-PC] [NCSG-SubPro] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: <84ab7236-8415-1368-242d-331e37eb59b6@mail.utoronto.ca> References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> <34eec13d-0d2f-1172-ecbb-7159174e82ec@KathyKleiman.com> <84ab7236-8415-1368-242d-331e37eb59b6@mail.utoronto.ca> Message-ID: <580983134.276764.1650672624177@mail.yahoo.com> I agree, if it will not be attached we should send it directly. JUAN MANUEL ROJAS P. Director - MINKA DIGITAL ColombiaGNSO Councilor - ICANNCivil Soc. Rep - CODECTI? (Comit? Departamental de Ciencia Tecnolog?a e Innovaci?n) Master IT candidate, Universidad de los AndesRegistered Linux User No.533108. Cel. +57 301 743 56 00 Instagram/Twitter:?@JmanuRojas ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? El viernes, 22 de abril de 2022, 04:21:17 p.?m. GMT-5, Stephanie E Perrin escribi?: I think we should. Stephanie On 2022-04-22 5:16 p.m., Tomslin Samme-Nlar wrote: Hi all, I think the council has now decided not to include the letter. So I guess that leaves us to send it to the board ourselves? Tomslin On Sat, 23 Apr 2022 at 02:49, Kathy Kleiman wrote: Hi Manju, This is disappointing, but not surprising. Tx to you and our other Councilors for the trying to hold a fair and balanced line here. Can I ask whether the Council will include our entire NCSG letter of objection to their response - or do they want to select parts of it? If Council is willing to including our NCSG objection - whatever terms we would like to include in the Council letter - with a clear and prominent reference to our NCSG letter of objection as an appendix-? then would it make it easier for the Board to see our concerns??? One place, one document to read (?) Of course, if the Council wants to edit our letter, then sending it separately makes sense.? Also perhaps there are advantages to sending it separately that I may not be seeing. But the overall issue - that sending a few well-known, very-opinionated, and frankly extreme (on this issue) Councilors to the GAC (not including Manju, of course!) without guidance from the GNSO Community is a distortion and misuse of the policy development process. Best, Kathy On 4/21/2022 10:30 PM, ??? Manju Chen wrote: Hi all,? Thought it's worth it to report back to you that our objection to the dialogue was acknowledged but brushed aside by the Council chair.? I would be optimistic and say that we still have many chances to voice our opinions during the latter process, the?first step being broadening the dialogue to include more stakeholders within the GNSO, not limited to Councilors.? Attached is the Council's draft response to the Board. There are discussions going on about whether the NCSG's letter of objection should be included in the response.? My personal opinion is opt-out of being included in the Council's response and send our letter to the?Board ourselves. But I'd like to know what you think. Council plans to send out the response by the Board Workshop next week so we'll have to respond before April 27th 1200 UTC (Wednesday). Any suggestions are welcome! Best, Manju On Thu, Apr 14, 2022 at 7:38 AM Rafik Dammak wrote: Hi, I think the argument that will be used to respond to the idea of public comment is : councillors are representing their SG/C and are supposed to bring their input.? Moreover in more practical matter, we are raising issues about discussing this issue with GAC but public comment means another group like ALAC would be involved.? Any wider discussion should be then done within PDP and not through ad-hoc approach. I can see there might be some possible alignment with ALAC in the topic (just an assumption) but I would object to open the door just for tactical gain. If we fail to stop the process, the next step would be to discuss the rules of engagement and scope for any discussion. Best. Rafik? On Thu, Apr 14, 2022, 00:59 Kathy Kleiman via NCSG-SubPro wrote: Hi Manju, Great letter and great edits by Bruna.? I edited a few small things and then pulled out and expanded our "ask" - that we would like the GNSO Council to hold a comment period to provide input and guidance to this small group of individuals appointed to talk to the GAC (should our excellent and well-founded objections to the process be overruled).? This will provide a way for the GNSO Council to know the issues/concerns/hopes o the GNSO Community on this matter - and to provide clear input? and guidance to the the small Committee for the negotiations that may lie ahead.? Here's the paragraph - building on opening sentences of Manju and edits of Bruna: We strongly support as the first step that the GNSO Council seek public comment from the community on how to proceed with Closed Generics, as opposed to having a ?closed dialogue? with the GAC where the scope and interlocutors of such dialogue is dictated by the ICANN Board.? This input will provide the Council with issues and concerns of the GNSO Community.? The Council, in turn, can provide guidance to the members of the Council who will be leading this discussion - should it occur despite our deep concerns for Multistakeholder process and precedent. How else will this small team - some with very, very long-held personal views on the subject - be bound to a discussion on behalf of the entire GNSO Community? I recommend putting the paragraph in bold for those who tend to scan their email. Best, Kathy On 4/11/2022 11:04 PM, ??? Manju Chen wrote: Hi all, As discussed per yesterday's policy call, I've drafted our formal response to be sent to the Council (and the Board?) You can find the statement here:?https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing Feedbacks and suggestions are welcome and will be highly appreciated! Best, Manju On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen wrote: Hi Tomslin and all, Kurt and others obviously wanted it to be discussed in the Council meeting this week. Steve has suggested if that was the intent we could propose a late motion. I think?NCSG is not in a hurry about this, so I'll let others handle it if they want to propose the motion.? I can share more details and answer questions today later during our policy call. Best, Manju On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar wrote: Hi Manju, Thank you so much for the update. Nice strategy there with the small team representation. Do you know when that deferral will be brought to the council's attention? Or maybe I missed it in my hundreds of emails. Thanks again. Tomslin On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: Hi team, Borrowing this thread to report back to you about what happened in the small team.? So as you might have guessed, I was the only one saying no to the 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the discussion of how we engage with GAC in this 'facilitated dialogue' but thankfully they still respected our objection. My first point of objection is that the small team is really not representative enough to make the decision of whether the Council should meet with the GAC. For now, we agreed to refer this back to the Council and make the decision at the Council level.? I'm afraid though NCSG would be the only one saying no when we're at the Council level. Also when this pops up, we really have to have our statement ready?explaining why we're saying no. I've put notes in the document Tomslin created and Kathy has been extremely helpful by providing reference material and edits:?https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing? We will still need to phrase them into a formal statement, but I think it'd be an easy task now we have all the contents.? Best, Manju On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar wrote: Hi team, I just wanted to call your attention to this response we promised to put together on the board proposed dialogue between GAC and Council on closed generics. The Council small team is about to be activated to start deliberations and I believe @??? Manju Chen?who is representing us there hopes to rely on the response we pen down to guide her contribution to that team.? In this?regard, can I request that we find some time to please put our ideas down on the Google formhttps://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing Looking forward to your help with this. In the meantime, i'll review my meeting notes and put down some feedback we got during our policy call on the document.? Warmly, Tomslin On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, wrote: Hi all, As a follow-up to my previous email regarding the board's proposed facilitated dialogue between GAC and GNSO council, I have created this Google doc [ https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing ] to capture our response to this proposal in the form of a letter to the council small team on Closed Generics. Inputs to the document are welcomed and for your convenience, attached again is the letter from the board and the accompanying framing paper. Regards, Tomslin On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar wrote: Dear everyone, Here is the framing paper on the board's proposed dialogue between GNSO Council and the GAC on Closed Generics that was promised. Comments are welcomed. I will also be sending a separate email with a link to the Google doc where we intend to draft a letter as a response to this. Regards, Tomslin ---------- Forwarded message --------- From: Wendy Profit via Gnso-chairs Date: Fri, 11 Mar 2022 at 04:33 Subject: [gnso-chairs][CORRESPONDENCE] Maarten Botterman to Manal Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics To: manal.ismail at board.icann.org , Manal Ismail , philippe.fouquart at orange.com , gnso-chairs at icann.org Cc: Secretary , Correspondence , Board Ops Team , gnso-secs at icann.org , GACSTAFF , Maarten Botterman Dear Manal and Philippe, ? Pursuant to the letter sent recently (6 March 2022, attached for reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated Process for a GAC - GNSO Council Dialogue on Closed Generics?, also attached. ? Thank you and best regards, ? Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 ? ? ? ? From: Wendy Profit Date: Sunday, March 6, 2022 at 3:58 PM To: "manal.ismail at board.icann.org" , "manal at tra.gov.eg" , "philippe.fouquart at orange.com" Cc: Maarten Botterman , "gnso-chairs at icann.org" , GACSTAFF , "gnso-secs at icann.org" , ICANN Board Ops , Correspondence , Secretary Subject: [CORRESPONDENCE] Maarten Botterman to Manal Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics ? Dear Manal and Philippe, ? Please find the attached letter from ICANN Chair Maarten Botterman regarding a proposed formal consultation between the GAC and GNSO Council on how to handle the subject of closed generics in gTLD applications. ? Thank you and best regards, ? Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 ? ? _______________________________________________ Gnso-chairs mailing list Gnso-chairs at icann.org https://mm.icann.org/mailman/listinfo/gnso-chairs _______________________________________________ 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. -- NCSG-SubPro mailing list NCSG-SubPro at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-subpro _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc _______________________________________________ NCSG-PC mailing list NCSG-PC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Sat Apr 23 04:46:07 2022 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Sat, 23 Apr 2022 03:46:07 +0200 Subject: [NCSG-PC] [NCSG-SubPro] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: <580983134.276764.1650672624177@mail.yahoo.com> References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> <34eec13d-0d2f-1172-ecbb-7159174e82ec@KathyKleiman.com> <84ab7236-8415-1368-242d-331e37eb59b6@mail.utoronto.ca> <580983134.276764.1650672624177@mail.yahoo.com> Message-ID: So, as much as I think it?s rather unfortunate that the GNSO Council is clearly opting to hide our opposition, I guess we were all somehow aware that this should happen. And that?s exactly why I guess I was suggesting that we sent this letter to the board, together with the Council give that there would be at least a more institutionalised answer. But If we agree on sending it to the board I?d be happy to modify the letter tomorrow and add the information about us sending that to the GNSO previously. Best, B On Sat 23. Apr 2022 at 02:10, Juan Manuel Rojas via NCSG-PC < ncsg-pc at lists.ncsg.is> wrote: > I agree, if it will not be attached we should send it directly. > > > *JUAN MANUEL ROJAS P.* > Director - MINKA DIGITAL Colombia > GNSO Councilor - ICANN > Civil Soc. Rep - CODECTI (Comit? Departamental de Ciencia Tecnolog?a e > Innovaci?n) > Master IT candidate, Universidad de los Andes > Registered Linux User No.*533108.* > > > > *Cel. +57 301 743 56 00Instagram/Twitter: @JmanuRojas > * > > > > > > > > > El viernes, 22 de abril de 2022, 04:21:17 p. m. GMT-5, Stephanie E Perrin < > stephanie.perrin at mail.utoronto.ca> escribi?: > > > I think we should. > > Stephanie > On 2022-04-22 5:16 p.m., Tomslin Samme-Nlar wrote: > > Hi all, > > I think the council has now decided not to include the letter. So I guess > that leaves us to send it to the board ourselves? > > Tomslin > > > On Sat, 23 Apr 2022 at 02:49, Kathy Kleiman > wrote: > > Hi Manju, > > This is disappointing, but not surprising. Tx to you and our other > Councilors for the trying to hold a fair and balanced line here. > > *Can I ask whether the Council will include our entire NCSG letter of > objection to their response - or do they want to select parts of it? * > > If Council is willing to including our NCSG objection - whatever terms > *we** would like to include in the Council letter *- with a clear and > prominent reference to our NCSG letter of objection as an appendix- then > would it make it easier for the Board to see our concerns? One place, one > document to read (?) > > Of course, if the Council wants to edit our letter, then sending it > separately makes sense. Also perhaps there are advantages to sending it > separately that I may not be seeing. > > But the overall issue - that sending a few well-known, very-opinionated, > and frankly extreme (on this issue) Councilors to the GAC (not including > Manju, of course!) without guidance from the GNSO Community is a distortion > and misuse of the policy development process. > > Best, Kathy > > On 4/21/2022 10:30 PM, ??? Manju Chen wrote: > > Hi all, > > Thought it's worth it to report back to you that our objection to the > dialogue was acknowledged but brushed aside by the Council chair. > I would be optimistic and say that we still have many chances to voice our > opinions during the latter process, the first step being broadening the > dialogue to include more stakeholders within the GNSO, not limited to > Councilors. > > Attached is the Council's draft response to the Board. There are > discussions going on about whether the NCSG's letter of objection should be > included in the response. > > My personal opinion is opt-out of being included in the Council's response > and send our letter to the Board ourselves. But I'd like to know what you > think. > > Council plans to send out the response by the Board Workshop next week so > we'll have to respond before April 27th 1200 UTC (Wednesday). > > Any suggestions are welcome! > > > Best, > Manju > > > On Thu, Apr 14, 2022 at 7:38 AM Rafik Dammak > wrote: > > Hi, > > > I think the argument that will be used to respond to the idea of public > comment is : councillors are representing their SG/C and are supposed to > bring their input. > > Moreover in more practical matter, we are raising issues about discussing > this issue with GAC but public comment means another group like ALAC would > be involved. Any wider discussion should be then done within PDP and not > through ad-hoc approach. I can see there might be some possible alignment > with ALAC in the topic (just an assumption) but I would object to open the > door just for tactical gain. > > If we fail to stop the process, the next step would be to discuss the > rules of engagement and scope for any discussion. > > Best. > > Rafik > > On Thu, Apr 14, 2022, 00:59 Kathy Kleiman via NCSG-SubPro < > ncsg-subpro at lists.ncsg.is> wrote: > > Hi Manju, > > Great letter and great edits by Bruna. I edited a few small things and > then pulled out and expanded our "ask" - that we would like the GNSO > Council to hold a comment period to provide input and guidance to this > small group of individuals appointed to talk to the GAC (should our > excellent and well-founded objections to the process be overruled). This > will provide a way for the GNSO Council to know the issues/concerns/hopes o > the GNSO Community on this matter - and to provide clear input and > guidance to the the small Committee for the negotiations that may lie > ahead. > > Here's the paragraph - building on opening sentences of Manju and edits of > Bruna: > > We strongly support as the first step that the GNSO Council seek public > comment from the community on how to proceed with Closed Generics, as > opposed to having a ?closed dialogue? with the GAC where the scope and > interlocutors of such dialogue is dictated by the ICANN Board. This input > will provide the Council with issues and concerns of the GNSO Community. > The Council, in turn, can provide guidance to the members of the Council > who will be leading this discussion - should it occur despite our deep > concerns for Multistakeholder process and precedent. How else will this > small team - some with very, very long-held personal views on the subject - > be bound to a discussion on behalf of the entire GNSO Community? > > I recommend putting the paragraph in bold for those who tend to scan their > email. > > Best, Kathy > > On 4/11/2022 11:04 PM, ??? Manju Chen wrote: > > Hi all, > > As discussed per yesterday's policy call, I've drafted our formal response > to be sent to the Council (and the Board?) > > You can find the statement here: > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > Feedbacks and suggestions are welcome and will be highly appreciated! > > > Best, > Manju > > On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen wrote: > > Hi Tomslin and all, > > Kurt and others obviously wanted it to be discussed in the Council meeting > this week. > Steve has suggested if that was the intent we could propose a late motion. > I think NCSG is not in a hurry about this, so I'll let others handle it if > they want to propose the motion. > > I can share more details and answer questions today later during our > policy call. > > Best, > Manju > > > > On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar > wrote: > > Hi Manju, > Thank you so much for the update. Nice strategy there with the small team > representation. Do you know when that deferral will be brought to the > council's attention? Or maybe I missed it in my hundreds of emails. > > Thanks again. > Tomslin > > > On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: > > Hi team, > > Borrowing this thread to report back to you about what happened in the > small team. > > So as you might have guessed, I was the only one saying no to the > 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the > discussion of how we engage with GAC in this 'facilitated dialogue' but > thankfully they still respected our objection. My first point of objection > is that the small team is really not representative enough to make the > decision of whether the Council should meet with the GAC. For now, we > agreed to refer this back to the Council and make the decision at the > Council level. > > I'm afraid though NCSG would be the only one saying no when we're at the > Council level. Also when this pops up, we really have to have our statement > ready explaining why we're saying no. I've put notes in the document > Tomslin created and Kathy has been extremely helpful by providing reference > material and edits: > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > > We will still need to phrase them into a formal statement, but I think > it'd be an easy task now we have all the contents. > > Best, > Manju > > On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar > wrote: > > Hi team, > > I just wanted to call your attention to this response we promised to put > together on the board proposed dialogue between GAC and Council on closed > generics. The Council small team is about to be activated to start > deliberations and I believe @??? Manju Chen who is > representing us there hopes to rely on the response we pen down to guide > her contribution to that team. > > In this regard, can I request that we find some time to please put our > ideas down on the Google form > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > > Looking forward to your help with this. In the meantime, i'll review my > meeting notes and put down some feedback we got during our policy call on > the document. > > Warmly, > Tomslin > > On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, > wrote: > > Hi all, > > As a follow-up to my previous email regarding the board's proposed > facilitated dialogue between GAC and GNSO council, I have created this > Google doc [ > https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing > ] to capture our response to this proposal in the form of a letter to the > council small team on Closed Generics. > > Inputs to the document are welcomed and for your convenience, attached > again is the letter from the board and the accompanying framing paper. > > Regards, > Tomslin > > > On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar > wrote: > > Dear everyone, > > Here is the framing paper on the board's proposed dialogue between GNSO > Council and the GAC on Closed Generics that was promised. > > Comments are welcomed. I will also be sending a separate email with a link > to the Google doc where we intend to draft a letter as a response to this. > > Regards, > Tomslin > > > ---------- Forwarded message --------- > From: *Wendy Profit via Gnso-chairs* > Date: Fri, 11 Mar 2022 at 04:33 > Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal Ismail > and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics > To: manal.ismail at board.icann.org , Manal > Ismail , philippe.fouquart at orange.com < > philippe.fouquart at orange.com>, gnso-chairs at icann.org < > gnso-chairs at icann.org> > Cc: Secretary , Correspondence < > Correspondence at icann.org>, Board Ops Team , > gnso-secs at icann.org , GACSTAFF , > Maarten Botterman > > > Dear Manal and Philippe, > > > > Pursuant to the letter sent recently (6 March 2022, attached for > reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated > Process for a GAC - GNSO Council Dialogue on Closed Generics?, also > attached. > > > > Thank you and best regards, > > > > Wendy Profit > > ICANN > > Board Operations Senior Manager > > 12025 Waterfront Drive, Suite 300 > > > > > Los Angeles, CA 90094 > > > > > > > > > > > *From: *Wendy Profit > *Date: *Sunday, March 6, 2022 at 3:58 PM > *To: *"manal.ismail at board.icann.org" , " > manal at tra.gov.eg" , "philippe.fouquart at orange.com" < > philippe.fouquart at orange.com> > *Cc: *Maarten Botterman , " > gnso-chairs at icann.org" , GACSTAFF < > gac-staff at icann.org>, "gnso-secs at icann.org" , ICANN > Board Ops , Correspondence < > Correspondence at icann.org>, Secretary > *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and > Philippe Fouquart - GAC-GNSO Consultation on Closed Generics > > > > Dear Manal and Philippe, > > > > Please find the attached letter from ICANN Chair Maarten Botterman > regarding a proposed formal consultation between the GAC and GNSO Council > on how to handle the subject of closed generics in gTLD applications. > > > > Thank you and best regards, > > > > Wendy Profit > > ICANN > > Board Operations Senior Manager > > 12025 Waterfront Drive, Suite 300 > > > > > Los Angeles, CA 90094 > > > > > > _______________________________________________ > Gnso-chairs mailing list > Gnso-chairs at icann.org > https://mm.icann.org/mailman/listinfo/gnso-chairs > _______________________________________________ > 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. > > -- > NCSG-SubPro mailing list > NCSG-SubPro at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-subpro > > > _______________________________________________ > NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin f?r Sozialforschung (WZB) Member | Coaliz?o Direitos na Rede Chair | Non-Commercial Stakeholder Group at ICANN Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos *bruna.martinsdossantos at wzb.eu * and bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From wisdom.dk at gmail.com Sat Apr 23 12:47:48 2022 From: wisdom.dk at gmail.com (Wisdom Donkor) Date: Sat, 23 Apr 2022 09:47:48 +0000 Subject: [NCSG-PC] [NCSG-SubPro] NCSG Response to the proposed GAC-GNSO Consultation on Closed Generics In-Reply-To: References: <53C7C97B-A842-4F43-A04B-A17128E4CBEB@icann.org> <83618385-bdbb-5b9c-40e7-cc34d17f0797@KathyKleiman.com> <34eec13d-0d2f-1172-ecbb-7159174e82ec@KathyKleiman.com> <84ab7236-8415-1368-242d-331e37eb59b6@mail.utoronto.ca> <580983134.276764.1650672624177@mail.yahoo.com> Message-ID: Since the council has failed to recognise include our position letter, the best option left is to send it directly to the board. Very disappointing. On Sat, 23 Apr 2022, 1:46 am Bruna Martins dos Santos, < bruna.mrtns at gmail.com> wrote: > So, as much as I think it?s rather unfortunate that the GNSO Council is > clearly opting to hide our opposition, I guess we were all somehow aware > that this should happen. And that?s exactly why I guess I was suggesting > that we sent this letter to the board, together with the Council give that > there would be at least a more institutionalised answer. > > But If we agree on sending it to the board I?d be happy to modify the > letter tomorrow and add the information about us sending that to the GNSO > previously. > > Best, > B > > On Sat 23. Apr 2022 at 02:10, Juan Manuel Rojas via NCSG-PC < > ncsg-pc at lists.ncsg.is> wrote: > >> I agree, if it will not be attached we should send it directly. >> >> >> *JUAN MANUEL ROJAS P.* >> Director - MINKA DIGITAL Colombia >> GNSO Councilor - ICANN >> Civil Soc. Rep - CODECTI (Comit? Departamental de Ciencia Tecnolog?a e >> Innovaci?n) >> Master IT candidate, Universidad de los Andes >> Registered Linux User No.*533108.* >> >> >> >> *Cel. +57 301 743 56 00Instagram/Twitter: @JmanuRojas >> * >> >> >> >> >> >> >> >> >> El viernes, 22 de abril de 2022, 04:21:17 p. m. GMT-5, Stephanie E Perrin >> escribi?: >> >> >> I think we should. >> >> Stephanie >> On 2022-04-22 5:16 p.m., Tomslin Samme-Nlar wrote: >> >> Hi all, >> >> I think the council has now decided not to include the letter. So I guess >> that leaves us to send it to the board ourselves? >> >> Tomslin >> >> >> On Sat, 23 Apr 2022 at 02:49, Kathy Kleiman >> wrote: >> >> Hi Manju, >> >> This is disappointing, but not surprising. Tx to you and our other >> Councilors for the trying to hold a fair and balanced line here. >> >> *Can I ask whether the Council will include our entire NCSG letter of >> objection to their response - or do they want to select parts of it? * >> >> If Council is willing to including our NCSG objection - whatever terms >> *we** would like to include in the Council letter *- with a clear and >> prominent reference to our NCSG letter of objection as an appendix- then >> would it make it easier for the Board to see our concerns? One place, one >> document to read (?) >> >> Of course, if the Council wants to edit our letter, then sending it >> separately makes sense. Also perhaps there are advantages to sending it >> separately that I may not be seeing. >> >> But the overall issue - that sending a few well-known, very-opinionated, >> and frankly extreme (on this issue) Councilors to the GAC (not including >> Manju, of course!) without guidance from the GNSO Community is a distortion >> and misuse of the policy development process. >> >> Best, Kathy >> >> On 4/21/2022 10:30 PM, ??? Manju Chen wrote: >> >> Hi all, >> >> Thought it's worth it to report back to you that our objection to the >> dialogue was acknowledged but brushed aside by the Council chair. >> I would be optimistic and say that we still have many chances to voice >> our opinions during the latter process, the first step being broadening the >> dialogue to include more stakeholders within the GNSO, not limited to >> Councilors. >> >> Attached is the Council's draft response to the Board. There are >> discussions going on about whether the NCSG's letter of objection should be >> included in the response. >> >> My personal opinion is opt-out of being included in the Council's >> response and send our letter to the Board ourselves. But I'd like to know >> what you think. >> >> Council plans to send out the response by the Board Workshop next week so >> we'll have to respond before April 27th 1200 UTC (Wednesday). >> >> Any suggestions are welcome! >> >> >> Best, >> Manju >> >> >> On Thu, Apr 14, 2022 at 7:38 AM Rafik Dammak >> wrote: >> >> Hi, >> >> >> I think the argument that will be used to respond to the idea of public >> comment is : councillors are representing their SG/C and are supposed to >> bring their input. >> >> Moreover in more practical matter, we are raising issues about discussing >> this issue with GAC but public comment means another group like ALAC would >> be involved. Any wider discussion should be then done within PDP and not >> through ad-hoc approach. I can see there might be some possible alignment >> with ALAC in the topic (just an assumption) but I would object to open the >> door just for tactical gain. >> >> If we fail to stop the process, the next step would be to discuss the >> rules of engagement and scope for any discussion. >> >> Best. >> >> Rafik >> >> On Thu, Apr 14, 2022, 00:59 Kathy Kleiman via NCSG-SubPro < >> ncsg-subpro at lists.ncsg.is> wrote: >> >> Hi Manju, >> >> Great letter and great edits by Bruna. I edited a few small things and >> then pulled out and expanded our "ask" - that we would like the GNSO >> Council to hold a comment period to provide input and guidance to this >> small group of individuals appointed to talk to the GAC (should our >> excellent and well-founded objections to the process be overruled). This >> will provide a way for the GNSO Council to know the issues/concerns/hopes o >> the GNSO Community on this matter - and to provide clear input and >> guidance to the the small Committee for the negotiations that may lie >> ahead. >> >> Here's the paragraph - building on opening sentences of Manju and edits >> of Bruna: >> >> We strongly support as the first step that the GNSO Council seek public >> comment from the community on how to proceed with Closed Generics, as >> opposed to having a ?closed dialogue? with the GAC where the scope and >> interlocutors of such dialogue is dictated by the ICANN Board. This input >> will provide the Council with issues and concerns of the GNSO Community. >> The Council, in turn, can provide guidance to the members of the Council >> who will be leading this discussion - should it occur despite our deep >> concerns for Multistakeholder process and precedent. How else will this >> small team - some with very, very long-held personal views on the subject - >> be bound to a discussion on behalf of the entire GNSO Community? >> >> I recommend putting the paragraph in bold for those who tend to scan >> their email. >> >> Best, Kathy >> >> On 4/11/2022 11:04 PM, ??? Manju Chen wrote: >> >> Hi all, >> >> As discussed per yesterday's policy call, I've drafted our formal >> response to be sent to the Council (and the Board?) >> >> You can find the statement here: >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> Feedbacks and suggestions are welcome and will be highly appreciated! >> >> >> Best, >> Manju >> >> On Mon, Apr 11, 2022 at 10:22 AM ??? Manju Chen wrote: >> >> Hi Tomslin and all, >> >> Kurt and others obviously wanted it to be discussed in the Council >> meeting this week. >> Steve has suggested if that was the intent we could propose a late >> motion. I think NCSG is not in a hurry about this, so I'll let others >> handle it if they want to propose the motion. >> >> I can share more details and answer questions today later during our >> policy call. >> >> Best, >> Manju >> >> >> >> On Sat, Apr 9, 2022 at 4:08 AM Tomslin Samme-Nlar >> wrote: >> >> Hi Manju, >> Thank you so much for the update. Nice strategy there with the small team >> representation. Do you know when that deferral will be brought to the >> council's attention? Or maybe I missed it in my hundreds of emails. >> >> Thanks again. >> Tomslin >> >> >> On Thu, 7 Apr 2022 at 08:18, ??? Manju Chen wrote: >> >> Hi team, >> >> Borrowing this thread to report back to you about what happened in the >> small team. >> >> So as you might have guessed, I was the only one saying no to the >> 'facilitated dialogue'. Jeff, Paul, and Kurt were eager to dive into the >> discussion of how we engage with GAC in this 'facilitated dialogue' but >> thankfully they still respected our objection. My first point of objection >> is that the small team is really not representative enough to make the >> decision of whether the Council should meet with the GAC. For now, we >> agreed to refer this back to the Council and make the decision at the >> Council level. >> >> I'm afraid though NCSG would be the only one saying no when we're at the >> Council level. Also when this pops up, we really have to have our statement >> ready explaining why we're saying no. I've put notes in the document >> Tomslin created and Kathy has been extremely helpful by providing reference >> material and edits: >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> >> We will still need to phrase them into a formal statement, but I think >> it'd be an easy task now we have all the contents. >> >> Best, >> Manju >> >> On Thu, Mar 31, 2022 at 9:08 AM Tomslin Samme-Nlar >> wrote: >> >> Hi team, >> >> I just wanted to call your attention to this response we promised to put >> together on the board proposed dialogue between GAC and Council on closed >> generics. The Council small team is about to be activated to start >> deliberations and I believe @??? Manju Chen who is >> representing us there hopes to rely on the response we pen down to guide >> her contribution to that team. >> >> In this regard, can I request that we find some time to please put our >> ideas down on the Google form >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> >> Looking forward to your help with this. In the meantime, i'll review my >> meeting notes and put down some feedback we got during our policy call on >> the document. >> >> Warmly, >> Tomslin >> >> On Wed, 16 Mar 2022, 22:25 Tomslin Samme-Nlar, >> wrote: >> >> Hi all, >> >> As a follow-up to my previous email regarding the board's proposed >> facilitated dialogue between GAC and GNSO council, I have created this >> Google doc [ >> https://docs.google.com/document/d/1buufalOjubifqZJoPLqF4wBaIUxHKLWor7NvILtnrKg/edit?usp=sharing >> ] to capture our response to this proposal in the form of a letter to the >> council small team on Closed Generics. >> >> Inputs to the document are welcomed and for your convenience, attached >> again is the letter from the board and the accompanying framing paper. >> >> Regards, >> Tomslin >> >> >> On Tue, 15 Mar 2022 at 08:12, Tomslin Samme-Nlar >> wrote: >> >> Dear everyone, >> >> Here is the framing paper on the board's proposed dialogue between GNSO >> Council and the GAC on Closed Generics that was promised. >> >> Comments are welcomed. I will also be sending a separate email with a >> link to the Google doc where we intend to draft a letter as a response to >> this. >> >> Regards, >> Tomslin >> >> >> ---------- Forwarded message --------- >> From: *Wendy Profit via Gnso-chairs* >> Date: Fri, 11 Mar 2022 at 04:33 >> Subject: [gnso-chairs] [CORRESPONDENCE] Maarten Botterman to Manal Ismail >> and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >> To: manal.ismail at board.icann.org , Manal >> Ismail , philippe.fouquart at orange.com < >> philippe.fouquart at orange.com>, gnso-chairs at icann.org < >> gnso-chairs at icann.org> >> Cc: Secretary , Correspondence < >> Correspondence at icann.org>, Board Ops Team , >> gnso-secs at icann.org , GACSTAFF , >> Maarten Botterman >> >> >> Dear Manal and Philippe, >> >> >> >> Pursuant to the letter sent recently (6 March 2022, attached for >> reference), we are now forwarding the associated framework paper entitled ?Board-Facilitated >> Process for a GAC - GNSO Council Dialogue on Closed Generics?, also >> attached. >> >> >> >> Thank you and best regards, >> >> >> >> Wendy Profit >> >> ICANN >> >> Board Operations Senior Manager >> >> 12025 Waterfront Drive, Suite 300 >> >> >> >> >> Los Angeles, CA 90094 >> >> >> >> >> >> >> >> >> >> >> *From: *Wendy Profit >> *Date: *Sunday, March 6, 2022 at 3:58 PM >> *To: *"manal.ismail at board.icann.org" , " >> manal at tra.gov.eg" , "philippe.fouquart at orange.com" < >> philippe.fouquart at orange.com> >> *Cc: *Maarten Botterman , " >> gnso-chairs at icann.org" , GACSTAFF < >> gac-staff at icann.org>, "gnso-secs at icann.org" , ICANN >> Board Ops , Correspondence < >> Correspondence at icann.org>, Secretary >> *Subject: *[CORRESPONDENCE] Maarten Botterman to Manal Ismail and >> Philippe Fouquart - GAC-GNSO Consultation on Closed Generics >> >> >> >> Dear Manal and Philippe, >> >> >> >> Please find the attached letter from ICANN Chair Maarten Botterman >> regarding a proposed formal consultation between the GAC and GNSO Council >> on how to handle the subject of closed generics in gTLD applications. >> >> >> >> Thank you and best regards, >> >> >> >> Wendy Profit >> >> ICANN >> >> Board Operations Senior Manager >> >> 12025 Waterfront Drive, Suite 300 >> >> >> >> >> Los Angeles, CA 90094 >> >> >> >> >> >> _______________________________________________ >> Gnso-chairs mailing list >> Gnso-chairs at icann.org >> https://mm.icann.org/mailman/listinfo/gnso-chairs >> _______________________________________________ >> 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. >> >> -- >> NCSG-SubPro mailing list >> NCSG-SubPro at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-subpro >> >> >> _______________________________________________ >> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > -- > > *Bruna Martins dos Santos * > > German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von > Humboldt Foundation > > Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin > f?r Sozialforschung (WZB) > > Member | Coaliz?o Direitos na Rede > Chair | Non-Commercial Stakeholder Group at ICANN > > Co-Coordinator | Internet Governance Caucus > > Twitter: @boomartins // Skype: > bruna.martinsantos > *bruna.martinsdossantos at wzb.eu * and > bruna.mrtns at gmail.com > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Sat Apr 30 09:58:52 2022 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 30 Apr 2022 16:58:52 +1000 Subject: [NCSG-PC] Internationalized Domain Names and string similarity reviews Message-ID: Dear NCSG, The Internationalized Domain Names (IDN) EPDP team is currently discussing charter questions on how string similarity should be performed on variant labels of future TLD labels. 3 options described as *levels* were proposed as you will see on the attached slide deck and the team is to choose one of them. I'll try to summarize the description of the 3 levels below and indicate my preferred level. *Notes for those not familiar with the topic:* *In IDNs, a TLD has a primary label (P) and variants (v), which are labels in different languages and/or scripts of the primary label.Consider P1 as the applied-for primary gTLD 1 and P1 could have variant labels, say three for the sake of this discussion:? P1v1: allocatable and requested for activation? P1v2: allocatable but not requested? P1v3: blocked* Now, the question is, during an application round, for string similarity reviews, should P with its variants P1v1, P1v2 & P1v3 be compared with - *Level 1*:* Existing & applied for Primary labels + ONLY Requested Allocatable Variants* - *Pros*: (a) Limited pool of labels for comparison; (b) Simplest, fastest & least expensive to conduct the review - *Cons*: An entity may potentially not be able to apply for its label variant (P1v2) in the future if another entity applies for a label or variant which causes it to be visually confusable to P1v2. - *Level 2: Existing & applied for Primary labels + ALL Allocatable Variants* - *Pros:* (a) Relatively manageable pool of labels for comparison, except for certain TLDs in Arabic; (b) Allows entities to ensure that all of their allocatable strings and all other possible future similar strings would be blocked. This creates predictability because all entities have their original string and allocatable variants. - *Cons*: (a) Certain TLDs in Arabic may have extremely large number of allocatable variants, therefore more expensive than Level 1; (b) 7 scripts in RZ-LGR-5 have allocatable variants - *Level 3: Existing & applied for Primary labels + ALL Variants (Blocked & Allocatable)* - *Pros*: Maximally conservative approach and may reduce the possibility of visual confusability among all valid labels in an application round. - *Cons*: (a) Slowest, most complicated & expensive to conduct the review; (b) 21 scripts in RZ-LGR-5 have variants; (c) Certain TLDs in Arabic, Cyrillic & Latin may have extremely large number of blocked variants; (d) May reject strings due to conflict with blocked variants that will never be delegated. I previously gave my personal preference to the working group as being Level 2. However, the more I read through available information and listen to debate on this issue, the more I lean towards Level 1. Therefore, I would love to hear what NCSG members think so that the Policy Committee can agree on an official NCSG preference. I understand this is a bit of a complex topic, but* if we don't get any responses by Thursday May 5, we'll assume no official NCSG preference*. Warmly, Tomslin @LinkedIn: https://www.linkedin.com/in/tomslin/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EPDP Team Meeting 30 Slides - E3 E1 E3a.pdf Type: application/pdf Size: 965231 bytes Desc: not available URL: