- IPC-GNSO - lists.icann.org

Fwd: [isoc-ny] Fwd: 2017 Global Survey on Internet Security and Trust
by Greg Shatan April 25, 2017

April 25, 2017

I thought this would be of interest to many of you, especially given how often the word "trust" comes up in ICANN conversations. I have not read the report yet, but if anyone sees results that would be of particular interest to the IPC in ICANN policy discussions, or more generally, please share it with the group. Thanks! Greg ---------- Forwarded message --------- From: ISOC-NY announcements <announce(a)lists.isoc-ny.org> Date: Tue, Apr 25, 2017 at 8:17 AM Subject: [isoc-ny] Fwd: 2017 Global Survey on Internet Security and Trust To: announce_list <announce(a)isoc-ny.org> A message from the Internet Society's Vice President of Global Policy Development . ---------- Forwarded message ---------- 2017 Global Survey on Internet Security and Trust <https://connect.internetsociety.org/communities/community-home/digestviewer…> [image: Sally Wentworth] <https://connect.internetsociety.org/network/members/profile/?UserKey=69a755…> Apr 25, 2017 7:26 AM Sally Wentworth <https://connect.internetsociety.org/network/members/profile/?UserKey=69a755…> Dear colleagues, Yesterday, it was my pleasure to join CIGI-Ipsos in Geneva for the launch of their 2017 Global Survey on Internet Security and Trust. The Internet Society is a proud sponsor of this survey, which examines important issues such as the state of online trust and Internet use across 24 economies around the world. We encourage you to read the results here <https://www.cigionline.org/internet-survey>. One of the questions respondents were asked was whether they agree with the statement "overall, I trust the Internet". Only 56% responded that they agree with that statement. This underlines how important it is that we address online trust. First, by understanding what builds and maintains user trust, as well as what destroys trust. And, second by taking action now. Among the main reasons given for this lack of trust were: - the Internet is not secure - the Internet is not reliable - the Internet does not allow them to communicate privately. If we don't trust the Internet, we won't want to use it to its fullest extent. What's worse, we may event stop using it all together. This could have a serious impact on the evolution of the Internet, its use, and growth. One essential way to build an Internet people trust is by implementing strong encryption to protect their online interactions. Strong encryption is a critical piece to the future of the world's economy. Online, it should be the norm. It allows us to confidently do our banking, conduct business, operate communications networks and share information privately. I invite you to join us in encouraging business and government leaders around the world to build trust and strengthen the Internet through encryption. ------------------------------ wentworth(a)isoc.org Vice President -- Joly MacFie President - Internet Society New York Chapter (ISOC-NY) http://isoc-ny.org 218 565 9365 ____ Internet Society - NYC Metropolitan Area Chapter http://isoc-ny.org 'The Internet is for Everyone." ___________________________________________ Announce mailing list Announce(a)lists.isoc-ny.org http://lists.isoc-ny.org/listinfo.cgi/announce-isoc-ny.org -- *Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc(a)gmail.com

1 0

Input requested: CCWG Accountability Work Stream 2: please complete the Ombudsman Survey
by Chantelle Doerksen April 19, 2017

April 19, 2017

** sent on behalf of CCWG Accountability Work Stream 2** Dear all, As part of the CCWG Accountability Work Stream 2 assignments, the ICANN Office of the Ombudsman is currently being assessed by an independent assessor. It would be great if you could spare 5-10min maximum to take part in the survey that closes at the end of this week. Survey link: http://www.surveygizmo.com/s3/3462816/ICANN Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC 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

Fwd: [Soac-infoalert] ICANN News Alert -- Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available
by Greg Shatan April 19, 2017

April 19, 2017

