- IPC-GNSO - lists.icann.org

Register Now: Pre-ICANN61 Policy Open House – 1 March 2018 - ICANN
by Chantelle Doerksen Feb. 8, 2018

Feb. 8, 2018

https://www.icann.org/news/announcement-2-2018-02-08-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Register Now: Pre-ICANN61 Policy Open House – 1 March 2018 The Policy Development Support Team is pleased to announce two sessions for an upcoming webinar: Pre-ICANN61 Policy Open House Thursday, 1 March 2018 10:00 and 19:00 Coordinated Universal Time (UTC) The webinar will run in English and will be conducted in Adobe Connect along with a dial-in conference bridge for audio. Recordings of the sessions will be made available here[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. Please register via this form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_vZw8kM&d=DwMGaQ…> by 26 February 2018! In this interactive 60-minute open house, the focus will be an active question and answer session with the Policy Development Support Team. To ensure that your questions about policy activities are addressed during the session, the Policy Team invites you to submit your questions through the registration form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_dVbmhQOT8…> or email them to policyinfo(a)icann.org<mailto:policyinfo@icann.org>. To assist with your preparation for this webinar and for ICANN61, the "Pre-ICANN61 Policy Report" and "Generic Names Supporting Organization Policy Briefing: ICANN61 Edition" will be published by Monday, 26 February 2018. Please be sure to download and review these materials beforehand for helpful background on policy activities and topics that the Policy Development Support Team will discuss during the open house, such as: * An overview of the cross-community discussions that will take place at ICANN61: * General Data Protection Regulation (GDPR): WHOIS Compliance Models * A Walk in the Shoes of a New Generic Top-Level Domain (gTLD) Registry Operator * Name Collisions * Open Data at ICANN * Policy development processes underway in the Country Code Names Supporting Organization (ccNSO), the Generic Names Supporting Organization (GNSO) and the Address Supporting Organization (ASO): * Retirement of Country Code Top-Level Domains (ccTLDs) * Review of All Rights Protection Mechanisms in All gTLDs * Next-Generation Registration Directory Service to Replace WHOIS * International Governmental Organizations and International Non-Governmental Organizations Access to Curative Rights Dispute Resolution Mechanisms * Protections for Red Cross National Society Names in the Domain Name System * New gTLD Subsequent Procedures * Regional Internet Registry policy development activities * Advisory Committee activities within the At Large Advisory Committee (ALAC), Governmental Advisory Committee (GAC), Root Server System Advisory Committee (RSSAC) and Security & Stability Advisory Committee (SSAC): * Organizational Review of the At-Large community * At-Large Summit (ATLAS) III * GAC discussion on the .amazon Independent Review Process * GAC discussion on evolving relationships with ICANN Board and ICANN Org * RSSAC statement on entries in DNS Root Sources * RSSAC & SSAC Response to the GNSO's New gTLD Subsequent Procedures Working Group on Root Scaling * SSAC Response to the ICANN Internationalized Domain Name Guidelines Working Group * SSAC work concerning the use of emoji in domain names * Other topics of note: * Organizational Review of the ASO * ccNSO Rejection Action Procedure as a Decisional Participant in the ICANN Empowered Community * Impact of ICANN's Implementation of the General Data Protection Regulation (GDPR) on ccTLDs The Policy Development Support Team looks forward to helping the ICANN community prepare for ICANN61! Please register via this form[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_vZw8kM&d=DwMGaQ…> by 26 February 2018! About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.

1 0

IPC Input Requested - Proposed GDPR/WHOIS Discussion Event (Tentative Date January 25, 2018)
by Brian Winterfeldt Jan. 19, 2018

Jan. 19, 2018

