July 2016 - ALAC-Announce - lists.icann.org

UPDATE 1/ GNSO and At-Large Calls - Week of 01 August- 05 August 2016
by ICANN At-Large Staff July 29, 2016

July 29, 2016

Hello All, Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 01 August – 05 August 2016. Update 1: Tuesday, 02 August 2016 added: 16:30 UTC: ALAC Subcommittee on Outreach and Engagement Updates will follow as Doodles close. Monday 01 August 2016 13:00 UTC: (GNSO) New gTLD Subsequent Procedures Working Group https://community.icann.org/x/Jgp1Aw Tuesday 02 August 2016 14:30 UTC: At-Large Community Regional Outreach Pilot Program Review Team (CROPP RT) https://community.icann.org/x/IxKbAw 16:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag 16:30 UTC: ALAC Subcommittee on Outreach and Engagement https://community.icann.org/x/cwCsAw Wednesday 03 August 2016 16:00 UTC (GNSO) Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group https://community.icann.org/x/wCWAAw Thursday 04 August 2016 16:00 UTC: (GNSO) IGO-INGO Access to Curative Rights Protection Mechanisms Working Group https://community.icann.org/x/37rhAg 20:00 UTC: CWG IANA Meeting Stewardship https://community.icann.org/x/37fhAg Friday 05 August 2016 none Please confirm your dial-out requests or apology notice to: For GNSO calls: GNSO Secretariats gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> For At-Large calls or ALAC :staff@atlarge.icann.org<mailto:staff@atlarge.icann.org> For CWG IANA Stewardship Brenda.Brewer(a)icann.org<mailto:Brenda.brewer@icann.org> For CCWG on Enhancing ICANN Accountability:acct-staff@icann.org<mailto:acct-staff@icann.org> For CCWG-IG desiree.cabrera(a)icann.org<mailto:desiree.cabrera@icann.org> Thank you. Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png]

1 0

GNSO and At-Large Calls - Week of 01 August- 05 August 2016
by ICANN At-Large Staff July 29, 2016

July 29, 2016

Hello All, Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 01 August – 05 August 2016. Updates will follow as Doodles close. Monday 01 August 2016 13:00 UTC: (GNSO) New gTLD Subsequent Procedures Working Group https://community.icann.org/x/Jgp1Aw Tuesday 02 August 2016 14:30 UTC: At-Large Community Regional Outreach Pilot Program Review Team (CROPP RT) https://community.icann.org/x/IxKbAw 16:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag Wednesday 03 August 2016 16:00 UTC (GNSO) Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group https://community.icann.org/x/wCWAAw Thursday 04 August 2016 16:00 UTC: (GNSO) IGO-INGO Access to Curative Rights Protection Mechanisms Working Group https://community.icann.org/x/37rhAg 20:00 UTC: CWG IANA Meeting Stewardship https://community.icann.org/x/37fhAg Friday 05 August 2016 none Please confirm your dial-out requests or apology notice to: For GNSO calls: GNSO Secretariats gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> For At-Large calls or ALAC :staff@atlarge.icann.org<mailto:staff@atlarge.icann.org> For CWG IANA Stewardship Brenda.Brewer(a)icann.org<mailto:Brenda.brewer@icann.org> For CCWG on Enhancing ICANN Accountability:acct-staff@icann.org<mailto:acct-staff@icann.org> For CCWG-IG desiree.cabrera(a)icann.org<mailto:desiree.cabrera@icann.org> Thank you. Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png]

1 0

ICANN News Alert -- Results Available for 27 July 2016 New gTLD Program Auction
by ICANN At-Large Staff July 29, 2016

