*Jim. please see a reply from Jeff and me interspaced below...* On Sat, 12 Dec 2020 at 03:23, Jim Prendergast <jim@galwaysg.com> wrote:

Jorge – I am sympathetic to your concerns. Ironically, ICANN org will be closed for a good period of time during that window so governments are not unique.

I have a different question.

With this extension of the timeline, should the WG be notifying the GNSO Council that we will be missing the Dec 23rd deadline? *We (Jeff and I) notified Council at the same time as this list was updated...* And what are the consequence of that? *They are, we believe, discussing it and it is possible that when Flip provides his scheduled update on the meeting of the 17th any such consequences will become clear to us all...* Do we need to file for an extension? *We believe that will be resolved by Council at the December Meeting as well if so resolved then Jeff and I will lodge such an extention...*

I’m admittedly not a PDP 3.0 expert so welcome other’s insight here.

Jim Prendergast

The Galway Strategy Group

+1 202-285-3699

*From:* Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> *On Behalf Of *Jorge.Cancio--- via Gnso-newgtld-wg *Sent:* Friday, December 11, 2020 9:11 AM *To:* jeff@jjnsolutions.com; gnso-newgtld-wg@icann.org *Subject:* Re: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls

Dear Jeff and all

Thanks very much for this email!

Speaking personally, I’m afraid that the proposed timeline with consensus calls over the holiday break (at least in the Northern hemisphere) is not very helpful.

At least for those of us needing to do extensive consultations (be it inside a Government or within a larger community) such dates are completely unworkable.

Not sure how others feel about this…

Personally, I would suggest starting the consensus calls once we are back from the break, e.g. on January 4th.

In addition, I feel that for the same reasons (need for consultations etc.) the time allotted between consensus designations by the co-chairs and the deadline for submitting minority reports should be significantly extended (e.g. at least to one full week).

Hope this is doable…

Kind regards

Jorge

