- rssac-caucus - lists.icann.org

[rssac-caucus] MTU, MSS and Frag
by George Michaelson March 27, 2017

March 27, 2017

I propose RSSAC caucus explore an understanding of the MTU, MSS and fragmentation behaviour of all instances of the roots, in IPv6 and IPv4. If we had this data, we would be able to understand if what we see with any given instance of query to a root was local, or more likely along the path. Some evidence from random query tests suggests both that there is no consistency between the root operators, and some inconsistency within a given root letter, depending on where you query goes, or what protocol you use. Because of the increase in TCP, and packetsizes in responses, this is of interest because of the exposure to fragmentation, or loss of pMTU signalling, or the variances in MSS/TCP against interface MTU and UDP. This question has a quality which goes to "only the root operators can say" which is why it feels to me like a well-formed question for the caucus to consider, which implies RSSAC taking it on board to ask the root operators about. -George

3 3

[rssac-caucus] aggressive NXDOMAIN in pDNS, and its effect on traffic to the root
by George Michaelson March 27, 2017

March 27, 2017

I would like to propose a study in rssac-caucus to collect information about the effects of the deployment of aggressive NSEC response, on the volume of query at the root. The work is late stage in DNSOP and I would expect to go to last-call and publication. This means that we can also expect deployment soon after, or even proceeding publication. DITL style infrequent capture would be useful but its possible a less costly mechanism to construct a measurement exists: I am unsure if the current RSAC002 captures this, certainly the RCODE-VOLUME measure would provide it in aggregate, but because it's dissociated from the resolver its hard to do any more qualified analysis except to say 'it dropped'. Because the change would herald a shift in the volume of undelegated (bogus) queries to the root and also reduce pressure in the known bad cases like .local, it has impacts on other policy questions under the oversight of the ICANN. It goes to that borderline between operations, and zone content. -George

4 4

[rssac-caucus] RSSAC Caucus Meeting at IETF98, Sunday, March 26 2017 from 2030-2200 UTC
by Andrew Mcconachie March 26, 2017

March 26, 2017