Dear colleagues, As mentioned during today's IPC membership meeting, we are hoping to hold an event next week, tentatively scheduled for the afternoon of Thursday, January 25, 2018, to discuss the various GDPR compliance models published by ICANN for community input. Our tentative plan is to host the event in our WIPG offices in Washington, DC to accommodate in-person attendance, as well as provide remote participation for any IPC members and other interested community participants who are unable to attend in person. As noted during the membership meeting, this date should help us leverage the event being hosted by the Global Innovation Policy Center (GIPC) of the U.S. Chamber of Commerce earlier in the day with Cherine Chalaby, Chair of the ICANN Board of Directors. The primary purpose of the event would be to present and discuss the various models, in order to help clarify our thinking and advocacy approach in responding to ICANN's request for input, and to also demonstrate to ICANN and the wider community that the IPC and its allies are coordinated and focused on this very critical issue. Please let us know whether you have any objection to holding this proposed event. Otherwise, please share any comments, questions, or suggestions with us so we can be sure that the event is as impactful as possible. Thank you, Brian ________________________________ [https://daks2k3a4ib2z.cloudfront.net/59358b8cf7332631232417e8/595fb59d73c5b…]<https://www.winterfeldt.law/> Brian J. Winterfeldt Principal Winterfeldt IP Group 1200 17<x-apple-data-detectors://12/1>th<x-apple-data-detectors://12/1> St NW<x-apple-data-detectors://12/1>, Ste 501<x-apple-data-detectors://12/1> Washington, DC 20036<x-apple-data-detectors://12/1> brian(a)winterfeldt.law<mailto:brian@winterfeldt.law> +1 202 903 4422

7 6

FW: [IPC Discussion List] Fwd: [Ext] Re: Attendance, AC recording and AC chat / GNSO Council Drafting Team Charter ICANN Procedure for Handling Whois Conflicts / Wednesday, 10 January 2018 at 22:00 UTC
by Brian Winterfeldt Jan. 17, 2018

Jan. 17, 2018

Resending while our “listserv” is taking a break! ________________________________ [https://daks2k3a4ib2z.cloudfront.net/59358b8cf7332631232417e8/595fb59d73c5b…]<https://www.winterfeldt.law/> Brian J. Winterfeldt Principal Winterfeldt IP Group 1200 17<x-apple-data-detectors://12/1>th<x-apple-data-detectors://12/1> St NW<x-apple-data-detectors://12/1>, Ste 501<x-apple-data-detectors://12/1> Washington, DC 20036<x-apple-data-detectors://12/1> brian(a)winterfeldt.law<mailto:brian@winterfeldt.law> +1 202 903 4422 From: Brian Winterfeldt Sent: Tuesday, January 16, 2018 8:01 PM To: 'listserv(a)ipconstituency.org' <listserv(a)ipconstituency.org>; 'haforrestesq(a)gmail.com' <haforrestesq(a)gmail.com>; 'icannlists(a)winston.com' <icannlists(a)winston.com> Cc: Kiran Malancharuvil <Kiran(a)winterfeldt.law>; Phillip Marano <Phil(a)Winterfeldt.law>; Griffin Barnett <Griffin(a)Winterfeldt.law> Subject: RE: [IPC Discussion List] Fwd: [Ext] Re: Attendance, AC recording and AC chat / GNSO Council Drafting Team Charter ICANN Procedure for Handling Whois Conflicts / Wednesday, 10 January 2018 at 22:00 UTC Importance: High Dear Heather and all, With apologies for not weighing in on the call, we support the charter as edited, which narrows the scope to focus on procedure and not policy. We will want to keep a close watch on the progress of the group, but the edits to the charter appropriately addressed our concerns. We also support you making the motion as Council Chair, but would ask that you make it clear that you are making the motion as Chair to facilitate progress and compromise. We think it is important to avoid the optics that the IPC sponsored this motion. Thank you! Best, Brian ________________________________ [https://daks2k3a4ib2z.cloudfront.net/59358b8cf7332631232417e8/595fb59d73c5b…]<https://www.winterfeldt.law/> Brian J. Winterfeldt Principal Winterfeldt IP Group 1200 17<x-apple-data-detectors://12/1>th<x-apple-data-detectors://12/1> St NW<x-apple-data-detectors://12/1>, Ste 501<x-apple-data-detectors://12/1> Washington, DC 20036<x-apple-data-detectors://12/1> brian(a)winterfeldt.law<mailto:brian@winterfeldt.law> +1 202 903 4422 From: listserv(a)ipconstituency.simplelists.com<mailto:listserv@ipconstituency.simplelists.com> [mailto:listserv@ipconstituency.simplelists.com] On Behalf Of Heather Forrest Sent: Friday, January 12, 2018 2:40 AM To: Paul McGrady <policy(a)paulmcgrady.com<mailto:policy@paulmcgrady.com>>; IPC Discussion List <listserv(a)ipconstituency.org<mailto:listserv@ipconstituency.org>> Subject: [IPC Discussion List] Fwd: [Ext] Re: Attendance, AC recording and AC chat / GNSO Council Drafting Team Charter ICANN Procedure for Handling Whois Conflicts / Wednesday, 10 January 2018 at 22:00 UTC Dear colleagues (especially our WHOIS experts), Status update on WHOIS Conflicts Procedure charter drafting in the attached clean draft, which integrates the comments made by Bradley Silver (which, happily, were in line with RrSG comments). Two questions: 1. Can IPC support this document? 2. Is IPC opposed to me being the maker of the motion as Council Chair? (I'm trying to assume a leadership role in bringing everyone together on this one in a reasonably harmonious way, but I know we object in principle to the formation of this new group given our participation in the previous IAG, so I can fully appreciate objections, if there are any.) Best wishes, Heather ---------- Forwarded message ---------- From: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>> Date: Fri, Jan 12, 2018 at 6:35 PM Subject: Re: [Ext] Re: Attendance, AC recording and AC chat / GNSO Council Drafting Team Charter ICANN Procedure for Handling Whois Conflicts / Wednesday, 10 January 2018 at 22:00 UTC To: Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> Cc: Julie Bisland <julie.bisland(a)icann.org<mailto:julie.bisland@icann.org>>, "kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>" <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>>, Stephanie Perrin <stephanie.perrin(a)mail.utoronto.ca<mailto:stephanie.perrin@mail.utoronto.ca>>, Michele Blacknight <michele(a)blacknight.com<mailto:michele@blacknight.com>>, Pam Little <pam.little(a)alibaba-inc.com<mailto:pam.little@alibaba-inc.com>>, Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, Paul McGrady <policy(a)paulmcgrady.com<mailto:policy@paulmcgrady.com>> Dear WHOIS Conflicts charter drafting team, As agreed in our call of 10 January, Marika and I have distilled the points raised by Stephanie, RrSG and IPC into the attached clean document. For easier reading, rather than send a messy redline, I've highlighted in yellow the relevant areas of change which require your focussed review. There remains one outstanding point, which is staff support. We need to decide whether it should be GNSO Policy or GDD to support this effort. We are one week away from the January Council document deadline. If we are to make that deadline, we must get the document circulated to SGs/Cs and any tinkering done by next Friday 20th. If we're not at a point of agreement by next Friday, I'll exercise my discretion to hold the motion until February. As we've said on other occasions, and I see no reason to be inconsistent now, this matter is too important to the GNSO community to duke it out in a vote. Let's be sure to reach agreement before it goes to a vote at Council. With best wishes to all, Heather On Thu, Jan 11, 2018 at 9:59 AM, Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> wrote: All, Here are the informal notes that staff captured during the meeting as well. There are some AC chat contributions included in the notes, but you may want to review the full chat transcript and/or the recording for better context. Best, Steve ACTION: Marika, Heather to revise draft charter, particularly scope and composition section in line with input received. Try to have draft before end of week. ACTION: Prepare draft of motion for upcoming meeting --RrSG - General support for keeping it simple. Composition like a group like the GNSO Review. Scope: -- Keep it narrow, on process and procedure, not on policy. -- Any review of policy should take place in a PDP, though it could identify policy issues to be referred to a PDP for resolution. -- More support for a light and simple scope -- Should try to guard against reaching a similar conclusion of IAG (e.g., no solution). -- User rights - could a user request an exemption for publication of their data in Whois -- The scope of the this DT is only for the charter, not the substance -- Review of the procedure - no timeline available now. -- Can review of the implementation be part of the scope? Currently, focuses on public comment received. Up to DT to determine if it could be included. Pam Little: "The proposal does not establish expectations for the timeline of a review.The apparent expectation that contracted parties continue to comply with WHOIS requirements while the review is ongoing is doubly problematic when paired with the fact that the Procedure does not provide a timeline by which such review will occur. ICANN’s handling of the Registry Service Evaluation Request Process (RSEP) has been notoriously slow despite a clear timeline set in the consensus policy establishing a reasonable timeline for review to occur. The Procedure should include a similarly expedited timeline for granting an initial waiver of enforcement, given legal compliance risks to contracted parties if conflicts are drawn out." Pam Little: This was the comment by RySG/RrSG -- Current scope would pick up Pam's concern, by focusing on public comment. -- Previous comments may not have identified feasible triggers, so limiting to existing comments could be problematic. Composition: -- GNSO Review: Each SG/C provides a primary and alternate member. Observers are welcome (no limit), but concensus limited to members. -- Preliminary support from Pam. Pam Little: Although one RrSG member proposed (preferred) CCWG model but that seems to be a minority view Marika Konings: you may need to specify, like for the SSC charter what that breaks down to so that there is no duplication on the NCPH between Cs & SGs on that side? -- It may be helpful to be specific about ow allocations are done (SG and/or C). See Option 4. Pam Little: When we consider composition, I think we should keep in mind that the contracted parties are those who will be directed impacted this so they should not have less reps than other groups. Marika Konings: appointments per SG could ensure parity, while at the same time allowing SGs on the NCPH to factor in the need for each C to have representation? Marika Konings: For example, 3 members per SG? -- Could be "up to" 3 members rather than requiring 3, but it may be good to have a minimum. From: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>> Date: Wednesday, January 10, 2018 at 2:54 PM To: Julie Bisland <julie.bisland(a)icann.org<mailto:julie.bisland@icann.org>> Cc: "kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>" <kdrazek(a)verisign.com<mailto:kdrazek@verisign.com>>, icannlists <icannlists(a)winston.com<mailto:icannlists@winston.com>>, Stephanie Perrin <stephanie.perrin(a)mail.utoronto.ca<mailto:stephanie.perrin@mail.utoronto.ca>>, Michele Blacknight <michele(a)blacknight.com<mailto:michele@blacknight.com>>, Pam Little <pam.little(a)alibaba-inc.com<mailto:pam.little@alibaba-inc.com>>, Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>, Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: [Ext] Re: Attendance, AC recording and AC chat / GNSO Council Drafting Team Charter ICANN Procedure for Handling Whois Conflicts / Wednesday, 10 January 2018 at 22:00 UTC Thanks very much, Julie - Just a quick note so everyone has a clear view of current status. We were missing Keith, Paul and Michele on the call, but Stephanie, Pam and I forged ahead and commented on the two big issues - scope and composition. Next steps: * Marika and I will work on a next version strawman that captures the RrSG, NCSG and IPC inputs, circulating to the group by close Friday LA time. That then gives us all ONE WEEK to circulate within our respective SGs/Cs in order to edit as needed and be ready for document deadline next Friday. * Marika and staff team to draft motion for inclusion in Council agenda in time for review by the group and document deadline Sincere thanks to Pam and Stephanie for helping to move this forward today, and as always to staff for their excellent support. Best wishes, Heather On Thu, Jan 11, 2018 at 9:48 AM, Julie Bisland <julie.bisland(a)icann.org<mailto:julie.bisland@icann.org>> wrote: Dear all, Please find attached the AC chat and below the AC recording and attendance of the GNSO Council Drafting Team Charter ICANN Procedure for Handling Whois Conflicts held on Wednesday, 10 January 2018 at 22:00 UTC. AC Recording: https://participate.icann.org/p5ctyusfhk4/<https://participate.icann.org/p5ctyusfhk4/?OWASP_CSRFTOKEN=f6e4081fec6a3980…> Attendance: Heather Forrest, Stephane Perrin, Pam Little Apology: Michele Neylon Staff: Marika Konings, Steve Chan, Julie Bisland Thank you. Kind regards, Julie

1 0

ListServ Email List
by Andrea Glandon Jan. 16, 2018

Jan. 16, 2018

Dear all, We are currently experiencing technical issues with the private list, listserv(a)ipconstituency.org<mailto:listserv@ipconstituency.org>, please do not use listserv until the issues have been resolved. I will send an email when this list is working again. Kind Regards, Andrea Glandon | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation for Assigned Names and Numbers Skype: acglandon76(a)yahoo.com | M: +1-563-940-8403

1 0

IPC Membership Meeting Agenda - Tuesday, January 16, 2018 at 22:00 UTC
by Brian Winterfeldt Jan. 16, 2018

Jan. 16, 2018

Dear IPC: Please find attached, the agenda for the Membership Call TODAY, Tuesday January 16, 2018 at 22:00 UTC. As a reminder, we are still testing a combination one hour Membership and Policy Call, and times allotted for each topic are noted. Further discussion is encouraged in small volunteer groups and on the list. Paul/Heather, can you please circulate the GNSO Council Update at your convenience prior to the call. I look forward to speaking with you all soon! Best, Brian ________________________________ [https://daks2k3a4ib2z.cloudfront.net/59358b8cf7332631232417e8/595fb59d73c5b…]<https://www.winterfeldt.law/> Brian J. Winterfeldt Principal Winterfeldt IP Group 1200 17<x-apple-data-detectors://12/1>th<x-apple-data-detectors://12/1> St NW<x-apple-data-detectors://12/1>, Ste 501<x-apple-data-detectors://12/1> Washington, DC 20036<x-apple-data-detectors://12/1> brian(a)winterfeldt.law<mailto:brian@winterfeldt.law> +1 202 903 4422

1 0

IGF MKD Internet Governance Forum Macedonia 2017
by Aleksandar Icokaev Nov. 23, 2017

Nov. 23, 2017

1 1

Fwd: [liaison6c] GNSO Council resolution 1 November 2017
by Greg Shatan Nov. 7, 2017

Nov. 7, 2017

Please see below for the resolution passed by the GNSO Council at ICANN60 in Abu Dhabi. Greg Shatan IPC President ---------- Forwarded message ---------- From: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Mon, Nov 6, 2017 at 3:29 AM Subject: [liaison6c] GNSO Council resolution 1 November 2017 To: "liaison6c(a)gnso.icann.org" <liaison6c(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Dear all, The following resolution was adopted by the GNSO Council at its meeting on Wednesday, 1 November 2017. *Motion – Appointment of a GNSO Liaison to the Governmental Advisory Committee* *Submitted by Susan Kawaguchi* *Seconded by James Bladel* Whereas: 1. As part of the discussions within ICANN between the GNSO and GAC, on how to facilitate early engagement of the GAC in GNSO policy development activities, a GNSO liaison to the GAC was piloted during FY15 and FY16. 2. Based on the review of the GAC-GNSO Consultation Group (see http://gnso.icann.org/en/drafts/review-liaison-gac- pilot-29feb16-en.pdf[gnso.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>) and discussions between the GAC and GNSO during their joint session at the ICANN meeting in Marrakesh, the GNSO Council confirmed on 14 April 2016 role and process for a GNSO Liaison to the Governmental Advisory Committee as a permanent feature (see https://gnso.icann.org/ en/drafts/request-liaison-gac-30mar16-en.pdf)[gnso.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> . 3. The GNSO Council delegated the responsibility of the application, review and selection process to the GNSO Standing Selection Committee (SSC). 4. Following a call for candidates three applications were received all of which were evaluated by the SSC based on the criteria outlined in the call for candidates. 5. Full consensus was achieved by the SSC for selecting Julf Helsingius as the preferred candidate. The SSC subsequently recommended to the GNSO Council that Julf Helsingius be appointed to the role of GNSO Liaison to the GAC. Resolved: 1. The GNSO Council hereby appoints Julf Helsingius to the role of GNSO Liaison to the Governmental Advisory Committee until the end of the ICANN AGM 2018. 2. The GNSO Council will review the role and is expected to annually reconfirm the appointment, unless the review indicates otherwise and/or the Liaison has indicated that he/she is no longer available to continue in this role in which case a new selection process will take place and/or the review indicates. 3. The GNSO Council Leadership Team will co-ordinate with Julf Helsingius as well as the GAC Leadership Team and GAC Secretariat on next steps and the successful implementation of this role. 4. The GNSO Council and the SSC thank all the candidates for their interest and would like to express its appreciation for the highly qualified applications received. 5. The GNSO Council thanks Carlos Raul Guttierez for his service as the GNSO Council Liaison to the GAC. Vote Results[gnso.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> Thank you, Nathalie _______________________________________________ liaison6c mailing list liaison6c(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/liaison6c

2 1

Safety
by Jonathan Cohen Oct. 18, 2017

Oct. 18, 2017

Just saw a ranking of the 50 safest cities in the world #1 The safest city is.... Sitting down?..... Abu Dhabi!!! Sent from my iPhone Jonathan Cohen Of Counsel P: 1-613-232-5300 ext.317 mailto:jcohen@shapirocohen.com http://www.shapirocohen.com Shapiro Cohen LLP | Intellectual Property Law Celebrating over 50 years of IP protection P: 613-232-5300 F: 613-563-9231 P.O. Box 13002, Kanata, ON Canada K2K 0E2 200 - 411 Legget Drive, Ottawa, ON Canada K2K 3C9 ----------------------------- This correspondence is intended for the person to whom it is addressed and may contain information that is confidential, privileged or proprietary in nature. If you have received this e-mail in error, please notify us immediately and delete this e-mail from your mail box. From time to time, e-mails do not reach their intended recipient. If your e-mail contains time-sensitive instructions and you do not receive a prompt acknowledgement, please follow up by fax or telephone. -----------------------------

3 3

GNSO Policy Briefing for ICANN60
by Greg Shatan Oct. 14, 2017

Oct. 14, 2017

Fellow IPC Members, The GNSO Policy Briefing is now available at https://gnso.icann.org/en/ issues/policy-briefing. Whether or not you are going to iCANN60, this is a very useful snapshot of current policy activity in the GNSO. Greg David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) _______________________________________________ So-ac-sg-cleaders mailing list So-ac-sg-cleaders(a)icann.org https://mm.icann.org/mailman/listinfo/so-ac-sg-cleaders

1 0

ICANN Webinar on Operating Standards for Reviews 19 October 2017
by Greg Shatan Oct. 13, 2017

Oct. 13, 2017

Join the ICANN webinar on Review Operating Standards <http://icann.org/news/announcement-2-2017-10-12-en> LOS ANGELES - 12 October 2017 - The Internet Corporation for Assigned Names and Numbers (ICANN) organization will host a webinar on the draft Operating Standards, which will be released for public comment on 17 October. This Bylaw-mandated document has been compiled by the ICANN organization with community input (see below). It contains guidelines and best practices for ICANN's four specific reviews. During the 19 October webinar, the ICANN organization will provide an overview of the draft, explain the underlying principals, and highlight the existing review best practices and processes o... Read more <http://icann.org/news/announcement-2-2017-10-12-en>

1 0