July 29, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2-2016-07-28-en ________________________________ Results Available for 27 July 2016 New gTLD Program Auction 28 July 2016 On 27 July 2016, Power Auctions LLC<http://www.powerauctions.com/>, ICANN's authorized auction service provider, conducted a New Generic Top-Level Domain (gTLD) Program auction to resolve contention for .WEB and .WEBS<https://gtldresult.icann.org/application-result/applicationstatus/contentio…>. Auction serves as the method of last resort for determining which applicant may operate a gTLD when several entities have applied for the same or confusingly similar gTLDs. This method was defined through ICANN's bottom-up, multistakeholder process. Eight applicants completed the requirements for participating in the .WEB/.WEBS auction. NU DOT CO LLC prevailed in the auction for the price of $135 million to operate the .WEB gTLD, and Vistaprint Ltd prevailed with a price of $1 for the .WEBS gTLD. Auction Proceeds The proceeds from New gTLD Program auctions, which will total more than $230 million, are being reserved. The multistakeholder community will develop proposals for how these proceeds could be distributed. A community-based drafting team is currently working on a charter for a Cross-Community Working Group that will create recommendations for Board consideration. Learn more<https://community.icann.org/display/NGAPDT/New+gTLD+Auction+Proceeds+Drafti…> about this work. "New gTLD Program auctions are the community-established, last resort method to help determine which applicant will have the opportunity to operate a particular new generic top-level domain, when multiple entities vied for the same or confusingly similar domains." said Akram Atallah, president of ICANN's Global Domains Division. "We look forward to seeing the community's recommendations for the use of these proceeds." Auctions and the New gTLD Applicant Guidebook The Internet community spent nearly three years developing a playbook for rolling out new gTLDs under the New gTLD Program, known as the New gTLD Applicant Guidebook. The guidebook outlines measures for addressing a variety of circumstances that could occur throughout the gTLD application and evaluation processes, including instances where multiple applicants applied for the same or confusingly similar new gTLDs. Only one entity can operate a given new gTLD, so contention must be resolved. Applicants can resolve contention among themselves, and ICANN encourages them to do so. However, this isn't always possible. The ICANN stakeholder community helped develop methods for resolving contention, and it decided that auction should serve as the method of last resort. ICANN is responsible for implementing auctions in accordance with the rules defined in the New gTLD Applicant Guidebook. There are two different types of contention sets: direct and indirect. Direct contention occurs when multiple applicants are vying for the same or confusingly similar gTLDs. Indirect contention exists when two or more applications are in direct contention with a third application, but not with one another. .WEB/.WEBS was an indirect contention set consisting of one application for .WEBS and seven applications for .WEB. In this case, the application for .WEBS prevailed along with one application for .WEB. For a more detailed description of auction and indirect contention, see Module 4 of New gTLD Program Applicant Guidebook<http://newgtlds.icann.org/en/applicants/agb>. More Information * Contention Set Status<https://gtldresult.icann.org/application-result/applicationstatus/stringcon…>: 218 of 234 contention sets are now resolved. The majority have self-resolved, but 16 sets resolved via ICANN auction. * Auction Results<https://gtldresult.icann.org/application-result/applicationstatus/auctionre…>: Reports on this page of the New gTLD Microsite provide additional information on each auction outcome. * Auction Proceeds and Costs<http://newgtlds.icann.org/en/applicants/auctions/proceeds>: A detailed summary of the proceeds and costs of each auction through July 2016. This information will be updated within seven days of each auction. * Auction Schedule<https://newgtlds.icann.org/en/applicants/auctions/schedule-28jul16-en.pdf> [PDF, 263 KB]: Updated as of 28 July 2016. * General New gTLD Program Auctions<http://newgtlds.icann.org/en/applicants/auctions> information. 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/>.

1 0

ICANN News Alert -- Successful Candidates Announced for ICANN57 Fellowship
by ICANN At-Large Staff July 29, 2016