Dear RSSAC Caucus Members, The next RSSAC Caucus meeting will be held at IETF 98 in Chicago, USA. The meeting is scheduled for Sunday, March 26 2017 from 2030-2200 UTC/1530-1700 CDT. For other times: http://bit.ly/2nfHXWM Please find the agenda attached. Verizon US: +1 (866) 780-9216 (Dial in numbers for other countries listed in the bottom of email) Participant Passcode: Participant: 2111690 Adobe Connect: https://participate.icann.org/rssac Dial in numbers*: Country Local/Toll Number Freephone/Toll Free Number ARGENTINA 0800-777-0487 AUSTRALIA ADELAIDE: 61-8-8121-4859 1-800-880-484 AUSTRALIA BRISBANE: 61-7-3102-0961 1-800-880-484 AUSTRALIA CANBERRA: 61-2-6100-1961 1-800-880-484 AUSTRALIA MELBOURNE: 61-3-9010-7730 1-800-880-484 AUSTRALIA PERTH: 61-8-9467-5240 1-800-880-484 AUSTRALIA SYDNEY: 61-2-8211-1382 1-800-880-484 AUSTRIA 43-1-92-89-574 0800-999-850 BELGIUM 32-2-400-6717 0800-4-8474 BRAZIL 55-11-3958-0764 0800-7610666 CHILE 1230-020-0288 CHINA CHINA A: 86-400-810-4757 10800-712-1194 CHINA CHINA B: 86-400-810-4757 10800-120-1194 COLOMBIA 01800-9-156471 CROATIA 080-08-06-319 CZECH REPUBLIC 420-2-25-98-56-11 800-700-164 DENMARK 45-7014-0235 8088-5347 ESTONIA 800-011-1124 FINLAND 358-9-5424-7147 0-800-1-12418 FRANCE LYON: 33-4-26-69-12-72 080-511-1516 FRANCE MARSEILLE: 33-4-86-06-00-72 080-511-1516 FRANCE PARIS: 33-1-70-70-60-73 080-511-1516 GERMANY 49-69-2222-20267 0800-101-4259 GREECE 30-80-1-100-0635 00800-12-6136 HONG KONG 852-3001-3828 800-964-135 HUNGARY 36-1-700-8841 06-800-15442 INDIA INDIA B: 000-800-001-6249 INDIA INDIA C: 1800-300-00430 INDIA INDIA A: 000-800-852-1213 INDONESIA 001-803-011-3491 IRELAND 353-1-246-0095 1800-992-121 ISRAEL 1-80-9214002 ITALY MILAN: 39-02-3600-3564 800-985-429 ITALY ROME: 39-06-8751-6013 800-985-429 ITALY TORINO: 39-011-510-0113 800-985-429 JAPAN OSAKA: 81-6-7878-2653 00531-12-1150 JAPAN TOKYO: 81-3-6868-2653 00531-12-1150 LATVIA 8000-3168 LUXEMBOURG 352-27-000-1310 8002-9125 MALAYSIA 1-800-80-8105 MEXICO GUADALAJARA (JAL): 52-33-3208-7322 001-866-318-9747 MEXICO MEXICO CITY: 52-55-5062-9122 001-866-318-9747 MEXICO MONTERREY: 52-81-2482-0622 001-866-318-9747 NETHERLANDS 31-20-712-1372 0800-023-1492 NEW ZEALAND 64-9-970-4637 0800-443-823 NORWAY 47-21-59-00-10 800-12069 PANAMA 011-001-800-5072077 PERU 0800-53715 PHILIPPINES 63-2-858-3706 1800-111-42452 POLAND 00-800-1210160 PORTUGAL 8008-12108 ROMANIA 40-31-630-01-64 RUSSIA 8-10-8002-9913011 SAUDI ARABIA 800-8-110058 SINGAPORE 65-6883-9193 800-120-4060 SLOVAK REPUBLIC 421-2-322-422-12 0800-002032 SOUTH AFRICA 080-09-93392 SOUTH KOREA 82-2-6744-1048 00798-14800-6324 SPAIN 34-91-414-14-65 800-099-374 SWEDEN 46-8-566-10-474 0200-887-680 SWITZERLAND 41-44-580-3270 0800-000-246 TAIWAN 886-2-2795-7342 00801-137-568 THAILAND 001-800-1206-65076 TURKEY 00-800-151-1241 UNITED ARAB EMIRATES 8000-35702362 UNITED KINGDOM BIRMINGHAM: 44-121-210-9012 0800-279-9352 UNITED KINGDOM GLASGOW: 44-141-202-3212 0800-279-9352 UNITED KINGDOM LEEDS: 44-113-301-2112 0800-279-9352 UNITED KINGDOM LONDON: 44-20-7019-0830 0800-279-9352 UNITED KINGDOM MANCHESTER: 44-161-601-1412 0800-279-9352 URUGUAY 000-413-598-3452 USA 1-210-795-0469 866-780-9216 VENEZUELA 0800-1-00-2853

2 3

[rssac-caucus] RSSAC Caucus Tools Collaboration
by Wes Hardaker March 12, 2017

March 12, 2017

In past caucus meeting discussions we've agreed that it would be nice to have a common repository for those that are developing tools related to the root server system, be them RSSAC-002 statistics processing or anything else. To that extent, I've had a new mailing list created and a github organization. If you're interested in participating in this work and collaborating with peers about tools, please respond and I'll have you added to the mailing list. mailing list: rssac-tools(a)icann.org github: https://github.com/rssac-caucus If you have specific proposals for work you'd like to do, plan on discussing it with people at the RSSAC Caucus meeting in Chicago if you'll be attending, or otherwise you can send it to the mailing list once everyone is subscribed. We'll discuss organizing and creating repositories for code at that time. -- Wes Hardaker USC/ISI

