- Gnso-review-wg - lists.icann.org

Actions/Discussion Notes for GNSO Review WG Meeting on 29 March 2018
by Julie Hedlund March 29, 2018

March 29, 2018

Dear GNSO Review Working Group members, Please see below and attached the action items and discussion notes captured by staff from the meeting on 29 March 2018. These high-level notes are designed to help WG members navigate through the content of the call and are not meant to be a substitute for the recording or transcript, which are posted on the wiki at: https://community.icann.org/display/GRWG/2018. Please note that the next meeting will occur on 12 April at 1300 UTC. Best regards, Julie Julie Hedlund, Policy Director Action Items and Notes GNSO Review Working Group Meeting on Thursday, 29 March 2018 at 13:00 UTC Action Items: Implementation Charter for Recommendations 1, 2, & 3: Staff will research metrics related to the fellowship program and see if these might be referenced in the charter and included as an appendix. Staff will also look into the fellowship program consultation currently underway and include a reference in the charter text. Staff will research whether there are metrics associated with the CROP program, for example an evaluation of the pilot. Staff will ask support staff from SG/Cs if there are additional metrics on participation that can be referenced and add this information to the charter. Staff will draft the determination reference existing efforts to collect metrics, noting that resources are stretched, and recommending that the GNSO leverage any metrics that already exist or are being gathered. Staff will circulate by email in advance of the next meeting. Staff will investigate the best way for the WG to provide input on the fellowship program. Should the WG provide input directly into the fellowship program consultation? Implementation Charter for Recommendations 7 & 12: In addressing recommendation 12, staff will revise text to focus the content of the recommendation itself, which addresses real-time transcription. Information about other services should be provided as context. Staff will adjust text regarding demand-based approach to live translation on Working Group calls to provide greater flexibility – drawing on feedback from WG members. Staff will seek to circulate a revised version of this charter to the mailing list prior to the next call, incorporating feedback from members received on the call and over email. Notes: Review agenda/SOIs: No Updates. Status of Consensus Call for revised implementation charter for recommendation 22: The three-week consensus call will end today, March 29. No objections have been raised so far. If there are no objections raised, it will be agreed by consensus. Staff will provide an update on 30 March. Discussion of the revised implementation charter for recommendations 1, 2, & 3: Staff has completed revisions requested during the last call regarding GNSO Council comments on budget cuts for CROP. See page 3. On page 4, language on the use of dues for SG/C outreach has been made more neutral. No concerns were raised about these edits. There is not yet a Working Group determination for these recommendations. Part of the recommendation is to gather metrics. Some of the comments on the FY19 budget included calls for metrics to show the effectiveness of outreach programs. Are these useful recommendations or suggestions? The suggestions for metrics are helpful. For the fellowship program, there is an ongoing process to gather feedback using a survey. Is this done for other programs, as well, such as CROP? Perhaps the WG should reference these surveys or reviews as a method of data collection for the future. Staff will research metrics related to the fellowship program. Are there statistics on membership or activity levels at the SG/C level? ISPCP and NCSG/NCUC collect some information about participation and new members joining. It is possible for SG/Cs to look at, for example, increases in membership numbers after outreach events? Another perspective on metrics – a report/survey was previously done. It provided some demographic information about fellows, for example country, age, etc. It did not provide information that might help evaluate success. Concern about metrics – may cause additional administrative burdens. How do you balance the need for information and limited resources (volunteer time, staff time, etc)? Consider mentioning in the charter that there are currently strains on resources. Some of the questions about metrics on engagement are being addressed by GSE. Chris Mondini is working on a North America GSE plan to collect some information about this. Efforts should be coordinated. This data may be a little different than what is being sought in this recommendation, as it is not specific to GNSO working group participation. Staff will draft the determination to reference existing efforts to collect metrics, noting that resources are stretched, and recommending that the GNSO leverage any metrics that already exist or are being gathered. Staff will gather input on whether there are any additional comments on sections 4. and 5. Fellows come into the program with very different backgrounds. Some might be more in a position than others to participate actively with less extensive ramp up. This should be taken into account. Will this group provide input to the survey on the fellowship program and provide input on metrics and other recommendations? There are different elements to the feedback the WG can provide. One is to the ICANN Organization and the other is to the fellowship program itself. It is important not to have metrics for the sake of metrics. Data should be collected for a specific purpose to evaluate if programs are meeting their goals. Discussion of the implementation charter for recommendations 7 & 12: Staff looked into the option of translating documents as an alternative to transcription in multiple languages. Language was to point 3 on page 3. Information about all of ICANN’s translation services is included as an appendix to this charter. Staff added text on SG/C engagement related to recommendation 7: Language services offers translation of policy-development related documents, as well as SG/C comments. Text was added about audio transcription that can be provided after a call has taken place. It was noted that this is a relatively low-cost option. Analysis provided by Wolf-Ulrich has been added for illustration, with an additional note about potential additional costs that may need to be considered. Working Group Determination has been added at the bottom of page 5. It should be clear that we are mainly providing advice with respect to the content of the recommendation itself, which applies to real-time transcription, and that the other information provided about additional services is primarily for context. In the Working Group Determination, there is currently text indicating that interpretation should be demand-based. Should there be greater flexibility in terms of the approach the GNSO takes to interpretation? Discussion of the implementation charter for recommendations 20 and 21: Postponed to the next meeting. Next Meeting: 12 April 1300 UTC AOB: None.