July 29, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2016-07-28-en ________________________________ Successful Candidates Announced for ICANN57 Fellowship 28 July 2016 51 fellows from 35 countries have been selected to participate in ICANN's Fellowship program at the 57th Public Meeting in Hyderabad, India 3-9 November 2016. Of those fifty-two selected, 17 are returning fellows from at least one previous meeting and various experience levels, 10 of whom will be coaches to the 34 attending as first time fellows. The selected fellows represent all sectors of society including civil, government, ccTLD Operations, academia, facets of the business community, technical, security and end user groups. An independent selection committee assessed the 319 fellowship applications received for this meeting; 76 of those met minimum requirements for possible selection. Priority is given to applicants who not only meet minimum program requirements, but who are current residents of developing and least developed nations and who are interested in participating in ICANN and its supporting organizations, advisory committees, stakeholder and constituency groups. Click here to see the list of selected candidates and learn more about the fellowship program: http://www.icann.org/en/about/participate/fellowships<https://www.icann.org/en/about/participate/fellowships>

1 0

Fwd: Statement on changes to the Fellowship Program
by Alan Greenberg July 28, 2016

July 28, 2016

>To: ALAC <alac(a)atlarge-lists.icann.org> >From: Alan Greenberg <alan.greenberg(a)mcgill.ca> >Subject: Statement on changes to the Fellowship Program > >As discussed during the ALAC call earlier this week, there is a >Public Comment just about to close on changes to the ICANN Fellowship Program. > >Some people in At-Large have been (rightfully) VERY vocal about >perceived problems in the Fellowship program, specifically: > >- people from some countries (such as Argentina) have recently >become ineligible to participate in the Fellowship Program because >the country has had its status upgraded in the World Bank list of >development status (based on income); >- some people, particularly from some island territories were not eligible. > >In both cases, the status of the overall economy might not have met >the criteria, but that did not alter the perception that the people >were not well represented in ICANN. > >The proposed changes to the Fellowship Program address these >problems and more. > >Unfortunately, no one chose to volunteer to draft a brief statement >of support for the changes. > >At the ALAC Leadership Team meeting yesterday, it was decided that >the Fellowship Program is sufficiently important to At-Large, the >people we represent, and to ICANN in general that we MUST submit >something. Accordingly, I drafted a set of notes which Ariel Liang >ably transformed into a statement to be submitted. > >The statement can be found at https://community.icann.org/x/LiOOAw. > >The deadline for submission is tomorrow, Friday, 29 July at 23:59 >UTC. I will conduct a Consensus Call for formally ratify the >statement next week, but if anyone has any concern with the >statement, please bring that concern to my attention immediately. > >Alan

1 0

ICANN News Alert -- Call for Volunteers: GNSO Review Working Group
by ICANN At-Large Staff July 28, 2016

