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

Status Summary, Charter Review, and Consensus Calls
by Julie Hedlund June 27, 2017

June 27, 2017

Dear GNSO Review Working Group members, In order to assist the Working Group in tracking the status of its work and progress on reviewing and approving implementation plans for recommendations, staff has created the following page on the wiki: https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Cons…. Feel free to reference this page if you receive inquiries from the GNSO or ICANN community concerning the most recent status and progress. Please also let staff know if you have any questions, comments, or suggestions for improving this information. Best regards, Julie Julie Hedlund, Policy Director

2 4

Re: [Gnso-review-wg] Proposal: Reschedule Next Meeting to 13 July
by Julie Hedlund June 26, 2017

June 26, 2017

Dear GNSO Review Working Group members, As there have been no objections to the proposal below to move the meeting we will reschedule it to 1200 UTC on Thursday, 13 July. Best regards, Julie Julie Hedlund, Policy Director From: <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, June 22, 2017 at 5:07 PM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] Proposal: Reschedule Next Meeting to 13 July Dear GNSO Review Working Group members, On today’s call the Working Group members noted that due to travel after the ICANN59 meeting there may be conflicts for people who wish to attend the next Working Group call on 06 July. Consequently, the Working Group proposed canceling the meeting on 06 July and rescheduling it for 13 July. The action from today’s call was for staff to convey this proposal to the list. Staff hereby conveys the proposal to cancel the call on 06 July and reschedule it at the usual time of 1200 UTC for Thursday, 13 July. If there are no objections to this proposal by Monday, 26 June, the meeting will rescheduled. Best regards, Julie Julie Hedlund, Policy Director

1 0

Re: [Gnso-review-wg] Proposal: Reschedule Next Meeting to 13 July
by Sara Bockey June 23, 2017

June 23, 2017

No objections here. From: <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, June 22, 2017 at 5:07 PM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] Proposal: Reschedule Next Meeting to 13 July Dear GNSO Review Working Group members, On today’s call the Working Group members noted that due to travel after the ICANN59 meeting there may be conflicts for people who wish to attend the next Working Group call on 06 July. Consequently, the Working Group proposed canceling the meeting on 06 July and rescheduling it for 13 July. The action from today’s call was for staff to convey this proposal to the list. Staff hereby conveys the proposal to cancel the call on 06 July and reschedule it at the usual time of 1200 UTC for Thursday, 13 July. If there are no objections to this proposal by Monday, 26 June, the meeting will rescheduled. Best regards, Julie Julie Hedlund, Policy Director

2 1

Proposal: Reschedule Next Meeting to 13 July
by Julie Hedlund June 23, 2017

June 23, 2017

Dear GNSO Review Working Group members, On today’s call the Working Group members noted that due to travel after the ICANN59 meeting there may be conflicts for people who wish to attend the next Working Group call on 06 July. Consequently, the Working Group proposed canceling the meeting on 06 July and rescheduling it for 13 July. The action from today’s call was for staff to convey this proposal to the list. Staff hereby conveys the proposal to cancel the call on 06 July and reschedule it at the usual time of 1200 UTC for Thursday, 13 July. If there are no objections to this proposal by Monday, 26 June, the meeting will rescheduled. Best regards, Julie Julie Hedlund, Policy Director

2 1

Recordings, Attendance & AC Chat from GNSO Review WG call call on Thursday, 22 June 2017 at 12:00 UTC
by Michelle DeSmyter June 22, 2017

June 22, 2017

Dear all, Please find the mp3, attendance and chat below for the GNSO Review Working Group held on Thursday, 22 June 2017 at 12:00 UTC. Mp3: https://audio.icann.org/gnso/gnso-review-22jun17-en.mp3 AC Recording: https://participate.icann.org/p656u0cveff/ The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:http://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> Mailing list archives: http://mm.icann.org/pipermail/gnso-review-wg/ Wiki page: https://community.icann.org/x/q7bRAw Attendees: Members: Wolf-Ulrich Knoben (ISPCP Primary) Jennifer Wolfe (RySG Primary) Heath Dixon (RrSG Primary) Lori Schulman (IPC Primary) Lawrence Olawale-Roberts (BC Primary) Rafik Dammak (NCSG Primary) Participants: Apologies: Marika Konings (staff) ICANN staff: Julie Hedlund Amr Elsadr Berry Cobb Michelle DeSmyter ** Please let me know if your name has been left off the list ** Thank you. Kind regards, Michelle ------------------------------- Adobe Connect chat transcript for 22 June 2017