1 0

Agenda and Materials for 29 March Meeting 13:00 UTC
by Julie Hedlund March 29, 2018

March 29, 2018

Dear GNSO Review Working Group members, Please see below the draft agenda for the meeting on Thursday, 29 March at 13:00 UTC. Please also see the attached materials and the action items below with updates from the previous meeting. Draft agenda: Review agenda/SOIs Status of Consensus Call for revised implementation charter for recommendation 22 Discussion of the revised implementation charter for recommendations 1, 2, & 3 Discussion of the implementation charter for recommendations 7 & 12 Discussion of the implementation charter for recommendations 20 and 21 Next Meeting: 12 April 1300 UTC AOB Action Items & Updates: GNSO Review Working Group Meeting on Thursday, 01 March 2018 at 13:00 UTC Implementation Charter for Recommendation 22: Action Item 1: Staff will update the organization of training materials on the GNSO website. Staff will update the WG Determination that take into account that there are already trainings that are accessible and include real-time interaction. The WG Determination will note that staff will update the website and will link to the updated GNSO webpage when it is ready. Staff will put the changes out for a 3-week Consensus Call. (DONE: Consensus Call ends on COB, 29 March – No objections thus far.) Implementation Charter for Recommendations 1, 2, & 3: Action Item 2: Staff will add information about Council comment on CROP to the implementation charter once posted to public forum. Staff will also add text based on additional feedback that may be received on SG/C outreach. Action Item 3: Staff will adjust the text of the "note" on page 4 to be more neutral regarding dues collected. Staff will also add text clarifying how dues are used within the BC with respect to voting. Action Item 4: Staff will add text to the charter elaborating on the link between GSE activities and recruitment for PDP WGs. (DONE: See attached revised charter.) Implementation Charter for Recommendations 7 & 12: Action Item 5: Update implementation charter title to "Language Translation and Transcription." Action Item 6: Staff will add text about the translation of written material, including benefits, uses, and costs. Action Item 7: Staff will add some possible scenarios outlining the costs if GNSO WGs began using translation on their calls. (DONE: See attached revised charter.) Update to the GNSO Council: Action Item 8: Remove the target end date of June 2018 from the status update to the GNSO Council. (DONE: Submitted to the GNSO Council on 02 March and presented at the GNSO Council meeting on 14 March.) Next Meeting: Action Item 9: Staff will send a note to the list asking whether the next meeting on 29 March should take place at 12:00 UTC or 13:00 UTC (due to US change to Daylight Saving Time on 11 March 2018). (DONE: Time kept at 13:00 UTC.) Best regards, Julie Julie Hedlund, Policy Director