FYI *Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc(a)gmail.com ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Wed, Apr 19, 2017 at 1:25 AM Subject: [Soac-infoalert] ICANN News Alert -- Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available To: "soac-infoalert(a)icann.org" <soac-infoalert(a)icann.org> [image: ICANN] <http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2017-04-18-en ------------------------------ Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available 18 April 2017 LOS ANGELES – 18 April 2017 – The Internet Corporation for Assigned Names and Numbers (ICANN) today published the updated Procedure for Handling WHOIS Conflicts with Privacy Laws (WHOIS Procedure), which is effective immediately. *Read the Revised WHOIS Procedure <https://www.icann.org/resources/pages/whois-privacy-conflicts-procedure-200…>.* The WHOIS Procedure has been revised to incorporate an alternative trigger to invoke the WHOIS Procedure. The current trigger in the WHOIS Procedure allows a registry operator or ICANN-accredited registrar to invoke the procedure if the contracted party is in receipt of a notification of an action that its compliance with WHOIS obligations is prevented by local laws. With the additional trigger, a registry operator or ICANN-accredited registrar may now also invoke the WHOIS Procedure by providing ICANN with a written statement from the applicable government agency responsible for enforcing its data privacy laws and indicating that a WHOIS obligation in an ICANN contract conflicts with such applicable national law. The modification to the WHOIS Procedure is based on input from the community and the work of an Implementation Advisory Group (IAG), which was tasked with reviewing possible changes to the WHOIS Procedure and providing the Generic Names Supporting Organization (GNSO) with recommendations to facilitate resolution of issues where WHOIS requirements conflict with applicable laws. In May 2016, the IAG submitted its final report <https://gnso.icann.org/en/drafts/iag-review-whois-conflicts-procedure-23may…> [PDF, 155 KB] and recommendation to the GNSO Council. In February 2017, the GNSO Council passed a resolution <https://gnso.icann.org/en/council/resolutions#201703> adopting IAG's recommendation and confirmed that the modification to the WHOIS Procedure does not change the intent of the original GNSO policy recommendations. Background In November 2005, the GNSO concluded a policy development process (PDP) <https://gnso.icann.org/en/issues/whois-privacy/council-rpt-18jan06.htm> establishing a Procedure to allow gTLD registry operators and registrars to demonstrate when they are prevented by local laws from fully complying with the provisions of their respective ICANN contracts regarding personal data in WHOIS. The ICANN Board of Directors adopted the recommendations in May 2006 and directed staff to develop such a procedure. A contracted party that credibly demonstrates that it is legally prevented from complying with its WHOIS obligations can invoke the procedure, which became effective in January 2008. To date, the procedure has never been invoked. ICANN launched a review <https://www.icann.org/public-comments/whois-conflicts-procedure-2014-05-22-…> of the procedure in May 2014 and has concluded this review with this update to the WHOIS Procedure. Following a Call for Volunteers <https://www.icann.org/news/announcement-2014-10-14-en> addressed to all interested parties, an IAG was formed to review the implementation of the policy recommendations and began its work in January 2015. The IAG devoted most of its time to discussing whether additional triggers to invoke the Procedure should be incorporated and, if so, how to ensure that they remain consistent with the existing policy. About ICANN *ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or a number. That address has to 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 and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org <https://www.icann.org/>.* _______________________________________________ soac-infoalert mailing list soac-infoalert(a)icann.org https://mm.icann.org/mailman/listinfo/soac-infoalert

1 0

Fwd: [Soac-infoalert] The Chairman’s Blog: Reconsideration Requests, the Board Governance Committee and the Empowered Community - ICANN
by Greg Shatan April 19, 2017

April 19, 2017