July 28, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2016-07-27-en ________________________________ Call for Volunteers: GNSO Review Working Group 27 July 2016 In Brief The Generic Names Supporting Organization (GNSO) Council adopted the Charter<http://gnso.icann.org/en/drafts/gnso-review-charter-11jul16-en.pdf> [PDF, 565 KB] of the GNSO Review Working Group during its meeting on 21 July 2016. This Working Group is tasked to develop an implementation plan for the GNSO Review recommendations<http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-e…> [PDF, 407 KB] which were recently adopted<https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2.e> by the ICANN Board. This is the Call for Volunteers to join this Working Group. Anyone interested in the GNSO Review and contributing to the development of the implementation plan and subsequent implementation is encouraged to volunteer. What This Working Group Will Do Per the GNSO Review Working Group Charter<http://gnso.icann.org/en/drafts/gnso-review-charter-11jul16-en.pdf> [PDF, 565 KB] the GNSO Review Working Group will be responsible for developing an implementation plan, containing a realistic timeline for the implementation, definition of desired outcomes and a way to measure current state as well as progress toward the desired outcome for the GNSO Review recommendations adopted by the ICANN Board (thirty-four (34) recommendations of the Final Report<https://www.icann.org/en/system/files/files/gnso-review-final-summary-15sep…> [PDF, 727 KB] of the Independent Examiner (i.e. all recommendations excluding recommendations 23 and 32). This implementation plan is to be submitted for approval to the GNSO Council, followed by consideration by the ICANN Board. Following the approval of the implementation plan, the Working Group is also expected to execute and oversee the implementation of the GNSO Review recommendations unless specified differently in the implementation plan. The GNSO Review Working Group will also be responsible for considering any new requests1<https://www.icann.org/news/announcement-2016-07-27-en#foot1> by the GNSO Council concerning issues related to the GNSO Council processes and procedures and to Working Group guidelines that have been identified either by the GNSO Council, or a group chartered by the GNSO Council, as needing discussion. However, the first priority of the Working Group will be the development of an implementation plan and the subsequent implementation of the GNSO Review recommendations. Timeline and Deliverables The GNSO Review Working Group is expected to deliver the implementation plan to the GNSO Council for consideration at the GNSO Council meeting at ICANN57 at the latest in order to meet the Board set objective of 'an implementation plan, containing a realistic timeline for the implementation, definition of desired outcomes and a way to measure current state as well as progress toward the desired outcome, shall be submitted to the Board as soon as possible, but no later than six (6) months after the adoption of this resolution'2<https://www.icann.org/news/announcement-2016-07-27-en#foot2> i.e., December 2016. How to Join Each GNSO Stakeholder Group and/or Constituency will identify one primary and one alternate member to serve on the GNSO Review Working Group. In addition to these appointed members, anyone interested will be able to join this working group as a participant or observer. Please note that participants are expected to attend conference calls and to actively participate in online discussions. They also must submit a Statement of Interest per Section 5.0 of the GNSO Operating Procedures<http://gnso.icann.org/en/council/op-procedures-16feb16-en.pdf> [PDF, 1.31 MB]. Observers can follow the group's work on the mailing list but can neither send to the mailing list nor participate actively in the calls. Interested participants and observers are requested to complete the sign-up sheet<https://docs.google.com/forms/d/e/1FAIpQLSdrRa0ZNK45sDzHq2Rh1C7-I8TRFjya0zS…> by Friday, 19 August 2016. Next steps It is anticipated that the GNSO Review Working Group will convene online for the first time in the last week of August 2016. Following that, regular online meetings will be scheduled in accordance with the Working Group's work plan, which it is expected to develop as one of its first tasks. Further information and preparation For those interested in volunteering for this effort, you are encouraged to review the following materials: 1. GNSO Review Recommendations<http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-e…> [PDF, 407 KB] 2. Independent Examiner Final Report<https://www.icann.org/en/system/files/files/gnso-review-final-summary-15sep…> [PDF, 727 KB] 3. Frequently Asked Questions<https://community.icann.org/x/UBCbAw> Background The second independent review of the GNSO commenced in 2014. The Final Report of the independent examiner was published on 15 September 2015 (see https://www.icann.org/en/system/files/files/gnso-review-final-15sep15-en.pdf [PDF, 1.99 MB]) and contained 36 recommendations in the areas of: participation & representation, continuous development, transparency and alignment with ICANN's future. The GNSO Council adopted the GNSO Review Recommendations Feasibility and Prioritization analysis (see: http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-e… [PDF, 407 KB]) on 14 April 2016 with the modification of Recommendation 21, that the council recommends staff working with the GNSO to institute methods of information sharing of highly relevant research related to gTLDs to help the GNSO community members increase their knowledge base (low priority). On 25 June, the ICANN Board accepted the Final Report from the independent examiner, taking into account the GNSO Working Party's Feasibility and Prioritization Analysis of the GNSO Review Recommendations, adopted with modifications by the GNSO Council. The Board adopted thirty-four (34) recommendations of the Final Report (i.e. all recommendations excluding recommendations 23 and 32). Furthermore, the Board requested that the GNSO Council convene a group that oversees the implementation of Board-accepted recommendations. Per the motion<https://community.icann.org/x/BAObAw> adopted on 21 July 2016, the GNSO Council adopted the Charter<http://gnso.icann.org/en/drafts/gnso-review-charter-11jul16-en.pdf> [PDF, 565 KB] of the GNSO Review Working Group and directed staff to send a Call for Volunteers for the Working Group. ________________________________ 1<https://www.icann.org/news/announcement-2016-07-27-en#note1> For items that are submitted for review 'on request', the GNSO Review WG expects to receive detailed input from the group affected by the process/operational change concerned. See request template at: https://community.icann.org/download/attachments/14713135/GNSO-SCI-ReviewRe… [DOCX, 102 KB]. 2<https://www.icann.org/news/announcement-2016-07-27-en#note2> The Board resolution was adopted on 25 June 2016