1 0

REVISED/EXTENDED CONSENSUS CALL: Recommendations 24/25 GNSO Review Implementation Charter
by Julie Hedlund June 22, 2017

June 22, 2017

Dear GNSO Review Working Group members, Per the action items and notes below from the call on 22 June this is a revised and extended consensus call for the GNSO Review Implementation Charter for Recommendations 24 and 25. For information and guidance on the decision-making process please see the background below. Per the notes, staff has revised the charter determinations to correct item 1, and to add a new item 3 recommendation. The changes are in redline in the attached revised charter. As noted in the attached charter, recommendations 24 and 25 state: Recommendation 24: That the GNSO Council and Stakeholder Groups and Constituencies adhere to the published process for applications for new Constituencies. That the ICANN Board in assessing an application satisfy itself that all parties have followed the published process, subject to which the default outcome is that a new Constituency is admitted. That all applications for new Constituencies, including historic applications, be published on the ICANN website with full transparency of decision-making. Recommendation 25: That the GNSO Council commission the development of, and implement, guidelines to provide assistance for groups wishing to establish a new Constituency. Working Group members are requested to respond to this consensus call by COB Monday, 10 July. For a list of Working Group members and the Stakeholder Groups and Constituencies represented see:https://community.icann.org/display/GRWG/WG+members+and+mailing+list. Please note that if no objections are raised, we will take that to mean there is approval of the charter as written. Best regards, Julie Julie Hedlund, Policy Director Background on Decision-Making from the Working Group Charter: Per the Working Group Charter at https://community.icann.org/display/GRWG/Charter?preview=/61610405/61610404… the WG conducts decision-making via consensus. Specifically, the Charter states: “In developing its output, work plan and any other reports, the GNSO Review Working Group shall seek to act by consensus. The chair(s) may make a call for Consensus. If making such a call, they should always make reasonable efforts to involve all Stakeholder Groups/Constituencies appointed Members of the Working Group. The chair(s) shall be responsible for designating each position as having one of the following designations: 1. Full consensus - when no one in the group speaks against the recommendation in its last readings. This is also sometimes referred to as Unanimous Consensus. 2. Consensus - a position where only a small minority disagrees, but most agree.” The Charter further states: “In the case of recommended changes to the GNSO Operating Procedures and/or ICANN Bylaws, only recommendations that have achieved full consensus of the WG shall be forwarded to the GNSO Council. All other recommendations shall be forwarded if they achieve either consensus or full consensus of the WG.” In the case of this consensus call, as the implementation does not result in any new recommended changes to the GNSO Operating Procedures and/or ICANN Bylaws, the recommendation will be decided via consensus, although if there are no objections it may be that the decision will be full consensus. Action Items/Discussion Notes 22 June Action Items: Charter for Recommendations 24/25: 1) Revise the charter determinations to correct item 1, and to add a new item 3 recommendation; 2) send out for a new extended Consensus Call to end on COB Monday, 10 July. Charter for Recommendations 10/11: Evaluate Geographic Names facilitated sessions at ICANN59 in a brief survey. Place this charter on hold until Geographic Names session results are evaluated. Charter for Recommendation 13: Look at what ICANN may be developing for a document management system. Next Meeting: Propose on the list moving the 06 July meeting to 13 July and if there no objections reschedule. Discussion Notes: 1. Consensus Call for Recommendation 24/25 Charter: -- Suggestion to add a recommendation that current and historic information be consolidated in one web page. -- Staff suggests to accept edits from Wolf-Ulrich - that current processes address recommendation 24, and that they are effective and accessible, but notes that to be more clear the wording should mirror that for Recommendation 25 as follows: “That the current processes address Recommendation 24 and that they are effective and accessible.” -- Question: Should the consensus call be extended, following circulation of track changes by staff? The Working Group agreed to extend the Consensus Call on the revised document to COB 10 July. 2. Charter for Recommendations 10/11: -- Pilot Project -- not sure it was helpful to have a F2F facilitated meeting. Pilot was conducted twice for the PPSAI PDP, and once for the IGO/INGO access to curative rights PDP. The link to the results is contained in the charter. Results of the survey were mixed -- not conclusive that the F2F sessions were helpful. -- Hard to say in future if there will be a need for a facilitator. If we leave it as it is what could be done if it comes up? Could we establish a framework or do we leave it as it is? -- Suggestion: Evaluate Geographic Names facilitated sessions at ICANN59 in a brief survey -- were they helpful? Should there be guidelines? -- Perhaps if we have criteria they could be very broad. -- Place this charter on hold until we can evaluate the Geographic Names session results. 3. Charter for Recommendation 13: -- Note that access to Google Doc is not universal - some might not have access (example: because of geo blocking), while access to Microsoft Word could also be challenging due to licensing costs. -- Question: The SSAC conducted research on a tool. What were the results? Answer: Decided to use Google Docs and Microsoft Word. Using Google Docs for drafts and Microsoft Word for final drafts. -- Question: Are there access issues? What if there are public interests? Answer: Access can be moderated -- to edit, comment, etc. based on who has the link. Access also depends on if someone has a Google account or if one can afford Microsoft. Google Drive is not accessible in China. -- Maybe need criteria to have in mind. There is the issue of user acceptance for new tools. -- One thing that works for those in the developing region is what you have with Microsoft Word where you can work offline. Google Docs has its own advantages to see comments in real time. Both platforms have advantages. If ICANN is looking at a document management system it must have the ability to work offline. -- Action: Look at what ICANN may be developing for a document management system. 4. Next meeting: -- Propose on the list moving the 06 July meeting to 13 July and if there no objections reschedule.