2 2

REMINDER-CONSENSUS CALL: Recommendation 22 Implementation Charter
by Julie Hedlund March 22, 2018

March 22, 2018

Dear GNSO Review Working Group members, This is a reminder of the Consensus Call for the GNSO Review Implementation Charter for Recommendation 22, per the action items from the meeting on 01 March. The redlines in the Working Group Determination section of the document reflect the agreed-upon changes during the meeting. As noted in the attached charter, this is the recommendation for implementation: “That the GNSO Council develop a competency-based framework, which its members should use to identify development needs and opportunities.” Staff is circulating the revised version of the charter for a three-week Consensus Call to end on Thursday, 29 March 2018. If there are no objections the recommendation will be deemed to have been implemented by Full Consensus. Best regards, Julie Julie Hedlund, Policy Director

1 0

REMINDER re: Response Requested re: Timing of meeting on 29 March
by Julie Hedlund March 21, 2018

March 21, 2018

Dear GNSO Review Working Group members, This is a reminder. Please see the following action item from the last meeting: Action Item 9: Staff will send a note to the list asking whether the next meeting on 29 March should take place at 12:00 UTC or 13:00 UTC (due to US change to Daylight Saving Time on 11 March 2018). Note that upon the change to Daylight Saving Time (DT) in the US, the usual time of 13:00 UTC will change from 05:00 to 06:00 PDT/08:00 to 09:00 EDT. Please indicate whether you prefer that the time should stay at 13:00 UTC, or revert to 12:00 UTC (thus maintaining the time at 05:00 PDT/08:00 EDT). Thank you very much for your assistance. Kind regards, Julie Julie Hedlund, Policy Director

4 4

PLEASE READ-NEW SESSION INFORMATION ICANN61
by Nathalie Peregrine March 14, 2018

March 14, 2018

