At-Large Advisory Committee (ALAC) Advice Status

Board Advice Home | RSSAC Advice Status | SSAC Advice Status | GAC Advice Status


Latest Advice to the ICANN Board

As of 29 February 2020

Advisory Committee Advice Document
At-Large Advisory Committee (ALAC)

Board Advice Register Phases and Descriptions

Board Advice Register Phases and Descriptions

Advice Items by Advisory Committee

Phase ALAC
Phase 1 | Receive & Acknowledge -
Phase 2 | Understand 16
Phase 3 | Evaluate & Consider -
Phase 3 | Deferred -
Phase 4 | Implement 2
Phase 4 | Deferred -
Phase 5 | Close -
Total Open Items by Advisory Committee 18
Total Items Closed in Past 12 Months 4

Open Advice Items

See also "Advice Status Reports" on Board Advice Home for PDF/Excel versions of the information below.

Advice Item Phase Action(s) Taken

ALAC: DNS Abuse (R-1)

(24 Dec 2019)

Phase 2 | Understand Request

ICANN received ALAC: DNS Abuse on 10 January 2020 and is currently reviewing. ICANN org understands ALAC to advise the Board to direct ICANN org to establish a clear definition of "abuse" that is within ICANN's remit. We assume that any such definition would, without limitation, include harmful activity insofar as they intersects with the DNS and involves the use of malware, botnets, phishing, pharming, and spam (when it serves as a delivery mechanism for the other forms of DNS abuse). ICANN org further understands ALAC to advise the Board to direct org to clarify the "purposes and applications of ""abuse"" before further work is done to define DNS abuse." We are unsure, however, what ALAC's reference to "purposes and applications" of abuse is intended to mean and request clarification on this point. Is ALAC's advice to identify the characteristics of abuse (e.g., behavior that affects the DNS in specified ways) that would be within ICANN's remit? If so, ICANN org also understands ALAC to advise that once the scope and characteristics of abuse within ICANN's remit is identified, a determination should be made whether abuse definitions used by outside sources can serve as references for the ICANN community, or whether a new, outcomes-based nomenclature could be useful (including impersonation, fraud, or other types of abuse) to accurately describe problems being addressed. ICANN sent this understanding to the ALAC for review on 27 January 2020.

ALAC: DNS Abuse (R-2)

(24 Dec 2019)

Phase 2 | Understand Request

ICANN received ALAC: DNS Abuse on 10 January 2020 and is currently reviewing. ICANN org understands ALAC to advise the Board to direct ICANN org to prohibit Contracted Parties from rate limiting WHOIS (eventually RDAP) requests or to require Contracted Parties to simplify the process of whitelisting. ICANN understands that ALAC believes that these changes would facilitate improved reporting on the rate of abuse in the registration ecosystem that falls within ICANN's remit. ICANN also understands that ALAC advises the Board to cause ICANN to require Contracted Parties to adopt a uniform and timely access framework for publicly available registrant data, but requests further clarification as to ALAC's expectations in this regard. Does the ALAC recommendation refer to something beyond universal adoption of RDAP and implementation of policies developed by the EPDP? With respect to implementation of this recommendation, and taking into account that ALAC is empowered to initiate discussions leading to the creation of a PDP, ICANN org understands that ALAC advises the Board either to (i) initiate a PDP process by calling for an Issues Report or (ii) cause ICANN Org to enter into voluntary negotiations with Contracted Parties to prohibit rate limiting or simplify the white-listing process and to adopt a uniform and timely framework for access to publicly available registrant data. ICANN sent this understanding to the ALAC for review on 27 January 2020.

ALAC: DNS Abuse (R-3)

(24 Dec 2019)

Phase 2 | Understand Request

