- Gnso-newgtld-wg - lists.icann.org

Webinar in Support of the New gTLD Subsequent Procedures Policy Development Process Working Group’s Draft Final Report
by ICANN Policy Calendar Sept. 3, 2020

Sept. 3, 2020

Meeting:  Webinar in Support of the New gTLD Subsequent Procedures Policy Development Process Working Group’s Draft Final Report Date/time:  Monday, 14 September 2020 at 20:00 UTC for 90 minutes Before joining the call: Please be sure you have read the Expected Standards of Behavior [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki agenda page: https://community.icann.org/x/DwC-C Check your time zone: https://tinyurl.com/y5639mdm ••••••••••••••••••••••••••••••••••••••••••••••••• Please click the link below to join the webinar: https://icann.zoom.us/j/96228789659?pwd=SUNxZ1dGZGlPaVNHcmRNLzJrVHdQQT09 Passcode: E91YcT&9X^ The New gTLD Subsequent Procedures Policy Development Process Working Group published<https://www.icann.org/public-comments/gnso-new-gtld-subsequent-draft-final-…> its draft Final Report for public comment on 20 August 2020. This draft report is the culmination of several years of deliberations and numerous public consultations, in support of the large number of topics captured in the Working Group’s Charter. You can read our blog post about the Working Group reaching this milestone here<https://www.icann.org/news/blog/public-comment-on-the-gnso-new-gtld-subsequ…>. The Working Group has worked extremely hard to reach this point and is looking forward to considering feedback received as it seeks to complete its Final Report and deliver it to the GNSO Council. To aid in your review and understanding of the draft Final Report now open for public comment, the Co-Chairs have scheduled a webinar on Monday, 14 September 2020 at 20:00 UTC to present on a selection of the topics within the draft report, answer questions you may have, and provide context where it may be needed. ••••••••••••••••••••••••••••••••••••••••••••••••• Or iPhone one-tap: US: +16699006833,,96228789659#,,,,,,0#,,8883615260# or +13462487799,,96228789659#,,,,,,0#,,8883615260# ••••••••••••••••••••••••••••••••••••••••••••••••• ••••••••••••••••••••••••••••••••••••••••••••••••• Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 346 248 7799 or +1 253 215 8782 or +1 312 626 6799 or +1 929 436 2866 or +1 301 715 8592 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 962 2878 9659 Passcode: 8883615260 International numbers available: https://icann.zoom.us/u/acEBw59hZz Webinar recordings will be published and circulated shortly after the end of the session.

1 0

Proposed Agenda - New gTLD Subsequent Procedures PDP WG - Thursday, 03 September at 15:00 UTC for 90 Minutes
by Julie Hedlund Sept. 1, 2020

Sept. 1, 2020

Dear WG Members, Please find below the proposed agenda for the WG meeting on Thursday, 03 September 2020 at 15:00 UTC for 90 minutes. Proposed Agenda: 1. Review Agenda/Updates to Statements of Interest 2. Update on the Public Comment Forum/Early Feedback (if any) 3. Closed Generics Proposals: In-Depth Discussion – see: * A Proposal for Public Interest Closed Generic gTLDs (PICG TLDs)(submitted by Alan Greenberg, Kathy Kleiman, George Sadowsky, Greg Shatan): Word<https://community.icann.org/download/attachments/144376220/ProposalforPICGn…>, PDF<https://community.icann.org/download/attachments/144376220/ProposalforPICGn…> * The Case for Delegating Closed Generics (submitted by Kurt Pritz, Marc Trachtenberg, Mike Rodenbaugh): PDF<https://community.icann.org/download/attachments/144376220/ClosedGenerics24…> * Closed Generics Proposal (submitted by Jeff Neuman in his individual capacity): Word<https://community.icann.org/download/attachments/144376220/Neuman%20Closed%…>, PDF<https://community.icann.org/download/attachments/144376220/Neuman%20Closed%…> (see original email message<https://mm.icann.org/pipermail/gnso-newgtld-wg/2020-August/003328.html>) 4. AOB If you need a dial out or would like to submit an apology, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Best, Julie Julie Hedlund, Policy Director

1 0

Why meetings
by Kathy Kleiman Aug. 24, 2020

Aug. 24, 2020

Hi Jeff and Cheryl,Why are we planning WG meetings during the comment period? Now is the time for us to work with our SGs and constituencies, the community and the public to help them understand the complex materials that we (WG) shared and work to help them find, form and submit their comments. As volunteers, this is all that can reasonably (and responsibly) be expected of us. It is supposed to be quiet period in the WG. What is happening/ Tx, Kathy

5 4

Webinar in Support of the New gTLD Subsequent Procedures Policy Development Process Working Group’s Draft Final Report
by ICANN Policy Calendar Aug. 24, 2020

Aug. 24, 2020

Meeting: Webinar in Support of the New gTLD Subsequent Procedures Policy Development Process Working Group’s Draft Final Report Date/time: Monday, 14 September 2020 at 20:00 UTC for 1 hour Before joining the call: Please be sure you have read the Expected Standards of Behavior [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki agenda page: https://community.icann.org/x/DwC-C Check your time zone: https://tinyurl.com/y5639mdm * Please click the link below to join the webinar: https://icann.zoom.us/j/96228789659?pwd=SUNxZ1dGZGlPaVNHcmRNLzJrVHdQQT09 Passcode: E91YcT&9X^ The New gTLD Subsequent Procedures Policy Development Process Working Group published<https://www.icann.org/public-comments/gnso-new-gtld-subsequent-draft-final-…> its draft Final Report for public comment on 20 August 2020. This draft report is the culmination of several years of deliberations and numerous public consultations, in support of the large number of topics captured in the Working Group’s Charter. You can read our blog post about the Working Group reaching this milestone here<https://www.icann.org/news/blog/public-comment-on-the-gnso-new-gtld-subsequ…>. The Working Group has worked extremely hard to reach this point and is looking forward to considering feedback received as it seeks to complete its Final Report and deliver it to the GNSO Council. To aid in your review and understanding of the draft Final Report now open for public comment, the Co-Chairs have scheduled a webinar on Monday, 14 September 2020 at 20:00 UTC to present on a selection of the topics within the draft report, answer questions you may have, and provide context where it may be needed. * Or iPhone one-tap : US: +16699006833,,96228789659#,,,,,,0#,,8883615260# or +13462487799,,96228789659#,,,,,,0#,,8883615260# * Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 346 248 7799 or +1 253 215 8782 or +1 312 626 6799 or +1 929 436 2866 or +1 301 715 8592 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 962 2878 9659 Passcode: 8883615260 International numbers available: https://icann.zoom.us/u/acEBw59hZz Webinar recordings will be published and circulated shortly after the end of the session. Thank you. Kind Regards, Terri

1 0

Meeting Invitation | New gTLD Subsequent Procedures Webinar | Monday, 14 September 2020 at 20:00 UTC for 1 hour
by Terri Agnew Aug. 24, 2020

Aug. 24, 2020

Dear all, The New gTLD Subsequent Procedures Webinar is scheduled on Monday, 14 September 2020 at 20:00 UTC for 1 hour. Before joining the call: Please be sure you have read the Expected Standards of Behavior [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki agenda page: https://community.icann.org/x/DwC-C Check your time zone: https://tinyurl.com/y5639mdm * Please click the link below to join the webinar: https://icann.zoom.us/j/96228789659?pwd=SUNxZ1dGZGlPaVNHcmRNLzJrVHdQQT09 Passcode: E91YcT&9X^ * Or iPhone one-tap : US: +16699006833,,96228789659#,,,,,,0#,,8883615260# or +13462487799,,96228789659#,,,,,,0#,,8883615260# * Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 346 248 7799 or +1 253 215 8782 or +1 312 626 6799 or +1 929 436 2866 or +1 301 715 8592 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 962 2878 9659 Passcode: 8883615260 International numbers available: https://icann.zoom.us/u/acEBw59hZz Webinar recordings will be published and circulated shortly after the end of the session. Thank you. Kind Regards, Terri

1 0

New gTLD Subsequent Procedures Webinar
by ICANN Policy Calendar Aug. 24, 2020

Aug. 24, 2020

Meeting: New gTLD Subsequent Procedures Webinar Date/time: Monday, 14 September 2020 at 20:00 UTC for 1 hour Before joining the call: Please be sure you have read the Expected Standards of Behavior [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki agenda page: https://community.icann.org/x/DwC-C Check your time zone: https://tinyurl.com/y5639mdm * Please click the link below to join the webinar: https://icann.zoom.us/j/96228789659?pwd=SUNxZ1dGZGlPaVNHcmRNLzJrVHdQQT09 Passcode: E91YcT&9X^ * Or iPhone one-tap : US: +16699006833,,96228789659#,,,,,,0#,,8883615260# or +13462487799,,96228789659#,,,,,,0#,,8883615260# * Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 346 248 7799 or +1 253 215 8782 or +1 312 626 6799 or +1 929 436 2866 or +1 301 715 8592 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 962 2878 9659 Passcode: 8883615260 International numbers available: https://icann.zoom.us/u/acEBw59hZz Webinar recordings will be published and circulated shortly after the end of the session. Thank you. Kind Regards, Terri

1 0

GNSO New gTLD Subsequent Procedures Draft Final Report - Published for Public Comment
by Steve Chan Aug. 21, 2020

Aug. 21, 2020

Dear WG Members, I am pleased to inform you that the draft Final Report has been published for public comment: https://www.icann.org/news/announcement-2020-08-20-en. Congratulations to the Working Group on achieving this milestone! Best, Steve Steven Chan  Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar

4 3

Deadline Wednesday 19 August: Final Check on Auctions: Mechanisms of Last Resort & Private Resolution of Contention Sets
by Emily Barabas Aug. 20, 2020

Aug. 20, 2020

Dear all, The final text on Auctions: Mechanisms of Last Resort & Private Resolution of Contention Sets is now available for your review here<https://docs.google.com/document/d/1ShY7lL07QrFKIDZybdGceXXvb_hmKGHI3qE9bxg…>. The edits based on the action items from the WG’s recent deliberations on 13 August<https://community.icann.org/display/NGSPP/2020-08-13+New+gTLD+Subsequent+Pr…> and August 17<https://community.icann.org/display/NGSPP/2020-08-17+New+gTLD+Subsequent+Pr…> are reflected in the redlines. The deadline for comments is Wednesday, 19 August at 23:59 UTC. A summary of the Can’t Live With comments and their resolution is available here<https://docs.google.com/spreadsheets/d/1blgQjzh_vR7WQ1utsqBnHDb8_b2DD7IDQu-…>. * Please limit feedback to errors in the edits, for example a revision that you believe does not accurately reflect the outcome of discussions about a “Can’t Live With” item. * Please send this type of feedback to the mailing list. Typo corrections can be sent directly to staff. * Please do not raise new issues, introduce new “Can’t Live With” items, or re-open deliberations. Kind regards, Emily

3 2

Deadline Tuesday, 18 August: Final Check on Predictability and Closed Generics
by Julie Hedlund Aug. 19, 2020

Aug. 19, 2020

Dear all, The final text on Predictability and Closed Generics is now available for your review in the production document<https://docs.google.com/document/d/1S4aOGxln9b93E_j3eF-dm0E6M8-VYToD8U9AkPl…>. The edits based on the action items from the WG’s recent deliberations on 13 August<https://community.icann.org/display/NGSPP/2020-08-13+New+gTLD+Subsequent+Pr…> are reflected in the redlines. The deadline for comments is Tuesday, 18 August at 23:59 UTC. * Please limit feedback to errors in the edits, for example a revision that you believe does not accurately reflect the outcome of discussions about a “Can’t Live With” item. * Please send this type of feedback to the mailing list. Typo corrections can be sent directly to staff. * Please do not raise new issues, introduce new “Can’t Live With” items, or re-open deliberations. Kind regards, Julie

4 4

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 17 August at 15:00 UTC
by Julie Hedlund Aug. 17, 2020

Aug. 17, 2020

Dear Working Group members, Please see below the notes from the meeting on 17 August at 15:00 UTC. These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted at: https://community.icann.org/display/NGSPP/2020-08-17+New+gTLD+Subsequent+Pr…. Kind regards, Julie Notes and Action Items: Actions: 1. “Can’t Live With” Comments on the new draft report section on Auctions: Mechanisms of Last Resort & Private Resolution of Contention Sets (Including Private Auction): Re: “Applicants may mark portions of any such responses as “confidential” if the responses include proprietary business information and such portions will not be shared or communicated by the Evaluator [or ICANN as appropriate].” ACTION ITEM: Delete text (shown via strikethrough) in “Applicants may mark portions of any such responses as “confidential” if the responses include proprietary business information and such portions will not be shared or communicated by the Evaluator.” Add to the AGB terms and conditions section that confidentiality provisions that apply to ICANN should apply to only those who have a need to know including any third party contractors providing dispute or appeals services.” Re: “The potential non-exhaustive list of “Factors”...” ACTION ITEM: Change to “ [that ICANN may consider whether an application was submitted with a bona fide intention to operate the gTLD]” and add in “[The WG discussed the following] potential non-exhaustive list of “Factors”. Put all factors out for public comment. Re: “If an Applicant applies for [four] [five] [four] or more strings...” ACTION ITEM: Put “five” and “four” in brackets. Re: “If an applicant is awarded a top-level domain and sells [attempts to sell] [assigns] the TLD (separate and apart from a sale of all or substantially all of its non-TLD related assets) within (1) year, this may be a factor considered by ICANN in determining non-good faith intent for that applicant.” ACTION ITEM: Figure out a way to put all of the suggestions in brackets for public comment. Also include a question “on applicable penalty in the event of absence of bona fide intent i.e. where there are no other credible explanations for the existence of listed factors, and if not, why not?"” Re: [Additional text proposed by Elaine Pruis: If an applicant with multiple applications resolves contention sets by means other than private auctions and does not win any TLDs.] ACTION ITEM: Include in the list of factors for public comment. Re: “At the end of the String [Similarity] Evaluation period, Applicants in contention sets will be informed of the number of other applications in their contention set, but no other information regarding the other applications will be shared.” ACTION ITEM: Change to “At the end of the String Similarity Evaluation period, Applicants in contention sets will be informed of the number of other applications in their contention set, but no other information regarding the other applications will be shared. All applicants that wish to compete for their applied-for string in an ICANN Auction of Last Resort must submit a sealed bid for each relevant application (“Last Resort Sealed Bids”). Any applicant that does not submit a sealed bid [or withdraw a sealed bid] at this time will be deemed to submit a bid of zero.” Add “Failure to timely submit a sealed bid will result in disqualification to participate in the Auction of Last Resort if held." Re: “[Justine Chew suggested making the following edits (in bold) to the previous bullet point: To the extent any contention sets are shrunk, by having other applications removed from the process (e.g., withdrawal, losing objections, failing evaluation, Community Priority Evaluation identifying only Community-based Applications which prevailed, etc.), applicants will NOT be allowed to adjust their sealed bids. However, in the event of a partial resolution of a contention set through the formation of a business combination or joint venture and the corresponding withdrawal of one or more Applications, the remaining Application AND each of the other existing applications in the contention set will be allowed, but are not required, to submit a new Last Resort Sealed Bid]” ACTION ITEM: Accept the edits suggested by Justine Chew. Re: “auction of last resort” ACTION ITEM: Change to “ICANN Auction of Last Resort”. Make consistent throughout. Re: “Once payment is received [within the specified time period], the applicant may proceed to the Transition to Delegation.” ACTION ITEM: Accept the text in brackets. Re: “ [five (5) business days] of resolution and ICANN must, in turn, publish the same within 72 hours [three (3) business days] of receipt. This includes:” ACTION ITEM: Keep “72 hours” and see what comments come in. Re: “Protections for Disclosing Applicants: Except as otherwise set forth in the transparency requirements above, no participant in any private resolution process shall be required to disclose any proprietary information such as trade secrets, business plans, financial records, or personal information of officers and directors unless such information is otherwise required as part of a standard [normal] TLD application.” ACTION ITEM: Change “standard” to “normal”. Re: “The information obtained from the contention resolution process may not be used by ICANN for any purpose other than as necessary to evaluate the application, evaluate the New gTLD Program, or to otherwise comply with [applicable] law.” ACTION ITEM: Add text in brackets “applicable”. Re: “The Working Group discussed a number of possible alternatives to auctions of last resort for resolving contention [sets],” and “Therefore, the Working Group affirms the use of auctions as a method of last resort to resolve contention [sets],” ACTION ITEM: Adopt the change. Re: “By requiring all applicants to agree to the bona fide use clause, [some in] the Working Group believe...” ACTION ITEM: Adopt the change. Re: “Finally, some in the Working Group remain concerned that the practice of leveraging financial gains in one private auction to resolve other contention sets has not been addressed adequately. [A proposal that would have required sealed bids for private auctions submitted at the same time, which would have prevented the rolling of funds from one auction to another, was discussed but agreement was not possible.]” ACTION ITEM: Adopt concept, making clear that the proposal came from those that were concerned. Re: “Rationale for Implementation Guidance xx (Rationale 3): The Working Group believes that second-price, sealed bid auctions are preferable to the ascending bid auctions used in the 2012 round [ICANN Auctions of Last Resort],” ACTION ITEM: Adopt the change – including the bracketed text. Re: “[Susan Payne proposed adding the following paragraph: Some in the Working Group have argued that requiring submission of sealed bids for auctions of last resort before the identity of the identity of other Applicants is known fails to recognize that the value of a TLD to an Applicant may be different depending on who the other potential owners of the TLD are and that applicants should know all the facts available when determining what is an appropriate level to bid.]” ACTION ITEM: Include additional text from Susan Payne – and in following sections. Re: “Rationale for Implementation Guidance xx (Rationale 4):” ACTION ITEM: Adopt the suggested text in brackets. 2. Draft Final Report Change Analysis – Questions Highlighted in Yellow ACTION ITEM: Add the questions from the WG discussions on 17 August with respect to private resolutions – implications of not having a bona fide intent (Justine Chew’s comments). 4. Public Comment Survey Tool – Draft PDF ACTION ITEM: Staff will send the PDF of the survey form and the WG will have 24 hours to ask questions on the format (not the content). See the attached PDF. NOTE: This is only a draft; the final survey tool will be updated with the questions resulting from the meeting on 17 August, as well as to correct any possible typos. Note also that the format of the actual survey will differ slightly from the format of the PDF. Notes: 1. Updates to Statements of Interest: No updates provided. 2. “Can’t Live With” Comments on the new draft report section on Auctions: Mechanisms of Last Resort & Private Resolution of Contention Sets (Including Private Auction): https://docs.google.com/document/d/1ShY7lL07QrFKIDZybdGceXXvb_hmKGHI3qE9bxg…<https://docs.google.com/document/d/1ShY7lL07QrFKIDZybdGceXXvb_hmKGHI3qE9bxg…> -- start at page 2 Re: “Applicants may mark portions of any such responses as “confidential” if the responses include proprietary business information and such portions will not be shared or communicated by the Evaluator [or ICANN as appropriate].” JP9.4: Jim Prendergast proposed deleting the highlighted text. Rationale: "Similar to my previous point, evaluators are temporary hires. Once the evaluators are done evaluating, what information does ICANN have in order to be able to enforce bona fide intent long-term? If the “Factors” are a suspicion that the applicant didn’t meet that intent, and the evaluators are gone, who is going to raise that concern if ICANN hasn’t seen those concerns." -- Need to control the scope of sharing or build into terms and conditions. -- Those that do reviews should have access to certain information, but not sure that applies to confidential info. -- Looking at the last AGB, confidentiality clause. -- Might need language for the public comment period. -- Who at ICANN would be on the “need to know” list? -- Then let's limit Evaluator disclosure to ICANN to only those who need to know. Problem fixed. -- Wonder if this should be a general term & condition instead of specific to private settlement outcomes? -- Don’t think we should let the applicant designate anything it wants to be confidential. -- The AGB determines what is or isn’t confidential. -- Responses to public questions are never confidential. Responses to non-public questions are always confidential. The others are specified in their contexts. -- Amount of compensation would be confidential, but a change in the board would not be confidential as it isn’t deemed to be by the AGB. ACTION ITEM: Delete text (shown in strikethrough) in “Applicants may mark portions of any such responses as “confidential” if the responses include proprietary business information and such portions will not be shared or communicated by the Evaluator.” Add to the AGB terms and conditions section that confidentiality provisions that apply to ICANN should apply to only those who have a need to know including any third party contractors providing dispute or appeals services.” Re: “The potential non-exhaustive list of “Factors”...” -- Discussion on email, put out for public comments and include “potential” before Factors. -- Get rid of “non-good faith intent” – we are taking about bona fide intent. -- Make the factors Implementation Guidance that the IRT can consider. -- But still put out for public comment – but structure it that these are a potential list of factors that members of the WG discussed. Put them all in and see what comes back in public comment and decide after reviewing comments to either include as policy or Implementation Guidance. -- But my primary comment is "that ICANN may consider in determining whether or not an Applicant had a bona fide intention to operate a...” -- What about asking what are the consequences if the factors aren’t met? ACTION ITEM: Change to “ [that ICANN may consider whether an application was submitted with a bona fide intention to operate the gTLD]” and add in “[The WG discussed the following] potential non-exhaustive list of “Factors”. Put all factors out for public comment. Re: “If an Applicant applies for [four] [five] [four] or more strings...” EP9.1: Elaine Pruis proposes changing "five" to "four." Rationale: "Half of five is 2.5. Use a number that is divisible by 2 and results in a whole number. ACTION ITEM: Put “five” and “four” in brackets. Re: “If an applicant is awarded a top-level domain and sells [attempts to sell] [assigns] the TLD (separate and apart from a sale of all or substantially all of its non-TLD related assets) within (1) year, this may be a factor considered by ICANN in determining non-good faith intent for that applicant.” JC9.2: Justine Chew suggested changing "sells" to "attempts to sell" and also stated "Please include a request for input on penalty for identified occurrence of “no bona fide intent”." Rationale: "• An attempt to sell just the TLD is a better and more timely identifier of intention since “sells” implies an aftert-the-fact event. We should try to “catch”an intention as early as possible. Are we not asking the community for input on applicable penalty in the event of absence of bona fide intent i.e. where there are no other credible explanations for the existence of listed factors, and if not, why not?" ACTION ITEM: Figure out a way to put all of the suggestions in brackets for public comment. Also include a question “on applicable penalty in the event of absence of bona fide intent i.e. where there are no other credible explanations for the existence of listed factors, and if not, why not?"” Re: [Additional text proposed by Elaine Pruis: If an applicant with multiple applications resolves contention sets by means other than private auctions and does not win any TLDs.] EP9.3: Elaine Pruis proposes adding the bracketed text as a new bullet in this list. Rationale: "If ICANN isn’t privy to the material terms of settlements, some resolutions could purposely lose without any money changing hands or business combinations being made. Captures possible “paid (not necessarily in cash) to go away” settlements." ACTION ITEM: Include in the list of factors for public comment. Re: “At the end of the String [Similarity] Evaluation period, Applicants in contention sets will be informed of the number of other applications in their contention set, but no other information regarding the other applications will be shared.” “[Donna Austin proposed alternative text to the previous sentence: All applicants in a contention set will be required to submit a sealed bid for each application in a contention set at this time. This sealed bid will only become relevant if the contention set is resolved through an ICANN Auction of Last Resort. (“Last Resort Sealed Bids”).]” DA9.1: Donna Austin proposed replacing previous bullet with bracketed text. Rationale: "If it’s only applicants that wish to compete for their applied-for string in an ICANN Auction of Last Resort that submit a sealed bid at this point in the process, at what point would applicants who intend to resolve the contention set through private resolution, but end up in a contention set resolution via an ICANN Auction of Last Resort submit their sealed bid? It was my understanding that if one applicant in the contention set opts for the ICANN Auction of Last Resort that negates the preference for private resolution of all the other applicants in the contention set. " -- At what point do the others in the contention set know that it will be resolved by an ICANN auction of last resort and when do they submit their sealed bids? -- Change to: “Any applicant who wishes to contest the contention should submit a sealed bid, which will be held on file in case of an auction of last resort.” -- Any applicant who has not submitted a bid at this point in time will be deemed to have submitted a bid of zero. -- Also make it explicit that at this point an applicant can withdraw from the contention set. -- This is not the AGB. The team that writes the AGB can fill in these details. -- Add "Failure to timely submit a sealed bid will result in disqualification to participate in the Auction of Last Resort if held." ACTION ITEM: Change to “At the end of the String Similarity Evaluation period, Applicants in contention sets will be informed of the number of other applications in their contention set, but no other information regarding the other applications will be shared. All applicants that wish to compete for their applied-for string in an ICANN Auction of Last Resort must submit a sealed bid for each relevant application (“Last Resort Sealed Bids”). Any applicant that does not submit a sealed bid [or withdraw a sealed bid] at this time will be deemed to submit a bid of zero.” Add “Failure to timely submit a sealed bid will result in disqualification to participate in the Auction of Last Resort if held." Re: [Phil Buckingham proposed alternative text to the previous sentence: All applicants on finding themselves in a contention set (on Reveal Day) must submit an additional private ICANN last resort sealed bid for each application ( Last Resort Sealed Bids) within 7 days (in the event that the contention set ends up being resolved by the Final ICANN auction of Last Resort , after all other options have failed). ] PB9.2: Phil Buckingham proposed replacing the previous sentence with bracketed text. Rationale: "Agree with Donna’s comment . We cannot have a situation ( as happened last time) whereby only one applicant refused to go to a private auction and thereby forced an ICANN last resort takes all auction. Have Added a time limit when it needs to be done. " -- Radically different from what the WG has discussed. Could be submitted as a comment in the public comment period. Re: All applications shall be evaluated and are subject to other application procedures (e.g., Initial Evaluation, Extended Evaluation, Objections, GAC Early Warning/Advice, Community Priority Evaluation).” CT9.6: Question from Christa Taylor: "'How are the needs of Applicant Support applicants being considered? i.e. date of the auction, deposit, education, etc.? These references in the process should be included." -- Don’t think any of this changes. It is a good question in terms of communication plans. Re: “all applicants (including both the existing members of the contention set as well as the new members) will be allowed, but are not required, to submit a new Last Resort Sealed Bid.” JP9.5: Jim Prendergast proposed eliminating the opportunity for new bids and forcing parties to rely on previously submitted bids. Rationale: "As I have pointed out, the proposal as written falls short in addressing Board concerns with gaming. The submission of new bids provides more gaming incentives. While waiting for the string confusion objections to come through on this contention set, the applicant could be losing other contention sets in the meantime and building up a bigger bid for this set. Instead of preventing this behavior, allowing new bid submissions actually expands the opportunity for this activity. " -- Good to file a comment on this. Re: “However, in the event of a partial resolution of a contention set through the formation of a business combination or joint venture and the corresponding withdrawal of one or more Applications, the remaining Application AND existing members of the contention set will be allowed, but are not required, to submit a new Last Resort Sealed Bid.” CT9.5: Christa Taylor suggested adding a reference an LOI which can be provided to ICANN as evidence. Rationale: "Confusing. If applicants enter into a JV or business combination before the TLD is acquired, all parties will be able to submit a new bid provided that one applicant has withdrawn their application? This is difficult to do without first acquiring the asset." -- Add “or the intention of forming a business combination”? -- Christa will check for the reference. Re: “[Justine Chew suggested making the following edits (in bold) to the previous bullet point: To the extent any contention sets are shrunk, by having other applications removed from the process (e.g., withdrawal, losing objections, failing evaluation, Community Priority Evaluation identifying only Community-based Applications which prevailed, etc.), applicants will NOT be allowed to adjust their sealed bids. However, in the event of a partial resolution of a contention set through the formation of a business combination or joint venture and the corresponding withdrawal of one or more Applications, the remaining Application AND each of the other existing applications in the contention set will be allowed, but are not required, to submit a new Last Resort Sealed Bid]” JC9.3: Justine Chew suggested making the edits in bold to the paragraph above. Rationale: "• An attempt to account for possibility of CPE limiting only Community-based applications which prevailed which can proceed to an auction. Just avoiding use of the phrase “existing members of the contention set” and making it clear that each of the other existing applications may submit a new bid. (word-smithing)" -- These aren’t substantive changes. Only for clarity. ACTION ITEM: Accept the edits suggested by Justine Chew. Re: “auction of last resort” DA9.2: Comment from Donna Austin: "I believe that where ‘auction of last resort’ is used we mean ICANN Auction of Last Resort. Rather than use the terms interchangeably it would be best if the same term can be used for consistency and remove possibility for confusion." ACTION ITEM: Change to “ICANN Auction of Last Resort”. Make consistent throughout. Re: “Once payment is received [within the specified time period], the applicant may proceed to the Transition to Delegation.” JC9.4: Justine Chew suggested adding the bracketed text, and additional new bullet in brackets. Rationale: "• A time limit for payment needs to be mentioned. Query: Is there a reason why we have not specified what would happen if an applicant which succeeded in an auction does not pay within the specified time period? Consequence suggested." ACTION ITEM: Accept the text in brackets. Re: “ [five (5) business days] of resolution and ICANN must, in turn, publish the same within 72 hours [three (3) business days] of receipt. This includes:” CT9.7: Christa Taylor proposed alternate timeframes (in brackets). Rationale: "72 hours does not provide the applicant with sufficient time to meet all of the settlement terms & conditions, legal agreements, funding requirements, share registrars, etc. No reference to working days. " ACTION ITEM: Keep “72 hours” and see what comments come in. Re: “Protections for Disclosing Applicants: Except as otherwise set forth in the transparency requirements above, no participant in any private resolution process shall be required to disclose any proprietary information such as trade secrets, business plans, financial records, or personal information of officers and directors unless such information is otherwise required as part of a standard [normal] TLD application.” JC9.6: Justine Chew suggested changing "standard" to "normal." Rationale: "Use of “a standard TLD application” – in the AGB “standard application” is specifically distinguished from “community-based application”, so we don’t mean to exclude any community-based applications from transparency requirements." ACTION ITEM: Change “standard” to “normal”. Re: “The information obtained from the contention resolution process may not be used by ICANN for any purpose other than as necessary to evaluate the application, evaluate the New gTLD Program, or to otherwise comply with [applicable] law.” JC9.7: Justine Chew suggested adding the word "applicable." Rationale: "Word missing?" ACTION ITEM: Add text in brackets “applicable”. Re: “The Working Group discussed a number of possible alternatives to auctions of last resort for resolving contention [sets],” and “Therefore, the Working Group affirms the use of auctions as a method of last resort to resolve contention [sets],” JC9.8: Justine Chew suggested adding the word "sets" after "contention" ACTION ITEM: Adopt the change. Re: “By requiring all applicants to agree to the bona fide use clause, [some in] the Working Group believe...” JP9.6: Jim Prendergast proposed adding the bracketed text. Rationale: "There wasn’t broad agreement in the WG that this effort fully mitigated concerns." ACTION ITEM: Adopt the change. Re: “Finally, some in the Working Group remain concerned that the practice of leveraging financial gains in one private auction to resolve other contention sets has not been addressed adequately. [A proposal that would have required sealed bids for private auctions submitted at the same time, which would have prevented the rolling of funds from one auction to another, was discussed but agreement was not possible.]” JP9.7: Jim Prendergast proposed adding the bracketed text. Rationale: "I think its important to mention the group considered sealed bid proposal as a viable solution to this practice but could not reach agreement." -- In the dependent clause change "which would have" to :"which may have" or just strike the dependent clause as the commentary on the deliberations that it is.  ACTION ITEM: Adopt concept, making clear that the proposal came from those that were concerned. Re: “Rationale for Implementation Guidance xx (Rationale 3): The Working Group believes that second-price, sealed bid auctions are preferable to the ascending bid auctions used in the 2012 round [ICANN Auctions of Last Resort],” DA9.3: Donna Austin proposed adding the bracketed text. Rationale: "It’s unclear whether this refers only to ICANN Auctions of Last Resort or private resolution auctions—I have assumed ICANN Auctions of Last Resort, but it would be helpful if this is explicit." ACTION ITEM: Adopt the change – including the bracketed text. Re: “because [this method eliminates collusion and bid rigging; it is the preferred method used by governments to allocate critical resources; bidders are forced to value the TLD in absolute terms; and] second price auctions reduce the risk of “bidding wars” that can occur in ascending bid auctions.” EP9.5: Elaine Pruis proposes adding the text in brackets if Susan Payne's proposed text against second-price, sealed bid auctions is accepted/included. Rationale: "IF Susan Payne’s language arguing the counterpoints against second-price, sealed bid auctions is accepted/included, THEN the benefits of second-price, sealed bid auctions should be expounded upon in this section." -- Keep the original text. Re: “[Susan Payne proposed adding the following paragraph: Some in the Working Group have argued that requiring submission of sealed bids for auctions of last resort before the identity of the identity of other Applicants is known fails to recognize that the value of a TLD to an Applicant may be different depending on who the other potential owners of the TLD are and that applicants should know all the facts available when determining what is an appropriate level to bid.]” SP9.2: Susan Payne suggested adding a new paragraph. Rationale: "The text for this rationale implies that all in the working group support the whole of the recommendation. This is not the case, particularly with respect to the timing of bid submission. A number of WG members have pointed out that the value of a TLD to a bidding party can vary, depending on who else is in the contention set, and so do not favour bid submission being required before this information is available. Whilst this is not a view supported by everyone, the draft report does not currently reflect that there is this divergence. " ACTION ITEM: Include additional text from Susan Payne – and in following sections. Re: “Rationale for Implementation Guidance xx (Rationale 4):” ACTION ITEM: Adopt the suggested text in brackets. 3. Draft Final Report Change Analysis – Questions Highlighted in Yellow (which will be leveraged for the public comment proceeding): https://docs.google.com/document/d/17oV-BTJGtm2Q6w15qxqtsvRZg6PuW9WHGPOG1Kg… ACTION ITEM: Add the questions from the WG discussions on 17 August with respect to private resolutions – implications of not having a bona fide intent (Justine Chew’s comments). 4. Public Comment Survey Tool – Draft PDF ACTION ITEM: Staff will send the PDF of the survey form and the WG will have 24 hours to ask questions on the format (not the content). 5. Schedule: -- Post for comment the Draft Final Report by 21 August. -- Begin meetings on 03 September. -- Close comment period at the end of September. -- Leadership will send a list of possible topics to discuss during the public comment period.

1 0