Dear all, Due to security difficulties, (see Goran’s blog here[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>) the Adobe Connect room facilities will no longer be available to ICANN61 participants. In order to minimize disruption, we have the following steps we encourage you to follow: 1. TO JOIN THE AUDIO * Audio streaming will be available for all open, public meetings. Links can be find on the ICANN61 schedule meeting pages: https://61.schedule.icann.org/[61.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_…> * The audio bridge is available for those who would like to ask questions or comment over the telephone. Dial in details for open GNSO sessions can be found here: https://community.icann.org/x/3wC8B[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> 1. TO ACCESS THE PRESENTATIONS * All presentations and documents which were to be shown in the AC room will be uploaded to the corresponding page on the ICANN61 schedule meeting pages: https://61.schedule.icann.org/[61.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_…> * Presentations and documents will also be circulated via email on demand 1. ASKING QUESTIONS AND COMMENTING IN WRITTEN FORMAT * These will be handed via live management of email comments and questions by the Remote Participation Manager. Please see list of meeting room email addresses here: https://61.schedule.icann.org/pages/2350[61.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_…> We apologize for the inconvenience caused. We encourage participants who have not already done so to download the ICANN61 mobile app by searching for “ICANN61” in your app stores. Please do not hesitate to email us at gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> if you need a dial out specifying which meeting you would like to join and your preferred contact number. Kind regards, Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

CONSENSUS CALL: Recommendation 22 Implementation Charter
by Julie Hedlund March 8, 2018

March 8, 2018

Dear GNSO Review Working Group members, This is a Consensus Call for the GNSO Review Implementation Charter for Recommendation 22, per the action items from the meeting on 01 March. The redlines in the Working Group Determination section of the document reflect the agreed-upon changes during the meeting. As noted in the attached charter, this is the recommendation for implementation: “That the GNSO Council develop a competency-based framework, which its members should use to identify development needs and opportunities.” Staff is circulating the revised version of the charter for a three-week Consensus Call to end on Thursday, 29 March 2018. If there are no objections the recommendation will be deemed to have been implemented by Full Consensus. Best regards, Julie Julie Hedlund, Policy Director

1 0

REMINDER re: Response Requested re: Timing of meeting on 29 March
by Julie Hedlund March 8, 2018

March 8, 2018

Dear GNSO Review Working Group members, This is a reminder. Please see the following action item from last week’s meeting: Action Item 9: Staff will send a note to the list asking whether the next meeting on 29 March should take place at 12:00 UTC or 13:00 UTC (due to US change to Daylight Saving Time on 11 March 2018). Note that upon the change to Daylight Saving Time (DT) in the US, the usual time of 13:00 UTC will change from 05:00 to 06:00 PDT/08:00 to 09:00 EDT. Please indicate whether you prefer that the time should stay at 13:00 UTC, or revert to 12:00 UTC (thus maintaining the time at 05:00 PDT/08:00 EDT). Thank you very much for your assistance. Kind regards, Julie Julie Hedlund, Policy Director

2 1

Final Status Report to the GNSO Council
by Julie Hedlund March 2, 2018

March 2, 2018

Dear all, As there have been no further changes, please see attached the final status report that will be sent to the GNSO Council today. Kind regards, Julie From: Gnso-review-wg <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Friday, March 2, 2018 at 9:51 AM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] FW: UPDATED FOR REVIEW: Draft Status Report to the GNSO Council Reminder: Please send any further edits by 1500 UTC today. Best, Julie From: Gnso-review-wg <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, March 1, 2018 at 10:38 AM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] UPDATED FOR REVIEW: Draft Status Report to the GNSO Council Dear GNSO Review Working Group members, Please see the attached revised document (in Word and PDF) with redlined changes based on the discussion on our call today. Please let us know if you have further edits as soon as possible but not later than 1500 UTC tomorrow, Friday, 02 March. Kind regards, Julie From: Gnso-review-wg <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, February 28, 2018 at 7:27 PM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] FOR REVIEW: Draft Status Report to the GNSO Council Dear GNSO Review Working Group members, The GNSO Council has requested a brief written status report from the GNSO Review Working Group for ICANN61. At this point this is not an item on the GNSO Council’s agenda at its ICANN61 meeting on 14 March, but after receiving the written report the Council could decide to add an item to its agenda. In that case, the status report should be sent to the Council by the document and motion deadline, which is Sunday, 04 March. Please see the attached draft brief report for discussion on tomorrow’s call. The final draft report will be conveyed via email by staff on behalf of the GNSO Review Working Group Chair and Vice Chair in time for the deadline. Kind regards, Julie Julie Hedlund, Policy Director

1 0

Re: [Gnso-review-wg] Actions/Discussion Notes for GNSO Review WGMeeting on 01 March 2018
by Kris Seeburn March 2, 2018

March 2, 2018