ICANN received ALAC: DNS Abuse on 10 January 2020 and is currently reviewing. ICANN org understands ALAC to advise the Board to direct ICANN org to establish low thresholds for identifying bad actors. We interpret this to mean that ALAC advises the Board to direct ICANN org to use DAAR to identify operators with high concentrations of malware, botnets, phishing, pharming, and spam (when it serves as a delivery mechanism for the other forms of DNS abuse) and other abusive behaviors within ICANN's remit once, with respect to the latter, agreement is reached on the scope and characteristics of abuse within ICANN's remit (either through Consensus Policy development or through voluntary contract negotiations between ICANN and Contracted Parties). ICANN also understands that ALAC advises the Board to direct ICANN org to identify and acquire data needed to publish more actionable DAAR data and to identify registrars that sponsor or registries containing high concentrations of domain registrations engaged in such behaviors. ICANN sent this understanding to the ALAC for review on 27 January 2020.

ALAC: DNS Abuse (R-4)

(24 Dec 2019)

Phase 2 | Understand Request

ICANN received ALAC: DNS Abuse on 10 January 2020 and is currently reviewing. ICANN org understands ALAC to advise the Board to provide an explicit mandate to ICANN Contractual Compliance to regularly use the audit function to root out "systemic" abuse; not to regulate content, but to proactively exercise enforceability. We interpret this to mean that the ALAC is advising the Board to direct ICANN org to do so now with respect to malware, botnets, phishing, pharming, and spam (when it serves as a delivery mechanism for the other forms of DNS abuse) and, once agreement is reached on the scope and characteristics of abuse within ICANN's remit (either through Consensus Policy development or through voluntary contract negotiations between ICANN and Contracted Parties), other such behaviors. We understand that the ALAC is advising the Board to direct ICANN org to undertake regular audits of compliance with resulting obligations. ICANN sent this understanding to the ALAC for review on 27 January 2020.

ALAC: DNS Abuse (R-5)

(24 Dec 2019)

Phase 2 | Understand Request

ICANN received ALAC: DNS Abuse on 10 January 2020 and is currently reviewing. ICANN org understands ALAC to advise the Board to direct ICANN org to prohibit Contracted Parties from processing registrations where the payor is or the method of payment belongs to an individual or entity other than the registrant, unless such payment methods have been approved in advance of registration. With respect to implementation of this recommendation, and taking into account that ALAC is empowered to initiate discussions leading to the creation of a PDP, ICANN Org understands that ALAC advises the Board either to (1) initiate a PDP by calling for an Issue Report on this topic or (ii) cause ICANN Org to enter into voluntary negotiations with Contracted Parties to implement ALAC's advice. ICANN sent this understanding to the ALAC for review on 27 January 2020.

ALAC: DNS Abuse (R-6)

(24 Dec 2019)

Phase 2 | Understand Request

ICANN received ALAC: DNS Abuse on 10 January 2020 and is currently reviewing.

ALAC: DNS Abuse (R-7)

(24 Dec 2019)

Phase 2 | Understand Request

ICANN received ALAC: DNS Abuse on 10 January 2020 and is currently reviewing. ICANN org understands ALAC to advise the Board to direct ICANN org to compel Contracted Parties to adhere to industry-wide good behavior, for example, by increasing per domain transaction fees for registrars that continually demonstrate high abuse rates. With respect to implementation of this recommendation, ICANN org understands that ALAC advises the Board to cause ICANN org to enter into voluntary negotiations with Contracted Parties regarding (i) pricing and (ii) industry best practices. We interpret "abuse" in this context to refer, for the time being, to harmful activity insofar as it intersects with the DNS and involves the use of malware, botnets, phishing, pharming, and spam (when it serves as a delivery mechanism for the other forms of DNS abuse). We understand that the scope of this could expand once agreement has been reached (either through Consensus Policy development or through voluntary contract negotiations between ICANN and Contracted Parties) on the scope and characteristics of "abuse" within ICANN's remit. ICANN sent this understanding to the ALAC for review on 27 January 2020.

ALAC: DNS Abuse (R-8)

(24 Dec 2019)

Phase 2 | Understand Request