FYI *Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc(a)gmail.com ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Wed, Apr 19, 2017 at 1:07 AM Subject: [Soac-infoalert] The Chairman’s Blog: Reconsideration Requests, the Board Governance Committee and the Empowered Community - ICANN To: "soac-infoalert(a)icann.org" <soac-infoalert(a)icann.org> https://www.icann.org/news/blog/the-chairman-s-blog- reconsideration-requests-the-board-governance-committee- and-the-empowered-community The Chairman’s Blog: Reconsideration Requests, the Board Governance Committee and the Empowered Community <https://www.icann.org/news/blog/the-chairman-s-blog-reconsideration-request…> <https://www.icann.org/news/blog/the-chairman-s-blog-reconsideration-request…> <https://www.icann.org/news/blog/the-chairman-s-blog-reconsideration-request…> <https://www.icann.org/news/blog/the-chairman-s-blog-reconsideration-request…> <https://www.icann.org/news/blog/the-chairman-s-blog-reconsideration-request…> <https://www.icann.org/news/blog/the-chairman-s-blog-reconsideration-request…> In February this year, the Board passed a resolution <https://www.icann.org/resources/board-material/resolutions-2017-02-03-en> to move reconsideration requests out of the Board Governance Committee (BGC) and create a separate Board committee specifically devoted to oversight of ICANN’s accountability mechanisms, including the reconsideration responsibilities. The BGC’s reconsideration responsibilities are specified in ICANN’s fundamental bylaws, so this change requires affirmative approval by the Empowered Community. This recommendation is out for public comment <https://www.icann.org/public-comments/bylaws-bgc-2017-03-31-en> now, and will be closing 10 May 2017. I want to make sure that everyone knows about this from the beginning, because it’s the first time the Empowered Community power may be used. One of the BGC’s primary role is the administration of the Board’s internal structure. Each year, it polls Board members on their preferences for committee memberships and their interests in the positions of Board chair and vice-chair, and then offers potential slates to the Board for their consideration. The BGC is also responsible for helping the Board implement its Conflicts of Interest Policy, which has included the use of Conflicts and Ethics subcommittees to help Board members evaluate how potential or perceived conflicts of interest might impact decisions. In its role of enhancing Board effectiveness, the BGC has overseen the development of training opportunities for Board members. In addition to these, and other governance-related activities, the BGC has also handled appeals when someone challenges one of the Board’s or ICANN Org’s decisions. This appeals process is known as “reconsideration.” Over the past several years, the number of reconsideration requests has grown. Moreover, during the Enhancing ICANN Accountability work, the ICANN community proposed enhancements to the Reconsideration Process, including expanding the times when reconsideration can be sought and placing more direct responsibility on the BGC for substantive work in resolving requests within a shorter time frame. The Board fully supports improvements in the reconsideration process and has focused on how best to continue to implement the recommendations of the Cross Community Working Group (CCWG) on Accountability. In anticipation of increased future workloads, as well as a need to have a group that is focused on the appeals process, the Board recommends moving the reconsideration process into a committee responsible for the oversight of ICANN’s accountability mechanisms. You can read about the resolution and our rationale for putting it forward in a blog <https://www.icann.org/news/blog/chairman-s-blog-en> that BGC Committee Chair Chris Disspain and I posted in February. After the public comment period, the Board will review the proposed Fundamental Bylaws amendments, and, if approved, the Empowered Community will then have an opportunity to consider whether it supports the amendments. It will be up to the Empowered Community to choose how to approach this task. One possibility includes hosting a Community Forum on the amendments to the Fundamental Bylaws during ICANN59 <https://meetings.icann.org/en/johannesburg59> in Johannesburg, South Africa, in June 2017. Information on the Empowered Community can be found in Article 6 <https://www.icann.org/resources/pages/governance/bylaws-en/#article6> of ICANN’s bylaws, and information on the Fundamental Bylaws Approval Process can be found in Annex D <https://www.icann.org/resources/pages/governance/bylaws-en/#annexD>, Article 1. Sent from my iPhone David A. Olive Senior Vice President, Policy Development Support Managing Director, ICANN Regional Headquarters –Istanbul Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349 Fulya, Besiktas, Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6212 Mobile: + 1. 202.341.3611 <+%201.%20202.341.3611> Mobile: +90.533.341.6550 _______________________________________________ soac-infoalert mailing list soac-infoalert(a)icann.org https://mm.icann.org/mailman/listinfo/soac-infoalert

1 0

Fwd: Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available
by Greg Shatan April 19, 2017

April 19, 2017

---------- Forwarded message --------- From: <email(a)addthis.com> Date: Tue, Apr 18, 2017 at 11:48 PM Subject: Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available To: <gregshatanipc(a)gmail.com> https://www.icann.org/news/announcement-2017-04-18-en#.WPbd9ds4-_E.email --- This message was sent by gregshatanipc(a)gmail.com via http://addthis.com. Please note that AddThis does not verify email addresses. To stop receiving any emails from AddThis, please visit: http://www.addthis.com/privacy/email-opt-out?e=WRIDbwF6F3UFaQVzDW0HXQNwBXQI… -- *Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc(a)gmail.com