4 4

[rssac-caucus] Monthly update
by Carlos Reyes March 6, 2017

March 6, 2017

Hello, Caucus members. Below is a monthly update for your review. As always, please do not hesitate to contact my colleagues or me with any questions about RSSAC or Caucus activities. Best, Carlos Two New Caucus Members Please welcome Fred Baker and Robert Story to the Caucus. They have been subscribed to this list and their statements of interest are available here. Next Caucus Meeting As you know, the next Caucus meeting will be on Sunday, 26 March in Chicago, IL, USA during IETF98 (remote participation will be available). Andrew McConachie (andrew.mcconachie(a)icann.org) will be on site and is also leading the agenda development process. Please stand by for updated information from him. ICANN58 The next ICANN meeting begins this Saturday in Copenhagen, Denmark. The RSSAC will be participating in two “How It Works: Root Server Operations” tutorials on Sunday, 12 March and Monday, 13 March. The RSSAC will have a joint meeting with the ICANN Board and a public session on Tuesday, 14 March as well as several work sessions throughout the week. Work Parties Two work parties are active in the Caucus. Please contact John Bond (john.bond(a)icann.org) for information about “Technical Analysis of the Naming Scheme used for Individual Root Servers” and Kaveh Ranjbar (kaveh.ranjbar(a)ripe.net) for information about “Distribution of Anycast Instances.” RSSAC Meeting Minutes The minutes from the RSSAC meetings on 5 January and 2 February have been posted here.

1 0

[rssac-caucus] RSSAC Caucus meeting at IETF 98
by Andrew Mcconachie Feb. 10, 2017

Feb. 10, 2017

Dear RSSAC Caucus, This is a reminder that our next RSSAC Caucus meeting will be held at IETF 98 in Chicago Sunday March 26. The meeting will be held from 15:30 - 16:30 local time(18:30 - 19:30 UTC). If you have any agenda items please send them to the list. More information on the meeting(e.g., agenda, location, dial-in, etc) will be sent later. Thanks, Andrew

2 2

[rssac-caucus] FW: [Ext] ICANN News Alert -- Call for Volunteers for the Third Review of ICANN Accountability and Transparency (ATRT3)
by Carlos Reyes Feb. 2, 2017

Feb. 2, 2017