ICANN received ALAC: DNS Abuse on 10 January 2020 and is currently reviewing. ICANN org understands ALAC to advise the ICANN Board to direct ICANN org to enter into voluntary contract negotiations with Contracted Parties to implement the above advise, and to include clear enforcement language to facilitates ICANN Contractual Compliance to enforce. ICANN org further understands ALAC to advise the ICANN Board to direct ICANN org to ensure that ICANN Contractual Compliance has the tools it will need to enforce the output of any relevant Consensus Policy and/or voluntary contract negotiations. ICANN sent this understanding to the ALAC for review on 27 January 2020.

ALAC: ISOC/PIR Issue (R-1)

(31 Jan 2020)

Phase 2 | Understand Request

ICANN received ALAC: ISOC/PIR Issue (R-1) on 31 January 2020 and is currently reviewing.

ALAC: ISOC/PIR Issue (R-2)

(31 Jan 2020)

Phase 2 | Understand Request

ICANN received ALAC: ISOC/PIR Issue (R-2) on 31 January 2020 and is currently reviewing.

ALAC: ISOC/PIR Issue (R-3)

(31 Jan 2020)

Phase 2 | Understand Request

ICANN received ALAC: ISOC/PIR Issue (R-3) on 31 January 2020 and is currently reviewing.

ALAC: ISOC/PIR Issue (R-4)

(31 Jan 2020)

Phase 2 | Understand Request

ICANN received ALAC: ISOC/PIR Issue (R-4) on 31 January 2020 and is currently reviewing.

ALAC: ISOC/PIR Issue (R-5)

(31 Jan 2020)

Phase 2 | Understand Request

ICANN received ALAC: ISOC/PIR Issue (R-5) on 31 January 2020 and is currently reviewing.

ALAC: ISOC/PIR Issue (R-6)

(31 Jan 2020)

Phase 2 | Understand Request

ICANN received ALAC: ISOC/PIR Issue (R-6) on 31 January 2020 and is currently reviewing.

ALAC: ISOC/PIR Issue (R-7)

(31 Jan 2020)

Phase 2 | Understand Request

ICANN received ALAC: ISOC/PIR Issue (R-7) on 31 January 2020 and is currently reviewing.

ALAC: ISOC/PIR Issue (R-8)

(31 Jan 2020)

Phase 2 | Understand Request

ICANN received ALAC: ISOC/PIR Issue (R-8) on 31 January 2020 and is currently reviewing.

Enabling Inclusive, Informed and Meaningful Participation at ICANN: A Joint Statement by ALAC and GAC (R1)

(2 Nov 2017)

Phase 4 | Implement

The Information Transparency Initiative (ITI) team previewed new Announcements and Blog pages on feedback.icann.org in October 2018. Work on the authoring and content model in the document management system has begun and several content types have been completed. Since the launch of ITI in January 2018, the team has published eight blogs on icann.org and conducted several public sessions to provide the community with updates and input into the progress of this project. On 30 October 2019, the Information Transparency Initiative (ITI) team released the proposed new search experience for Board Meeting content for community input via the ITI feedback site. The improved searchability, which is core to ITI, includes: filters to narrow search by document type (Resolutions, Minutes, Agenda), Board Committees (current and former), and Board Meeting type; a date range filter; an expandable and collapsible table structure, jump-to links for upcoming Board Meetings, Year, and Month/Year; and keyword(s) search within Board Meeting content with results available by relevance (number of instances of the keyword(s)) or newest (search results ordered by publish date). Also, the ITI team is developing an improved Public Comment feature based on invaluable input from members of ICANN's Supporting Organizations and Advisory Committees. This new feature will be available for testing in late January 2020. ITI is aiming for an April 2020 soft launch of the new site. In September 2019 and October 2019, blogs were published to https://icann.org, which provided the community with an update on the project's status.

Enabling Inclusive, Informed and Meaningful Participation at ICANN: A Joint Statement by ALAC and GAC (R2)

(2 Nov 2017)

Phase 4 | Implement