1 0

Fwd: [Soac-infoalert] Elise Gerich to Leave ICANN After Seven Years of Service - ICANN Blog by Akram Atallah
by Greg Shatan April 18, 2017

April 18, 2017

Elise Gerich is leaving ICANN/PTI/IANA. *Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc(a)gmail.com ---------- Forwarded message ---------- From: David Olive <david.olive(a)icann.org> Date: Mon, Apr 17, 2017 at 12:25 PM Subject: [Soac-infoalert] Elise Gerich to Leave ICANN After Seven Years of Service - ICANN Blog by Akram Atallah To: "soac-infoalert(a)icann.org" <soac-infoalert(a)icann.org> Cc: Diane Schroeder <diane.schroeder(a)icann.org>, Duncan Burns < duncan.burns(a)icann.org> https://www.icann.org/news/blog/elise-gerich-to-leave- icann-after-seven-years-of-service *Elise Gerich to Leave ICANN After Seven Years of Service* I want to let you know that Elise Gerich has decided to step down from her role at ICANN as Vice President, IANA Services and President, Public Technical Identifiers (PTI) in October 2017. Until she leaves, Gerich will continue to oversee the IANA department and PTI, and has committed to working with ICANN and our various community partners and their leadership teams to ensure an efficient and seamless transition of duties. Gerich, Göran Marby, ICANN’s President and CEO, and I are all fully committed to ensuring that the IANA functions continue to operate smoothly and in service of our community. Gerich has been with ICANN since May 2010, serving as VP, IANA Services, before assuming the additional role of President, PTI, in October 2016. During her tenure at ICANN, she has overseen several important organizational milestones: receiving the EFQM Commitment to Excellence recognition in 2013 <https://www.icann.org/news/blog/iana-technical-operations-department-recogn…>, the allocation of the last blocks of unallocated IPv4 IP addresses to the Regional Internet Registries, the launching of the Root Zone Management System (RZMS), which provided a more automated system for handling root zone requests, and, of course, managing the IANA functions during the transition of the stewardship of the IANA functions contract. These are just a few of the many achievements related to IANA under Gerich’s guidance and direction. During her remaining time, she will be leading the IANA functions through another major milestone, with the rollover of the root zone Key Signing Key (KSK) scheduled to occur on 11 October 2017. I know that Elise did not come to this decision lightly, but I also know that she has great confidence in her team’s continuing ability to perform the IANA functions seamlessly under a new team leader. While we will miss her greatly, she is leaving behind a well-established and high performing organization for which we are very grateful. When I asked her about her time at ICANN, she said, “My decision to leave was a difficult one, but this seems like a good time for a hand-off, as the new affiliate PTI is established and stable. And in October, we will have achieved a major milestone with the rollover of the root zone Key Signing Key (KSK).” She added that, “It has been a privilege to work for ICANN and I specifically want to commend my team for their constant commitment to excellence and dedication to serving the community.” I am grateful to Elise for her partnership and contributions over the last seven years and for helping with a smooth handover. I hope you will also join me in thanking her for her dedication and service too! We will be posting a job description shortly and will conduct an open search for her replacement. In the meantime, I want to reiterate that we are committed to continuing the high performing service of the IANA functions that everyone has come to expect during this transition and beyond. David A. Olive Senior Vice President Policy Development Support Managing Director, ICANN Regional Headquarters –Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6212 Mobile: + 1. 202.341.3611 <+%201.%20202.341.3611> Mobile: +90.533.341.6550 _______________________________________________ soac-infoalert mailing list soac-infoalert(a)icann.org https://mm.icann.org/mailman/listinfo/soac-infoalert

1 0

Fwd: [Soac-infoalert] ICANN Quarterly Stakeholder Call for FY17 Q3 takes place on 27 April 1500 UTC. Register now.
by Greg Shatan April 13, 2017

April 13, 2017