HI, The calculations makes sense. What i am wondering whether ICANN org can afford. Looking at the financials. Perhaps we add Financials permitting > On Mar 2, 2018, at 16:24, Wolf-Ulrich.Knoben <wolf-ulrich.knoben(a)t-online.de> > > <https://www.boxbe.com/overview> This message is eligible for Automatic Cleanup! (wolf-ulrich.knoben(a)t-online.de) Add cleanup rule <https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey…> | More info <http://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=37155819935…> > All, > > I did a short analysis wrt to potential language interpretation and transscription costs (see attached). The calculation of meetings is taken from the GNSO calendar 2017 (https://gnso.icann.org/en/group-activities/calendar/2017 <https://gnso.icann.org/en/group-activities/calendar/2017>). It is just WGs and WTs, no SG- or Constituency-specific meetings, no council meetings. > Under the assumptions made an additional budget of around 100 k$ may be needed. Everybody can "play" with the input parameters in the Excel sheet. E.g. if a "big" WG like SubPro doesn't request interpretation it would significantly reduce the cost. > > Maybe other scenarios are more realistic. We should discuss them. > > Best regards > > Wolf-Ulrich > > Am 01.03.2018 um 16:58 schrieb Julie Hedlund: >> Dear GNSO Review Working Group members, <> >> Â >> >> Please see below the action items and discussion notes captured by staff from the meeting on 01 March 2018.Â These high-level notes are designed to help WG members navigate through the content of the call and are not meant to be a substitute for the recording or transcript, which are posted on the wiki at:https://community.icann.org/display/GRWG/2018 <https://community.icann.org/display/GRWG/2018>. >> >> Â >> >> Please note that the next meeting will occur on 29 March either at 1200 or 1300 UTC (time to be determined via separate message). >> >> Â >> >> Best regards, >> >> Julie >> >> Â >> >> Julie Hedlund, Policy Director >> >> Â >> >> Â >> >> Notes & Action Items GNSO Review Working Group Meeting on Thursday, 01 March 2018 at 13:00 UTC >> >> Â >> >> Action Items: >> >> Â >> >> Implementation Charter for Recommendation 22: >> >> Action Item 1: Staff will update the organization of training materials on the GNSO website. Staff will update the WG Determination that take into account that there are already trainings that are accessible and include real-time interaction. The WG Determination will note that staff will update the website and will link to the updated GNSO webpage when it is ready. Â Staff will put the changes out for a 3-week Consensus Call. >> >> Â >> >> Implementation Charter for Recommendations 1, 2, & 3: >> >> Action Item 2: Staff will add information about Council comment on CROP to the implementation charter once posted to public forum. Staff will also add text based on additional feedback that may be received on SG/C outreach. >> >> Action Item 3: Staff will adjust the text of the "note" on page 4 to be more neutral regarding dues collected. Staff will also add text clarifying how dues are used within the BC with respect to voting. >> >> Action Item 4: Staff will add text to the charter elaborating on the link between GSE activities and recruitment for PDP WGs. >> >> Â >> >> Implementation Charter for Recommendations 7 & 12: >> >> Action Item 5: Update implementation charter title to "Language Translation and Transcription." >> >> Action Item 6: Staff will add text about the translation of written material, including benefits, uses, and costs. >> >> Action Item 7: Staff will add some possible scenarios outlining the costs if GNSO WGs began using translation on their calls. >> >> Â >> >> Update to the GNSO Council: >> >> Action Item 8: Remove the target end date of June 2018 from the status update to the GNSO Council. >> >> Â >> >> Next Meeting: >> >> Action Item 9: Staff will send a note to the list asking whether the next meeting on 29 March should take place at 12:00 UTC or 13:00 UTC (due to US change to Daylight Saving Time on 11 March 2018). >> >> Â >> >> Notes: >> >> Â >> >> 1. Review agenda/SOIs: No updates. >> >> Â >> >> 2. Status of Consensus Call for revised implementation charter for recommendation 34: >> >> Â >> >> -- The consensus call ended on 8 February. No objections were raised to the text for this implementation charter. >> >> -- This recommendation is seen as implemented. The work is complete on this recommendation. >> >> Â >> >> 3. Discussion of the revised implementation charter for recommendation 22: >> >> Â >> >> -- This charter has been updated based on previous discussions. >> >> -- The change discussed on the call on the 8th was to make minor updates to the WG determination. >> >> -- Two additional sentences have been added to the end of this section "The Working Group recommends that training options should focus on accessibility of training, and in particular real-time interaction through remote platforms. The Working Group also recommends that all of the training and learning materials are linked from the GNSO website and described in the context of the competency-based framework." >> >> -- Earlier in the document, the trainings are organized into a framework. The recommendation states that information about the trainings should be organized following this framework on the GNSO website. >> >> -- Question: The WGs mandate is to finalize the implementation. Should we simply make a recommendation or should the WG take additional steps to implement the work itself in collaboration with staff? >> >> -- Response: Even if it says "recommend" this does not include a mandate, noting that many trainings have the recommended features. Staff can go ahead an updating the GNSO website as recommended by the WG. >> >> -- Question: someone reading this recommendation may wonder if the recommendation will be followed. It is possible that the recommendation will be implemented or can only be implemented under certain circumstances. >> >> -- The changes suggested in Action Item 1 will be circulated and go out for consensus call. The WG will aim to have the consensus call closed by the next WG meeting after ICANN61. >> >> Â >> >> 4. Discussion of the revised implementation charter for recommendations 1, 2, & 3: >> >> Â >> >> -- During the last meeting, staff was asked to make additional edits. >> >> -- Staff investigated the CROP program and updated text on this program based on status of the FY19 budget. The draft FY19 budget does not include funding for CROP. >> >> Â >> >> Chat excerpt: >> >> Marika Konings: Note that this is also input that the Council is considering in relation to the FY19 budget (focus on KPIs and metrics for outreach programs) >> >> Â >> >> -- Staff added content about Global Stakeholder Engagement. >> >> -- Staff investigated outreach conducted by SG/Cs and added text based on responses received. >> >> -- Additional text was included on suggested metrics based on feedback from the WG. >> >> -- Question: The note regarding BC and IPC dues may be confusing. The justification and rationales are not included. Could this text be worded in a more neutral manner. For example " There are Constituencies that collect dues . .." >> >> -- Question: How is GSE linked to recruiting more participants to GNSO PDP WGs? Some community members are not clear about the link. >> >> -- Response: Staff will add language about this link. >> >> -- Feedback: The community onboarding program may be useful to include in this implementation charter. >> >> -- Clarification: Membership dues allow members to reach decisions in the BC. While voting is not always used, when voting does take place, different members have a different number of votes based on the dues they pay. >> >> Â >> >> 5. Discussion of the implementation charter for recommendations 7 & 12: >> >> Â >> >> -- Staff had an action item to update text regarding current language services and costs. This text has been updated. >> >> Â >> >> Chat excerpt: >> >> Rafik Dammak: if I am not mistaking the budget for FY19 includes reduction on interpretation and translation service to be provided. captioning seems the more reasonable option for now >> >> Â >> >> -- The implementation charter includes possible approaches to using language services. >> >> -- Question: is this charter only covering interpretation services or also document translation services? >> >> -- Answer: because recommendation 7 is broad, the implementation charter should likely also include text about document translation. >> >> -- Question: If it is up to the WGs to determine the extent to which they use translation, what will be the impact on the budget? Could we check to see how many times GNSO WGs met last year and calculate the potential costs of using these services if X% chose to use translation services? >> >> Â >> >> Chat excerpt: >> >> Marika Konings: @Wolf-Ulrich - the costs of that would be substantial so it would be a question of priorities for the GNSO/Council. >> >> Rafik Dammak: we used interpretation to french and spanish at ccwg diveristy subgroup in the last calls, few people usedÂ it...and we got people asking for it >> >> Marika Konings: I recall that the CCWG-WS1 also 'demanded' interpretation for its calls, but a review of the numbers of users also showed that on many calls there were zero or just 1 or 2 people on one or more of the languages offered. >> >> Marika Konings: maybe some more awareness of the costs involved may ensure that it is a more conscious decision when interpretation is asked (and used) >> >> Rafik Dammak: interpretation for weinars make sense since the number of attendees is much higher >> >> Wolf-Ulrich Knoben: that's why we need a "solid" scenario, Marika >> >> Marika Konings: @Rafik - but my personal view is that it should be demand driven, even for webinars. >> >> Wolf-Ulrich Knoben: demand should be estimated by the WG >> >> Marika Konings: @Wolf-Ulrich, but it is probably for the Council to oversee if/how resources are used, as this would add a significant cost which would need to be funded from something else noting the budget situation we are in? >> >> Â >> >> 6. Discussion of the updated Work Plan: >> >> Â >> >> -- Anticipated for 29 March: Recommendations 22, 7, 12, 20, and 21 as well as revisiting recommendations 26-29 which have been on hold pending additional information about GDPR implementation. >> >> -- In April, the WG will revisit recommendations 6, 33, 35, and 36 which have been on hold pending work from the CCWG Accountability sub-group on diversity. >> >> Â >> >> Chat excerpt: >> >> Rafik Dammak: diveristy final recommendations passed the first reading yesterday >> >> Rafik Dammak: close to be approved >> >> Â >> >> -- The goal is for all recommendations to be implemented in June 2018. The WG will provide a Final Implementation Status Report to OEC and the GNSO Council. >> >> -- Additional time may be needed for implementation of some of the outstanding items. >> >> Â >> >> 7. Planning for Update to GNSO Council: >> >> Â >> >> -- Status report will be provided to the GNSO Council. This item is not currently on the GNSO Council agenda for ICANN61 but could be added under AOB. >> >> -- Suggestion: Do not include the internal June 2018 target date in the Council update. >> >> Â >> >> 8. Discussion of the implementation charter for recommendations 20 and 21 (time permitting):Â This item was not covered. >> >> Â >> >> 9. Next Meeting: 29 March 1300 UTC: Staff will send a note to the list asking whether the next meeting should take place at 12:00 UTC or 13:00 UTC. >> >> >> >> _______________________________________________ >> Gnso-review-wg mailing list >> Gnso-review-wg(a)icann.org <mailto:Gnso-review-wg@icann.org> >> https://mm.icann.org/mailman/listinfo/gnso-review-wg <https://mm.icann.org/mailman/listinfo/gnso-review-wg> > <language cost scenario.xlsx>_______________________________________________ > Gnso-review-wg mailing list > Gnso-review-wg(a)icann.org > https://mm.icann.org/mailman/listinfo/gnso-review-wg Kris Seeburn seeburn.k(a)gmail.com www.linkedin.com/in/kseeburn/ <http://www.linkedin.com/in/kseeburn/> "Life is a Beach, it all depends at how you look at it"

