Changes

This finding gave rise to substantial concern among the ICANN Board. As [[Maarten Botterman]] noted in a letter to the GNSO Council, "[t]here is no guarantee that SSAD users would receive the registration data they request via this system" because such a high volume of registration data is contained within a proxy or privacy service.<ref name="odaletter">[https://mm.icann.org/pipermail/council/attachments/20220125/81d60ddc/2022-01-24BoardtoCouncilonSSADconsultation-0001.pdf GNSO Council Listserv Archive - Board to Council re: Upcoming SSAD Consultation], January 24, 2022</ref> Botterman's letter was intended to initiate conversation and thought prior to a scheduled meeting of the Board and GNSO Council on January 27, 2022.<ref name="odaletter" /><ref name="odpdash" /> That meeting was a constructive exchange of views on the viability of SSAD, although no conclusions were drawn. In particular, the discussants raised topics such as the merits and costs of accreditation, the legal risks involved in SSAD, the development of a requestor code of conduct, the need for a pilot version, shortening the timeline, and improving the estimate of potential users.

This finding gave rise to substantial concern among the ICANN Board. As [[Maarten Botterman]] noted in a letter to the GNSO Council, "[t]here is no guarantee that SSAD users would receive the registration data they request via this system" because such a high volume of registration data is contained within a proxy or privacy service.<ref name="odaletter">[https://mm.icann.org/pipermail/council/attachments/20220125/81d60ddc/2022-01-24BoardtoCouncilonSSADconsultation-0001.pdf GNSO Council Listserv Archive - Board to Council re: Upcoming SSAD Consultation], January 24, 2022</ref> Botterman's letter was intended to initiate conversation and thought prior to a scheduled meeting of the Board and GNSO Council on January 27, 2022.<ref name="odaletter" /><ref name="odpdash" /> That meeting was a constructive exchange of views on the viability of SSAD, although no conclusions were drawn. In particular, the discussants raised topics such as the merits and costs of accreditation, the legal risks involved in SSAD, the development of a requestor code of conduct, the need for a pilot version, shortening the timeline, and improving the estimate of potential users.

==Simple Ticketing System (aka SSAD Light)==

== Whois Disclosure System (FKA Simple Ticketing System or SSAD Light)==

One outcome of the ODA is the development of an idea for a simple ticketing system (STS) designed to centralize requests for registrant information disclosures.<ref>[https://circleid.com/posts/20220404-icann-ssad-proposal-poised-to-succeed ICANN SSAD Proposal Poised to Succeed, Paul McGrady, CircleID]</ref> If it runs as a pilot version of the SSAD, it will provide data that may help ICANN staff refine the SSAD proposal. Following its review of the ODA and a meeting and several rounds of correspondence with the board, the GNSO Council formed a small team to develop the concept of the simple ticketing system (STS) and ICANN Staff began researching the STS's development cost and timeframe. The STS will document requests' nature, receiving registrars, response speed (if at all), and appropriateness of disclosure. The STS will also yield estimates of how many users and requests to expect of the eventual SSAD.<ref>[https://circleid.com/posts/20220404-icann-ssad-proposal-poised-to-succeed ICANN SSAD Proposal Poised to Succeed, Paul McGrady, CircleID]</ref> <br/>

One outcome of the ODA is the development of an idea for a simple ticketing system (STS) designed to centralize requests for registrant information disclosures.<ref>[https://circleid.com/posts/20220404-icann-ssad-proposal-poised-to-succeed ICANN SSAD Proposal Poised to Succeed, Paul McGrady, CircleID]</ref> If it runs as a pilot version of the SSAD, it will provide data that may help ICANN staff refine the SSAD proposal. Following its review of the ODA and a meeting and several rounds of correspondence with the board, the GNSO Council formed a small team to develop the concept of the simple ticketing system (STS) and ICANN Staff began researching the STS's development cost and timeframe. The STS will document requests' nature, receiving registrars, response speed (if at all), and appropriateness of disclosure. The STS will also yield estimates of how many users and requests to expect of the eventual SSAD.<ref>[https://circleid.com/posts/20220404-icann-ssad-proposal-poised-to-succeed ICANN SSAD Proposal Poised to Succeed, Paul McGrady, CircleID]</ref> <br/>

At the April 2022 GNSO Council meeting, [[Sebastien Ducos]] explained that the idea was for the Board to pause any decision on the SSAD and instead enter what was a pilot phase but became a [https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos-to-gnso-council-et-al-04apr22-en.pdf proof of concept] phase (as of April 4, 2022) to arrive at a simplified SSAD version to run for up to two years in six-month increments to review/test hypotheses about who, what, when, why in terms of traffic at each interval and estimate what would be required and how to deliver it.<ref>[https://gnso.icann.org/sites/default/files/policy/2022/transcript/transcript-gnso-council-14apr22-en.pdf GNSO Council Meeting April 4, 2022, Transcript pg. 16, GNSO, ICANN.org]</ref><br/>

At the April 2022 GNSO Council meeting, [[Sebastien Ducos]] explained that the idea was for the Board to pause any decision on the SSAD and instead enter what was a pilot phase but became a [https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos-to-gnso-council-et-al-04apr22-en.pdf proof of concept] phase (as of April 4, 2022) to arrive at a simplified SSAD version to run for up to two years in six-month increments to review/test hypotheses about who, what, when, why in terms of traffic at each interval and estimate what would be required and how to deliver it.<ref>[https://gnso.icann.org/sites/default/files/policy/2022/transcript/transcript-gnso-council-14apr22-en.pdf GNSO Council Meeting April 4, 2022, Transcript pg. 16, GNSO, ICANN.org]</ref><br/>

* minimize development and operational costs of the system,

* minimize development and operational costs of the system,

* collect request statuses (e.g., approved, denied) from [[CPH|contracted parties]], and

* collect request statuses (e.g., approved, denied) from [[CPH|contracted parties]], and

* gather data on response times from contracted parties for requests of different priorities.<ref>[https://gnso.icann.org/sites/default/files/policy/2022/correspondence/fouquart-to-botterman-27apr22-en.pdf Status Update EPDP Phase 2 & Review of ODA, GNSO Council Letter to ICANN Board, April 27, 2022]</ref>

* gather data on response times from contracted parties for requests of different priorities.<ref>[https://gnso.icann.org/sites/default/files/policy/2022/correspondence/fouquart-to-botterman-27apr22-en.pdf Status Update EPDP Phase 2 & Review of ODA, GNSO Council Letter to ICANN Board, April 27, 2022]</ref><br/>

==References==

==References==