1 0

New Public Comment: Proposed Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes
by ICANN At-Large Staff July 27, 2016

July 27, 2016

Dear All, This is to let you know that the Public Comment on the ‘Proposed Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes ' has now gone live: https://www.icann.org/public-comments/proposed-measures-two-char-2016-07-08…. Public comment will end on 17 August 2016 23:59 UTC. During this period, anyone can submit comment via comments-proposed-measures-two-char-08jul16(a)icann.org<mailto:comments-proposed-measures-two-char-08jul16@icann.org>. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Additionally, the wiki workspace for developing a potential ALAC Statement is here: https://community.icann.org/x/uAKbAw. All pertinent resources for this public comment can also be found there. Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 1

UPDATE 2/ GNSO and At-Large Calls - Week of 25 July- 29 July 2016
by ICANN At-Large Staff July 27, 2016

July 27, 2016

Hello All, Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 25 July- 29 June 2016. Update 2: Wednesday added 14:00U UTC: At-Large Review Working Party call https://community.icann.org/x/5Q6bAw Updates will follow as Doodles close. Monday 25 July 2016 none Tuesday 26 July 2016 13:00 UTC: GNSO Working Group Communication Tools Classroom Please RSVP via this form<http://goo.gl/forms/mR4HD9XNZU> for call details (by 25 July 2016) 16:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag 18:00 UTC: (At-Large) EURALO Monthly call https://community.icann.org/x/hwObAw 21:00 UTC: ALAC Monthly call https://community.icann.org/x/JAmbAw Wednesday 27 July 2016 12:00 UTC: (GNSO) New gTLD Auction Proceeds CCWG Charter Drafting Team https://community.icann.org/x/px6AAw 14:00U UTC: At-Large Review Working Party call https://community.icann.org/x/5Q6bAw 20:0 0UTC: ALAC Leadership Team (ALT) Monthly Call https://community.icann.org/x/GA2bAw 21:00 UTC (GNSO) Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group https://community.icann.org/x/wCWAAw Thursday 28 July 2016 14:00 UTC: CWG IANA Meeting Stewardship https://community.icann.org/x/37fhAg 16:00 UTC: (GNSO) IGO-INGO Access to Curative Rights Protection Mechanisms Working Group https://community.icann.org/x/37rhAg 23:00 UTC: LACRALO-GSE Capacity Building Webinar on the topic “ Next-Generation gTLD Registration Directory Services (RDS) to replace WHOIS (WHOIS PDP)” https://community.icann.org/x/bw_bAw Friday 29 July 2016 none Please confirm your dial-out requests or apology notice to: For GNSO calls: GNSO Secretariats gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> For At-Large calls or ALAC :staff@atlarge.icann.org<mailto:staff@atlarge.icann.org> For CWG IANA Stewardship Brenda.Brewer(a)icann.org<mailto:Brenda.brewer@icann.org> For CCWG on Enhancing ICANN Accountability:acct-staff@icann.org<mailto:acct-staff@icann.org> For CCWG-IG desiree.cabrera(a)icann.org<mailto:desiree.cabrera@icann.org> Thank you. Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png]

1 0

ICANN News Alert -- New Registration Data Directory Services Requirements for gTLD Registries, Registrars to Take Effect in February 2017
by ICANN At-Large Staff July 27, 2016