Dear all, Please see the announcement (below) about the call for volunteers for the third review of ICANN accountability and transparency (ATRT3). Best, Carlos Carlos Reyes | Policy and Community Engagement Manager carlos.reyes(a)icann.org | +1 (202) 802-8019 ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006 From: ICANN News Alert <no-reply(a)external.icann.org> Reply-To: "no-reply(a)external.icann.org" <no-reply(a)external.icann.org> Date: Tuesday, January 31, 2017 at 5:17 PM To: Carlos Reyes <carlos.reyes(a)icann.org> Subject: [Ext] ICANN News Alert -- Call for Volunteers for the Third Review of ICANN Accountability and Transparency (ATRT3) [icann.org] News Alert https://www.icann.org/news/announcement-2017-01-31-en[icann.org] Call for Volunteers for the Third Review of ICANN Accountability and Transparency (ATRT3) 31 January 2017 Represent the global stakeholder community by participating in ICANN Reviews. Apply today to join the team of global experts that will help improve the transparency and accountability of ICANN, and ensure it meets its commitments to the global community. ICANN is seeking volunteers to serve on the third review of ICANN Accountability and Transparency (ATRT3)[icann.org]. To apply, please click here[icann.org] [PDF, 2.78 MB] to fill out your Statement of Interest. You may also print out the Statement of Interest form and submit it to reviews(a)icann.org. Candidates are asked to submit their application materials by Friday, 21 April 2017, 23:59 UTC. All applications and supporting materials will be published as they are received on the public ATRT3 wiki page[community.icann.org]. Context and Chronology The specific objectives for the Accountability and Transparency (ATRT3) Review are to review ICANN's execution of its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency so as to ensure that the outcomes of its decision-making reflect the public interest and are accountabile to the Internet community. ICANN's Accountability and Transparency Review originated under the Affirmation of Commitments in 2009. Effective 1 October 2016, ICANN's obligation to conduct this review was incorporated into ICANN Bylaws. The composition of the Review Team will be determined by the ICANN community. For more information, please see Section 4.6. of the ICANN Bylaws[icann.org]. More information is included in the "Background" section below to provide an overview of events leading up to this Call for Volunteers. Scope of the Accountability and Transparency Review The ICANN Bylaws[icann.org] mandate that the community conduct a periodic Review to assess how ICANN is executing its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency. This ensures that the outcomes of its decision-making reflect the public interest and are accountable to the Internet community. The focus of the ATRT3 Review may include, but is not limited to, the following: Assess and improve Board governance which may include an ongoing evaluation of Board performance, the Board selection process, the extent to which the Board's composition and allocation structure meets ICANN's present and future needs, and the appeal mechanisms for Board decisions contained in the Bylaws; Assess the role and effectiveness of the GAC's interaction with the Board and with the broader ICANN community; make recommendations for improvements to ensure effective consideration by ICANN of GAC input on the public policy aspects of the technical coordination of the DNS; Assess and improve the processes by which ICANN receives public input (including adequate explanation of decisions taken and rationale); Assess the extent to which ICANN's decisions are supported and accepted by the Internet community; Assess the policy development process to facilitate enhanced cross community deliberations, and effective and timely policy development; Assess and improve the Independent Review Process; and Assess the extent to which prior Accountability and Transparency Review recommendations have been implemented and the extent to which implementation of such recommendations has resulted in the intended effect. Compensation ATRT3 Review Team members will not receive compensation from ICANN for their service on the team. However, travel, meal and lodging costs for Review Team members who participate in Review Team meetings will be reimbursed upon request in accordance with ICANN's community support travel guidelines[icann.org]. Responsibilities Review Team members will have the following general responsibilities: Participate in creation of charter documents for the Review Team; Select appropriate performance indicators and benchmarks; Consider public, ICANN Organization and Board input and incorporate it as appropriate in Review Team recommendations; Determine whether additional data or analysis is needed and participate in an ensuing provider selection, if necessary, in accordance with ICANN procurement practices; Provide timely updates to the community on the status of the Review Team's work; Analyze findings; Draw conclusions based on findings, develop useful, feasible and implementable recommendations; Provide guidance on prioritization of recommendations and definition of desired outcomes; Post the Draft Report of the Review Team for public review and comment; Deliver a Final Report of the Review Team; Designate several Review Team members to participate in the implementation planning work that follows the delivery of the Final Report of the Review Team and Board action on the recommendations. Skills and Experience To compose a well-balanced Review Team, ICANN seeks members who, in the aggregate, possess the following skills and experience: Performance assessment and audits Good governance and board performance Performance measurement Process improvement Knowledge of recognized frameworks for organizational excellence Principles of accountability applicable to organizations broadly similar to ICANN Desired Attributes Applicants should possess the following professional and personal attributes: Commitment and time to participate Multistakeholder community understanding Team spirit, adaptability, consensus-seeking attitude Willingness to learn Readiness to contribute Capacity to reason objectively, putting aside personal opinions or preconceptions Analytical skills Good communication skills using multiple methods and tools Methodology, Budget and Support ICANN will provide the Review Team with a clearly articulated review budget. Throughout the Review, the Review Team will periodically report on its progress related to planned schedule and budget. ICANN organizational support will be made available to the Review Team. Support will include assistance with project management, organization of work, documents and activities, and sharing of tools and best practices for conducting an effective review. English is the working language of the Review Team. Key communications and documents will be translated in accordance with the ICANN Language Services policies[icann.org] [PDF, 277 KB]. Background The ICANN Bylaws[icann.org] stipulate that "The Accountability and Transparency Review shall be conducted no less frequently than every five years measured from the date the previous Accountability and Transparency Review Team was convened." That would mean that the Call for Volunteers would take place no later than 4 October 2017. However, prior to the incorporation of this review into the ICANN Bylaws, several events took place leading up to ICANN's current commitment to launch the Call for Volunteers for ATRT3 in January 2017. The information presented below provides an overview of events leading up to this Call for Volunteers. October 2012 – Call for Volunteers[icann.org] for the Second Accountability and Transparency Review Team (ATRT2). February 2013 – Review Team (ATRT2) announced[icann.org]. December 2013 – ATRT2 issued Final Report[icann.org] [PDF, 3.46 MB] and Recommendations. June 2014 - the ICANN Board of Directors accepted all twelve ATRT2 Recommendations and directed the President and CEO of ICANN, through his designee(s), to proceed with the implementation - Resolution 2014.06.26.14[icann.org]. For more information on the status of the implementation activities, please visit the ATRT2 Implementation Wiki[community.icann.org]. July 2015 - In response to community concerns about workload, the ICANN Board delayed the start of ATRT3 until July 2017 via Resolution 2015.07.28.09[icann.org]. Note that under the Affirmation of Commitments, reviews were on a shorter cycle. January 2016 - In response to concerns raised by The National Telecommunications and Information Administration (NTIA) about delaying ATRT3 until July 2017, ICANN noted[icann.org] [PDF, 469 KB] that the Call for Volunteers to form the ATRT3 Review Team will be launched in January 2017. August 2016 - the Co-Chairs of the Cross Community Working Group on ICANN Accountability (CCWG-Accountability) wrote[icann.org] [PDF, 118 KB] to the ICANN Board, presenting possible options of how to combine Work Stream 2 (WS2) efforts and the ATRT3 work, to avoid work duplication. The co-Chairs took this step because as the IANA Stewardship Transition was being completed, and the ICANN Community was engaged in WS2 to address remaining issues, many of the WS2 topics were related to issues expected to be addressed in the ATRT3, i.e. accountability and transparency. October 2016 - The ICANN Board responded[icann.org] [PDF, 439 KB] that, "It is not up to the Board to dictate the scope of this important community review. While we share the concerns raised of avoiding duplication of resources, it is essential that the broader ICANN community have a voice in determining how the ATRT3 should be scoped in alignment with the Bylaws. The Board and the ICANN Organization stand ready to support the community's direction." December 2016 - the CCWG-Accountability Co-Chairs contacted the SO/AC Chairs, proposing a limited scope for ATRT3 as well as a reduced-size Review Team. They suggested that, if the broader ICANN Community agrees with the proposal and rationale, the SO/AC chairs issue a public statement or a letter to the ICANN CEO and Board Chair that explains why a limited scope is appropriate and indicate the level of support among the ICANN community for this limitation. ICANN organization is not aware of any collective community response to the CCWG-Accountability Co-Chair's note. Additional Materials Call for Volunteers: Accountability & Transparency Review Team[slideshare.net] from ICANN[slideshare.net] Contact If you have any questions, please send an email to: reviews(a)icann.org. This message was sent to carlos.reyes(a)icann.org from:ICANN News Alert | no-reply(a)external.icann.org | ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536Email Marketing by [icontact.com] Manage Your Subscription [app.icontact.com]