---------- Forwarded message --------- From: David Olive <david.olive(a)icann.org> Date: Thu, Apr 13, 2017 at 5:11 AM Subject: [Soac-infoalert] ICANN Quarterly Stakeholder Call for FY17 Q3 takes place on 27 April 1500 UTC. Register now. To: soac-infoalert(a)icann.org <soac-infoalert(a)icann.org> [image: ICANN][icann.org] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2017-04-12-en[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ------------------------------ ICANN Quarterly Stakeholder Call for FY17 Q3 takes place on 27 April 1500 UTC. Register now. 12 April 2017 ICANN has announced its FY17 Q3 Stakeholder Call, which will take place on 27 April 1500 UTC. The call will focus on how ICANN has implemented community policy for the quarter ending 31 March 2017, as well as provide an update from our European engagement team. This European update is part of a new format to spotlight regional activities. Please click here[survey.clicktools.com] <https://urldefense.proofpoint.com/v2/url?u=http-3A__survey.clicktools.com_a…> to register for the call and receive instructions on how to join. If you are unable to access the form, please email us <icann.communications(a)icann.org> your full name and an email address to be registered. The call is open to anyone and live interpretation will be offered in Arabic, Chinese, English, French, Portuguese, Russian and Spanish. There will be a question & answer (Q&A) session and all materials (recordings, transcripts and presentations) will be made available on the ICANN website[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> . ?These calls were organized to enhance ICANN's accountability and transparency efforts. They are also a great way for you to stay informed on what the organization has done in line with ICANN's mission of keeping the Internet secure, stable and interoperable. More information Please visit the Reporting page[icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> on the ICANN website for more information, including recordings of previous calls. The presentation will be posted 24-48 hours in advance. ______________________________________________ _______________________________________________ soac-infoalert mailing list soac-infoalert(a)icann.org https://mm.icann.org/mailman/listinfo/soac-infoalert -- *Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc(a)gmail.com

1 0

Fwd: [CCWG-ACCT] Please Respond: Survey of the ICANN Ombudsman Office
by Greg Shatan April 12, 2017

April 12, 2017

IPC members, Please take a few minutes if you can and complete the survey below regarding the ICANN Ombudsman. Thank you. Greg *Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc(a)gmail.com ---------- Forwarded message ---------- From: MSSI Secretariat <mssi-secretariat(a)icann.org> Date: Mon, Apr 10, 2017 at 2:05 PM Subject: [CCWG-ACCT] Please Respond: Survey of the ICANN Ombudsman Office To: CCWG Accountability <accountability-cross-community(a)icann.org>, " ws2-staff_acct(a)icann.org" <ws2-staff_acct(a)icann.org>, " ws2-diversity(a)icann.org" <ws2-diversity(a)icann.org>, " ws2-jurisdiction(a)icann.org" <ws2-jurisdiction(a)icann.org>, " ws2-so_ac(a)icann.org" <ws2-so_ac(a)icann.org>, "ws2-guidelines(a)icann.org" < ws2-guidelines(a)icann.org>, "ws2-cep(a)icann.org" <ws2-cep(a)icann.org>, " ws2-transparency(a)icann.org" <ws2-transparency(a)icann.org> Dear all, On behalf of the Rapporteur for WS2 Subgroup ‘Ombudsman’, Sébastien Bachollet, we would like to encourage you and your peers to participate in the *survey <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.surveygizmo.com_s3_…> on the ICANN Ombudsman Office*. The survey will take approximately 5-10min. The survey <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.surveygizmo.com_s3_…> is part of the ongoing assessment of the ICANN Ombudsman Office and it has been designed in cooperation with the WS2 Subgroup ‘Ombudsman’. The survey <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.surveygizmo.com_s3_…> is available in 6 UN languages and links to the translations, as well as instructions on how to respond to the non-English versions, are provided on the survey wiki page <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> . If you have questions on the assessment of the Ombudsman Office, including the survey, please contact reviews(a)icann.org. Best wishes, MSSI *Link to the survey:* http://www.surveygizmo.com/s3/ 3462816/ICANN[surveygizmo.com] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.surveygizmo.com_s3_…> *Link to the survey wiki page with translations:* https://community.icann.org/x/vc3RAw[community.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> ------------------------------ Kind Regards, *Yvette Guigneaux* *(MSSI) Multistakeholder Strategy & Strategic Initiatives * Projects & Operations Assistant. *ICANN – Internet Corporation for Assigned Names and Numbers* Email: yvette.guigneaux(a)icann.org Cell: +1-310-460-8432 <(310)%20460-8432> Skype: yvette.guigneaux.icann www.icann.org[icann.org] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFAw…> _______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community(a)icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community

1 0

Fwd: [Soac-infoalert] Community Anti-Harassment Policy - ICANN - Blog from the ICANN Ombudsman- Herb Waye
by Greg Shatan April 11, 2017

April 11, 2017

---------- Forwarded message --------- From: David Olive <david.olive(a)icann.org> Date: Mon, Apr 10, 2017 at 1:34 PM Subject: [Soac-infoalert] Community Anti-Harassment Policy - ICANN - Blog from the ICANN Ombudsman- Herb Waye To: soac-infoalert(a)icann.org <soac-infoalert(a)icann.org> Cc: Herb Waye <herb.waye(a)icann.org> https://www.icann.org/news/blog/community-anti-harassment-policy [image: cann logo] <https://www.icann.org/> *Community Anti-Harassment Policy* The ICANN Board unanimous passed a resolution at ICANN58, effectively putting into place the new ICANN Community Anti-Harassment Policy that not only supports ICANN’s Expected Standards of Behavior, but now gives community members recourse if they identify or are victims of inappropriate behavior or harassment. Frequently, offenders are unaware that their behavior is offensive or inappropriate, possibly due to differences in cultural or social norms. It is important to consider that the behavior may not be intentional or malicious. For that reason, the Anti-Harassment Policy complaint procedure begins with the option of confronting the offender to resolve the issue informally. If the behavior is unintentional or unwelcome, merely identifying the behavior as offensive or inappropriate often results in a change in behavior, and very likely, an apology. The role of the Ombuds in dealing with inappropriate behavior or harassment is first and foremost to address the issue as informally as the circumstances allow. There is clearly a continuum of severity that must be considered. The Ombuds will not treat an inappropriate comment the same way as an allegation of sexual harassment or assault. One complaint may call for an informal intervention, where the next may call for the involvement of law enforcement. The Ombuds will also take into consideration whether the reason for the complaint is a one-time event or a recurring behavior. The policy further authorizes the Ombuds to impose sanctions on an offender if deemed necessary. Though considered to be an action of last resort, the sanctions do serve to remind community participants that they will be held accountable for their actions and there may be consequences imposed. With an extensive background in harassment training and policy implementation, I understand not only the impact harassment has on an organization, but more importantly, the often-devastating impact it has on the victim. There is no place for harassment, bullying or any other type of inappropriate behavior in today’s world. It is important to note that ICANN staff (employees and contractors) are covered by internal policies against harassment, and the Ombuds does not have jurisdiction. In closing, I would like to once again remind everyone to act professionally, embrace diversity and human rights, and above all, treat others with respect. Together we can make ICANN a safe and harassment-free environment for all. David A. Olive Senior Vice President Policy Development Support Managing Director, ICANN Regional Headquarters –Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6212 Mobile: + 1. 202.341.3611 <+%201.%20202.341.3611> Mobile: +90.533.341.6550 _______________________________________________ soac-infoalert mailing list soac-infoalert(a)icann.org https://mm.icann.org/mailman/listinfo/soac-infoalert -- *Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc(a)gmail.com

1 0

Reminder for today: Please RSVP - GNSO Webinar on ICANN's Draft FY18 Operating Plan & Budget | Tuesday 4th April 2017 at 21:00 UTC
by Chantelle Doerksen April 4, 2017

April 4, 2017

Dear all, As discussed during the GNSO wrap up session at ICANN58, a webinar has been scheduled for the GNSO Community on Tuesday 4 April at 21.00 UTC with ICANN’s Finance Team to discuss ICANN's Draft FY18 Operating Plan & Budget and an associated update to the Five-Year Operating Plan which were recently published for public comment (seehttps://www.icann.org/public-comments/fy18-budget-2017-03-08-en)[icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>. If you are interested to participate, please send a message to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> following which you will receive the call details. If there are any specific questions you would like the Finance Team to address during their presentation, please feel free to submit these in advance. Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC 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