4 3

INTA and IPC Cordially Invite You to Our ICANN Reception on March 13th in San Juan
by Lori Schulman March 2, 2018

March 2, 2018

[International Trademark Association: PowerfulNetworkPowerfulBrands]<http://www.inta.org> [ICANN San Juan Benefit]<https://www.inta.org/Calendar/Pages/Inta%20Events.aspx> You are Cordially Invited! Please join our friends and colleagues for an evening to benefit the Ricky Martin Foundation for Puerto Rico Hurricane Relief. Date: Tuesday, March 13, 2018 Time: 7:00 pm - 8:30 pm Where: La Concha Renaissance 1077 Avenida Doctor Ashford San Juan, 00907, Puerto Rico Hosted by: [http://echo4.bluehornet.com/cimages/73d08cc42669e84a270f24fa5d864ccb/INTALo…] [http://echo4.bluehornet.com/cimages/73d08cc42669e84a270f24fa5d864ccb/IPC_IC…] Sponsored by: [http://echo4.bluehornet.com/cimages/73d08cc42669e84a270f24fa5d864ccb/com_la…] [http://echo4.bluehornet.com/cimages/73d08cc42669e84a270f24fa5d864ccb/ferrai…] RSVP Today!<mailto:mjohnson@inta.org?subject=RSVP%20for%20San%20Juan%20ICANN%20event> To benefit the Ricky Martin Foundation for Puerto Rico.<https://www.youcaring.com/peopleofpuertorico-957793> Copyright (c) 2018 International Trademark Association, 655 Third Avenue, 10th Floor, New York, NY 10017-5646 USA phone +1-212-642-1700 | fax +1-212-768-7796 | www.inta.org<http://www.inta.org> | MemberOperations(a)inta.org<mailto:MemberOperations@inta.org> Unsubscribe<http://echo4.bluehornet.com/phase2/survey1/survey.htm?CID=kbwhil&action=upd…> | Forward to a friend<http://echo4.bluehornet.com/forwardthis/ft.php?mID=58397524&em=lschulman%40…> ________________________________

2 1