July 27, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2016-07-26-en ________________________________ New Registration Data Directory Services Requirements for gTLD Registries, Registrars to Take Effect in February 2017 26 July 2016 ICANN today announced that gTLD contracted parties must update their Registration Data Directory Services (RDDS) by 1 February 2017. Registries and registrars are required to implement the new Registration Data Access Protocol (RDAP) gTLD Profile<https://www.icann.org/rdap-gtld-profile>. Registries must also implement the data specifications defined in the Registry Registration Data Directory Services Consistent Labeling and Display Policy<https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en>. The RDAP gTLD Profile and the RDDS Consistent Labeling and Display Policy are the products of community efforts to improve the current system used to discover who controls a domain name. This system comprises data retrieval protocols - WHOIS and a web-based version of WHOIS - and databases controlled by registries and registrars that contain domain registration information. ICANN has notified contracted parties that they are responsible for modifying their systems within six months. ICANN consulted these parties when defining the new requirements and implementation plans. Background The Registration Data Access Protocol was developed by the Internet Engineering Task Force<https://ietf.org/> to eventually replace the WHOIS protocol. This new protocol is superior to WHOIS in terms of data access security, support for international characters, extensibility, and in the standardization of query, response and error messages. The RDAP gTLD Profile maps ICANN policy and contractual requirements onto technical requirements in order to standardize directory services across gTLD contracted parties. The RDDS Consistent Labeling and Display Policy is a Consensus Policy developed and adopted in accordance with ICANN Bylaws. The policy is the result of recommendations adopted by the GNSO Council after the completion of the Thick WHOIS Policy Development Process. The ICANN board adopted these recommendations on 7 February 2014. The goal of the RDDS Consistent Labeling and Display Policy is to align the way registries and registrars label and display registration data outputs. The policy uses the output specifications found in the 2013 Registrar Accreditation Agreement as the standard, thus only registries need to update their systems. Changes might include renaming or re-ordering fields and displaying additional data, such as registrar abuse contact information. For more information on these topics, visit: * Registration Data Access Protocol gTLD Profile<https://www.icann.org/rdap-gtld-profile> * Registry RDDS Consistent Labeling and Display Policy<https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en> * Thick WHOIS Policy Implementation<https://www.icann.org/resources/pages/thick-whois-2016-06-27-en> * Policy Implementation at ICANN<https://www.icann.org/policy/implementation> 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/>.

1 0

Call for Volunteers: GNSO Review Working Group
by staff＠atlarge.icann.org July 27, 2016

July 27, 2016