1 0

Actions/Discussion Notes for GNSO Review WG Meeting on 22 June
by Julie Hedlund June 22, 2017

June 22, 2017

Dear GNSO Review Working Group members, Please see below the action items and discussion notes captured by staff from the meeting on 22 June. 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/2017-06-22+GNSO+Review+WG. Best regards, Julie Julie Hedlund, Policy Director Action Items/Discussion Notes 22 June Action Items: Charter for Recommendations 24/25: 1) Revise the charter determinations to correct item 1, and to add a new item 3 recommendation; 2) send out for a new extended Consensus Call to end on COB Monday, 10 July. Charter for Recommendations 10/11: Evaluate Geographic Names facilitated sessions at ICANN59 in a brief survey. Place this charter on hold until Geographic Names session results are evaluated. Charter for Recommendation 13: Look at what ICANN may be developing for a document management system. Next Meeting: Propose on the list moving the 06 July meeting to 13 July and if there no objections reschedule. Discussion Notes: 1. Consensus Call for Recommendation 24/25 Charter: -- Suggestion to add a recommendation that current and historic information be consolidated in one web page. -- Staff suggests to accept edits from Wolf-Ulrich - that current processes address recommendation 24, and that they are effective and accessible, but notes that to be more clear the wording should mirror that for Recommendation 25 as follows: “That the current processes address Recommendation 24 and that they are effective and accessible.” -- Question: Should the consensus call be extended, following circulation of track changes by staff? The Working Group agreed to extend the Consensus Call on the revised document to COB 10 July. 2. Charter for Recommendations 10/11: -- Pilot Project -- not sure it was helpful to have a F2F facilitated meeting. Pilot was conducted twice for the PPSAI PDP, and once for the IGO/INGO access to curative rights PDP. The link to the results is contained in the charter. Results of the survey were mixed -- not conclusive that the F2F sessions were helpful. -- Hard to say in future if there will be a need for a facilitator. If we leave it as it is what could be done if it comes up? Could we establish a framework or do we leave it as it is? -- Suggestion: Evaluate Geographic Names facilitated sessions at ICANN59 in a brief survey -- were they helpful? Should there be guidelines? -- Perhaps if we have criteria they could be very broad. -- Place this charter on hold until we can evaluate the Geographic Names session results. 3. Charter for Recommendation 13: -- Note that access to Google Doc is not universal - some might not have access (example: because of geo blocking), while access to Microsoft Word could also be challenging due to licensing costs. -- Question: The SSAC conducted research on a tool. What were the results? Answer: Decided to use Google Docs and Microsoft Word. Using Google Docs for drafts and Microsoft Word for final drafts. -- Question: Are there access issues? What if there are public interests? Answer: Access can be moderated -- to edit, comment, etc. based on who has the link. Access also depends on if someone has a Google account or if one can afford Microsoft. Google Drive is not accessible in China. -- Maybe need criteria to have in mind. There is the issue of user acceptance for new tools. -- One thing that works for those in the developing region is what you have with Microsoft Word where you can work offline. Google Docs has its own advantages to see comments in real time. Both platforms have advantages. If ICANN is looking at a document management system it must have the ability to work offline. -- Action: Look at what ICANN may be developing for a document management system. 4. Next meeting: -- Propose on the list moving the 06 July meeting to 13 July and if there no objections reschedule.