1 0

[rssac-caucus] Welcome six new Caucus members
by Carlos Reyes Jan. 27, 2017

Jan. 27, 2017

Dear Caucus, On 5 January at the recommendation of the Membership Committee, the RSSAC appointed six new members of the Caucus: · Anupam Agrawal · Shailesh Gupta · Ramet Khalili · Paul Muchene · Anand Raje · Mukund Sivaraman They have been added to this distribution list and are listed as members on the Caucus webpage. Their statements of interest can be viewed here. Please join me in welcoming them to the Caucus. Best, Carlos Carlos Reyes | Policy and Community Engagement Manager carlos.reyes(a)icann.org | +1 (202) 802-8019 ICANN | Internet Corporation for Assigned Names and Numbers 801 17th Street NW, Suite 400 | Washington, DC 20006

2 1

[rssac-caucus] The Collection of Yeti Technical activities and Findings
by Davey Song Jan. 16, 2017

Jan. 16, 2017

Hi folks, For your information , in order to give a full view of Yeti’s findings and activities to the people who are interested, we summarized them and update one page in Yeti website. http://yeti-dns.org/documents.html On another hand, I’m writing this mail to ask your attention on specific issues such as KSK rollover and IPv6 fragmentation. KSK roll experiment is important because ICANN will kick off KSK rollover September 19, 2017. IPv6 fragmentation is important because IPv6 traffic continue grow rapidly and IAB just issued out a statement on IPv6-only practice. In Yeti project we do find some problems on these two aspects worth attention. I also would like to invite people who are in this list to join our discussion in Yeti ML. http://lists.yeti-dns.org/mailman/listinfo/discuss Best regards, Davey