On 9 February 2018, the ICANN Board sent a letter to Alan Greenberg, chair of the ALAC, regarding this joint ALAC-GAC advice. Please see the letter here: https://www.icann.org/en/system/files/correspondence/chalaby-to-greenberg-09feb18-en.pdf. In August 2019, ICANN Org shared an update that a meeting will be facilitated at ICANN66 with the ALAC, GAC, and NCSG to discuss the needs of all groups regarding simple language documentation and capacity building activities. Additionally, the co-chairs of the At-Large Consolidated Policy WG will prepare podcasts for each public comment which ALAC has agreed to prepare a statement. During ICANN66, representatives of the ALAC and NPOC, with input from GAC support staff, held an informative session on current communication procedures and tools within their respective groups. They received useful comments from Sally Costerton and Sally Newell-Cohen. Next steps will include the ALAC reaching out to the GAC and NPOC leadership on organizing an inter-sessional call early in 2020 to discuss follow up from their successful session. The ALAC will propose a joint f2f session during ICANN67 in Cancun.

Advice Items Closed in the Last 12 Months

Advice Item Close Date Action(s) Taken

The 2nd At-Large Summit (ATLAS II) Final Declaration -- At-Large Community Engagement in ICANN (R-37)

(26 Jun 2014)

9/25/19

Staff, under the direction of At-Large leadership, has already begun to rework the website and Wiki to ensure that our "Policy Advice" pages are accurate and understandable. This will continue as volunteer and staff resources allow. We will also ensure that as documents are published, the classification of the document is clear. The goal is to address two issues: • Confusion about the type of document (ie "Advice" vs "Comment") • The "End user" justification for intervention. Accordingly, staff together with At-Large leadership will categorize the existing documents (as advice, public comment, correspondence, etc.) in a more granular fashion and provided enhanced tools with which to filter search results based on these categories. Furthermore, staff will create a new field in the database for "End User Issue" and At-Large leadership will populate this field both in current documents and those generated going forward. The following items have been created to satisfy these goals: • An Executive Summaries: ALAC Policy Comments & Advice resource page has been created to address "type" of document (#1). • The At-Large Consolidated Policy Working Group (CPWG) meets weekly to discuss "end user" justification for intervention (#2). With these simple modifications, it should be easier for a Wiki visitor to peruse the work of the At-large and to quickly understand the rationale for creating individual documents.

The 2nd At-Large Summit (ATLAS II) Final Declaration -- Future of Multi-Stakeholder Models (R-7)

(26 Jun 2014)

9/25/19

The Board in its 9 September 2014 resolution acknowledged the Final ATLAS II Declaration: https://www.icann.org/resources/board-material/resolutions-2014-09-09-en... This recommendation was discussed by the Board Organization Effectiveness Committee (OEC), which subsequently added the item to the OEC workplan: "Holistic Assessment of ICANN structures". The OEC agreed that the work underway on the current cycle of 11 reviews and the recommendations of WS2-Accountability should progress further, before the topic of "holistic assessment of ICANN structures" is to be addressed. Updates on OEC's progress on this work item are reported on the Semi-Annual Committee Report (most recent published report – page 8 :https://www.icann.org/en/system/files/files/oec-activities-19jan18-en.pdf). For further information on the OEC's consideration of this topic, see: https://www.icann.org/resources/board-material/minutes-oec-2017-10-27-en; and latest OEC meeting minutes: https://www.icann.org/resources/board-material/minutes-oec-2018-06-24-en).

Joint GAC-ALAC Statement on the EPDP

(25 Mar 2019)

5/7/19

The ICANN org understands that this is the Joint GAC-ALAC Statement on the EPDP. As this item will be considered via the Public Comment process, the item will be considered closed. The Board will provide its rationale for its action in the Board Resolution on the EPDP Recommendations. This understanding was sent to the ALAC on 7 May 2019.

Follow-Up to the Joint Statement by ALAC and GAC: Enabling Inclusive, Informed and Meaningful Participation at ICANN

(12 Dec 2018)

4/23/19

On 27 January 2019 the Board addressed this advice in their Barcelona Scorecard. Additionally, Cherine Chalaby included a response in his 6 February 2019 letter to Maureen Hilyard. On 23 April 2019 the ICANN org notified the ALAC this advice is considered closed due to these two responses.