1 0

CONSENSUS CALL: Recommendations 24/25 GNSO Review Implementation Charter
by Julie Hedlund June 21, 2017

June 21, 2017

Dear GNSO Review Working Group members, Per the action items and notes below from the call on 08 June (see below), and following a one-week review of the attached charter, this is a consensus call for the GNSO Review Implementation Charter for Recommendations 24 and 25. For information and guidance on the decision-making process please see the background below. The last version of the charter is attached for your review and posted on the wiki at: https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Cons…. As noted in the attached charter, recommendations 24 and 25 state: Recommendation 24: That the GNSO Council and Stakeholder Groups and Constituencies adhere to the published process for applications for new Constituencies. That the ICANN Board in assessing an application satisfy itself that all parties have followed the published process, subject to which the default outcome is that a new Constituency is admitted. That all applications for new Constituencies, including historic applications, be published on the ICANN website with full transparency of decision-making. Recommendation 25: That the GNSO Council commission the development of, and implement, guidelines to provide assistance for groups wishing to establish a new Constituency. After discussing this recommendation at length during multiple meetings the WG determined that the recommendation had been implemented as stated in the charter based on activities that have already occurred. Working Group members are requested to respond to this consensus call in two weeks, by COB Monday, 03 July. For a list of Working Group members and the Stakeholder Groups and Constituencies represented see:https://community.icann.org/display/GRWG/WG+members+and+mailing+list. Please note that if no objections are raised, we will take that to mean there is approval of the charter as written. Best regards, Julie Julie Hedlund, Policy Director Background on Decision-Making from the Working Group Charter: Per the Working Group Charter at https://community.icann.org/display/GRWG/Charter?preview=/61610405/61610404… the WG conducts decision-making via consensus. Specifically, the Charter states: “In developing its output, work plan and any other reports, the GNSO Review Working Group shall seek to act by consensus. The chair(s) may make a call for Consensus. If making such a call, they should always make reasonable efforts to involve all Stakeholder Groups/Constituencies appointed Members of the Working Group. The chair(s) shall be responsible for designating each position as having one of the following designations: 1. Full consensus - when no one in the group speaks against the recommendation in its last readings. This is also sometimes referred to as Unanimous Consensus. 2. Consensus - a position where only a small minority disagrees, but most agree.” The Charter further states: “In the case of recommended changes to the GNSO Operating Procedures and/or ICANN Bylaws, only recommendations that have achieved full consensus of the WG shall be forwarded to the GNSO Council. All other recommendations shall be forwarded if they achieve either consensus or full consensus of the WG.” In the case of this consensus call, as the implementation does not result in any new recommended changes to the GNSO Operating Procedures and/or ICANN Bylaws, the recommendation will be decided via consensus, although if there are no objections it may be that the decision will be full consensus. From: <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, June 15, 2017 at 11:14 AM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] REMINDER FOR REVIEW: Recommendations 24/25 GNSO Review Implementation Charter Dear GNSO Review Working Group members, Per the action items and notes below from the call on 08 June, please review the attached revised GNSO Review Implementation Charter for Recommendations 24/25 in Word and PDF with changes highlighted as redlines. As noted in the attached charter, these are the recommendations for implementation: Recommendation 24: That the GNSO Council and Stakeholder Groups and Constituencies adhere to the published process for applications for new Constituencies. That the ICANN Board in assessing an application satisfy itself that all parties have followed the published process, subject to which the default outcome is that a new Constituency is admitted. That all applications for new Constituencies, including historic applications, be published on the ICANN website with full transparency of decision-making. Recommendation 25: That the GNSO Council commission the development of, and implement, guidelines to provide assistance for groups wishing to establish a new Constituency. Working Group members are requested to respond to this review in one week, by COB Thursday, 15 June. If no comments are received during the review period staff will accept the changes and circulate the final version of the charter for a two-week Consensus Call. Best regards, Julie Julie Hedlund, Policy Director Action Items/Discussion Notes 08 June Action Items: Contracted Party House Membership: Staff will provide details concerning membership processes, particularly with respect to interest groups or non-contracted parties, and add these to the Google Document for tracking overarching or out-of-scope questions. Charter for Recommendations 24/25: 1) Revise the charter to indicate that the Working Group has discussed the following action from the GNSO Review Working Party: “determine whether or not there is a presumption that a new Constituency should be admitted if all requirements are met and if such a presumption is appropriate” and the Working Group determined that there is not a presumption that a new Constituency should be admitted if all requirements are met since a Constituency applicant could fail the evaluation process by the Board or the Stakeholder Group if it did not meet the criteria; 2) include the Process for Recognition of New GNSO Constituencies as an attachment in the revised charter; 3) circulate the revised document for one week and if no comments are received initiate a Call for Consensus for two weeks. Charter for Recommendations 10/11: Send the charter to the list for review and to initiate discussion. Continue discussion at the meeting on 22 June. Discussion Notes: 1. Charter for Recommendation 16: -- Call for Consensus closed on 29 May. There were no objections to the implementation charter so it is approved by full consensus. -- See the wiki for status on Consensus Calls and Charters under review at: https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Cons…. 2. Continue Discussion of Charter for Recommendations 24/25: -- Question: Referring to documents regarding the process. Would it be necessary dive into the process itself -- such as the duration? Looking at the flow chart could be as short as 3 months, but could be longer. Are there specific criteria that must be met? Answer: It would seem that an analysis of the process itself would be out of scope of these recommendations, which only address whether the process is followed, is transparent, and if guidelines exist. -- Question of presumption of the default outcome: Is it appropriate? What are the options for the Working Group? Answer: The Working Group could decide whether the presumption of admission (the “default outcome”) is appropriate given the fact that even if a new Constituency has met the criteria, it still could fail the evaluation by the Stakeholder Group or the Board for other reasons. If it decides it is appropriate then the Working Group may need to suggest changes to the constituency application and evaluation process. If it decides it is not appropriate then the process does not need to be modified, but the Working Group should call out the fact that this part of Recommendation 24 “subject to which the default outcome is that a new Constituency is admitted” may not be applied if a Constituency is deemed not to meet the criteria in the evaluation process. -- Where is the bar in anticipation of participation? There is some peril in not having objective criteria in terms of effectiveness or activity. The idea of active participation is too loose. -- NPOC is the only new constituency and those rules grew out of the stress and tension of trying to create a new constituency. NCSG wanted to just have interest groups, but rules were developed to accommodate the need for a group that said they wanted a constituency. NPOC was the only one that made it through the process. -- Have we set the bar so high that it sets a deterrent? Should we be looking at the criteria? Should the criteria be as objective as possible? -- Is this process transparent enough? Do we make changes to the process or not? -- The criteria have a value. We have a balance to ensure that they are active and grow to find their mission. Important to have high bars. >From the Chat: avri doria: Perhaps this is Off Topic, but why do we have a Staff/Board imposed process for new constituencies in NCPH but not in CPH? i have never understood this imbalance. avri doria: Thanks, I missed last week's mtg. Marika Konings: My recollection is similar, because the contracted aspect creates an automatic qualifying criteria it was deemed not necessary to create a process (either you have a contract and you can join through a set membership process, or you don't). avri doria: This relates to membership in the SGs, but not to the creation of constituencies. Marika Konings: Correct, but I believe linked to that on the contracted party side the view was that there was no need for constituencies as everyone is a contracted party (registry or registrar). But to get the real insight into this, we may need to dig into history and ask those directly involved in that decision. avri doria: They call it an interest group instead of a constituency. but the NCPH is nt allowed to have interest groups instead of constituencies. Marika Konings: I think the interest group concept was created to address the interest of those wanting to participate but not yet qualifying as contracted parties as they had not signed a contract with ICANN yet. I don't know if that concept still exists, even though there are groups that are organized in a certain way such as the Geo Names and BRG. It might be interesting to see whether there is further discussion in those groups around this as, for example, in the near future there will potentially be a new group of contracted parties (P/P providers) and in the past, there has also been mention of escrow providers as a specific group of contracted parties. avri doria: I was deeply involved in that particular set of events. Amr Elsadr: Apart from a constituency application that was outright rejected, there was also an applicant that made it through to the candidate constituency phase in the NCSG for a few years, but it didn't make it to full constituency status. Lori Schulman: Amr: who was the applicant that "partially" made it Amr Elsadr: The Consumer Constituency. avri doria: yes, I was part of the effort to start the consumer constituency in NCSG, but it never got sufficient participant support within the candidate constituency to meet the requirements of both the ICANN process & the NCSG requirements for active participation. Lori Schulman: Diversity is a good point and objective Amr Elsadr: The CCAOI application did not meet the diversity criteria in more than one way, which is one of the reasons the application was rejected. avri doria: A presumption of acceptance would be hard for everyone, but even harder for CSG as that would change the number of seats each of the existing constituencies could hold. Since council seats in the NCSG are based on an SG wide selection process, its model can support a multitude of constituencies if they met the conditions without any change to council seating except through elections at the SG level.