*Von:* Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> *Im Auftrag von *Jeff Neuman *Gesendet:* Freitag, 11. Dezember 2020 06:08 *An:* gnso-newgtld-wg@icann.org *Betreff:* [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls

All,

The Leadership Team met a few hours ago to discuss a number of issues including how to get to the finish line……We are nearly there!

As discussed on the last call (about 24 hours ago), we are making the following changes to the Work Plan:

- *11 December 2020* - Latest Redline of Final Report containing changes from all topics discussed to date as well as changes (if any) as a result of the 9 Topical E-mails - Meeting of the small team on Auctions to see if there can be any recommendations to the Full Working Group - *14 December 2020* - Discussing (a) Auctions Topic (results if any from small team; (b) Conflicts of Interest, (c) Applicant Freedom of Expression, and (d) Dispute Resolution Procedures after Delegation. - *15 December 2020* - Comments due to 11 December 2020 Redline - Release of Any redlines to as a result of the topics discussed on 14 December 2020 - *17 December 2020* - Comments due to December 15 Redline - Working Group Call (already on your calendars) to close out any last issues - Content Freeze / Lockdown – Other than if there are any changes to close out last issues, all content is locked down for the Consensus Call - *22 December 2020* - Final Report is released to the Working Group - Commencement of Consensus Call (See some notes below) - *5 January 2020* - Consensus Call Ends - *6 January 2020* - Designation of Levels of Support by Working Group Leadership Team - *7 January 2020* - Call of the Working Group to discuss designations, answer questions, and hopefully celebrate a job well done - *8 January 2020* - Challenges to Designation of Levels of Support by Working Group Leadership Team are due (if any) - Minority Reports (if any) are due - *11 January 2020* - Final Report delivered to the Council - Document Deadline for discussion during January’s GNSO Council Meeting

*Some Notes*

1. A longer note will follow in the next couple of days on how we will structure the Consensus Call. We strongly recommend that if you were not on the last working group call on 10 December 2020 at 03:00 UTC, please do go back and review at least the first 15-20 minutes of the call. (Link to Call <https://community.icann.org/display/NGSPP/2020-12-07+New+gTLD+Subsequent+Pro...> )

1. Although more details will be provided later: 1. Leadership will be grouping the Topics into batches for purposes of the Consensus Calls. We will not be voting on each recommendation / implementation guidance separately (as there are several hundred of them). 2. We will do our best to only include in the batches the lesser controversial topics; stated differently, Leadership has a sense of which sections should be supported by either full consensus or (rough) consensus. Of course we could always be wrong, but we will do our best.

i. If there is a batch that contains a part that you do not support, then in the Consensus Call, we will ask you specifically which element or elements do you not support. In other words, if we grouped topics 1,2 and 3 together and you indicate that you do not support the batch, you will be asked to specify which of the Topics you do not support, and which element(s) within that topic you do not support. We will assume that the topics / elements you do not list are ones that you would support. So being specific will be important.

1. Topics where we can already foresee that there will be a difference of opinion (eg., Closed Generics, Mechanisms of Last Resort), we will make sure we have those topics in the Consensus Call on their own (i.e., not in batches with other topics). 2. All expressions of support / non support during the Consensus Call MUST be submitted through the formal mailing list. We will not be counting any responses to the Consensus Call that are not submitted on the list. It is critical that all of the information is on the record and documented. 3. The Consensus Call is NOT A VOTE – Leadership will not be determining levels of support based on the quantity of responses, but will take into consideration other factors such as the groups with whom an individual associates, etc. 4. We will be following Section 3.6 of the Working Group Guidelines ( https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-gn... ).

1. Minority Reports are due just 2 days after the designation of Levels of Consensus. We know that is not a lot of time. However, given that we have had a draft final report, comments to the draft final report, extensive discussions of those comments of the draft final report, and you have seen several redlines already, we believe that if you disagree with the way the group is heading, you should pretty much know that now. There is no reason to wait until the designations of levels of support to start drafting. In fact, I am told that the ALAC has already been working on a minority report to certain topics for some time now. *Bottom Line – you can start working on any minority report now. The worst thing that will happen is that you draft your report and there is a consensus call surprise where you find out you may not be in the minority and you decide not to submit the statement **😊*

1. We are nearly there!!!!!!!!!

Thanks.

Your humble Leadership Team,

Cheryl and Jeff – Co-Chairs

*With very special thanks to Martin, Annabeth, Robin and Flip who have been participating in Leadership calls for many months and providing valuable insight & of course to Steve, Emily and Julie, without whom, none of this would be possible*

_______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-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.

After listening to the Dec 10 call (which I could not attend), I have to say that normally a Minority Statement will require coordination with others to determine how many will join in the Minority Statement. It is pretty much impossible to do that in 2 days. You said on the call that WG members should know what the consensus designation will be but you also said that Leadership doesn’t know and that Leadership will have to take into account a number of different factors, not just the number of WG members who support a particular consensus designation. Then you said we could be surprised to find that Leadership did not find a consensus and so we might not need to file a Minority Statement. This is all very “loosey-goosey” so in fact, it’s not possible for WG members to draft and develop support for Minority Statements at this time except on issues that are major like Closed Generics, Auctions, etc. It’s important, in drafting a Minority Statement, to know whether Leadership will designate the section as Full Consensus, Rough Consensus, or Strong Support. A WG member can’t draft a proper Minority Statement without knowing what the designation is and reviewing notes/calls to say whether or not s(he) agrees with that designation. And there is no way to develop support for that draft Minority Statement in our constituencies or otherwise within 2 days. Thank you, Anne From: Aikman-Scalese, Anne Sent: Friday, December 11, 2020 8:37 AM To: 'Jorge.Cancio@bakom.admin.ch' <Jorge.Cancio@bakom.admin.ch>; jeff@jjnsolutions.com Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls +1. Regarding the following, this is not at all a reasonable expectation: Minority Reports are due just 2 days after the designation of Levels of Consensus. From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> On Behalf Of Jorge.Cancio--- via Gnso-newgtld-wg Sent: Friday, December 11, 2020 7:11 AM To: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls [EXTERNAL] ________________________________ Dear Jeff and all Thanks very much for this email! Speaking personally, I’m afraid that the proposed timeline with consensus calls over the holiday break (at least in the Northern hemisphere) is not very helpful. At least for those of us needing to do extensive consultations (be it inside a Government or within a larger community) such dates are completely unworkable. Not sure how others feel about this… Personally, I would suggest starting the consensus calls once we are back from the break, e.g. on January 4th. In addition, I feel that for the same reasons (need for consultations etc.) the time allotted between consensus designations by the co-chairs and the deadline for submitting minority reports should be significantly extended (e.g. at least to one full week). Hope this is doable… Kind regards Jorge Von: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> Im Auftrag von Jeff Neuman Gesendet: Freitag, 11. Dezember 2020 06:08 An: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Betreff: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls All, The Leadership Team met a few hours ago to discuss a number of issues including how to get to the finish line……We are nearly there! As discussed on the last call (about 24 hours ago), we are making the following changes to the Work Plan: * 11 December 2020 * Latest Redline of Final Report containing changes from all topics discussed to date as well as changes (if any) as a result of the 9 Topical E-mails * Meeting of the small team on Auctions to see if there can be any recommendations to the Full Working Group * 14 December 2020 * Discussing (a) Auctions Topic (results if any from small team; (b) Conflicts of Interest, (c) Applicant Freedom of Expression, and (d) Dispute Resolution Procedures after Delegation. * 15 December 2020 * Comments due to 11 December 2020 Redline * Release of Any redlines to as a result of the topics discussed on 14 December 2020 * 17 December 2020 * Comments due to December 15 Redline * Working Group Call (already on your calendars) to close out any last issues * Content Freeze / Lockdown – Other than if there are any changes to close out last issues, all content is locked down for the Consensus Call * 22 December 2020 * Final Report is released to the Working Group * Commencement of Consensus Call (See some notes below) * 5 January 2020 * Consensus Call Ends * 6 January 2020 * Designation of Levels of Support by Working Group Leadership Team * 7 January 2020 * Call of the Working Group to discuss designations, answer questions, and hopefully celebrate a job well done * 8 January 2020 * Challenges to Designation of Levels of Support by Working Group Leadership Team are due (if any) * Minority Reports (if any) are due * 11 January 2020 * Final Report delivered to the Council * Document Deadline for discussion during January’s GNSO Council Meeting Some Notes 1. A longer note will follow in the next couple of days on how we will structure the Consensus Call. We strongly recommend that if you were not on the last working group call on 10 December 2020 at 03:00 UTC, please do go back and review at least the first 15-20 minutes of the call. (Link to Call<https://community.icann.org/display/NGSPP/2020-12-07+New+gTLD+Subsequent+Pro...>) 1. Although more details will be provided later: * Leadership will be grouping the Topics into batches for purposes of the Consensus Calls. We will not be voting on each recommendation / implementation guidance separately (as there are several hundred of them). * We will do our best to only include in the batches the lesser controversial topics; stated differently, Leadership has a sense of which sections should be supported by either full consensus or (rough) consensus. Of course we could always be wrong, but we will do our best. i. If there is a batch that contains a part that you do not support, then in the Consensus Call, we will ask you specifically which element or elements do you not support. In other words, if we grouped topics 1,2 and 3 together and you indicate that you do not support the batch, you will be asked to specify which of the Topics you do not support, and which element(s) within that topic you do not support. We will assume that the topics / elements you do not list are ones that you would support. So being specific will be important. * Topics where we can already foresee that there will be a difference of opinion (eg., Closed Generics, Mechanisms of Last Resort), we will make sure we have those topics in the Consensus Call on their own (i.e., not in batches with other topics). * All expressions of support / non support during the Consensus Call MUST be submitted through the formal mailing list. We will not be counting any responses to the Consensus Call that are not submitted on the list. It is critical that all of the information is on the record and documented. * The Consensus Call is NOT A VOTE – Leadership will not be determining levels of support based on the quantity of responses, but will take into consideration other factors such as the groups with whom an individual associates, etc. * We will be following Section 3.6 of the Working Group Guidelines (https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-gn...). 1. Minority Reports are due just 2 days after the designation of Levels of Consensus. We know that is not a lot of time. However, given that we have had a draft final report, comments to the draft final report, extensive discussions of those comments of the draft final report, and you have seen several redlines already, we believe that if you disagree with the way the group is heading, you should pretty much know that now. There is no reason to wait until the designations of levels of support to start drafting. In fact, I am told that the ALAC has already been working on a minority report to certain topics for some time now. Bottom Line – you can start working on any minority report now. The worst thing that will happen is that you draft your report and there is a consensus call surprise where you find out you may not be in the minority and you decide not to submit the statement 😊 1. We are nearly there!!!!!!!!! Thanks. Your humble Leadership Team, Cheryl and Jeff – Co-Chairs With very special thanks to Martin, Annabeth, Robin and Flip who have been participating in Leadership calls for many months and providing valuable insight & of course to Steve, Emily and Julie, without whom, none of this would be possible ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

Anne, This is not what we are saying. There is a difference between a Minority Viewpoint and a Minority Report. 1. When Cheryl and I indicate level of support, if there is full consensus, then there obviously would be no minority view. 2. If we determine that there is Consensus, then according to the definition, we will have found that “only a small minority disagrees…” We do not need a Minority Report or documentation of the Minority Viewpoint to determine that a small minority of members disagree. 3. If we determine that there is Strong Support but significant opposition, again we will have determined that there is a larger, but still minority group of members, that disagree. Once we set forth the levels of support designations, then (and only then) will the Working Group Leadership accept documented “Minority View”. As stated in 3.6, “Documentation of Minority View recommendations normally depends on text offered by the proponent(s).” And by “proponent(s)”, that means Working Group Member(s), not by ACs, SGs or Cs. We expect that all those responding to a Consensus Call will do so on their own behalf and not necessarily on behalf of the Cs, SGc, or ACs. The Cs, SGs and ACs have not been involved in all of the discussions and have not been part of the compromises which needed to be made. In many ways, requiring input from your Cs, SGs and ACs, could have the negative affect of undoing our many years’ worth of work. Now of course we cannot tell you how to respond to the Consensus Call. But we can urge you to respond as a Working Group member. I hope this helps. [cid:image002.png@01D6D212.5E6E4EA0] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: Aikman-Scalese, Anne <AAikman@lrrc.com> Sent: Monday, December 14, 2020 11:32 AM To: Jorge.Cancio@bakom.admin.ch; Jeff Neuman <jeff@jjnsolutions.com> Cc: gnso-newgtld-wg@icann.org Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls Jeff and Cheryl, It sounds as though you are saying there will be no Minority Viewpoints expressed from our deliberations when you publish the Consensus call. Is that the case? Then if that is the case, are you saying that only Leadership will determine when a Minority Viewpoint exists after receiving something you call a “minority report”? How does the process you described on the call allow for the drafter of a proposed Minority Viewpoint to develop support – given that a Minority Viewpoint is not supposed to be an individual viewpoint but is rather supported by “a small number of people”? From the WG Guidelines: •MinorityView-refers to a proposal where a small number of people support the recommendation.This can happen in response to a Consensus, Strong support but significant opposition, and No Consensus; or,it can happen in cases where there is neither support nor opposition to a suggestion made by a small number of individuals. In cases of Consensus, Strong support but significant opposition, and NoConsensus, an effort should be made to document that variance in viewpoint and to present any Minority View recommendations that may have been made. Documentation of Minority View recommendations normally depends on text offered by the proponent(s). In all cases of Divergence, the WG Chair should encourage the submission of minority viewpoint(s). From: Aikman-Scalese, Anne Sent: Friday, December 11, 2020 2:15 PM To: 'Jorge.Cancio@bakom.admin.ch' <Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>>; 'jeff@jjnsolutions.com' <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls After listening to the Dec 10 call (which I could not attend), I have to say that normally a Minority Statement will require coordination with others to determine how many will join in the Minority Statement. It is pretty much impossible to do that in 2 days. You said on the call that WG members should know what the consensus designation will be but you also said that Leadership doesn’t know and that Leadership will have to take into account a number of different factors, not just the number of WG members who support a particular consensus designation. Then you said we could be surprised to find that Leadership did not find a consensus and so we might not need to file a Minority Statement. This is all very “loosey-goosey” so in fact, it’s not possible for WG members to draft and develop support for Minority Statements at this time except on issues that are major like Closed Generics, Auctions, etc. It’s important, in drafting a Minority Statement, to know whether Leadership will designate the section as Full Consensus, Rough Consensus, or Strong Support. A WG member can’t draft a proper Minority Statement without knowing what the designation is and reviewing notes/calls to say whether or not s(he) agrees with that designation. And there is no way to develop support for that draft Minority Statement in our constituencies or otherwise within 2 days. Thank you, Anne From: Aikman-Scalese, Anne Sent: Friday, December 11, 2020 8:37 AM To: 'Jorge.Cancio@bakom.admin.ch' <Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>>; jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls +1. Regarding the following, this is not at all a reasonable expectation: Minority Reports are due just 2 days after the designation of Levels of Consensus. From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> On Behalf Of Jorge.Cancio--- via Gnso-newgtld-wg Sent: Friday, December 11, 2020 7:11 AM To: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls [EXTERNAL] ________________________________ Dear Jeff and all Thanks very much for this email! Speaking personally, I’m afraid that the proposed timeline with consensus calls over the holiday break (at least in the Northern hemisphere) is not very helpful. At least for those of us needing to do extensive consultations (be it inside a Government or within a larger community) such dates are completely unworkable. Not sure how others feel about this… Personally, I would suggest starting the consensus calls once we are back from the break, e.g. on January 4th. In addition, I feel that for the same reasons (need for consultations etc.) the time allotted between consensus designations by the co-chairs and the deadline for submitting minority reports should be significantly extended (e.g. at least to one full week). Hope this is doable… Kind regards Jorge Von: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> Im Auftrag von Jeff Neuman Gesendet: Freitag, 11. Dezember 2020 06:08 An: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Betreff: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls All, The Leadership Team met a few hours ago to discuss a number of issues including how to get to the finish line……We are nearly there! As discussed on the last call (about 24 hours ago), we are making the following changes to the Work Plan: * 11 December 2020 * Latest Redline of Final Report containing changes from all topics discussed to date as well as changes (if any) as a result of the 9 Topical E-mails * Meeting of the small team on Auctions to see if there can be any recommendations to the Full Working Group * 14 December 2020 * Discussing (a) Auctions Topic (results if any from small team; (b) Conflicts of Interest, (c) Applicant Freedom of Expression, and (d) Dispute Resolution Procedures after Delegation. * 15 December 2020 * Comments due to 11 December 2020 Redline * Release of Any redlines to as a result of the topics discussed on 14 December 2020 * 17 December 2020 * Comments due to December 15 Redline * Working Group Call (already on your calendars) to close out any last issues * Content Freeze / Lockdown – Other than if there are any changes to close out last issues, all content is locked down for the Consensus Call * 22 December 2020 * Final Report is released to the Working Group * Commencement of Consensus Call (See some notes below) * 5 January 2020 * Consensus Call Ends * 6 January 2020 * Designation of Levels of Support by Working Group Leadership Team * 7 January 2020 * Call of the Working Group to discuss designations, answer questions, and hopefully celebrate a job well done * 8 January 2020 * Challenges to Designation of Levels of Support by Working Group Leadership Team are due (if any) * Minority Reports (if any) are due * 11 January 2020 * Final Report delivered to the Council * Document Deadline for discussion during January’s GNSO Council Meeting Some Notes 1. A longer note will follow in the next couple of days on how we will structure the Consensus Call. We strongly recommend that if you were not on the last working group call on 10 December 2020 at 03:00 UTC, please do go back and review at least the first 15-20 minutes of the call. (Link to Call<https://community.icann.org/display/NGSPP/2020-12-07+New+gTLD+Subsequent+Pro...>) 1. Although more details will be provided later: * Leadership will be grouping the Topics into batches for purposes of the Consensus Calls. We will not be voting on each recommendation / implementation guidance separately (as there are several hundred of them). * We will do our best to only include in the batches the lesser controversial topics; stated differently, Leadership has a sense of which sections should be supported by either full consensus or (rough) consensus. Of course we could always be wrong, but we will do our best. i. If there is a batch that contains a part that you do not support, then in the Consensus Call, we will ask you specifically which element or elements do you not support. In other words, if we grouped topics 1,2 and 3 together and you indicate that you do not support the batch, you will be asked to specify which of the Topics you do not support, and which element(s) within that topic you do not support. We will assume that the topics / elements you do not list are ones that you would support. So being specific will be important. * Topics where we can already foresee that there will be a difference of opinion (eg., Closed Generics, Mechanisms of Last Resort), we will make sure we have those topics in the Consensus Call on their own (i.e., not in batches with other topics). * All expressions of support / non support during the Consensus Call MUST be submitted through the formal mailing list. We will not be counting any responses to the Consensus Call that are not submitted on the list. It is critical that all of the information is on the record and documented. * The Consensus Call is NOT A VOTE – Leadership will not be determining levels of support based on the quantity of responses, but will take into consideration other factors such as the groups with whom an individual associates, etc. * We will be following Section 3.6 of the Working Group Guidelines (https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-gn...). 1. Minority Reports are due just 2 days after the designation of Levels of Consensus. We know that is not a lot of time. However, given that we have had a draft final report, comments to the draft final report, extensive discussions of those comments of the draft final report, and you have seen several redlines already, we believe that if you disagree with the way the group is heading, you should pretty much know that now. There is no reason to wait until the designations of levels of support to start drafting. In fact, I am told that the ALAC has already been working on a minority report to certain topics for some time now. Bottom Line – you can start working on any minority report now. The worst thing that will happen is that you draft your report and there is a consensus call surprise where you find out you may not be in the minority and you decide not to submit the statement 😊 1. We are nearly there!!!!!!!!! Thanks. Your humble Leadership Team, Cheryl and Jeff – Co-Chairs With very special thanks to Martin, Annabeth, Robin and Flip who have been participating in Leadership calls for many months and providing valuable insight & of course to Steve, Emily and Julie, without whom, none of this would be possible ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

Anne, The request several years ago for official representatives was met with a lot of controversy and was eventually dropped. It was initially intended to ensure that the Working Group was hearing all of the positions from all of the ICANN stakeholder, which did happen. That should not be confused with the ultimate results of a consensus call. In the case of Closed Generics, assuming there is Divergence (and I am not assuming that), but if there is, then I believe our rationale section already documents all of the views that have been expressed. That is already in the body of the Report. But if a working group member wants to submit an additional statement that they want appended to the report on Closed Generics, then they are free to do so. Sorry Anne, I am just not sure what there is a disagreement about here. What am I missing? [cid:image001.png@01D6D217.3648CDB0] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: Aikman-Scalese, Anne <AAikman@lrrc.com> Sent: Monday, December 14, 2020 12:28 PM To: Jeff Neuman <jeff@jjnsolutions.com>; Jorge.Cancio@bakom.admin.ch Cc: gnso-newgtld-wg@icann.org Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls Thanks Jeff. So, for example, in the Consensus designation on Closed Generics, Leadership would simply say “No Consensus” or “Divergence”, would not state any Minority Views and will require additional individual “minority reports” of individual WG members rather than including the Minority Views discussed to date in our deliberations? I note that the WG guidelines state that in the case of Divergence, Minority Views should be “encouraged”. To me, that means that Leadership should encourage Minority Views to be expressed and to allow time for WG members to develop support for those. That support would be developed among WG members (and not necessarily in their constituency) and that takes time. (The GAC has asked for a week.) A couple of years ago you asked for constituencies to designate representatives and you said that Leadership would need to take into account the views of representatives as possibly more weighty than individual views. Now you are saying constituencies can’t file Minority Views because they have other channels for providing advice? Please clarify. Anne From: Jeff Neuman <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Sent: Monday, December 14, 2020 10:12 AM To: Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>>; Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls [EXTERNAL] ________________________________ Anne, This is not what we are saying. There is a difference between a Minority Viewpoint and a Minority Report. 1. When Cheryl and I indicate level of support, if there is full consensus, then there obviously would be no minority view. 2. If we determine that there is Consensus, then according to the definition, we will have found that “only a small minority disagrees…” We do not need a Minority Report or documentation of the Minority Viewpoint to determine that a small minority of members disagree. 3. If we determine that there is Strong Support but significant opposition, again we will have determined that there is a larger, but still minority group of members, that disagree. Once we set forth the levels of support designations, then (and only then) will the Working Group Leadership accept documented “Minority View”. As stated in 3.6, “Documentation of Minority View recommendations normally depends on text offered by the proponent(s).” And by “proponent(s)”, that means Working Group Member(s), not by ACs, SGs or Cs. We expect that all those responding to a Consensus Call will do so on their own behalf and not necessarily on behalf of the Cs, SGc, or ACs. The Cs, SGs and ACs have not been involved in all of the discussions and have not been part of the compromises which needed to be made. In many ways, requiring input from your Cs, SGs and ACs, could have the negative affect of undoing our many years’ worth of work. Now of course we cannot tell you how to respond to the Consensus Call. But we can urge you to respond as a Working Group member. I hope this helps. [cid:image004.png@01D6D216.E829B810] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>> Sent: Monday, December 14, 2020 11:32 AM To: Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>; Jeff Neuman <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls Jeff and Cheryl, It sounds as though you are saying there will be no Minority Viewpoints expressed from our deliberations when you publish the Consensus call. Is that the case? Then if that is the case, are you saying that only Leadership will determine when a Minority Viewpoint exists after receiving something you call a “minority report”? How does the process you described on the call allow for the drafter of a proposed Minority Viewpoint to develop support – given that a Minority Viewpoint is not supposed to be an individual viewpoint but is rather supported by “a small number of people”? From the WG Guidelines: •MinorityView-refers to a proposal where a small number of people support the recommendation.This can happen in response to a Consensus, Strong support but significant opposition, and No Consensus; or,it can happen in cases where there is neither support nor opposition to a suggestion made by a small number of individuals. In cases of Consensus, Strong support but significant opposition, and NoConsensus, an effort should be made to document that variance in viewpoint and to present any Minority View recommendations that may have been made. Documentation of Minority View recommendations normally depends on text offered by the proponent(s). In all cases of Divergence, the WG Chair should encourage the submission of minority viewpoint(s). From: Aikman-Scalese, Anne Sent: Friday, December 11, 2020 2:15 PM To: 'Jorge.Cancio@bakom.admin.ch' <Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>>; 'jeff@jjnsolutions.com' <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls After listening to the Dec 10 call (which I could not attend), I have to say that normally a Minority Statement will require coordination with others to determine how many will join in the Minority Statement. It is pretty much impossible to do that in 2 days. You said on the call that WG members should know what the consensus designation will be but you also said that Leadership doesn’t know and that Leadership will have to take into account a number of different factors, not just the number of WG members who support a particular consensus designation. Then you said we could be surprised to find that Leadership did not find a consensus and so we might not need to file a Minority Statement. This is all very “loosey-goosey” so in fact, it’s not possible for WG members to draft and develop support for Minority Statements at this time except on issues that are major like Closed Generics, Auctions, etc. It’s important, in drafting a Minority Statement, to know whether Leadership will designate the section as Full Consensus, Rough Consensus, or Strong Support. A WG member can’t draft a proper Minority Statement without knowing what the designation is and reviewing notes/calls to say whether or not s(he) agrees with that designation. And there is no way to develop support for that draft Minority Statement in our constituencies or otherwise within 2 days. Thank you, Anne From: Aikman-Scalese, Anne Sent: Friday, December 11, 2020 8:37 AM To: 'Jorge.Cancio@bakom.admin.ch' <Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>>; jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls +1. Regarding the following, this is not at all a reasonable expectation: Minority Reports are due just 2 days after the designation of Levels of Consensus. From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> On Behalf Of Jorge.Cancio--- via Gnso-newgtld-wg Sent: Friday, December 11, 2020 7:11 AM To: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls [EXTERNAL] ________________________________ Dear Jeff and all Thanks very much for this email! Speaking personally, I’m afraid that the proposed timeline with consensus calls over the holiday break (at least in the Northern hemisphere) is not very helpful. At least for those of us needing to do extensive consultations (be it inside a Government or within a larger community) such dates are completely unworkable. Not sure how others feel about this… Personally, I would suggest starting the consensus calls once we are back from the break, e.g. on January 4th. In addition, I feel that for the same reasons (need for consultations etc.) the time allotted between consensus designations by the co-chairs and the deadline for submitting minority reports should be significantly extended (e.g. at least to one full week). Hope this is doable… Kind regards Jorge Von: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> Im Auftrag von Jeff Neuman Gesendet: Freitag, 11. Dezember 2020 06:08 An: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Betreff: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls All, The Leadership Team met a few hours ago to discuss a number of issues including how to get to the finish line……We are nearly there! As discussed on the last call (about 24 hours ago), we are making the following changes to the Work Plan: * 11 December 2020 * Latest Redline of Final Report containing changes from all topics discussed to date as well as changes (if any) as a result of the 9 Topical E-mails * Meeting of the small team on Auctions to see if there can be any recommendations to the Full Working Group * 14 December 2020 * Discussing (a) Auctions Topic (results if any from small team; (b) Conflicts of Interest, (c) Applicant Freedom of Expression, and (d) Dispute Resolution Procedures after Delegation. * 15 December 2020 * Comments due to 11 December 2020 Redline * Release of Any redlines to as a result of the topics discussed on 14 December 2020 * 17 December 2020 * Comments due to December 15 Redline * Working Group Call (already on your calendars) to close out any last issues * Content Freeze / Lockdown – Other than if there are any changes to close out last issues, all content is locked down for the Consensus Call * 22 December 2020 * Final Report is released to the Working Group * Commencement of Consensus Call (See some notes below) * 5 January 2020 * Consensus Call Ends * 6 January 2020 * Designation of Levels of Support by Working Group Leadership Team * 7 January 2020 * Call of the Working Group to discuss designations, answer questions, and hopefully celebrate a job well done * 8 January 2020 * Challenges to Designation of Levels of Support by Working Group Leadership Team are due (if any) * Minority Reports (if any) are due * 11 January 2020 * Final Report delivered to the Council * Document Deadline for discussion during January’s GNSO Council Meeting Some Notes 1. A longer note will follow in the next couple of days on how we will structure the Consensus Call. We strongly recommend that if you were not on the last working group call on 10 December 2020 at 03:00 UTC, please do go back and review at least the first 15-20 minutes of the call. (Link to Call<https://community.icann.org/display/NGSPP/2020-12-07+New+gTLD+Subsequent+Pro...>) 1. Although more details will be provided later: * Leadership will be grouping the Topics into batches for purposes of the Consensus Calls. We will not be voting on each recommendation / implementation guidance separately (as there are several hundred of them). * We will do our best to only include in the batches the lesser controversial topics; stated differently, Leadership has a sense of which sections should be supported by either full consensus or (rough) consensus. Of course we could always be wrong, but we will do our best. i. If there is a batch that contains a part that you do not support, then in the Consensus Call, we will ask you specifically which element or elements do you not support. In other words, if we grouped topics 1,2 and 3 together and you indicate that you do not support the batch, you will be asked to specify which of the Topics you do not support, and which element(s) within that topic you do not support. We will assume that the topics / elements you do not list are ones that you would support. So being specific will be important. * Topics where we can already foresee that there will be a difference of opinion (eg., Closed Generics, Mechanisms of Last Resort), we will make sure we have those topics in the Consensus Call on their own (i.e., not in batches with other topics). * All expressions of support / non support during the Consensus Call MUST be submitted through the formal mailing list. We will not be counting any responses to the Consensus Call that are not submitted on the list. It is critical that all of the information is on the record and documented. * The Consensus Call is NOT A VOTE – Leadership will not be determining levels of support based on the quantity of responses, but will take into consideration other factors such as the groups with whom an individual associates, etc. * We will be following Section 3.6 of the Working Group Guidelines (https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-gn...). 1. Minority Reports are due just 2 days after the designation of Levels of Consensus. We know that is not a lot of time. However, given that we have had a draft final report, comments to the draft final report, extensive discussions of those comments of the draft final report, and you have seen several redlines already, we believe that if you disagree with the way the group is heading, you should pretty much know that now. There is no reason to wait until the designations of levels of support to start drafting. In fact, I am told that the ALAC has already been working on a minority report to certain topics for some time now. Bottom Line – you can start working on any minority report now. The worst thing that will happen is that you draft your report and there is a consensus call surprise where you find out you may not be in the minority and you decide not to submit the statement 😊 1. We are nearly there!!!!!!!!! Thanks. Your humble Leadership Team, Cheryl and Jeff – Co-Chairs With very special thanks to Martin, Annabeth, Robin and Flip who have been participating in Leadership calls for many months and providing valuable insight & of course to Steve, Emily and Julie, without whom, none of this would be possible ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

Jeff, Where do you see reference to an individual “minority report” in the WG Guidelines? The GNSO Council and the ICANN Board, when reviewing the Consensus designations, should be able to understand a Minority View as defined by the Consensus Guidelines without having to read the entire report or numerous individual “minority reports” appended to the entire report as described on Monday’s call. The reference in the Consensus Call section of the WG Guidelines is to “proponent(s)” of the “text” – this can be either singular (individual) or plural and refers to one text. “In cases of Consensus, Strong support but significant opposition, and NoConsensus, an effort should be made to document that variance in viewpoint and to present any Minority View recommendations that may have been made. Documentation of Minority View recommendations normally depends on text offered by the proponent(s). In all cases of Divergence, the WG Chair should encourage the submission of minority viewpoint(s).” So, by way of example, those of us who support Greg Shatan’s suggestion to allow applications for Closed Generics, but to suspend those applications pending further policy work, thereby increasing predictability for applicants, could submit a Minority View on that topic. We should be able to put the text of that Minority View out on the list in order to develop more support for the Minority View and to permit Leadership to gauge the level of support. Requiring us to submit individual views would simply constitute more work for everyone involved and would “splinter” the effort. Under your procedure as described on Monday’s call, Greg would have to put out text to the list and ask any and all who support his idea to each file an individual “minority report”. This does not make sense. I urge you and Cheryl to reconsider the above and to facilitate submission by “a small number of individuals” of a “Minority View” as described in the WG Guidelines . Admittedly, a “Minority View” as defined in the Consensus call section should be short and a word count limitation may be appropriate. Thank you, Anne From: Aikman-Scalese, Anne Sent: Monday, December 14, 2020 2:11 PM To: 'Jeff Neuman' <jeff@jjnsolutions.com>; Jorge.Cancio@bakom.admin.ch Cc: gnso-newgtld-wg@icann.org Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls Level of Consensus designations include a Minority Viewpoint in the Consensus Designation itself where appropriate. It’s not just about what is in the Final Report (which is hundreds of pages). This is per the WG Guidelines (which you wrote.) A Minority Viewpoint forms “part and parcel” of the Consensus designation. From: Jeff Neuman <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Sent: Monday, December 14, 2020 10:47 AM To: Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>>; Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls [EXTERNAL] ________________________________ Anne, The request several years ago for official representatives was met with a lot of controversy and was eventually dropped. It was initially intended to ensure that the Working Group was hearing all of the positions from all of the ICANN stakeholder, which did happen. That should not be confused with the ultimate results of a consensus call. In the case of Closed Generics, assuming there is Divergence (and I am not assuming that), but if there is, then I believe our rationale section already documents all of the views that have been expressed. That is already in the body of the Report. But if a working group member wants to submit an additional statement that they want appended to the report on Closed Generics, then they are free to do so. Sorry Anne, I am just not sure what there is a disagreement about here. What am I missing? [cid:image001.png@01D6D28F.CE800120] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>> Sent: Monday, December 14, 2020 12:28 PM To: Jeff Neuman <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls Thanks Jeff. So, for example, in the Consensus designation on Closed Generics, Leadership would simply say “No Consensus” or “Divergence”, would not state any Minority Views and will require additional individual “minority reports” of individual WG members rather than including the Minority Views discussed to date in our deliberations? I note that the WG guidelines state that in the case of Divergence, Minority Views should be “encouraged”. To me, that means that Leadership should encourage Minority Views to be expressed and to allow time for WG members to develop support for those. That support would be developed among WG members (and not necessarily in their constituency) and that takes time. (The GAC has asked for a week.) A couple of years ago you asked for constituencies to designate representatives and you said that Leadership would need to take into account the views of representatives as possibly more weighty than individual views. Now you are saying constituencies can’t file Minority Views because they have other channels for providing advice? Please clarify. Anne From: Jeff Neuman <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Sent: Monday, December 14, 2020 10:12 AM To: Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>>; Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls [EXTERNAL] ________________________________ Anne, This is not what we are saying. There is a difference between a Minority Viewpoint and a Minority Report. 1. When Cheryl and I indicate level of support, if there is full consensus, then there obviously would be no minority view. 2. If we determine that there is Consensus, then according to the definition, we will have found that “only a small minority disagrees…” We do not need a Minority Report or documentation of the Minority Viewpoint to determine that a small minority of members disagree. 3. If we determine that there is Strong Support but significant opposition, again we will have determined that there is a larger, but still minority group of members, that disagree. Once we set forth the levels of support designations, then (and only then) will the Working Group Leadership accept documented “Minority View”. As stated in 3.6, “Documentation of Minority View recommendations normally depends on text offered by the proponent(s).” And by “proponent(s)”, that means Working Group Member(s), not by ACs, SGs or Cs. We expect that all those responding to a Consensus Call will do so on their own behalf and not necessarily on behalf of the Cs, SGc, or ACs. The Cs, SGs and ACs have not been involved in all of the discussions and have not been part of the compromises which needed to be made. In many ways, requiring input from your Cs, SGs and ACs, could have the negative affect of undoing our many years’ worth of work. Now of course we cannot tell you how to respond to the Consensus Call. But we can urge you to respond as a Working Group member. I hope this helps. [cid:image002.png@01D6D28F.CE800120] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>> Sent: Monday, December 14, 2020 11:32 AM To: Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>; Jeff Neuman <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls Jeff and Cheryl, It sounds as though you are saying there will be no Minority Viewpoints expressed from our deliberations when you publish the Consensus call. Is that the case? Then if that is the case, are you saying that only Leadership will determine when a Minority Viewpoint exists after receiving something you call a “minority report”? How does the process you described on the call allow for the drafter of a proposed Minority Viewpoint to develop support – given that a Minority Viewpoint is not supposed to be an individual viewpoint but is rather supported by “a small number of people”? From the WG Guidelines: •MinorityView-refers to a proposal where a small number of people support the recommendation.This can happen in response to a Consensus, Strong support but significant opposition, and No Consensus; or,it can happen in cases where there is neither support nor opposition to a suggestion made by a small number of individuals. In cases of Consensus, Strong support but significant opposition, and NoConsensus, an effort should be made to document that variance in viewpoint and to present any Minority View recommendations that may have been made. Documentation of Minority View recommendations normally depends on text offered by the proponent(s). In all cases of Divergence, the WG Chair should encourage the submission of minority viewpoint(s). From: Aikman-Scalese, Anne Sent: Friday, December 11, 2020 2:15 PM To: 'Jorge.Cancio@bakom.admin.ch' <Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>>; 'jeff@jjnsolutions.com' <jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls After listening to the Dec 10 call (which I could not attend), I have to say that normally a Minority Statement will require coordination with others to determine how many will join in the Minority Statement. It is pretty much impossible to do that in 2 days. You said on the call that WG members should know what the consensus designation will be but you also said that Leadership doesn’t know and that Leadership will have to take into account a number of different factors, not just the number of WG members who support a particular consensus designation. Then you said we could be surprised to find that Leadership did not find a consensus and so we might not need to file a Minority Statement. This is all very “loosey-goosey” so in fact, it’s not possible for WG members to draft and develop support for Minority Statements at this time except on issues that are major like Closed Generics, Auctions, etc. It’s important, in drafting a Minority Statement, to know whether Leadership will designate the section as Full Consensus, Rough Consensus, or Strong Support. A WG member can’t draft a proper Minority Statement without knowing what the designation is and reviewing notes/calls to say whether or not s(he) agrees with that designation. And there is no way to develop support for that draft Minority Statement in our constituencies or otherwise within 2 days. Thank you, Anne From: Aikman-Scalese, Anne Sent: Friday, December 11, 2020 8:37 AM To: 'Jorge.Cancio@bakom.admin.ch' <Jorge.Cancio@bakom.admin.ch<mailto:Jorge.Cancio@bakom.admin.ch>>; jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> Subject: RE: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls +1. Regarding the following, this is not at all a reasonable expectation: Minority Reports are due just 2 days after the designation of Levels of Consensus. From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> On Behalf Of Jorge.Cancio--- via Gnso-newgtld-wg Sent: Friday, December 11, 2020 7:11 AM To: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls [EXTERNAL] ________________________________ Dear Jeff and all Thanks very much for this email! Speaking personally, I’m afraid that the proposed timeline with consensus calls over the holiday break (at least in the Northern hemisphere) is not very helpful. At least for those of us needing to do extensive consultations (be it inside a Government or within a larger community) such dates are completely unworkable. Not sure how others feel about this… Personally, I would suggest starting the consensus calls once we are back from the break, e.g. on January 4th. In addition, I feel that for the same reasons (need for consultations etc.) the time allotted between consensus designations by the co-chairs and the deadline for submitting minority reports should be significantly extended (e.g. at least to one full week). Hope this is doable… Kind regards Jorge Von: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> Im Auftrag von Jeff Neuman Gesendet: Freitag, 11. Dezember 2020 06:08 An: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Betreff: [Gnso-newgtld-wg] Work Plan Changes and Preliminary Information on Consensus Calls All, The Leadership Team met a few hours ago to discuss a number of issues including how to get to the finish line……We are nearly there! As discussed on the last call (about 24 hours ago), we are making the following changes to the Work Plan: * 11 December 2020 * Latest Redline of Final Report containing changes from all topics discussed to date as well as changes (if any) as a result of the 9 Topical E-mails * Meeting of the small team on Auctions to see if there can be any recommendations to the Full Working Group * 14 December 2020 * Discussing (a) Auctions Topic (results if any from small team; (b) Conflicts of Interest, (c) Applicant Freedom of Expression, and (d) Dispute Resolution Procedures after Delegation. * 15 December 2020 * Comments due to 11 December 2020 Redline * Release of Any redlines to as a result of the topics discussed on 14 December 2020 * 17 December 2020 * Comments due to December 15 Redline * Working Group Call (already on your calendars) to close out any last issues * Content Freeze / Lockdown – Other than if there are any changes to close out last issues, all content is locked down for the Consensus Call * 22 December 2020 * Final Report is released to the Working Group * Commencement of Consensus Call (See some notes below) * 5 January 2020 * Consensus Call Ends * 6 January 2020 * Designation of Levels of Support by Working Group Leadership Team * 7 January 2020 * Call of the Working Group to discuss designations, answer questions, and hopefully celebrate a job well done * 8 January 2020 * Challenges to Designation of Levels of Support by Working Group Leadership Team are due (if any) * Minority Reports (if any) are due * 11 January 2020 * Final Report delivered to the Council * Document Deadline for discussion during January’s GNSO Council Meeting Some Notes 1. A longer note will follow in the next couple of days on how we will structure the Consensus Call. We strongly recommend that if you were not on the last working group call on 10 December 2020 at 03:00 UTC, please do go back and review at least the first 15-20 minutes of the call. (Link to Call<https://community.icann.org/display/NGSPP/2020-12-07+New+gTLD+Subsequent+Pro...>) 1. Although more details will be provided later: * Leadership will be grouping the Topics into batches for purposes of the Consensus Calls. We will not be voting on each recommendation / implementation guidance separately (as there are several hundred of them). * We will do our best to only include in the batches the lesser controversial topics; stated differently, Leadership has a sense of which sections should be supported by either full consensus or (rough) consensus. Of course we could always be wrong, but we will do our best. i. If there is a batch that contains a part that you do not support, then in the Consensus Call, we will ask you specifically which element or elements do you not support. In other words, if we grouped topics 1,2 and 3 together and you indicate that you do not support the batch, you will be asked to specify which of the Topics you do not support, and which element(s) within that topic you do not support. We will assume that the topics / elements you do not list are ones that you would support. So being specific will be important. * Topics where we can already foresee that there will be a difference of opinion (eg., Closed Generics, Mechanisms of Last Resort), we will make sure we have those topics in the Consensus Call on their own (i.e., not in batches with other topics). * All expressions of support / non support during the Consensus Call MUST be submitted through the formal mailing list. We will not be counting any responses to the Consensus Call that are not submitted on the list. It is critical that all of the information is on the record and documented. * The Consensus Call is NOT A VOTE – Leadership will not be determining levels of support based on the quantity of responses, but will take into consideration other factors such as the groups with whom an individual associates, etc. * We will be following Section 3.6 of the Working Group Guidelines (https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-gn...). 1. Minority Reports are due just 2 days after the designation of Levels of Consensus. We know that is not a lot of time. However, given that we have had a draft final report, comments to the draft final report, extensive discussions of those comments of the draft final report, and you have seen several redlines already, we believe that if you disagree with the way the group is heading, you should pretty much know that now. There is no reason to wait until the designations of levels of support to start drafting. In fact, I am told that the ALAC has already been working on a minority report to certain topics for some time now. Bottom Line – you can start working on any minority report now. The worst thing that will happen is that you draft your report and there is a consensus call surprise where you find out you may not be in the minority and you decide not to submit the statement 😊 1. We are nearly there!!!!!!!!! Thanks. Your humble Leadership Team, Cheryl and Jeff – Co-Chairs With very special thanks to Martin, Annabeth, Robin and Flip who have been participating in Leadership calls for many months and providing valuable insight & of course to Steve, Emily and Julie, without whom, none of this would be possible ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.