1 0

[rssac-caucus] ICANN News Alert -- Call for Volunteers for the Registration Directory Service (formerly WHOIS) Review Team
by Kathy Schnitt Jan. 12, 2017

Jan. 12, 2017

RSSAC Caucus, This may be of some interest to you. Best regards, Kathy Kathy Schnitt, Secretariat Services Coordinator for RSSAC and SSAC [CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DgMFaQ…> News Alert https://www.icann.org/news/announcement-2017-01-11-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Call for Volunteers for the Registration Directory Service (formerly WHOIS) Review Team 11 January 2017 DEADLINE EXTENSION – Applications to be appointed to the Registration Directory Service (RDS) Review Team are due on 20 January 2017, 23:59 UTC. ICANN is seeking volunteers to serve on the second review of Registration Directory Service (formerly known as the WHOIS Review). Interested individuals are invited to provide the following information, in the template[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_rdsapply…> [PDF, 2.66 MB] provided: * A biography, detailing relevant work and/or academic experience, as well as subject matter knowledge; * Your motivation for detailing your interest in serving on the Review Team and what you will bring to the team; * Specify the Supporting Organization (SO) or Advisory Committee (AC) that you would like to have consider you for nomination. Candidates are asked to submit their application materials to reviews(a)icann.org<mailto:reviews@icann.org> by 20 January 2017, 23:59 UTC. Note that all applications and supporting materials will be published as they are received on the RDS wiki page[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pa…>. Limited Scope Proposal Recent discussions among the leadership of the ICANN Supporting Organizations and Advisory Committees (SO/AC) and the Board Working Group on Registration Directory Service have highlighted concerns with the expected workload and community bandwidth in light of all the WHOIS related activities currently underway. To address these concerns, and to ensure that the RDS Review is conducted efficiently and effectively, the SO/AC leaders are considering a proposal to limit the scope and timeline for this review. The current proposal would ask that the RDS Review Team limit its review to conducting an investigation of the implementation results from the last WHOIS Review Team. Selection of the Review Team Under the new Bylaws[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, each SO/AC will have an opportunity to nominate up to seven applicants to serve on the Review Team. An applicant's name will only be presented to the SO/AC identified by the applicant for consideration. After SO/AC nomination process concludes, all nominations will be provided to the SO/AC Leaders to conduct the selection process for the Review Team according to the specified expertise and diversity (gender and geographic) requirements from the nominations received, the Review Team may contain up to 21 members, plus an ICANN Board member (designated by the ICANN Board). Timeline Call for volunteers published 28 October 2016 Deadline to apply for Review Team 20 January 2017 Time Commitment Applicants should be prepared to devote their time to the review process. Review Team work is expected to include regular conference calls (some of which may not be held during business hours in all time zones), and possibly up to three face-to-face meetings, each lasting two to three days. Under the Limited Scope Proposal, the RDS Review Team may be asked to complete its work within six months of its first meeting. Compensation RDS Review Team members will not receive compensation from ICANN for their service on the team. However, travel, meal and lodging costs for Review Team members who participate in Review Team meetings will be reimbursed upon request in accordance with ICANN's community travel support guidelines[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_news_…>. Responsibilities * Participate in creation of charter documents for the Review Team; * Select appropriate performance indicators and benchmarks; * Consider public, community and Board input and incorporate it as appropriate in Review Team recommendations; * Determine whether additional data or analysis is needed and participate in an ensuing provider selection, if necessary; * Provide timely updates to the community on the status of the Review Team's work; * Analyze findings; * Draw conclusions based on findings, develop useful and feasible recommendations; * Provide guidance on prioritization of recommendations and definition of desired outcomes; * Post the draft report of the Review Team for public review and comment; * Deliver a final Review Team report; and * Designate Review Team members to participate in the implementation planning work that follows the delivery of the final Review Team report. Skills and Experience To compose a well-balanced Review Team, ICANN seeks members who, in the aggregate, possess the following skills and experience: * Prior member of the 1st WHOIS Review Team or was an active contributor to its work * Prior member of the Expert Working Group on Registration Directory Service * Familiarity with operation of the Domain Name System (DNS) * Familiarity with WHOIS registrant data collection, compliance, directory service (RDDS) management * Familiarity with Translation and Transliteration of WHOIS Contact Information * Familiarity with ICANN Procedure for Handling WHOIS Conflicts with Privacy Law * Familiarity with malware and abuse vectors and mitigations, including cybercrime * Familiarity with WHOIS Data Retention Waiver Process Composition of the Review Team, depending on expertise and skills required, will aim to achieve: * Diversity in general, with particular attention on: * Geographic diversity; and * Gender diversity. Desired Attributes Applicants should possess the following professional and personal attributes: * Multistakeholder community understanding * Team spirit, adaptability, consensus-seeking attitude * Willingness to learn * Readiness to contribute * Capacity to reason objectively, putting aside personal opinions or preconceptions * Analytical skills Methodology, Budget & Support ICANN will provide the Review Team with a clearly articulated review budget at the start. Throughout the review, there will be periodic reporting by the Review Team on its progress relative to planned schedule and budget. A clear and focused review scope is expected to assist the Review Team with prioritizing recommendations in order to optimize finite ICANN resources (time and budget). ICANN organizational support will be made available to the Review Team. Support could include assistance with project management; organization of work, documents and activities; as well as sharing of tools and best practices for conducting an effective review. English is the working language of the Review Team. Key communications and documents will be translated in accordance with the ICANN Language Services policies. Background Community-led reviews are an important mechanism for furthering ICANN's obligations outlined in the new Bylaws[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> that went into force on 1 October 2016. * Ensuring accountability, transparency and the interests of global Internet users; * Preserving security, stability and resiliency of the DNS; * Promoting competition, consumer trust and consumer choice; * Registration Directory Service (WHOIS) policy. These Specific Reviews replace the reviews that were formerly mandated under the Affirmation of Commitments (AoC). The specific objectives for the Registration Directory Service (RDS) Review are to review the effectiveness of WHOIS, and whether its implementation meets the legitimate needs of law enforcement, promoting consumer trust and safeguarding registrant data. The first WHOIS review concluded in 2012 and was conducted under the AOC. The Final Report[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 1.44 MB] from the First Review Team was submitted to the ICANN Board on 11 May 2012, with Board action to approve the report and recommendations, including the implementation plan[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 119 KB] occurred on 8 November 2012. For more information on the status of the implementation activities arising out of the 1st WHOIS Review team, please visit the WHOIS Implementation Wiki[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. Additional Materials RDS Call for Volunteers presentation[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pa…> Contact If you have any questions, please contact Margie Milam or Karen Mulberry at reviews(a)icann.org<mailto:reviews@icann.org>.

1 0