Call for Volunteers: GNSO Review Working Group In Brief The Generic Names Supporting Organization (GNSO) Council adopted the Charter <http://gnso.icann.org/en/drafts/gnso-review-charter-11jul16-en.pdf> of the GNSO Review Working Group during its meeting on 21 July 2016. This Working Group is tasked to develop an implementation plan for the GNSO Review recommendations <http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-e n.pdf> which were recently adopted <https://www.icann.org/resources/board-material/resolutions-2016-06-25-en#2. e> by the ICANN Board. This is the Call for Volunteers to join this Working Group. Anyone interested in the GNSO Review and contributing to the development of the implementation plan and subsequent implementation is encouraged to volunteer. What This Working Group Will Do Per the GNSO Review Working Group Charter <http://gnso.icann.org/en/drafts/gnso-review-charter-11jul16-en.pdf> the GNSO Review Working Group will be responsible for developing an implementation plan, containing a realistic timeline for the implementation, definition of desired outcomes and a way to measure current state as well as progress toward the desired outcome for the GNSO Review recommendations adopted by the ICANN Board (thirty-four (34) recommendations of the Final Report <https://www.icann.org/zh/system/files/files/gnso-review-final-summary-15sep 15-en.pdf> of the Independent Examiner (i.e. all recommendations excluding recommendations 23 and 32). This implementation plan is to be submitted for approval to the GNSO Council, followed by consideration by the ICANN Board. Following the approval of the implementation plan, the Working Group is also expected to execute and oversee the implementation of the GNSO Review recommendations unless specified differently in the implementation plan. The GNSO Review Working Group will also be responsible for considering any new requests[1] <#_ftn1> by the GNSO Council concerning issues related to the GNSO Council processes and procedures and to Working Group guidelines that have been identified either by the GNSO Council, or a group chartered by the GNSO Council, as needing discussion. However, the first priority of the Working Group will be the development of an implementation plan and the subsequent implementation of the GNSO Review recommendations. Timeline and Deliverables The GNSO Review Working Group is expected to deliver the implementation plan to the GNSO Council for consideration at the GNSO Council meeting at ICANN57 at the latest in order to meet the Board set objective of an implementation plan, containing a realistic timeline for the implementation, definition of desired outcomes and a way to measure current state as well as progress toward the desired outcome, shall be submitted to the Board as soon as possible, but no later than six (6) months after the adoption of this resolution¹[2] <#_ftn2> i.e., December 2016. How to Join Each GNSO Stakeholder Group and/or Constituency will identify one primary and one alternate member to serve on the GNSO Review Working Group. In addition to these appointed members, anyone interested will be able to join this working group as a participant or observer. Please note that participants are expected to attend conference calls and to actively participate in online discussions. They also must submit a Statement of Interest per Section 5.0 of the GNSO Operating Procedures <http://gnso.icann.org/en/council/op-procedures-16feb16-en.pdf> . Observers can follow the group's work on the mailing list but can neither send to the mailing list nor participate actively in the calls. Interested participants and observers are requested to complete the sign-up sheet <https://goo.gl/forms/TbmkrEXT2xlx6jGn1> by Friday, 19 August 2016. Next steps It is anticipated that the GNSO Review Working Group will convene online for the first time in the last week of August 2016. Following that, regular online meetings will be scheduled in accordance with the Working Group¹s work plan, which it is expected to develop as one of its first tasks. Further information and preparation For those interested in volunteering for this effort, you are encouraged to review the following materials: 1. GNSO Review Recommendations <http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-e n.pdf> 2. Independent Examiner Final Report <https://www.icann.org/zh/system/files/files/gnso-review-final-summary-15sep 15-en.pdf> 3. Frequently Asked Questions <https://community.icann.org/x/UBCbAw> Background The second independent review of the GNSO commenced in 2014. The Final Report of the independent examiner was published on 15 September 2015 (see https://www.icann.org/en/system/files/files/gnso-review-final-15sep15-en.pdf <https://www.icann.org/en/system/files/files/gnso-review-final-15sep15-en.pd f> ) and contained 36 recommendations in the areas of: participation & representation, continuous development, transparency and alignment with ICANN's future. The GNSO Council adopted the GNSO Review Recommendations Feasibility and Prioritization analysis (see:http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb 16-en.pdf <http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-e n.pdf> ) on 14 April 2016 with the modification of Recommendation 21, that the council recommends staff working with the GNSO to institute methods of information sharing of highly relevant research related to gTLDs to help the GNSO community members increase their knowledge base (low priority). On 25 June, the ICANN Board accepted the Final Report from the independent examiner, taking into account the GNSO Working Party's Feasibility and Prioritization Analysis of the GNSO Review Recommendations, adopted with modifications by the GNSO Council. The Board adopted thirty-four (34) recommendations of the Final Report (i.e. all recommendations excluding recommendations 23 and 32). Furthermore, the Board requested that the GNSO Council convene a group that oversees the implementation of Board-accepted recommendations. Per the motion <https://community.icann.org/x/BAObAw> adopted on 21 July 2016, the GNSO Council adopted the Charter <http://gnso.icann.org/en/drafts/gnso-review-charter-11jul16-en.pdf> of the GNSO Review Working Group and directed staff to send a Call for Volunteers for the Working Group. [1] <#_ftnref1> For items that are submitted for review 'on request', the GNSO Review WG expects to receive detailed input from the group affected by theprocess/operational change concerned. See request template at: https://community.icann.org/download/attachments/14713135/GNSO-SCI-ReviewReq uest-yyymmdd_template.docx?version=1&modificationDate=1469143165000&api=v2 <https://community.icann.org/download/attachments/14713135/GNSO-SCI-ReviewRe quest-yyymmdd_template.docx?version=1&modificationDate=1469143165000&api=v2> . [2] <#_ftnref2> The Board resolution was adopted on 25 June 2016

1 0