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

ICANN60: GNSO Sessions How to Get Organized and Remote Participation Details
by Nathalie Peregrine Oct. 17, 2017

Oct. 17, 2017

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings’ team has put together a new ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN60 Meeting Schedule[schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.org_&d=…> GNSO Remote Participation wiki page<https://community.icann.org/x/7ichB> Step 1 – Create a profile and your personalized ICANN60 schedule Go to the Meeting Schedule webpage, and if not done yet for previous meetings, create a profile and login. Every session on the schedule can be selected and added to your individual schedule. By clicking to the left of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 At the top right-hand corner of the page click on the ‘Mobile App + ical” icon to download the mobile app and choose from various options how to sync your personalized schedule to your phone or laptop calendars. Step 3 All Adobe Connect rooms (which can be found on the session information on the Meeting Schedule and on the GNSO Remote Participation wiki page) will provide audio streaming. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the GNSO Remote Participation wiki page for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Nathalie Peregrine and Terri Agnew will be onsite to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<applewebdata://FB60497E-61D8-4FE9-BF9C-EB238191E416/gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Stepping down as co-chair
by avri doria Oct. 17, 2017

Oct. 17, 2017

Hi, I think the time has come for me to step down as co-chair of the group. Cheryl has been selected and approved and I am starting to have too many meeting conflicts, especially for Abu Dhabi. If it is ok with people, I will remain on the list as a participant, though I am willing to drop back to observer should that be better. Working within the GNSO and with this PDP has been very gratifying and I have nothing but confidence for the process and for you all to reach consensus on the many substantive issues that the group has yet to work through. Best Regards to all, avri

6 5

Re: [Gnso-newgtld-wg] Reminder regarding Expected Standards of Behavior
by Alan Greenberg Oct. 15, 2017

Oct. 15, 2017

There is no doubt that most people go into discussions hoping to achieve some end, but often is also a desire to achieve SOME end and to get there compromises may need to be made. The Board is the only GROUP that is charged with balancing the issues of all stakeholders. But multistakeholder discussions may be able to achieve that end (to be ratified by the Board) if the powers and ability to invest time and effort are balanced. In the absence of such balance, or if parties are not willing to find common ground, then we can have unbalanced decisions or stalemate. Alan At 13/10/2017 01:06 PM, Aikman-Scalese, Anne wrote: >Thanks James. This is a very thoughtful >response. I agree that everyone participating >has some interest in relation to point of >view. It strikes me that it is primarily the >Board of Directors, in their fiduciary capacity >that must act âin the overall best interest of >Internet users and the stability and security of >the Internetâs system of unique >identifiersâ, irrespective of personal >interests and the interests of any entity with which they are affiliated. > >This phrase in the Code of Conduct actually >strikes me as a pretty good âshort formâ >definition for the âGlobal Public Interestâ, >something we are always trying to grasp. > >Anne > > >Anne E. Aikman-Scalese >Of Counsel >520.629.4428 office >520.879.4725 fax ><mailto:AAikman@lrrc.com>AAikman(a)lrrc.com >_____________________________ >[] > >Lewis Roca Rothgerber Christie LLP >One South Church Avenue, Suite 700 >Tucson, Arizona 85701-1611 ><http://lrrc.com/>lrrc.com > >From: James M. Bladel [mailto:jbladel@godaddy.com] >Sent: Friday, October 13, 2017 8:29 AM >To: 'Terri Agnew'; gnso-newgtld-wg(a)icann.org; Aikman-Scalese, Anne >Cc: gnso-secs(a)icann.org >Subject: Re: [Gnso-newgtld-wg] Reminder >regarding Expected Standards of Behavior > >Hi Anne - > >Well, candidly, I think everyone has some >interest in the outcomes of Policy Development. >Whether thatâs direct, like those of us >representing our Employers of Clients, or >indirect, like those seeking to further their >own career in government or academia, or to >build a platform for future business development. > >I guess my point is that everyone is here on >behalf of an interest, even if it is theirs >personally. And this is the lens through which >we view the âoverall best interests of >Internet users.â I may focus on the desire of >an Internet user / domain registrant to launch a >business or blog in a frictionless environment, >unencumbered by confusing rules and regulations. >Others could focus on the trust element, that >users should have a reasonable level of >confidence that people and organizations they >are engaging with online are trustworthy and who >they claim to be. Another group might want to >participate online in a way that doesnât >expose them to frivolous legal risk or compromise their individual privacy. > >The beautiful thing about the Internet is that >all of these legitimate âoverall best >interestsâ can intersect in the same >âInternet userâ. We see this in companies >like GoDaddy, where we want the best experience >for our customers, but also want to protect them >from common online scams and fraud. We see >people misappropriating our name & brand, and we >hear complaints from customers about their >information being harvested for spam & >robocalls. I try to be mindful of all these >interests, and bring them to my work at ICANN. > >So ultimately it is a question of balancing, >rather than competing, interests. I believe that >all of the either-or, black-and-white problems >were solved decades ago, and weâve now taken >up permanent residence in a nebulous gray area. >Not sure if this was the response you were >looking for, but I hope it was helpful. > >Thanks > >J. > >On Oct 12, 2017, 21:00 -0500, Aikman-Scalese, >Anne <<mailto:AAikman@lrrc.com>AAikman(a)lrrc.com>, wrote: > >Thanks James. This is a good reminder. Just >seeking a clarification on one point: >cid:image001.png@01D3436A.29F43160 > > >Would you say that PDPs are characterized by >individuals acting in the overall best interests >of Internet users and the security and stability >of the Internet âirrespective of personal >interests and the interests of the entity to >which an individual might owe their appointmentâ? > >Wouldnât it be a bit strange if we expected >representatives of various entities that have a >financial stake in the GNSO policy process to >take positions and make contributions counter to >the interests of their employers when >participating in PDPs? (Honestly interested in your candid thoughts on this.) > >Thank you, >Anne > > >Anne E. Aikman-Scalese > >Of Counsel ><tel:520.629.4428>520.629.4428 office ><tel:520.879.4725>520.879.4725 fax ><mailto:AAikman@lrrc.com>AAikman(a)lrrc.com >_____________________________ >[] > >Lewis Roca Rothgerber Christie LLP >One South Church Avenue, Suite 700 >Tucson, Arizona 85701-1611 ><http://lrrc.com/>lrrc.com > >From: ><mailto:gnso-newgtld-wg-bounces@icann.org>gnso-newgtld-wg-bounces(a)icann.org >[mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Terri Agnew >Sent: Thursday, October 12, 2017 11:10 AM >To: <mailto:gnso-newgtld-wg@icann.org>gnso-newgtld-wg(a)icann.org >Cc: <mailto:gnso-secs@icann.org>gnso-secs(a)icann.org >Subject: [Gnso-newgtld-wg] Reminder regarding Expected Standards of Behavior > >Sent on behalf of the GNSO Council leadership team > >================ > >Dear Colleagues - > >Several recent interactions on PDP working group >calls and mailing lists have been referred to >the GNSO Chairs (Heather, Donna, and I). After >review, our level of concern is such that we >felt a refresher on ICANN's Expected Standards >of Behavior was warranted. A link to this >document is provided below, but in general terms >we are asking all participants in PDP working >groups to elevate the level of discourse on >calls and mailing lists to reflect a respectful >and professional environment for our work. > >With this in mind, donât attack fellow >volunteers personally, or question their >motives, or presume to know their positions >without giving them a chance to present >it. Humor (especially sarcasm) doesnât go >over well in emails or AC chat sessions, and >usually doesnât translate at all. Refrain >from escalating or retaliating to negative >comments. And, above all, remember that our >shared objective is not to âwinâ on any >given issue, but to seek out and build upon areas of common understanding. > >The Expected Standards of Behavior can be found >here: ><https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>https://www.icann.org/resources/pages/expected-standards-2012-05-15-en. >I know weâre all accustomed to just âclick >throughâ this text when joining a meeting, but >Iâm now asking everyone take a minute to two to review it again. > >Thank you for your help with this matter. > >J. > >---------------- >James Bladel >GNSO Chair > > > >---------- > >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. Â§<tel:2510-2521>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. >Content-Type: image/png; name="image005.png" >Content-Description: image005.png >Content-Disposition: inline; filename="image005.png"; size=15051; > creation-date="Fri, 13 Oct 2017 16:57:21 GMT"; > modification-date="Fri, 13 Oct 2017 16:57:21 GMT" >Content-ID: <image005.png(a)01D34409.A9DE29E0> >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:0tIGu/yw1RDzhyTVFlTi2QImeJpSiVporqJQb7Gg5zLyYx8FuSp4RMjque/RvZauSJUA4mMD8C5qGPp+50ztTxoeRoW1iA3i4zo+cLeGj26ynx1M9RK7XYRXfTf1cUN6 > >Content-Type: image/png; name="image006.png" >Content-Description: image006.png >Content-Disposition: inline; filename="image006.png"; size=6500; > creation-date="Fri, 13 Oct 2017 16:57:21 GMT"; > modification-date="Fri, 13 Oct 2017 16:57:21 GMT" >Content-ID: <image006.png(a)01D34409.A9DE29E0> >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:0tIGu/yw1RDzhyTVFlTi2QImeJpSiVporqJQb7Gg5zLyYx8FuSp4RMjque/RvZauSJUA4mMD8C5qGPp+50ztTxoeRoW1iA3i4zo+cLeGj26ynx1M9RK7XYRXfTf1cUN6 > >Content-Type: image/png; name="image001.png" >Content-Description: image001.png >Content-Disposition: inline; filename="image001.png"; size=6501; > creation-date="Fri, 13 Oct 2017 17:06:37 GMT"; > modification-date="Fri, 13 Oct 2017 17:06:37 GMT" >Content-ID: <image001.png(a)01D3440A.F542BDF0> >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:0tIGu/yw1RDzhyTVFlTi2QImeJpSiVporqJQb7Gg5zLyYx8FuSp4RMjque/RvZauSJUA4mMD8C5qGPp+50ztTxoeRoW1iA3i4zo+cLeGj26ynx1M9RK7XYRXfTf1cUN6 > > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;YQXPR0101MB1589;27:0tIGu/yw1RDzhyTVFlTi2QImeJpSiVporqJQb7Gg5zLyYx8FuSp4RMjque/RvZauSJUA4mMD8C5qGPp+50ztTxoeRoW1iA3i4zo+cLeGj26ynx1M9RK7XYRXfTf1cUN6 > >_______________________________________________ >Gnso-newgtld-wg mailing list >Gnso-newgtld-wg(a)icann.org >https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg

5 4

Re: [Gnso-newgtld-wg] Reminder regarding Expected Standards of Behavior
by Aikman-Scalese, Anne Oct. 15, 2017

Oct. 15, 2017

Thanks James. This is a good reminder. Just seeking a clarification on one point: [cid:image001.png@01D3436A.29F43160] Would you say that PDPs are characterized by individuals acting in the overall best interests of Internet users and the security and stability of the Internet “irrespective of personal interests and the interests of the entity to which an individual might owe their appointment”? Wouldn’t it be a bit strange if we expected representatives of various entities that have a financial stake in the GNSO policy process to take positions and make contributions counter to the interests of their employers when participating in PDPs? (Honestly interested in your candid thoughts on this.) Thank you, Anne Anne E. Aikman-Scalese Of Counsel 520.629.4428 office 520.879.4725 fax AAikman(a)lrrc.com<mailto:AAikman@lrrc.com> _____________________________ [cid:image004.png@01D3438C.57EB7ED0] Lewis Roca Rothgerber Christie LLP One South Church Avenue, Suite 700 Tucson, Arizona 85701-1611 lrrc.com<http://lrrc.com/> From: gnso-newgtld-wg-bounces(a)icann.org [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Terri Agnew Sent: Thursday, October 12, 2017 11:10 AM To: gnso-newgtld-wg(a)icann.org Cc: gnso-secs(a)icann.org Subject: [Gnso-newgtld-wg] Reminder regarding Expected Standards of Behavior Sent on behalf of the GNSO Council leadership team ================ Dear Colleagues - Several recent interactions on PDP working group calls and mailing lists have been referred to the GNSO Chairs (Heather, Donna, and I). After review, our level of concern is such that we felt a refresher on ICANN's Expected Standards of Behavior was warranted. A link to this document is provided below, but in general terms we are asking all participants in PDP working groups to elevate the level of discourse on calls and mailing lists to reflect a respectful and professional environment for our work. With this in mind, don’t attack fellow volunteers personally, or question their motives, or presume to know their positions without giving them a chance to present it. Humor (especially sarcasm) doesn’t go over well in emails or AC chat sessions, and usually doesn’t translate at all. Refrain from escalating or retaliating to negative comments. And, above all, remember that our shared objective is not to “win” on any given issue, but to seek out and build upon areas of common understanding. The Expected Standards of Behavior can be found here: https://www.icann.org/resources/pages/expected-standards-2012-05-15-en<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. I know we’re all accustomed to just “click through” this text when joining a meeting, but I’m now asking everyone take a minute to two to review it again. Thank you for your help with this matter. J. ---------------- James Bladel GNSO Chair ________________________________ 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.

5 5

Reminder regarding Expected Standards of Behavior
by Terri Agnew Oct. 12, 2017

Oct. 12, 2017

Sent on behalf of the GNSO Council leadership team ================ Dear Colleagues - Several recent interactions on PDP working group calls and mailing lists have been referred to the GNSO Chairs (Heather, Donna, and I). After review, our level of concern is such that we felt a refresher on ICANN's Expected Standards of Behavior was warranted. A link to this document is provided below, but in general terms we are asking all participants in PDP working groups to elevate the level of discourse on calls and mailing lists to reflect a respectful and professional environment for our work. With this in mind, don't attack fellow volunteers personally, or question their motives, or presume to know their positions without giving them a chance to present it. Humor (especially sarcasm) doesn't go over well in emails or AC chat sessions, and usually doesn't translate at all. Refrain from escalating or retaliating to negative comments. And, above all, remember that our shared objective is not to "win" on any given issue, but to seek out and build upon areas of common understanding. The Expected Standards of Behavior can be found here: https://www.icann.org/resources/pages/expected-standards-2012-05-15-en <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource s_pages_expected-2Dstandards-2D2012-2D05-2D15-2Den&d=DwMGaQ&c=MOptNlVtIETeDA LC_lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=nLTnlCjpaKa0PAoZ3Oo 9Hth_qedPM7PZZR9XOAEmRW8&s=rifMmlUtCDfJQ-7waiDNprOF9hRGXjwUtK_MFiJDj4g&e=> . I know we're all accustomed to just "click through" this text when joining a meeting, but I'm now asking everyone take a minute to two to review it again. Thank you for your help with this matter. J. ---------------- James Bladel GNSO Chair

1 0

Working Group Newsletter - October 2017
by Emily Barabas Oct. 11, 2017

Oct. 11, 2017

Dear Working Group members, The October edition of the New gTLD Subsequent Procedures PDP Working Group newsletter is now available: https://gnso.icann.org/en/news/working-group-newsletters/newsletter-new-gtl… Please feel free to share this newsletter with individuals and groups who may be interested in the Working Group’s activities. An archive of previous editions of the newsletter is available on the WG wiki<https://community.icann.org/pages/viewpage.action?pageId=58001970> and on the GNSO website<https://gnso.icann.org/en/news/working-group-newsletters>. Kind regards, Emily Emily Barabas | Senior Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

UPDATED Recordings, attendance & AC recording from New gTLD Subsequent Procedures Working Group call on Monday, 09 October 2017 15:00 UTC
by Michelle DeSmyter Oct. 9, 2017

Oct. 9, 2017

Dear All, Please find the attendance of the call attached to this email and the MP3 recording below for the New gTLD Subsequent Procedures Working Group call held on Monday, 09 October 2017 at 15:00 UTC. Attendance of the calls is also posted on the agenda wiki page: https://community.icann.org/x/AIJEB MP3: http://audio.icann.org/gnso/gnso-new-gtld-subsequent-09oct17-en.mp3<http://audio.icann.org/gnso/gnso-new-gtld-subsequent-09oct17-en.mp3[mailer.…> Adobe Connect Recording: https://participate.icann.org/p46netym3o7/ The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg/ Wiki page: https://community.icann.org/x/AIJEB Thank you. Kind regards, Michelle ------------------------------- Adobe Connect chat transcript for Monday, 09 October 2017 Michelle DeSmyter:Dear All, Welcome to the New gTLD Subsequent Procedures Working Group call on Monday, 09 October 2017 at 15:00 UTC. Michelle DeSmyter:Agenda wiki page: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Krishna Seeburn - Kris:yes Theo Geurts:It works Dietmar Lenden - Valideus Ltd:We can hear you Krishna Seeburn - Kris:it works Jim Prendergast:I have an item for AOB - could we get an update from Jeff on the discussuion he and Akram had at the Brands & Domains conference last week? thanks Maxim Alzoba (FAITID ):Hello all Maxim Alzoba (FAITID ):do we have adobe audio ? Jeff Neuman:@Jim - Just to clarify, you want an update on the panel we both were on, correct? We did not have a separate conversation Jim Prendergast:yes Jeff Neuman:ok...cool. I dont mind if others want to add that Jim Prendergast:i just saw the photos Jeff Neuman:Not my best side...... Kristina Rosette (Amazon Registry):Audio is surprisingly good at 30,000 feet. Go figure. Dietmar Lenden - Valideus Ltd:Monday Emily Barabas:WT4 call: Thursday, 12 October 2017 at 03:00 UTC for 60 minutes. Karen Day:From Rubens: "Call two weeks ago canceled due to conflict with WS2 schedule; call last week discussed name collisions, with good progress, and registry services, where there is still more to discuss. Call this week will focus exclusively on registry services. Steve Chan:@Jeff, no, not heard anything new Kristina Rosette (Amazon Registry):W/r/t GAC co-leader, it "may" be the case that their interested person is also running for GAC Chair and I suspect it would be difficult for that person to do both. Perhaps sugget that they can identify an alternate as a way to break the logjam? Jim Prendergast:Jeff - would it also make sense to circultate Martin's name to the email list as only 43 people are on the call? Greg Shatan:Apologies, I have. conflict today. I am only able to join briefly and without audio, Steve Chan:@Jeff, the approval of Cheryl is on the Consent Agenda. Michelle DeSmyter:We have been trying and no answer, we are continuing to dial her avri doria:https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_… Maxim Alzoba (FAITID ):does anyone have shot end URL for the Google doc? Kristina Rosette (Amazon Registry):By "can be implemented", do we mean "Implementable"? If so, should we say that (eg. "clear, implementable . . . )? Kristina Rosette (Amazon Registry):Is the use of passive voice intentional? If not, should we be identifying the actor to avoid future uncertainty? Cheryl Langdon-Orr:sorry to be late... Kristina Rosette (Amazon Registry):That's a general comment (passive voice). Jeff Neuman:I have put Kristina's suggestted text in the Google doc Jeff Neuman:Instead of "effect", can we use "adverse impact" Susan Payne:apologies, I was on another call. can someone tell me where we are in the document please? Jim Prendergast:how is material determined? Kristina Rosette (Amazon Registry):If we're going to use "material effect," we should use ICANN's written definition of it, which would be helpul to have. Martin Sutton:@Susan - towards bottom of third page Kristina Rosette (Amazon Registry):yes Susan Payne:thnx Martin Maxim Alzoba (FAITID ):to example of Minor process update ... lately ICANN updated so called GDD portal with the new Click through agreement (which reregistries , and later potentially applicants have to agree to), and cash things cause delays (unknown tetxt needs to pass through legal, and if the change is significant (as it was last time, the issue potentially is not minor anymore) Martin Sutton:@Susan - using the google doc https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume… Steve Chan:The document being shared should be unsynced. Kristina Rosette (Amazon Registry):@Jeff: having the definition of material effect that ICANN uses will be helpful to your issue, too, I think. Maxim Alzoba (FAITID):<QUESTION)>What happens when ICANN does not agree with the category (ICANN see something as minor internal and community see the same as major material)? Annebeth Lange:Sorry, I have to leave. Cheryl Langdon-Orr:bye ðŸ‘‹ Annabeth Maxim Alzoba (FAITID):Can not use mic, please read my question aloud Maxim Alzoba (FAITID):The same happens few days ago with GDD portal and new click through agreement (so my question was based on it) Jeff Neuman:@Avri - yep Kavouss Arasteh:Iagree with you NOT to add significantly Maxim Alzoba (FAITID):Given the speed Maxim Alzoba (FAITID):of the development of new processes Maxim Alzoba (FAITID):I think such process needs to be design in advance, and not just when needed Maxim Alzoba (FAITID):Please read my 3 lines of text Jeff Neuman:@Maxim - Good point....change in portals did result in new click-through agreement which is fundamentally different than the older one and could result in new terms superceding those in the Registry agreement Maxim Alzoba (FAITID):It was about the venue to resolve disagreements Maxim Alzoba (FAITID):OK. Will do in doc, when back to notebook Dietmar Lenden - Valideus Ltd:Naming Services Portal Kristina Rosette (Amazon Registry):Naming Services Portal Maxim Alzoba (FAITID):Jeff - thanks, that was correct Cheryl Langdon-Orr:I agree Avri, probably best to clarify that Maxim Alzoba (FAITID):sorry, need to drop the call Kristina Rosette (Amazon Registry):Have to drop for another meeting, which I'm also going to participate in from 30,000 feet. (This Internet thing is cool. We should keep it.) I'll read the transcript to catch up. Cheryl Langdon-Orr:ðŸ˜‰ðŸ‘‹ Kavouss Arasteh: Yes exactly as you said Jeff Neuman:yep Kavouss Arasteh:Have the structure of that SIRT is already determined Kavouss Arasteh:Does that SIRT representing the community? Jeff Neuman:Not yet Anne Aikman-Scalese (IPC):I like the standing IRT idea. Need to check all the language again between now and next meeting. Kavouss Arasteh:pls specifically mention that, if possible Anne Aikman-Scalese (IPC):There could be some confusion as to the role of public comments by some in the community so thats' a good idea to clarify Steve Chan:https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.or… Emily Barabas:Saturday 28 October (Day 1) from 12:15-15:00 and Wednesday 1 November (Day 5) from 8:30-12:00 Kavouss Arasteh: Jeff, do we would have a brief report or a working /reference doc. for the first meeting Kavouss Arasteh:we have or we would have, corrected text Martin Sutton:Unable to find the schedule on ICANN60 site - do you have the link? Roger Carney:https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.… Martin Sutton:got it, thx avri doria:unless this group were to decide to change the policy about new gTLDs in the future. Martin Sutton:It was a great session, thanks Jeff Jim Prendergast:thanks Donna Austin, Neustar:I thought it is already the policy that ICANN was to move forward with a next round/application window as soon as possible after the conclusion of the 2012 round. No further approval from the community is required. avri doria:which we have tentively decided not to do Kavouss Arasteh: Prudence and pacient i are of essence Kavouss Arasteh:That is absolutely right Kavouss Arasteh: Green light is in our hand Christa Taylor:Thank-you Kiran Malancharuvil:Thanks Katrin Ohlmer, DOTZON:bye, everybody. Martin Sutton:Thnaks all Cheryl Langdon-Orr:bye ðŸ‘‹

1 0

Recordings, attendance & AC recording from New gTLD Subsequent Procedures Working Group call on Monday, 09 October 2017 15:00 UTC
by Michelle DeSmyter Oct. 9, 2017

Oct. 9, 2017

Dear All, Please find the attendance of the call attached to this email and the MP3 recording below for the New gTLD Subsequent Procedures Working Group call held on Monday, 09 October 2017 at 15:00 UTC. Attendance of the calls is also posted on the agenda wiki page: https://community.icann.org/x/AIJEB MP3: http://audio.icann.org/gnso/gnso-new-gtld-subsequent-09oct17-en.mp3<http://audio.icann.org/gnso/gnso-new-gtld-subsequent-09oct17-en.mp3[mailer.…> Adobe Connect Recording: https://participate.icann.org/p46netym3o7/ The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-newgtld-wg/ Wiki page: https://community.icann.org/x/AIJEB Thank you. Kind regards, Michelle ------------------------------- Adobe Connect chat transcript for Monday, 09 October 2017 Michelle DeSmyter:Dear All, Welcome to the New gTLD Subsequent Procedures Working Group call on Monday, 09 October 2017 at 15:00 UTC. Michelle DeSmyter:Agenda wiki page: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Krishna Seeburn - Kris:yes Theo Geurts:It works Dietmar Lenden - Valideus Ltd:We can hear you Krishna Seeburn - Kris:it works Jim Prendergast:I have an item for AOB - could we get an update from Jeff on the discussuion he and Akram had at the Brands & Domains conference last week? thanks Maxim Alzoba (FAITID ):Hello all Maxim Alzoba (FAITID ):do we have adobe audio ? Jeff Neuman:@Jim - Just to clarify, you want an update on the panel we both were on, correct? We did not have a separate conversation Jim Prendergast:yes Jeff Neuman:ok...cool. I dont mind if others want to add that Jim Prendergast:i just saw the photos Jeff Neuman:Not my best side...... Kristina Rosette (Amazon Registry):Audio is surprisingly good at 30,000 feet. Go figure. Dietmar Lenden - Valideus Ltd:Monday Emily Barabas:WT4 call: Thursday, 12 October 2017 at 03:00 UTC for 60 minutes. Karen Day:From Rubens: "Call two weeks ago canceled due to conflict with WS2 schedule; call last week discussed name collisions, with good progress, and registry services, where there is still more to discuss. Call this week will focus exclusively on registry services. Steve Chan:@Jeff, no, not heard anything new Kristina Rosette (Amazon Registry):W/r/t GAC co-leader, it "may" be the case that their interested person is also running for GAC Chair and I suspect it would be difficult for that person to do both. Perhaps sugget that they can identify an alternate as a way to break the logjam? Jim Prendergast:Jeff - would it also make sense to circultate Martin's name to the email list as only 43 people are on the call? Greg Shatan:Apologies, I have. conflict today. I am only able to join briefly and without audio, Steve Chan:@Jeff, the approval of Cheryl is on the Consent Agenda. Michelle DeSmyter:We have been trying and no answer, we are continuing to dial her avri doria:https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_… Maxim Alzoba (FAITID ):does anyone have shot end URL for the Google doc? Kristina Rosette (Amazon Registry):By "can be implemented", do we mean "Implementable"? If so, should we say that (eg. "clear, implementable . . . )? Kristina Rosette (Amazon Registry):Is the use of passive voice intentional? If not, should we be identifying the actor to avoid future uncertainty? Cheryl Langdon-Orr:sorry to be late... Kristina Rosette (Amazon Registry):That's a general comment (passive voice). Jeff Neuman:I have put Kristina's suggestted text in the Google doc Jeff Neuman:Instead of "effect", can we use "adverse impact" Susan Payne:apologies, I was on another call. can someone tell me where we are in the document please? Jim Prendergast:how is material determined? Kristina Rosette (Amazon Registry):If we're going to use "material effect," we should use ICANN's written definition of it, which would be helpul to have. Martin Sutton:@Susan - towards bottom of third page Kristina Rosette (Amazon Registry):yes Susan Payne:thnx Martin Maxim Alzoba (FAITID ):to example of Minor process update ... lately ICANN updated so called GDD portal with the new Click through agreement (which reregistries , and later potentially applicants have to agree to), and cash things cause delays (unknown tetxt needs to pass through legal, and if the change is significant (as it was last time, the issue potentially is not minor anymore) Martin Sutton:@Susan - using the google doc https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume… Steve Chan:The document being shared should be unsynced. Kristina Rosette (Amazon Registry):@Jeff: having the definition of material effect that ICANN uses will be helpful to your issue, too, I think. Maxim Alzoba (FAITID):<QUESTION)>What happens when ICANN does not agree with the category (ICANN see something as minor internal and community see the same as major material)? Annebeth Lange:Sorry, I have to leave. Cheryl Langdon-Orr:bye ð?‘< Annabeth Maxim Alzoba (FAITID):Can not use mic, please read my question aloud Maxim Alzoba (FAITID):The same happens few days ago with GDD portal and new click through agreement (so my question was based on it) Jeff Neuman:@Avri - yep Kavouss Arasteh:Iagree with you NOT to add significantly Maxim Alzoba (FAITID):Given the speed Maxim Alzoba (FAITID):of the development of new processes Maxim Alzoba (FAITID):I think such process needs to be design in advance, and not just when needed Maxim Alzoba (FAITID):Please read my 3 lines of text Jeff Neuman:@Maxim - Good point....change in portals did result in new click-through agreement which is fundamentally different than the older one and could result in new terms superceding those in the Registry agreement Maxim Alzoba (FAITID):It was about the venue to resolve disagreements Maxim Alzoba (FAITID):OK. Will do in doc, when back to notebook Dietmar Lenden - Valideus Ltd:Naming Services Portal Kristina Rosette (Amazon Registry):Naming Services Portal Maxim Alzoba (FAITID):Jeff - thanks, that was correct Cheryl Langdon-Orr:I agree Avri, probably best to clarify that Maxim Alzoba (FAITID):sorry, need to drop the call Kristina Rosette (Amazon Registry):Have to drop for another meeting, which I'm also going to participate in from 30,000 feet. (This Internet thing is cool. We should keep it.) I'll read the transcript to catch up. Cheryl Langdon-Orr:ð??‰ð?‘< Kavouss Arasteh: Yes exactly as you said Jeff Neuman:yep Kavouss Arasteh:Have the structure of that SIRT is already determined Kavouss Arasteh:Does that SIRT representing the community? Jeff Neuman:Not yet Anne Aikman-Scalese (IPC):I like the standing IRT idea. Need to check all the language again between now and next meeting. Kavouss Arasteh:pls specifically mention that, if possible Anne Aikman-Scalese (IPC):There could be some confusion as to the role of public comments by some in the community so thats' a good idea to clarify Steve Chan:https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.or… Emily Barabas:Saturday 28 October (Day 1) from 12:15-15:00 and Wednesday 1 November (Day 5) from 8:30-12:00 Kavouss Arasteh: Jeff, do we would have a brief report or a working /reference doc. for the first meeting Kavouss Arasteh:we have or we would have, corrected text Martin Sutton:Unable to find the schedule on ICANN60 site - do you have the link? Roger Carney:https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.… Martin Sutton:got it, thx avri doria:unless this group were to decide to change the policy about new gTLDs in the future. Martin Sutton:It was a great session, thanks Jeff Jim Prendergast:thanks Donna Austin, Neustar:I thought it is already the policy that ICANN was to move forward with a next round/application window as soon as possible after the conclusion of the 2012 round. No further approval from the community is required. avri doria:which we have tentively decided not to do Kavouss Arasteh: Prudence and pacient i are of essence Kavouss Arasteh:That is absolutely right Kavouss Arasteh: Green light is in our hand Christa Taylor:Thank-you Kiran Malancharuvil:Thanks Katrin Ohlmer, DOTZON:bye, everybody. Martin Sutton:Thnaks all Cheryl Langdon-Orr:bye ð?‘<

1 0

Work Track 5 GNSO Co-Leader
by Jeff Neuman Oct. 9, 2017

Oct. 9, 2017

All, As discussed on the Full Subsequent Procedures Working Group call a few hours ago, after much deliberation on the phenomenal candidates that stepped forward to serve as the Co-Leader for Work Track 5 from the GNSO, the Working Group leadership has decided to recommend the appointment of Martin Sutton as the GNSO's Co-Leader for WT5. We had four excellent candidates and we wanted to thank all of them for volunteering. We hope that even though they were not selected, that each of the other three nominees will join Work Track 5 and become active members of the group on behalf of the GNSO. The next step will be to submit Martin's name to the GNSO Council for its review. I am including Paul McGrady on this e-mail as our Liaison to the GNSO Council. Unless we hear otherwise from the GNSO Council, we will continue Work Track 5 planning with Martin. Please look out this week for an announcement calling for volunteers to serve on this Work Track. As a reminder, the others appointed to serve as Co-Leaders of Work Track 5 include Christopher Wilkinson from the ALAC and Annabeth Lange from the ccNSO. We are hoping to receive the name of the person serving as a Co-Leader from the GAC in the next day or two. We will continue to keep you updated. Congratulations Martin and welcome to the leadership team! Best regards, Avri, Cheryl and Jeff Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514 M: +1.202.549.5079 @Jintlaw

3 2

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 9 October 2017
by Emily Barabas Oct. 9, 2017

Oct. 9, 2017

Dear WG Members, Please see below notes and action items from the meeting today, 9 October 2017. These high-level notes are designed to help Working Group members navigate through the content of the call and are not meant to be a substitute for the recording. Recordings, call transcripts, chat transcripts, and other documents are available at https://community.icann.org/x/AIJEB. Kind regards, Emily -------------------------------------------------------------------------------------------------------------------------------------------- ACTION ITEM: Leadership will send follow-up email to Tom Dale to see if the GAC can provide a co-leader on a provisional basis prior to ICANN60. ACTION ITEM: Leadership will send name of recommended candidate to the WG mailing list. Notes: 1. Welcome/SOIs - No SOI updates 2. Work Track Updates – WT1-4 - WT1 (Christa Taylor) - upcoming discussion topic - costing and clarity of application process - review of CC2 Comments - WT2 (Michael Flemming) - recent discussions have focused on Closed Generics, the WT has been looking at objections and language included in decisions. Upcoming meeting is on Thursday and will continue to focus on Closed Generics. - WT3 (Karen Day) - Upcoming meeting is tomorrow at 20:00, will focus on CC2 review - String Similarity and Freedom of Expression. There is a call tentatively scheduled for 24 Oct, the group will discuss whether to move or cancel the meeting. - WT4 - the upcoming call will take place WT4 call: Thursday, 12 October 2017 at 03:00 UTC for 60 minutes. Call two weeks ago canceled due to conflict with WS2 schedule; call last week covered name collisions, with good progress, and registry services, where there is still more to discuss. Call this week will focus exclusively on registry services (questions asked in the application on registry services). 3. Work Track 5 Update - ALAC has selected Christopher Wilkinson to serve as WT5 leader. - ccNSO has selected Annebeth Lange. - No name has been provided by the GAC yet, although the GAC has said that a person has been selected and the name will be shared soon. - GAC may consider detaching the identification of co-leader and the discussion of conditions related to participation. Even if the person is provisional, it would be good to include that person in discussions with the other co-leaders prior to Abu Dhabi ACTION ITEM: Send follow-up email to Tom Dale to see if the GAC can provide a co-leader on a provisional basis prior to ICANN60. From the chat: Kristina Rosette (Amazon Registry): W/r/t GAC co-leader, it "may" be the case that their interested person is also running for GAC Chair and I suspect it would be difficult for that person to do both. Perhaps sugget that they can identify an alternate as a way to break the logjam? - Four people have expressed interest in serving as the GNSO co-leader. All provided permission to share their expression of interest last week. There was a discussion period on the mailing list. - Leadership team feels that any one of the candidates could be a great co-leader, but will recommend one person. The leadership team hopes that the Working Group agrees with this recommendation. The leadership team recommends Martin Sutton. He has served in a number of leadership positions at ICANN and currently serves as Executive Director of BRG. He comes highly recommended. - The WG will also ask the GNSO Council to affirm the candidate. - No objections raised to this recommendation. ACTION ITEM: Send name of recommended candidate to the WG mailing list. - If any objections are raised on the WG mailing list from GNSO members, the Council can take these objections into account. - Call for volunteers will go out at the end of the week. All are welcome and encouraged to participate in WT5. - Last week the WG provisionally selected CLO for WG co-chair. This was submitted to GNSO Council, and will be on the consent agenda for the meeting this week. Cheryl will take over as a third co-chair effective immediately. After Abu Dhabi, she will continue to serve as co-chair after Avri leaves. 4. Drafting Team Discussion continued – Predictability Framework - We are getting close to a point where we can come to closure on these documents and reach first reading. Perhaps we can get to a first reading on this document after today's call. - (Reading through edits in the working document: https://docs.google.com/document/d/1lzXxBLMtFr03BKnHsa-Ss7kR7EAJt7pCI1EP3H8…) From the chat: Kristina Rosette (Amazon Registry): Is the use of passive voice intentional? If not, should we be identifying the actor to avoid future uncertainty? Kristina Rosette (Amazon Registry): That's a general comment (passive voice). Jeff Neuman: I have put Kristina's suggestted text in the Google doc - No objections raised to edits in Problem Statement and Anticipated Outcome. - Community Engagement section: From the chat: Kristina Rosette (Amazon Registry): By "can be implemented", do we mean "Implementable"? If so, should we say that (eg. "clear, implementable . . . )? - The Predictability Framework section: -- No objections raised to text in phase 1, 2 -- Suggestions to phase 3 text made inline in working document. -- "By way of example, the need for new contractual requirements is vastly different than ICANN meeting staffing needs by hiring a contractor." Additional wording needed following this sentence to explain the difference. - Categories/Types of Changes: -- No objections raised to examples added under Minor Process Updates. -- Revised Processes/Procedures: no objections raised to suggested deletions. From the chat: Jeff Neuman: Instead of "effect", can we use "adverse impact" (In reference to sentence "Definition: A change to ICANN’s internal processes that have an effect on applicants or other community members.") - Does someone need to determine an adverse impact up front? - Any change could in theory have an effect, so the term may be too broad. - Consider using the term "material effect" which is used earlier in the document. This will be added. From the chat: Jim Prendergast: how is material determined? Kristina Rosette (Amazon Registry): If we're going to use "material effect," we should use ICANN's written definition of it, which would be helpul to have. Maxim Alzoba (FAITID ): to example of Minor process update ... lately ICANN updated so called GDD portal with the new Click through agreement (which reregistries , and later potentially applicants have to agree to), and cash things cause delays (unknown tetxt needs to pass through legal, and if the change is significant (as it was last time, the issue potentially is not minor anymore) - Add footnotes throughout text with ICANN's definition of "material effect." - New Processes/Procedures -- An example was added - no objections raised. This example may need to be adjusted based on recommendations of the WG. -- Consider adding "material effect" in this text as well. This may need some addtional thinking before an edit is made. From the chat: Kristina Rosette (Amazon Registry): @Jeff: having the definition of material effect that ICANN uses will be helpful to your issue, too, I think. - Fundamental, Possibly Policy-Level Changes - We may also need a definition of “significant” if we keep this word in the text. - We may need to provide criteria for impact -- for “material,” the criteria will be those defined by ICANN org. As discussed previously, those will be added in a footnote to the document. From the chat: Maxim Alzoba (FAITID): <QUESTION)>What happens when ICANN does not agree with the category (ICANN see something as minor internal and community see the same as major material)? Kavouss Arasteh: Iagree with you NOT to add significantly - Regarding Maxim's comment in the chat -- this issue is discussed at the top of page 4 in the document. - why do we use materially and significantly? Maybe we should remove significantly and leave materially. - Consider adding a statement that the change will not be implemented until the entire process has been completed. From the chat: Maxim Alzoba (FAITID): The same happens few days ago with GDD portal and new click through agreement (so my question was based on it) Maxim Alzoba (FAITID): Given the speed Maxim Alzoba (FAITID): of the development of new processes Maxim Alzoba (FAITID): I think such process needs to be design in advance, and not just when needed Jeff Neuman: @Maxim - Good point....change in portals did result in new click-through agreement which is fundamentally different than the older one and could result in new terms superceding those in the Registry agreement Maxim Alzoba (FAITID): It was about the venue to resolve disagreements - In the expected mitigation strategy for internal changes within ICANN org -- the text states that communication with the community would happen before the solution is deployed. - Discussion of Maxim’s comment in the chat -- ICANN is moving to a new portal called the Naming Services Portal -- the changes are technically minor, but there is a new legal document that users are concerned about. There is a disagreement about whether the change is major or minor. How do we determine whether the change is major or minor? - Suggestion: perhaps if any stakeholder thinks the change is major it should be considered major. - This question should be considered further. We need to further define criteria to determine if a change is major. - New Policy -- -- This section answers a lot of the determinative questions raised in response to earlier sections of the document. -- Is this SIRT good as a basis for addressing the questions on the table? From the chat: Kavouss Arasteh: Have the structure of that SIRT is already determined Kavouss Arasteh: Does that SIRT representing the community? Jeff Neuman: Not yet Anne Aikman-Scalese (IPC): I like the standing IRT idea. Need to check all the language again between now and next meeting. Kavouss Arasteh: pls specifically mention that, if possible 5. ICANN60 Planning - Final schedule is posted: https://schedule.icann.org[schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__schedule.icann.org&d=D…>/ - SubPro meetings are Saturday 28 October (Day 1) from 12:15-15:00 and Wednesday 1 November (Day 5) from 8:30-12:00 - The first session will be devoted to WT 1-4. - The second session will focus of WT5 Terms of Reference and brainstorming on issues for the WT. - In another session, WT leads will update the GAC on Applicant Support and Communities. - The draft TOR will be posted as soon as possible for discussion 6. AOB - Brands and Domains conference was Held last Monday, Tuesday, and Wednesday in the Hague - There was a panel in which Jeff and Akram participated, Jeff contributed in personal capacity. - Akram did not want to move forward with New gTLD Program until the community provides permission to do so. - Jeff said the GNSO already has a policy, does not need permission to proceed with subsequent procedures. From the chat: avri doria: unless this group were to decide to change the policy about new gTLDs in the future. Donna Austin, Neustar: I thought it is already the policy that ICANN was to move forward with a next round/application window as soon as possible after the conclusion of the 2012 round. No further approval from the community is required. avri doria: which we have tentively decided not to do Kavouss Arasteh: Prudence and pacient i are of essence Kavouss Arasteh: That is absolutely right Kavouss Arasteh: Green light is in our hand

1 0