2 2

Agenda and Materials for GNSO Review WG Call on 22 June 1200 UTC
by Julie Hedlund June 20, 2017

June 20, 2017

Dear GNSO Review Working Group members, Please see the draft agenda below and attached materials for the meeting on Thursday, 22 June at 1200 UTC. Draft Agenda: Review agenda SOIs Consensus Call for Recommendation 24/25 Charter – Opened on 19 June; Closes on 03 July (2 weeks) Continue discussion of Charter for Recommendations 10/11 Begin discussion on Charter for Recommendation 13 Meeting Schedule: Next meeting 06 July AOB Best regards, Julie Julie Hedlund, Policy Director

1 0

REVIEW CLOSED: Recommendations 24/25 GNSO Review Implementation Charter
by Julie Hedlund June 19, 2017

June 19, 2017

Dear GNSO Review Working Group members, As no responses were reviewed during the review period that closed on COB Thursday, 15 June, per the message below staff will circulate the final version of the charter for a two-week consensus call. Best regards, Julie Julie Hedlund, Policy Director From: <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, June 15, 2017 at 11:14 AM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] REMINDER FOR REVIEW: Recommendations 24/25 GNSO Review Implementation Charter Dear GNSO Review Working Group members, Per the action items and notes below from the call on 08 June, please review the attached revised GNSO Review Implementation Charter for Recommendations 24/25 in Word and PDF with changes highlighted as redlines. As noted in the attached charter, these are the recommendations for implementation: Recommendation 24: That the GNSO Council and Stakeholder Groups and Constituencies adhere to the published process for applications for new Constituencies. That the ICANN Board in assessing an application satisfy itself that all parties have followed the published process, subject to which the default outcome is that a new Constituency is admitted. That all applications for new Constituencies, including historic applications, be published on the ICANN website with full transparency of decision-making. Recommendation 25: That the GNSO Council commission the development of, and implement, guidelines to provide assistance for groups wishing to establish a new Constituency. Working Group members are requested to respond to this review in one week, by COB Thursday, 15 June. If no comments are received during the review period staff will accept the changes and circulate the final version of the charter for a two-week Consensus Call. Best regards, Julie Julie Hedlund, Policy Director Action Items/Discussion Notes 08 June Action Items: Contracted Party House Membership: Staff will provide details concerning membership processes, particularly with respect to interest groups or non-contracted parties, and add these to the Google Document for tracking overarching or out-of-scope questions. Charter for Recommendations 24/25: 1) Revise the charter to indicate that the Working Group has discussed the following action from the GNSO Review Working Party: “determine whether or not there is a presumption that a new Constituency should be admitted if all requirements are met and if such a presumption is appropriate” and the Working Group determined that there is not a presumption that a new Constituency should be admitted if all requirements are met since a Constituency applicant could fail the evaluation process by the Board or the Stakeholder Group if it did not meet the criteria; 2) include the Process for Recognition of New GNSO Constituencies as an attachment in the revised charter; 3) circulate the revised document for one week and if no comments are received initiate a Call for Consensus for two weeks. Charter for Recommendations 10/11: Send the charter to the list for review and to initiate discussion. Continue discussion at the meeting on 22 June. Discussion Notes: 1. Charter for Recommendation 16: -- Call for Consensus closed on 29 May. There were no objections to the implementation charter so it is approved by full consensus. -- See the wiki for status on Consensus Calls and Charters under review at: https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Cons…. 2. Continue Discussion of Charter for Recommendations 24/25: -- Question: Referring to documents regarding the process. Would it be necessary dive into the process itself -- such as the duration? Looking at the flow chart could be as short as 3 months, but could be longer. Are there specific criteria that must be met? Answer: It would seem that an analysis of the process itself would be out of scope of these recommendations, which only address whether the process is followed, is transparent, and if guidelines exist. -- Question of presumption of the default outcome: Is it appropriate? What are the options for the Working Group? Answer: The Working Group could decide whether the presumption of admission (the “default outcome”) is appropriate given the fact that even if a new Constituency has met the criteria, it still could fail the evaluation by the Stakeholder Group or the Board for other reasons. If it decides it is appropriate then the Working Group may need to suggest changes to the constituency application and evaluation process. If it decides it is not appropriate then the process does not need to be modified, but the Working Group should call out the fact that this part of Recommendation 24 “subject to which the default outcome is that a new Constituency is admitted” may not be applied if a Constituency is deemed not to meet the criteria in the evaluation process. -- Where is the bar in anticipation of participation? There is some peril in not having objective criteria in terms of effectiveness or activity. The idea of active participation is too loose. -- NPOC is the only new constituency and those rules grew out of the stress and tension of trying to create a new constituency. NCSG wanted to just have interest groups, but rules were developed to accommodate the need for a group that said they wanted a constituency. NPOC was the only one that made it through the process. -- Have we set the bar so high that it sets a deterrent? Should we be looking at the criteria? Should the criteria be as objective as possible? -- Is this process transparent enough? Do we make changes to the process or not? -- The criteria have a value. We have a balance to ensure that they are active and grow to find their mission. Important to have high bars. >From the Chat: avri doria: Perhaps this is Off Topic, but why do we have a Staff/Board imposed process for new constituencies in NCPH but not in CPH? i have never understood this imbalance. avri doria: Thanks, I missed last week's mtg. Marika Konings: My recollection is similar, because the contracted aspect creates an automatic qualifying criteria it was deemed not necessary to create a process (either you have a contract and you can join through a set membership process, or you don't). avri doria: This relates to membership in the SGs, but not to the creation of constituencies. Marika Konings: Correct, but I believe linked to that on the contracted party side the view was that there was no need for constituencies as everyone is a contracted party (registry or registrar). But to get the real insight into this, we may need to dig into history and ask those directly involved in that decision. avri doria: They call it an interest group instead of a constituency. but the NCPH is nt allowed to have interest groups instead of constituencies. Marika Konings: I think the interest group concept was created to address the interest of those wanting to participate but not yet qualifying as contracted parties as they had not signed a contract with ICANN yet. I don't know if that concept still exists, even though there are groups that are organized in a certain way such as the Geo Names and BRG. It might be interesting to see whether there is further discussion in those groups around this as, for example, in the near future there will potentially be a new group of contracted parties (P/P providers) and in the past, there has also been mention of escrow providers as a specific group of contracted parties. avri doria: I was deeply involved in that particular set of events. Amr Elsadr: Apart from a constituency application that was outright rejected, there was also an applicant that made it through to the candidate constituency phase in the NCSG for a few years, but it didn't make it to full constituency status. Lori Schulman: Amr: who was the applicant that "partially" made it Amr Elsadr: The Consumer Constituency. avri doria: yes, I was part of the effort to start the consumer constituency in NCSG, but it never got sufficient participant support within the candidate constituency to meet the requirements of both the ICANN process & the NCSG requirements for active participation. Lori Schulman: Diversity is a good point and objective Amr Elsadr: The CCAOI application did not meet the diversity criteria in more than one way, which is one of the reasons the application was rejected. avri doria: A presumption of acceptance would be hard for everyone, but even harder for CSG as that would change the number of seats each of the existing constituencies could hold. Since council seats in the NCSG are based on an SG wide selection process, its model can support a multitude of constituencies if they met the conditions without any change to council seating except through elections at the SG level.

1 0