SSAD Next Steps and draft Assignment Form
Dear Councilors, As noted in the recent message<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> for the SSAD Supplemental Recommendations Team for the Council's review and feedback. Once finalised, this proposed Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al. Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below. Reminder of how we got here The Council began discussing possible next steps for the SSAD recommendations beginning in November<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>. In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee. Specifically, the Council discussed the ramifications of following the RDRS Standing Committee's recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following: * The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; * Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; * The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, * This would provide a procedurally efficient path that recognizes the ICANN Community's desire for this work to be completed in a timely manner. Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently. Remit of the Council under the Bylaws Annex A, Section 9 of the ICANN Bylaws<https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are "not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council." Subsequently, "at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board." The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council. Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC. Can the SSAD Supplemental Recommendations Team create new policy? The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team's draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work. The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with "specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations." In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it "encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot's evidence and the Standing Committee's considerations in [conducting its assignment from the Council.]" In light of the above, the Standing Committee's, ICANN Board's, and the Council's expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC's guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome. Can all GNSO Councilors participate? Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team. What is the expected time commitment? Because the Council has committed<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations "in months, not years," the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises. Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a one-day in-person workshop on Sunday, 7 June before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon. While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible. Other than the time commitment, is there anything else I should know if I would like to participate? Per the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including: * RDRS Standing Committee Final Findings Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; * SSAD Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> * RDRS Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary<https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...> Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents. What is the Council's role at this stage? We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on 16 April so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting. Thank you. Susan Susan Payne GNSO Council Chair Head of Legal Policy [cid:image001.png@01DCC6AF.7B2EBFB0]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 comlaude.com<http://comlaude.com> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0> [cid:image002.png@01DCC6AF.7B2EBFB0]<https://www.linkedin.com/company/com-laude> [cid:image003.png@01DCC6AF.7B2EBFB0] <https://twitter.com/comlaude?lang=en> [cid:image004.png@01DCC6AF.7B2EBFB0] <https://www.facebook.com/ComLaude/> [cid:image005.png@01DCC6AF.7B2EBFB0] <https://www.youtube.com/@comlaude> [cid:image006.jpg@01DCC6AF.7B2EBFB0] ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the "Com Laude Group") does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com>
Thanks Susan. Happy to hear there will be a Day zero meeting of this Supplemental Recommendations Team in Seville. I am an interested Councilor so please count me in as a member. Separately, in the documents section, will staff please link the GNSO Human Rights checklist and the ICANN Board-approved Human Rights Framework of Interpretation? (I may have missed these in some other section but they should both definitely be linked in Documents.) Is there some reason we are referring to a "Lead" on this team, rather than a "Chair" "or "Co-Chairs"? Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Tue, Apr 7, 2026 at 10:23 AM Susan Payne via council <council@icann.org> wrote:
Dear Councilors,
As noted in the recent message <https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031TneI/edit?usp=sharing>for the SSAD Supplemental Recommendations Team for the Council’s review and feedback.
Once finalised, this proposed Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al.
Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below.
*Reminder of how we got here*
The Council began discussing possible next steps for the SSAD recommendations beginning in November <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...> .
In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee.
Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following:
- The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; - Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; - The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, - This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner.
Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently.
*Remit of the Council under the Bylaws *
Annex A, Section 9 of the ICANN Bylaws <https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.”
The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council.
Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC.
*Can the SSAD Supplemental Recommendations Team create new policy? *
The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work.
The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.”
In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]”
In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome.
*Can all GNSO Councilors participate? *
Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team.
*What is the expected time commitment? *
Because the Council has committed <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises.
Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a *one-day in-person workshop on* *Sunday, 7 June* before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon.
While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible.
*Other than the time commitment, is there anything else I should know if I would like to participate?*
Per the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including:
- RDRS Standing Committee Final Findings Report <https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; - SSAD Operational Design Assessment <https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - RDRS Policy Alignment Analysis <https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary <https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...>
Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents.
*What is the Council’s role at this stage?*
We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits *before our Council meeting on 16 April* so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting.
Thank you.
Susan
Susan Payne GNSO Council Chair
Head of Legal Policy
28 Little Russell Street, London WC1A 2HN, UK *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*comlaude.com <http://comlaude.com>*
*Follow us on **LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0>** and** Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0>*
<https://www.linkedin.com/company/com-laude> <https://twitter.com/comlaude?lang=en> <https://www.facebook.com/ComLaude/> <https://www.youtube.com/@comlaude>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com> _______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
I find myself leaning in support of a distinction between a Supplemental Recommendations Team and a Working Group, so "Team Lead" makes sense to me (as was the case with the SubPro Small Team, and SubPro Small Team Plus) I see links to the GPIF checklist, HRIA tool, HR-FOI and Consensus Policies under Assignment on page 2. Kind regards, Justine On Fri, 10 Apr 2026 at 02:42, Anne ICANN via council <council@icann.org> wrote:
Thanks Susan. Happy to hear there will be a Day zero meeting of this Supplemental Recommendations Team in Seville. I am an interested Councilor so please count me in as a member.
Separately, in the documents section, will staff please link the GNSO Human Rights checklist and the ICANN Board-approved Human Rights Framework of Interpretation? (I may have missed these in some other section but they should both definitely be linked in Documents.)
Is there some reason we are referring to a "Lead" on this team, rather than a "Chair" "or "Co-Chairs"?
Thank you, Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, Apr 7, 2026 at 10:23 AM Susan Payne via council <council@icann.org> wrote:
Dear Councilors,
As noted in the recent message <https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031TneI/edit?usp=sharing>for the SSAD Supplemental Recommendations Team for the Council’s review and feedback.
Once finalised, this proposed Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al.
Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below.
*Reminder of how we got here*
The Council began discussing possible next steps for the SSAD recommendations beginning in November <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...> .
In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee.
Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following:
- The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; - Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; - The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, - This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner.
Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently.
*Remit of the Council under the Bylaws *
Annex A, Section 9 of the ICANN Bylaws <https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.”
The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council.
Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC.
*Can the SSAD Supplemental Recommendations Team create new policy? *
The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work.
The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.”
In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]”
In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome.
*Can all GNSO Councilors participate? *
Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team.
*What is the expected time commitment? *
Because the Council has committed <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises.
Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a *one-day in-person workshop on* *Sunday, 7 June* before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon.
While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible.
*Other than the time commitment, is there anything else I should know if I would like to participate?*
Per the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including:
- RDRS Standing Committee Final Findings Report <https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; - SSAD Operational Design Assessment <https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - RDRS Policy Alignment Analysis <https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary <https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...>
Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents.
*What is the Council’s role at this stage?*
We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits *before our Council meeting on 16 April* so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting.
Thank you.
Susan
Susan Payne GNSO Council Chair
Head of Legal Policy
28 Little Russell Street, London WC1A 2HN, UK *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*comlaude.com <http://comlaude.com>*
*Follow us on **LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0>** and** Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0>*
<https://www.linkedin.com/company/com-laude> <https://twitter.com/comlaude?lang=en> <https://www.facebook.com/ComLaude/> <https://www.youtube.com/@comlaude>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com> _______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
_______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
Thank you Justine - I'm guilty of skimming and looking for those docs in the wrong place! I'm ok with Team Lead. Will you be participating for the ALAC? Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Thu, Apr 9, 2026 at 8:09 PM Justine Chew <justine.chew.icann@gmail.com> wrote:
I find myself leaning in support of a distinction between a Supplemental Recommendations Team and a Working Group, so "Team Lead" makes sense to me (as was the case with the SubPro Small Team, and SubPro Small Team Plus)
I see links to the GPIF checklist, HRIA tool, HR-FOI and Consensus Policies under Assignment on page 2.
Kind regards, Justine
On Fri, 10 Apr 2026 at 02:42, Anne ICANN via council <council@icann.org> wrote:
Thanks Susan. Happy to hear there will be a Day zero meeting of this Supplemental Recommendations Team in Seville. I am an interested Councilor so please count me in as a member.
Separately, in the documents section, will staff please link the GNSO Human Rights checklist and the ICANN Board-approved Human Rights Framework of Interpretation? (I may have missed these in some other section but they should both definitely be linked in Documents.)
Is there some reason we are referring to a "Lead" on this team, rather than a "Chair" "or "Co-Chairs"?
Thank you, Anne
Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com
On Tue, Apr 7, 2026 at 10:23 AM Susan Payne via council < council@icann.org> wrote:
Dear Councilors,
As noted in the recent message <https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031TneI/edit?usp=sharing>for the SSAD Supplemental Recommendations Team for the Council’s review and feedback.
Once finalised, this proposed Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al.
Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below.
*Reminder of how we got here*
The Council began discussing possible next steps for the SSAD recommendations beginning in November <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...> .
In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee.
Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following:
- The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; - Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; - The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, - This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner.
Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently.
*Remit of the Council under the Bylaws *
Annex A, Section 9 of the ICANN Bylaws <https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.”
The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council.
Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC.
*Can the SSAD Supplemental Recommendations Team create new policy? *
The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work.
The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.”
In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]”
In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome.
*Can all GNSO Councilors participate? *
Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team.
*What is the expected time commitment? *
Because the Council has committed <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises.
Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a *one-day in-person workshop on* *Sunday, 7 June* before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon.
While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible.
*Other than the time commitment, is there anything else I should know if I would like to participate?*
Per the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including:
- RDRS Standing Committee Final Findings Report <https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; - SSAD Operational Design Assessment <https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - RDRS Policy Alignment Analysis <https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary <https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...>
Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents.
*What is the Council’s role at this stage?*
We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits *before our Council meeting on 16 April* so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting.
Thank you.
Susan
Susan Payne GNSO Council Chair
Head of Legal Policy
28 Little Russell Street, London WC1A 2HN, UK *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*comlaude.com <http://comlaude.com>*
*Follow us on **LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0>** and** Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0>*
<https://www.linkedin.com/company/com-laude> <https://twitter.com/comlaude?lang=en> <https://www.facebook.com/ComLaude/> <https://www.youtube.com/@comlaude>
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com> _______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
_______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
Hi all As a reminder, Councilors are asked to closely review the draft SSAD Supplemental Recommendations Team Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on Thursday, 16 April so that we can have a fulsome discussion and resolve any remaining questions or concerns during the meeting. Thank you to those of you who have already provided feedback. Council small team assignment forms are typically reviewed by the Council and proceed under non-objection, so if you have an objection or concern with the current text, we ask you to kindly provide alternative text that you can find acceptable before our Council meeting on Thursday, 16 April. To ensure timely progress on the Supplemental SSAD recommendations and in order to take advantage of the in-person time at ICANN 86 meeting, we plan to kick off this work and send out the call for volunteers shortly after the Council meeting. Thank you. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image007.png@01DCCC1F.9E5957A0] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org> Sent: 07 April 2026 18:23 To: Anne ICANN via council <council@icann.org> Subject: [council] SSAD Next Steps and draft Assignment Form Dear Councilors, As noted in the recent message<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> for the SSAD Supplemental Recommendations Team for the Council's review and feedback. Once finalised, this proposed Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al. Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below. Reminder of how we got here The Council began discussing possible next steps for the SSAD recommendations beginning in November<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>. In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee. Specifically, the Council discussed the ramifications of following the RDRS Standing Committee's recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following: * The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; * Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; * The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, * This would provide a procedurally efficient path that recognizes the ICANN Community's desire for this work to be completed in a timely manner. Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently. Remit of the Council under the Bylaws Annex A, Section 9 of the ICANN Bylaws<https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are "not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council." Subsequently, "at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board." The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council. Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC. Can the SSAD Supplemental Recommendations Team create new policy? The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team's draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work. The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with "specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations." In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it "encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot's evidence and the Standing Committee's considerations in [conducting its assignment from the Council.]" In light of the above, the Standing Committee's, ICANN Board's, and the Council's expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC's guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome. Can all GNSO Councilors participate? Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team. What is the expected time commitment? Because the Council has committed<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations "in months, not years," the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises. Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a one-day in-person workshop on Sunday, 7 June before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon. While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible. Other than the time commitment, is there anything else I should know if I would like to participate? Per the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including: * RDRS Standing Committee Final Findings Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; * SSAD Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> * RDRS Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary<https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...> Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents. What is the Council's role at this stage? We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on 16 April so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting. Thank you. Susan Susan Payne GNSO Council Chair Head of Legal Policy [cid:image008.png@01DCCC1F.9E5957A0]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 comlaude.com<http://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0> [cid:image009.png@01DCCC1F.9E5957A0]<https://www.linkedin.com/company/com-laude> [cid:image010.png@01DCCC1F.9E5957A0] <https://twitter.com/comlaude?lang=en> [cid:image011.png@01DCCC1F.9E5957A0] <https://www.facebook.com/ComLaude/> [cid:image012.png@01DCCC1F.9E5957A0] <https://www.youtube.com/@comlaude> [cid:image013.jpg@01DCCC1F.9E5957A0] ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the "Com Laude Group") does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the "Com Laude Group") does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>
Hi Farzaneh, all Thanks for your comments in the Assignment Form document. We have accepted or endeavoured to propose text to address them. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T... In particular: * Regarding the trigger for referring something back to Council, while noting your proposal that if one person has doubts it should be brought back to Council, Leadership feels that that sets the bar too low. The objection of just one person should not halt the work of the group, but your point is taken that a "consensus" may be too high a bar, and alternative language is suggested: The SSAD Supplemental Recommendations Team is expected to refer back to the GNSO Council if there is strong support in the group for the view that a particular proposed outcome may be out of scope of the Assignment, (e.g., developing new policy versus modifications rooted in foundational documents). In doing so, we take into consideration that: * the supplemental team will have many councillors participating, and any councillor may always propose agenda items for council meetings - this is not altered by the Assignment Form; * however, by the same token that many council members will be on the team, if one person's concern is not shared by others even within the supplemental team, then it is unlikely that those same councillors will be instructed to take a different view if the matter is brought to council. Some reasonable level of agreement/support to escalate to therefore is appropriate. * Regarding your query on "Confirmation of how the mechanism can be used to make and respond to requests for gTLD non-public registration data for underlying affiliated privacy/proxy domains", this, and the other 3 elements, are specifically identified in the Board's letter and resolution, and hence referred to as such in the Assignment Form. The Supplemental Recommendations Team should determine whether they are able to do so, or to make a recommendation for an alternative mechanism to address this. An edit to the Assignment Form has been made to address this. I hope that this addresses your concerns, but if not, perhaps you could suggest alternative text to do so. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCCD24.7A61AA90] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org> Sent: 14 April 2026 15:02 To: Anne ICANN via council <council@icann.org> Subject: [council] Reminder: SSAD Next Steps and draft Assignment Form Hi all As a reminder, Councilors are asked to closely review the draft SSAD Supplemental Recommendations Team Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on Thursday, 16 April so that we can have a fulsome discussion and resolve any remaining questions or concerns during the meeting. Thank you to those of you who have already provided feedback. Council small team assignment forms are typically reviewed by the Council and proceed under non-objection, so if you have an objection or concern with the current text, we ask you to kindly provide alternative text that you can find acceptable before our Council meeting on Thursday, 16 April. To ensure timely progress on the Supplemental SSAD recommendations and in order to take advantage of the in-person time at ICANN 86 meeting, we plan to kick off this work and send out the call for volunteers shortly after the Council meeting. Thank you. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCCD24.7A61AA90] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 07 April 2026 18:23 To: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: [council] SSAD Next Steps and draft Assignment Form Dear Councilors, As noted in the recent message<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> for the SSAD Supplemental Recommendations Team for the Council's review and feedback. Once finalised, this proposed Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al. Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below. Reminder of how we got here The Council began discussing possible next steps for the SSAD recommendations beginning in November<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>. In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee. Specifically, the Council discussed the ramifications of following the RDRS Standing Committee's recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following: * The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; * Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; * The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, * This would provide a procedurally efficient path that recognizes the ICANN Community's desire for this work to be completed in a timely manner. Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently. Remit of the Council under the Bylaws Annex A, Section 9 of the ICANN Bylaws<https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are "not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council." Subsequently, "at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board." The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council. Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC. Can the SSAD Supplemental Recommendations Team create new policy? The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team's draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work. The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with "specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations." In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it "encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot's evidence and the Standing Committee's considerations in [conducting its assignment from the Council.]" In light of the above, the Standing Committee's, ICANN Board's, and the Council's expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC's guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome. Can all GNSO Councilors participate? Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team. What is the expected time commitment? Because the Council has committed<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations "in months, not years," the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises. Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a one-day in-person workshop on Sunday, 7 June before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon. While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible. Other than the time commitment, is there anything else I should know if I would like to participate? Per the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including: * RDRS Standing Committee Final Findings Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; * SSAD Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> * RDRS Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary<https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...> Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents. What is the Council's role at this stage? We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on 16 April so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting. Thank you. Susan Susan Payne GNSO Council Chair Head of Legal Policy [cid:image002.png@01DCCD24.7A61AA90]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 comlaude.com<http://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0> [cid:image003.png@01DCCD24.7A61AA90]<https://www.linkedin.com/company/com-laude> [cid:image004.png@01DCCD24.7A61AA90] <https://twitter.com/comlaude?lang=en> [cid:image005.png@01DCCD24.7A61AA90] <https://www.facebook.com/ComLaude/> [cid:image006.png@01DCCD24.7A61AA90] <https://www.youtube.com/@comlaude> [cid:image007.jpg@01DCCD24.7A61AA90] ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the "Com Laude Group") does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the "Com Laude Group") does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the "Com Laude Group") does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>
Thanks Susan. After these changes, I put a few comments in the document but wanted to raise on the list a question regarding this new wording which applies to the Board's expectations listed in Tripti's letter denoting Items 1 through 4: The SSAD Supplemental Recommendations Team is expected to consider whether these four elements can be addressed via Supplemental Recommendation or make a recommendation to Council for how they may be addressed through some other mechanism Is the Council actually in a position to interpret the Bylaws provisions in this regard? Does the Board assume that all four elements are within the scope of Supplemental Recommendations? I think we need to hear from Board reps on this point. Personally, I don't see limitations on the scope of Supplemental Recommendations in the Bylaws language. It looks as though we are trying to carve out an exception on certain elements that might result in a need for a full PDP. Especially given the nature of the urgent requests considerations, I wonder if that is what we really mean? Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Wed, Apr 15, 2026 at 2:32 PM Susan Payne via council <council@icann.org> wrote:
Hi Farzaneh, all
Thanks for your comments in the Assignment Form document. We have accepted or endeavoured to propose text to address them. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...
In particular:
- Regarding the trigger for referring something back to Council, while noting your proposal that if one person has doubts it should be brought back to Council, Leadership feels that that sets the bar too low. The objection of just one person should not halt the work of the group, but your point is taken that a “consensus” may be too high a bar, and alternative language is suggested:
The SSAD Supplemental Recommendations Team is expected to refer back to the GNSO Council if there is strong support in the group for the view that a particular proposed outcome may be out of scope of the Assignment, (e.g., developing new policy versus modifications rooted in foundational documents).
In doing so, we take into consideration that:
· the supplemental team will have many councillors participating, and any councillor may always propose agenda items for council meetings - this is not altered by the Assignment Form;
· however, by the same token that many council members will be on the team, if one person's concern is not shared by others even within the supplemental team, then it is unlikely that those same councillors will be instructed to take a different view if the matter is brought to council. Some reasonable level of agreement/support to escalate to therefore is appropriate.
- Regarding your query on “Confirmation of how the mechanism can be used to make and respond to requests for gTLD non-public registration data for underlying affiliated privacy/proxy domains”, this, and the other 3 elements, are specifically identified in the Board’s letter and resolution, and hence referred to as such in the Assignment Form. The Supplemental Recommendations Team should determine whether they are able to do so, or to make a recommendation for an alternative mechanism to address this. An edit to the Assignment Form has been made to address this.
I hope that this addresses your concerns, but if not, perhaps you could suggest alternative text to do so.
Susan
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>** and** Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Susan Payne via council <council@icann.org> *Sent:* 14 April 2026 15:02 *To:* Anne ICANN via council <council@icann.org> *Subject:* [council] Reminder: SSAD Next Steps and draft Assignment Form
Hi all
As a reminder, Councilors are asked to closely review the draft SSAD Supplemental Recommendations Team Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits *before our Council meeting on Thursday, 16 April* so that we can have a fulsome discussion and resolve any remaining questions or concerns during the meeting. Thank you to those of you who have already provided feedback.
Council small team assignment forms are typically reviewed by the Council and proceed under non-objection, so if you have an objection or concern with the current text, *we ask you to kindly provide alternative text that you can find acceptable before our Council meeting on Thursday, 16 April.*
To ensure timely progress on the Supplemental SSAD recommendations and in order to take advantage of the in-person time at ICANN 86 meeting, we plan to kick off this work and send out the call for volunteers shortly after the Council meeting.
Thank you.
Susan
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>** and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Susan Payne via council <council@icann.org> *Sent:* 07 April 2026 18:23 *To:* Anne ICANN via council <council@icann.org> *Subject:* [council] SSAD Next Steps and draft Assignment Form
Dear Councilors,
As noted in the recent message <https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031TneI/edit?usp=sharing>for the SSAD Supplemental Recommendations Team for the Council’s review and feedback.
Once finalised, this proposed Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al.
Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below.
*Reminder of how we got here*
The Council began discussing possible next steps for the SSAD recommendations beginning in November <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...> .
In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee.
Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following:
- The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; - Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; - The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, - This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner.
Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently.
*Remit of the Council under the Bylaws *
Annex A, Section 9 of the ICANN Bylaws <https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.”
The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council.
Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC.
*Can the SSAD Supplemental Recommendations Team create new policy? *
The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work.
The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.”
In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]”
In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome.
*Can all GNSO Councilors participate? *
Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team.
*What is the expected time commitment? *
Because the Council has committed <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises.
Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a *one-day in-person workshop on* *Sunday, 7 June* before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon.
While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible.
*Other than the time commitment, is there anything else I should know if I would like to participate?*
Per the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including:
- RDRS Standing Committee Final Findings Report <https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; - SSAD Operational Design Assessment <https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - RDRS Policy Alignment Analysis <https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary <https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...>
Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents.
*What is the Council’s role at this stage?*
We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits *before our Council meeting on 16 April* so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting.
Thank you.
Susan
Susan Payne GNSO Council Chair
Head of Legal Policy
28 Little Russell Street, London WC1A 2HN, UK *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*comlaude.com <http://comlaude.com/>*
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0>** and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0>*
<https://www.linkedin.com/company/com-laude> <https://twitter.com/comlaude?lang=en> <https://www.facebook.com/ComLaude/> <https://www.youtube.com/@comlaude>
------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> ------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> ------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
Anne I responded in the Assignment Form, but will repeat here. The Board has asked for these items 1-4 to be considered, and so they are included in the Assignment Form. The role of the Team is to discuss, including with the Board Liaisons, and make a decision on how to affirm or modify the recommendation(s) - thereafter called Supplemental Recommendations. There clearly are some boundaries, therefore, set by the scope of the existing recommendations and the previous work done (eg by the RDRS SC). I don't believe that the Board's reference to these gaps is prescriptive. Council could determine that it could include Supplemental Rec(s) on these topic if it believes it is appropriate and in scope. Alternatively, the Council could determine that one or more of the topics is not in scope, and, if so, suggest another path (like new policy work). There will be Board Liaisons who will participate on the Supplemental Recommendations team, so they can address questions as they arise. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCCDC4.B42CC7F0] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN <anneicanngnso@gmail.com> Sent: 16 April 2026 00:57 To: Susan Payne <susan.payne@comlaude.com> Cc: Anne ICANN via council <council@icann.org> Subject: Re: [council] Re: SSAD Next Steps and draft Assignment Form Thanks Susan. After these changes, I put a few comments in the document but wanted to raise on the list a question regarding this new wording which applies to the Board's expectations listed in Tripti's letter denoting Items 1 through 4: The SSAD Supplemental Recommendations Team is expected to consider whether these four elements can be addressed via Supplemental Recommendation or make a recommendation to Council for how they may be addressed through some other mechanism Is the Council actually in a position to interpret the Bylaws provisions in this regard? Does the Board assume that all four elements are within the scope of Supplemental Recommendations? I think we need to hear from Board reps on this point. Personally, I don't see limitations on the scope of Supplemental Recommendations in the Bylaws language. It looks as though we are trying to carve out an exception on certain elements that might result in a need for a full PDP. Especially given the nature of the urgent requests considerations, I wonder if that is what we really mean? Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Wed, Apr 15, 2026 at 2:32 PM Susan Payne via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Farzaneh, all Thanks for your comments in the Assignment Form document. We have accepted or endeavoured to propose text to address them. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T... In particular: * Regarding the trigger for referring something back to Council, while noting your proposal that if one person has doubts it should be brought back to Council, Leadership feels that that sets the bar too low. The objection of just one person should not halt the work of the group, but your point is taken that a “consensus” may be too high a bar, and alternative language is suggested: The SSAD Supplemental Recommendations Team is expected to refer back to the GNSO Council if there is strong support in the group for the view that a particular proposed outcome may be out of scope of the Assignment, (e.g., developing new policy versus modifications rooted in foundational documents). In doing so, we take into consideration that: • the supplemental team will have many councillors participating, and any councillor may always propose agenda items for council meetings - this is not altered by the Assignment Form; • however, by the same token that many council members will be on the team, if one person's concern is not shared by others even within the supplemental team, then it is unlikely that those same councillors will be instructed to take a different view if the matter is brought to council. Some reasonable level of agreement/support to escalate to therefore is appropriate. * Regarding your query on “Confirmation of how the mechanism can be used to make and respond to requests for gTLD non-public registration data for underlying affiliated privacy/proxy domains”, this, and the other 3 elements, are specifically identified in the Board’s letter and resolution, and hence referred to as such in the Assignment Form. The Supplemental Recommendations Team should determine whether they are able to do so, or to make a recommendation for an alternative mechanism to address this. An edit to the Assignment Form has been made to address this. I hope that this addresses your concerns, but if not, perhaps you could suggest alternative text to do so. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCCDC4.B42CC7F0] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 14 April 2026 15:02 To: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: [council] Reminder: SSAD Next Steps and draft Assignment Form Hi all As a reminder, Councilors are asked to closely review the draft SSAD Supplemental Recommendations Team Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on Thursday, 16 April so that we can have a fulsome discussion and resolve any remaining questions or concerns during the meeting. Thank you to those of you who have already provided feedback. Council small team assignment forms are typically reviewed by the Council and proceed under non-objection, so if you have an objection or concern with the current text, we ask you to kindly provide alternative text that you can find acceptable before our Council meeting on Thursday, 16 April. To ensure timely progress on the Supplemental SSAD recommendations and in order to take advantage of the in-person time at ICANN 86 meeting, we plan to kick off this work and send out the call for volunteers shortly after the Council meeting. Thank you. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCCDC4.B42CC7F0] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 07 April 2026 18:23 To: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: [council] SSAD Next Steps and draft Assignment Form Dear Councilors, As noted in the recent message<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> for the SSAD Supplemental Recommendations Team for the Council’s review and feedback. Once finalised, this proposed Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al. Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below. Reminder of how we got here The Council began discussing possible next steps for the SSAD recommendations beginning in November<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>. In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee. Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following: * The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; * Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; * The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, * This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner. Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently. Remit of the Council under the Bylaws Annex A, Section 9 of the ICANN Bylaws<https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.” The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council. Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC. Can the SSAD Supplemental Recommendations Team create new policy? The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work. The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.” In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]” In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome. Can all GNSO Councilors participate? Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team. What is the expected time commitment? Because the Council has committed<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises. Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a one-day in-person workshop on Sunday, 7 June before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon. While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible. Other than the time commitment, is there anything else I should know if I would like to participate? Per the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including: * RDRS Standing Committee Final Findings Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; * SSAD Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> * RDRS Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary<https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...> Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents. What is the Council’s role at this stage? We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on 16 April so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting. Thank you. Susan Susan Payne GNSO Council Chair Head of Legal Policy [cid:image002.png@01DCCDC4.B42CC7F0]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 comlaude.com<http://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0> [cid:image003.png@01DCCDC4.B42CC7F0]<https://www.linkedin.com/company/com-laude> [cid:image004.png@01DCCDC4.B42CC7F0] <https://twitter.com/comlaude?lang=en> [cid:image005.png@01DCCDC4.B42CC7F0] <https://www.facebook.com/ComLaude/> [cid:image006.png@01DCCDC4.B42CC7F0] <https://www.youtube.com/@comlaude> [cid:image007.jpg@01DCCDC4.B42CC7F0] ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto:council-leave@icann.org> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>
Thanks Susan. I read the Board's letter as making a stronger ask than the request that the elements "be considered". The Board's letter states as follows: The Board expects the following four elements, as outlined in the RDRS Policy Alignment Analysis and GNSO Standing Committee’s recommendations, to be incorporated into the planned Supplemental Recommendations to produce a long-term solution for requesting access to gTLD nonpublic registration data. So the Board is stating it "expects" these four elements to be incorporated into the planned Supplemental Recommendations. This is why I think we must consult with Board reps before finalizing the assignment form. I'm not at all certain that we are on the same page. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Thu, Apr 16, 2026 at 9:16 AM Susan Payne <susan.payne@comlaude.com> wrote:
Anne
I responded in the Assignment Form, but will repeat here. The Board has asked for these items 1-4 to be considered, and so they are included in the Assignment Form. The role of the Team is to discuss, including with the Board Liaisons, and make a decision on how to affirm or modify the recommendation(s) - thereafter called Supplemental Recommendations. There clearly are some boundaries, therefore, set by the scope of the existing recommendations and the previous work done (eg by the RDRS SC). I don't believe that the Board's reference to these gaps is prescriptive. Council could determine that it could include Supplemental Rec(s) on these topic if it believes it is appropriate and in scope. Alternatively, the Council could determine that one or more of the topics is not in scope, and, if so, suggest another path (like new policy work).
There will be Board Liaisons who will participate on the Supplemental Recommendations team, so they can address questions as they arise.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>** and** Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Anne ICANN <anneicanngnso@gmail.com> *Sent:* 16 April 2026 00:57 *To:* Susan Payne <susan.payne@comlaude.com> *Cc:* Anne ICANN via council <council@icann.org> *Subject:* Re: [council] Re: SSAD Next Steps and draft Assignment Form
Thanks Susan. After these changes, I put a few comments in the document but wanted to raise on the list a question regarding this new wording which applies to the Board's expectations listed in Tripti's letter denoting Items 1 through 4:
The SSAD Supplemental Recommendations Team is expected to consider whether these four elements can be addressed via Supplemental Recommendation or make a recommendation to Council for how they may be addressed through some other mechanism
Is the Council actually in a position to interpret the Bylaws provisions in this regard? Does the Board assume that all four elements are within the scope of Supplemental Recommendations? I think we need to hear from Board reps on this point. Personally, I don't see limitations on the scope of Supplemental Recommendations in the Bylaws language. It looks as though we are trying to carve out an exception on certain elements that might result in a need for a full PDP. Especially given the nature of the urgent requests considerations, I wonder if that is what we really mean?
Thank you,
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026
anneicanngnso@gmail.com
On Wed, Apr 15, 2026 at 2:32 PM Susan Payne via council <council@icann.org> wrote:
Hi Farzaneh, all
Thanks for your comments in the Assignment Form document. We have accepted or endeavoured to propose text to address them. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...
In particular:
- Regarding the trigger for referring something back to Council, while noting your proposal that if one person has doubts it should be brought back to Council, Leadership feels that that sets the bar too low. The objection of just one person should not halt the work of the group, but your point is taken that a “consensus” may be too high a bar, and alternative language is suggested:
The SSAD Supplemental Recommendations Team is expected to refer back to the GNSO Council if there is strong support in the group for the view that a particular proposed outcome may be out of scope of the Assignment, (e.g., developing new policy versus modifications rooted in foundational documents).
In doing so, we take into consideration that:
· the supplemental team will have many councillors participating, and any councillor may always propose agenda items for council meetings - this is not altered by the Assignment Form;
· however, by the same token that many council members will be on the team, if one person's concern is not shared by others even within the supplemental team, then it is unlikely that those same councillors will be instructed to take a different view if the matter is brought to council. Some reasonable level of agreement/support to escalate to therefore is appropriate.
- Regarding your query on “Confirmation of how the mechanism can be used to make and respond to requests for gTLD non-public registration data for underlying affiliated privacy/proxy domains”, this, and the other 3 elements, are specifically identified in the Board’s letter and resolution, and hence referred to as such in the Assignment Form. The Supplemental Recommendations Team should determine whether they are able to do so, or to make a recommendation for an alternative mechanism to address this. An edit to the Assignment Form has been made to address this.
I hope that this addresses your concerns, but if not, perhaps you could suggest alternative text to do so.
Susan
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Susan Payne via council <council@icann.org> *Sent:* 14 April 2026 15:02 *To:* Anne ICANN via council <council@icann.org> *Subject:* [council] Reminder: SSAD Next Steps and draft Assignment Form
Hi all
As a reminder, Councilors are asked to closely review the draft SSAD Supplemental Recommendations Team Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits *before our Council meeting on Thursday, 16 April* so that we can have a fulsome discussion and resolve any remaining questions or concerns during the meeting. Thank you to those of you who have already provided feedback.
Council small team assignment forms are typically reviewed by the Council and proceed under non-objection, so if you have an objection or concern with the current text, *we ask you to kindly provide alternative text that you can find acceptable before our Council meeting on Thursday, 16 April.*
To ensure timely progress on the Supplemental SSAD recommendations and in order to take advantage of the in-person time at ICANN 86 meeting, we plan to kick off this work and send out the call for volunteers shortly after the Council meeting.
Thank you.
Susan
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Susan Payne via council <council@icann.org> *Sent:* 07 April 2026 18:23 *To:* Anne ICANN via council <council@icann.org> *Subject:* [council] SSAD Next Steps and draft Assignment Form
Dear Councilors,
As noted in the recent message <https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031TneI/edit?usp=sharing>for the SSAD Supplemental Recommendations Team for the Council’s review and feedback.
Once finalised, this proposed Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al.
Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below.
*Reminder of how we got here*
The Council began discussing possible next steps for the SSAD recommendations beginning in November <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...> .
In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee.
Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following:
- The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; - Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; - The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, - This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner.
Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently.
*Remit of the Council under the Bylaws *
Annex A, Section 9 of the ICANN Bylaws <https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.”
The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council.
Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC.
*Can the SSAD Supplemental Recommendations Team create new policy? *
The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work.
The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.”
In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]”
In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome.
*Can all GNSO Councilors participate? *
Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team.
*What is the expected time commitment? *
Because the Council has committed <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises.
Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a *one-day in-person workshop on* *Sunday, 7 June* before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon.
While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible.
*Other than the time commitment, is there anything else I should know if I would like to participate?*
Per the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including:
- RDRS Standing Committee Final Findings Report <https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; - SSAD Operational Design Assessment <https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - RDRS Policy Alignment Analysis <https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary <https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...>
Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents.
*What is the Council’s role at this stage?*
We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits *before our Council meeting on 16 April* so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting.
Thank you.
Susan
Susan Payne GNSO Council Chair
Head of Legal Policy
28 Little Russell Street, London WC1A 2HN, UK *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*comlaude.com <http://comlaude.com/>*
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0>*
<https://www.linkedin.com/company/com-laude> <https://twitter.com/comlaude?lang=en> <https://www.facebook.com/ComLaude/> <https://www.youtube.com/@comlaude>
------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> ------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> ------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/>
_______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/>
Anne, we will be joined on our call later by the Board liaisons, so may be able to seek clarity on the Board’s intent. But in any event, it should be possible to clarify before the Team begins meeting. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCCDD3.1955F710] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN <anneicanngnso@gmail.com> Sent: 16 April 2026 17:45 To: Susan Payne <susan.payne@comlaude.com> Cc: Anne ICANN via council <council@icann.org>; greg.dibiase@board.icann.org Subject: Re: [council] Re: SSAD Next Steps and draft Assignment Form Thanks Susan. I read the Board's letter as making a stronger ask than the request that the elements "be considered". The Board's letter states as follows: The Board expects the following four elements, as outlined in the RDRS Policy Alignment Analysis and GNSO Standing Committee’s recommendations, to be incorporated into the planned Supplemental Recommendations to produce a long-term solution for requesting access to gTLD nonpublic registration data. So the Board is stating it "expects" these four elements to be incorporated into the planned Supplemental Recommendations. This is why I think we must consult with Board reps before finalizing the assignment form. I'm not at all certain that we are on the same page. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Thu, Apr 16, 2026 at 9:16 AM Susan Payne <susan.payne@comlaude.com<mailto:susan.payne@comlaude.com>> wrote: Anne I responded in the Assignment Form, but will repeat here. The Board has asked for these items 1-4 to be considered, and so they are included in the Assignment Form. The role of the Team is to discuss, including with the Board Liaisons, and make a decision on how to affirm or modify the recommendation(s) - thereafter called Supplemental Recommendations. There clearly are some boundaries, therefore, set by the scope of the existing recommendations and the previous work done (eg by the RDRS SC). I don't believe that the Board's reference to these gaps is prescriptive. Council could determine that it could include Supplemental Rec(s) on these topic if it believes it is appropriate and in scope. Alternatively, the Council could determine that one or more of the topics is not in scope, and, if so, suggest another path (like new policy work). There will be Board Liaisons who will participate on the Supplemental Recommendations team, so they can address questions as they arise. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCCDD3.1955F710] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Sent: 16 April 2026 00:57 To: Susan Payne <susan.payne@comlaude.com<mailto:susan.payne@comlaude.com>> Cc: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: Re: [council] Re: SSAD Next Steps and draft Assignment Form Thanks Susan. After these changes, I put a few comments in the document but wanted to raise on the list a question regarding this new wording which applies to the Board's expectations listed in Tripti's letter denoting Items 1 through 4: The SSAD Supplemental Recommendations Team is expected to consider whether these four elements can be addressed via Supplemental Recommendation or make a recommendation to Council for how they may be addressed through some other mechanism Is the Council actually in a position to interpret the Bylaws provisions in this regard? Does the Board assume that all four elements are within the scope of Supplemental Recommendations? I think we need to hear from Board reps on this point. Personally, I don't see limitations on the scope of Supplemental Recommendations in the Bylaws language. It looks as though we are trying to carve out an exception on certain elements that might result in a need for a full PDP. Especially given the nature of the urgent requests considerations, I wonder if that is what we really mean? Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Wed, Apr 15, 2026 at 2:32 PM Susan Payne via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Farzaneh, all Thanks for your comments in the Assignment Form document. We have accepted or endeavoured to propose text to address them. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T... In particular: * Regarding the trigger for referring something back to Council, while noting your proposal that if one person has doubts it should be brought back to Council, Leadership feels that that sets the bar too low. The objection of just one person should not halt the work of the group, but your point is taken that a “consensus” may be too high a bar, and alternative language is suggested: The SSAD Supplemental Recommendations Team is expected to refer back to the GNSO Council if there is strong support in the group for the view that a particular proposed outcome may be out of scope of the Assignment, (e.g., developing new policy versus modifications rooted in foundational documents). In doing so, we take into consideration that: • the supplemental team will have many councillors participating, and any councillor may always propose agenda items for council meetings - this is not altered by the Assignment Form; • however, by the same token that many council members will be on the team, if one person's concern is not shared by others even within the supplemental team, then it is unlikely that those same councillors will be instructed to take a different view if the matter is brought to council. Some reasonable level of agreement/support to escalate to therefore is appropriate. * Regarding your query on “Confirmation of how the mechanism can be used to make and respond to requests for gTLD non-public registration data for underlying affiliated privacy/proxy domains”, this, and the other 3 elements, are specifically identified in the Board’s letter and resolution, and hence referred to as such in the Assignment Form. The Supplemental Recommendations Team should determine whether they are able to do so, or to make a recommendation for an alternative mechanism to address this. An edit to the Assignment Form has been made to address this. I hope that this addresses your concerns, but if not, perhaps you could suggest alternative text to do so. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCCDD3.1955F710] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 14 April 2026 15:02 To: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: [council] Reminder: SSAD Next Steps and draft Assignment Form Hi all As a reminder, Councilors are asked to closely review the draft SSAD Supplemental Recommendations Team Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on Thursday, 16 April so that we can have a fulsome discussion and resolve any remaining questions or concerns during the meeting. Thank you to those of you who have already provided feedback. Council small team assignment forms are typically reviewed by the Council and proceed under non-objection, so if you have an objection or concern with the current text, we ask you to kindly provide alternative text that you can find acceptable before our Council meeting on Thursday, 16 April. To ensure timely progress on the Supplemental SSAD recommendations and in order to take advantage of the in-person time at ICANN 86 meeting, we plan to kick off this work and send out the call for volunteers shortly after the Council meeting. Thank you. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCCDD3.1955F710] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 07 April 2026 18:23 To: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: [council] SSAD Next Steps and draft Assignment Form Dear Councilors, As noted in the recent message<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> for the SSAD Supplemental Recommendations Team for the Council’s review and feedback. Once finalised, this proposed Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al. Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below. Reminder of how we got here The Council began discussing possible next steps for the SSAD recommendations beginning in November<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>. In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee. Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following: * The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; * Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; * The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, * This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner. Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently. Remit of the Council under the Bylaws Annex A, Section 9 of the ICANN Bylaws<https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.” The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council. Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC. Can the SSAD Supplemental Recommendations Team create new policy? The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work. The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.” In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]” In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome. Can all GNSO Councilors participate? Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team. What is the expected time commitment? Because the Council has committed<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises. Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a one-day in-person workshop on Sunday, 7 June before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon. While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible. Other than the time commitment, is there anything else I should know if I would like to participate? Per the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including: * RDRS Standing Committee Final Findings Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; * SSAD Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> * RDRS Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary<https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...> Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents. What is the Council’s role at this stage? We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on 16 April so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting. Thank you. Susan Susan Payne GNSO Council Chair Head of Legal Policy [cid:image002.png@01DCCDD3.1955F710]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 comlaude.com<http://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0> [cid:image003.png@01DCCDD3.1955F710]<https://www.linkedin.com/company/com-laude> [cid:image004.png@01DCCDD3.1955F710] <https://twitter.com/comlaude?lang=en> [cid:image005.png@01DCCDD3.1955F710] <https://www.facebook.com/ComLaude/> [cid:image006.png@01DCCDD3.1955F710] <https://www.youtube.com/@comlaude> [cid:image007.jpg@01DCCDD3.1955F710] ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto:council-leave@icann.org> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>
All Leadership has made some adjustments to the draft SSAD Supplemental Recommendations Team Assignment Form to account for the discussion during last Thursday’s Council meeting. We believe that this updated version addresses the feedback received, and Councillors are kindly requested to review and provide any final proposed edits by Friday, 24 April. For convenience, here is the link again. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T... Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD270.93651E40] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org> Sent: 16 April 2026 18:59 To: Anne ICANN <anneicanngnso@gmail.com> Cc: Anne ICANN via council <council@icann.org>; greg.dibiase@board.icann.org Subject: [council] Re: SSAD Next Steps and draft Assignment Form Anne, we will be joined on our call later by the Board liaisons, so may be able to seek clarity on the Board’s intent. But in any event, it should be possible to clarify before the Team begins meeting. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD270.93651E40] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Sent: 16 April 2026 17:45 To: Susan Payne <susan.payne@comlaude.com<mailto:susan.payne@comlaude.com>> Cc: Anne ICANN via council <council@icann.org<mailto:council@icann.org>>; greg.dibiase@board.icann.org<mailto:greg.dibiase@board.icann.org> Subject: Re: [council] Re: SSAD Next Steps and draft Assignment Form Thanks Susan. I read the Board's letter as making a stronger ask than the request that the elements "be considered". The Board's letter states as follows: The Board expects the following four elements, as outlined in the RDRS Policy Alignment Analysis and GNSO Standing Committee’s recommendations, to be incorporated into the planned Supplemental Recommendations to produce a long-term solution for requesting access to gTLD nonpublic registration data. So the Board is stating it "expects" these four elements to be incorporated into the planned Supplemental Recommendations. This is why I think we must consult with Board reps before finalizing the assignment form. I'm not at all certain that we are on the same page. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Thu, Apr 16, 2026 at 9:16 AM Susan Payne <susan.payne@comlaude.com<mailto:susan.payne@comlaude.com>> wrote: Anne I responded in the Assignment Form, but will repeat here. The Board has asked for these items 1-4 to be considered, and so they are included in the Assignment Form. The role of the Team is to discuss, including with the Board Liaisons, and make a decision on how to affirm or modify the recommendation(s) - thereafter called Supplemental Recommendations. There clearly are some boundaries, therefore, set by the scope of the existing recommendations and the previous work done (eg by the RDRS SC). I don't believe that the Board's reference to these gaps is prescriptive. Council could determine that it could include Supplemental Rec(s) on these topic if it believes it is appropriate and in scope. Alternatively, the Council could determine that one or more of the topics is not in scope, and, if so, suggest another path (like new policy work). There will be Board Liaisons who will participate on the Supplemental Recommendations team, so they can address questions as they arise. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD270.93651E40] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Sent: 16 April 2026 00:57 To: Susan Payne <susan.payne@comlaude.com<mailto:susan.payne@comlaude.com>> Cc: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: Re: [council] Re: SSAD Next Steps and draft Assignment Form Thanks Susan. After these changes, I put a few comments in the document but wanted to raise on the list a question regarding this new wording which applies to the Board's expectations listed in Tripti's letter denoting Items 1 through 4: The SSAD Supplemental Recommendations Team is expected to consider whether these four elements can be addressed via Supplemental Recommendation or make a recommendation to Council for how they may be addressed through some other mechanism Is the Council actually in a position to interpret the Bylaws provisions in this regard? Does the Board assume that all four elements are within the scope of Supplemental Recommendations? I think we need to hear from Board reps on this point. Personally, I don't see limitations on the scope of Supplemental Recommendations in the Bylaws language. It looks as though we are trying to carve out an exception on certain elements that might result in a need for a full PDP. Especially given the nature of the urgent requests considerations, I wonder if that is what we really mean? Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Wed, Apr 15, 2026 at 2:32 PM Susan Payne via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Farzaneh, all Thanks for your comments in the Assignment Form document. We have accepted or endeavoured to propose text to address them. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T... In particular: * Regarding the trigger for referring something back to Council, while noting your proposal that if one person has doubts it should be brought back to Council, Leadership feels that that sets the bar too low. The objection of just one person should not halt the work of the group, but your point is taken that a “consensus” may be too high a bar, and alternative language is suggested: The SSAD Supplemental Recommendations Team is expected to refer back to the GNSO Council if there is strong support in the group for the view that a particular proposed outcome may be out of scope of the Assignment, (e.g., developing new policy versus modifications rooted in foundational documents). In doing so, we take into consideration that: • the supplemental team will have many councillors participating, and any councillor may always propose agenda items for council meetings - this is not altered by the Assignment Form; • however, by the same token that many council members will be on the team, if one person's concern is not shared by others even within the supplemental team, then it is unlikely that those same councillors will be instructed to take a different view if the matter is brought to council. Some reasonable level of agreement/support to escalate to therefore is appropriate. * Regarding your query on “Confirmation of how the mechanism can be used to make and respond to requests for gTLD non-public registration data for underlying affiliated privacy/proxy domains”, this, and the other 3 elements, are specifically identified in the Board’s letter and resolution, and hence referred to as such in the Assignment Form. The Supplemental Recommendations Team should determine whether they are able to do so, or to make a recommendation for an alternative mechanism to address this. An edit to the Assignment Form has been made to address this. I hope that this addresses your concerns, but if not, perhaps you could suggest alternative text to do so. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD270.93651E40] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 14 April 2026 15:02 To: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: [council] Reminder: SSAD Next Steps and draft Assignment Form Hi all As a reminder, Councilors are asked to closely review the draft SSAD Supplemental Recommendations Team Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on Thursday, 16 April so that we can have a fulsome discussion and resolve any remaining questions or concerns during the meeting. Thank you to those of you who have already provided feedback. Council small team assignment forms are typically reviewed by the Council and proceed under non-objection, so if you have an objection or concern with the current text, we ask you to kindly provide alternative text that you can find acceptable before our Council meeting on Thursday, 16 April. To ensure timely progress on the Supplemental SSAD recommendations and in order to take advantage of the in-person time at ICANN 86 meeting, we plan to kick off this work and send out the call for volunteers shortly after the Council meeting. Thank you. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD270.93651E40] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 07 April 2026 18:23 To: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: [council] SSAD Next Steps and draft Assignment Form Dear Councilors, As noted in the recent message<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> for the SSAD Supplemental Recommendations Team for the Council’s review and feedback. Once finalised, this proposed Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al. Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below. Reminder of how we got here The Council began discussing possible next steps for the SSAD recommendations beginning in November<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>. In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee. Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following: * The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; * Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; * The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, * This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner. Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently. Remit of the Council under the Bylaws Annex A, Section 9 of the ICANN Bylaws<https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.” The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council. Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC. Can the SSAD Supplemental Recommendations Team create new policy? The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work. The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.” In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]” In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome. Can all GNSO Councilors participate? Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team. What is the expected time commitment? Because the Council has committed<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises. Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a one-day in-person workshop on Sunday, 7 June before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon. While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible. Other than the time commitment, is there anything else I should know if I would like to participate? Per the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including: * RDRS Standing Committee Final Findings Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; * SSAD Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> * RDRS Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary<https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...> Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents. What is the Council’s role at this stage? We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on 16 April so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting. Thank you. Susan Susan Payne GNSO Council Chair Head of Legal Policy [cid:image002.png@01DCD270.93651E40]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 comlaude.com<http://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0> [cid:image003.png@01DCD270.93651E40]<https://www.linkedin.com/company/com-laude> [cid:image004.png@01DCD270.93651E40] <https://twitter.com/comlaude?lang=en> [cid:image005.png@01DCD270.93651E40] <https://www.facebook.com/ComLaude/> [cid:image006.png@01DCD270.93651E40] <https://www.youtube.com/@comlaude> [cid:image007.jpg@01DCD270.93651E40] ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto:council-leave@icann.org> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>
All The deadline for final comments/suggested edits on the draft SSAD Assignment Form was Friday 24th. With there being no further updates, the Assignment Form has now been cleaned-up and this version will be sent to SSAD Supplemental Recommendations Team shortly. Thank you to everyone for your comments and collaboration. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T... Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD72A.DCD8DB70] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org> Sent: 22 April 2026 16:01 To: Anne ICANN via council <council@icann.org> Subject: [council] SSAD updated draft Assignment Form All Leadership has made some adjustments to the draft SSAD Supplemental Recommendations Team Assignment Form to account for the discussion during last Thursday’s Council meeting. We believe that this updated version addresses the feedback received, and Councillors are kindly requested to review and provide any final proposed edits by Friday, 24 April. For convenience, here is the link again. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T... Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD72A.DCD8DB70] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 16 April 2026 18:59 To: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Cc: Anne ICANN via council <council@icann.org<mailto:council@icann.org>>; greg.dibiase@board.icann.org<mailto:greg.dibiase@board.icann.org> Subject: [council] Re: SSAD Next Steps and draft Assignment Form Anne, we will be joined on our call later by the Board liaisons, so may be able to seek clarity on the Board’s intent. But in any event, it should be possible to clarify before the Team begins meeting. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD72A.DCD8DB70] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Sent: 16 April 2026 17:45 To: Susan Payne <susan.payne@comlaude.com<mailto:susan.payne@comlaude.com>> Cc: Anne ICANN via council <council@icann.org<mailto:council@icann.org>>; greg.dibiase@board.icann.org<mailto:greg.dibiase@board.icann.org> Subject: Re: [council] Re: SSAD Next Steps and draft Assignment Form Thanks Susan. I read the Board's letter as making a stronger ask than the request that the elements "be considered". The Board's letter states as follows: The Board expects the following four elements, as outlined in the RDRS Policy Alignment Analysis and GNSO Standing Committee’s recommendations, to be incorporated into the planned Supplemental Recommendations to produce a long-term solution for requesting access to gTLD nonpublic registration data. So the Board is stating it "expects" these four elements to be incorporated into the planned Supplemental Recommendations. This is why I think we must consult with Board reps before finalizing the assignment form. I'm not at all certain that we are on the same page. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Thu, Apr 16, 2026 at 9:16 AM Susan Payne <susan.payne@comlaude.com<mailto:susan.payne@comlaude.com>> wrote: Anne I responded in the Assignment Form, but will repeat here. The Board has asked for these items 1-4 to be considered, and so they are included in the Assignment Form. The role of the Team is to discuss, including with the Board Liaisons, and make a decision on how to affirm or modify the recommendation(s) - thereafter called Supplemental Recommendations. There clearly are some boundaries, therefore, set by the scope of the existing recommendations and the previous work done (eg by the RDRS SC). I don't believe that the Board's reference to these gaps is prescriptive. Council could determine that it could include Supplemental Rec(s) on these topic if it believes it is appropriate and in scope. Alternatively, the Council could determine that one or more of the topics is not in scope, and, if so, suggest another path (like new policy work). There will be Board Liaisons who will participate on the Supplemental Recommendations team, so they can address questions as they arise. Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD72A.DCD8DB70] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Sent: 16 April 2026 00:57 To: Susan Payne <susan.payne@comlaude.com<mailto:susan.payne@comlaude.com>> Cc: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: Re: [council] Re: SSAD Next Steps and draft Assignment Form Thanks Susan. After these changes, I put a few comments in the document but wanted to raise on the list a question regarding this new wording which applies to the Board's expectations listed in Tripti's letter denoting Items 1 through 4: The SSAD Supplemental Recommendations Team is expected to consider whether these four elements can be addressed via Supplemental Recommendation or make a recommendation to Council for how they may be addressed through some other mechanism Is the Council actually in a position to interpret the Bylaws provisions in this regard? Does the Board assume that all four elements are within the scope of Supplemental Recommendations? I think we need to hear from Board reps on this point. Personally, I don't see limitations on the scope of Supplemental Recommendations in the Bylaws language. It looks as though we are trying to carve out an exception on certain elements that might result in a need for a full PDP. Especially given the nature of the urgent requests considerations, I wonder if that is what we really mean? Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Wed, Apr 15, 2026 at 2:32 PM Susan Payne via council <council@icann.org<mailto:council@icann.org>> wrote: Hi Farzaneh, all Thanks for your comments in the Assignment Form document. We have accepted or endeavoured to propose text to address them. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T... In particular: * Regarding the trigger for referring something back to Council, while noting your proposal that if one person has doubts it should be brought back to Council, Leadership feels that that sets the bar too low. The objection of just one person should not halt the work of the group, but your point is taken that a “consensus” may be too high a bar, and alternative language is suggested: The SSAD Supplemental Recommendations Team is expected to refer back to the GNSO Council if there is strong support in the group for the view that a particular proposed outcome may be out of scope of the Assignment, (e.g., developing new policy versus modifications rooted in foundational documents). In doing so, we take into consideration that: • the supplemental team will have many councillors participating, and any councillor may always propose agenda items for council meetings - this is not altered by the Assignment Form; • however, by the same token that many council members will be on the team, if one person's concern is not shared by others even within the supplemental team, then it is unlikely that those same councillors will be instructed to take a different view if the matter is brought to council. Some reasonable level of agreement/support to escalate to therefore is appropriate. * Regarding your query on “Confirmation of how the mechanism can be used to make and respond to requests for gTLD non-public registration data for underlying affiliated privacy/proxy domains”, this, and the other 3 elements, are specifically identified in the Board’s letter and resolution, and hence referred to as such in the Assignment Form. The Supplemental Recommendations Team should determine whether they are able to do so, or to make a recommendation for an alternative mechanism to address this. An edit to the Assignment Form has been made to address this. I hope that this addresses your concerns, but if not, perhaps you could suggest alternative text to do so. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD72A.DCD8DB70] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 14 April 2026 15:02 To: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: [council] Reminder: SSAD Next Steps and draft Assignment Form Hi all As a reminder, Councilors are asked to closely review the draft SSAD Supplemental Recommendations Team Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on Thursday, 16 April so that we can have a fulsome discussion and resolve any remaining questions or concerns during the meeting. Thank you to those of you who have already provided feedback. Council small team assignment forms are typically reviewed by the Council and proceed under non-objection, so if you have an objection or concern with the current text, we ask you to kindly provide alternative text that you can find acceptable before our Council meeting on Thursday, 16 April. To ensure timely progress on the Supplemental SSAD recommendations and in order to take advantage of the in-person time at ICANN 86 meeting, we plan to kick off this work and send out the call for volunteers shortly after the Council meeting. Thank you. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 [cid:image001.png@01DCD72A.DCD8DB70] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0> From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Sent: 07 April 2026 18:23 To: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Subject: [council] SSAD Next Steps and draft Assignment Form Dear Councilors, As noted in the recent message<https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> for the SSAD Supplemental Recommendations Team for the Council’s review and feedback. Once finalised, this proposed Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al. Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below. Reminder of how we got here The Council began discussing possible next steps for the SSAD recommendations beginning in November<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>. In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee. Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following: * The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; * Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; * The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, * This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner. Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently. Remit of the Council under the Bylaws Annex A, Section 9 of the ICANN Bylaws<https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.” The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council. Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC. Can the SSAD Supplemental Recommendations Team create new policy? The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work. The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.” In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]” In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome. Can all GNSO Councilors participate? Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team. What is the expected time commitment? Because the Council has committed<https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises. Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a one-day in-person workshop on Sunday, 7 June before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon. While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible. Other than the time commitment, is there anything else I should know if I would like to participate? Per the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including: * RDRS Standing Committee Final Findings Report<https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; * SSAD Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> * RDRS Policy Alignment Analysis<https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary<https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...> Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents. What is the Council’s role at this stage? We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits before our Council meeting on 16 April so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form<https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting. Thank you. Susan Susan Payne GNSO Council Chair Head of Legal Policy [cid:image002.png@01DCD72A.DCD8DB70]<https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 D +44 (0) 20 74218 255 comlaude.com<http://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube<https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0> [cid:image003.png@01DCD72A.DCD8DB70]<https://www.linkedin.com/company/com-laude> [cid:image004.png@01DCD72A.DCD8DB70] <https://twitter.com/comlaude?lang=en> [cid:image005.png@01DCD72A.DCD8DB70] <https://www.facebook.com/ComLaude/> [cid:image006.png@01DCD72A.DCD8DB70] <https://www.youtube.com/@comlaude> [cid:image007.jpg@01DCD72A.DCD8DB70] ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto:council-leave@icann.org> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/> ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com/>
I just wanted to note that if we want the team to consider all the 18 recommendations and consider coming up with an authentication for law enforcement policy process then they need more time. So depending on the outcome of deliberations, we might need more time or extend it. I think it’s good to be clear that there can be multiple phases of this team focusing on different issues. Farzaneh On Tue, Apr 28, 2026 at 11:21 AM Susan Payne via council <council@icann.org> wrote:
All
The deadline for final comments/suggested edits on the draft SSAD Assignment Form was Friday 24th. With there being no further updates, the Assignment Form has now been cleaned-up and this version will be sent to SSAD Supplemental Recommendations Team shortly. Thank you to everyone for your comments and collaboration.
https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on **LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0>** and** Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Susan Payne via council <council@icann.org> *Sent:* 22 April 2026 16:01 *To:* Anne ICANN via council <council@icann.org> *Subject:* [council] SSAD updated draft Assignment Form
All
Leadership has made some adjustments to the draft SSAD Supplemental Recommendations Team Assignment Form to account for the discussion during last Thursday’s Council meeting. We believe that this updated version addresses the feedback received, and Councillors are kindly requested to review and provide any final proposed edits by Friday, 24 April. For convenience, here is the link again.
https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Susan Payne via council <council@icann.org> *Sent:* 16 April 2026 18:59 *To:* Anne ICANN <anneicanngnso@gmail.com> *Cc:* Anne ICANN via council <council@icann.org>; greg.dibiase@board.icann.org *Subject:* [council] Re: SSAD Next Steps and draft Assignment Form
Anne, we will be joined on our call later by the Board liaisons, so may be able to seek clarity on the Board’s intent. But in any event, it should be possible to clarify before the Team begins meeting.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Anne ICANN <anneicanngnso@gmail.com> *Sent:* 16 April 2026 17:45 *To:* Susan Payne <susan.payne@comlaude.com> *Cc:* Anne ICANN via council <council@icann.org>; greg.dibiase@board.icann.org *Subject:* Re: [council] Re: SSAD Next Steps and draft Assignment Form
Thanks Susan. I read the Board's letter as making a stronger ask than the request that the elements "be considered". The Board's letter states as follows:
The Board expects the following four elements, as outlined in the RDRS Policy Alignment Analysis and GNSO Standing Committee’s recommendations, to be incorporated into the planned Supplemental Recommendations to produce a long-term solution for requesting access to gTLD nonpublic registration data.
So the Board is stating it "expects" these four elements to be incorporated into the planned Supplemental Recommendations. This is why I think we must consult with Board reps before finalizing the assignment form. I'm not at all certain that we are on the same page.
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026
anneicanngnso@gmail.com
On Thu, Apr 16, 2026 at 9:16 AM Susan Payne <susan.payne@comlaude.com> wrote:
Anne
I responded in the Assignment Form, but will repeat here. The Board has asked for these items 1-4 to be considered, and so they are included in the Assignment Form. The role of the Team is to discuss, including with the Board Liaisons, and make a decision on how to affirm or modify the recommendation(s) - thereafter called Supplemental Recommendations. There clearly are some boundaries, therefore, set by the scope of the existing recommendations and the previous work done (eg by the RDRS SC). I don't believe that the Board's reference to these gaps is prescriptive. Council could determine that it could include Supplemental Rec(s) on these topic if it believes it is appropriate and in scope. Alternatively, the Council could determine that one or more of the topics is not in scope, and, if so, suggest another path (like new policy work).
There will be Board Liaisons who will participate on the Supplemental Recommendations team, so they can address questions as they arise.
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Anne ICANN <anneicanngnso@gmail.com> *Sent:* 16 April 2026 00:57 *To:* Susan Payne <susan.payne@comlaude.com> *Cc:* Anne ICANN via council <council@icann.org> *Subject:* Re: [council] Re: SSAD Next Steps and draft Assignment Form
Thanks Susan. After these changes, I put a few comments in the document but wanted to raise on the list a question regarding this new wording which applies to the Board's expectations listed in Tripti's letter denoting Items 1 through 4:
The SSAD Supplemental Recommendations Team is expected to consider whether these four elements can be addressed via Supplemental Recommendation or make a recommendation to Council for how they may be addressed through some other mechanism
Is the Council actually in a position to interpret the Bylaws provisions in this regard? Does the Board assume that all four elements are within the scope of Supplemental Recommendations? I think we need to hear from Board reps on this point. Personally, I don't see limitations on the scope of Supplemental Recommendations in the Bylaws language. It looks as though we are trying to carve out an exception on certain elements that might result in a need for a full PDP. Especially given the nature of the urgent requests considerations, I wonder if that is what we really mean?
Thank you,
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026
anneicanngnso@gmail.com
On Wed, Apr 15, 2026 at 2:32 PM Susan Payne via council <council@icann.org> wrote:
Hi Farzaneh, all
Thanks for your comments in the Assignment Form document. We have accepted or endeavoured to propose text to address them. https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...
In particular:
- Regarding the trigger for referring something back to Council, while noting your proposal that if one person has doubts it should be brought back to Council, Leadership feels that that sets the bar too low. The objection of just one person should not halt the work of the group, but your point is taken that a “consensus” may be too high a bar, and alternative language is suggested:
The SSAD Supplemental Recommendations Team is expected to refer back to the GNSO Council if there is strong support in the group for the view that a particular proposed outcome may be out of scope of the Assignment, (e.g., developing new policy versus modifications rooted in foundational documents).
In doing so, we take into consideration that:
· the supplemental team will have many councillors participating, and any councillor may always propose agenda items for council meetings - this is not altered by the Assignment Form;
· however, by the same token that many council members will be on the team, if one person's concern is not shared by others even within the supplemental team, then it is unlikely that those same councillors will be instructed to take a different view if the matter is brought to council. Some reasonable level of agreement/support to escalate to therefore is appropriate.
- Regarding your query on “Confirmation of how the mechanism can be used to make and respond to requests for gTLD non-public registration data for underlying affiliated privacy/proxy domains”, this, and the other 3 elements, are specifically identified in the Board’s letter and resolution, and hence referred to as such in the Assignment Form. The Supplemental Recommendations Team should determine whether they are able to do so, or to make a recommendation for an alternative mechanism to address this. An edit to the Assignment Form has been made to address this.
I hope that this addresses your concerns, but if not, perhaps you could suggest alternative text to do so.
Susan
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Susan Payne via council <council@icann.org> *Sent:* 14 April 2026 15:02 *To:* Anne ICANN via council <council@icann.org> *Subject:* [council] Reminder: SSAD Next Steps and draft Assignment Form
Hi all
As a reminder, Councilors are asked to closely review the draft SSAD Supplemental Recommendations Team Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits *before our Council meeting on Thursday, 16 April* so that we can have a fulsome discussion and resolve any remaining questions or concerns during the meeting. Thank you to those of you who have already provided feedback.
Council small team assignment forms are typically reviewed by the Council and proceed under non-objection, so if you have an objection or concern with the current text, *we ask you to kindly provide alternative text that you can find acceptable before our Council meeting on Thursday, 16 April.*
To ensure timely progress on the Supplemental SSAD recommendations and in order to take advantage of the in-person time at ICANN 86 meeting, we plan to kick off this work and send out the call for volunteers shortly after the Council meeting.
Thank you.
Susan
Susan Payne Head of Legal Policy Com Laude *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAABB8AADw_RQA0> and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAABB8AADw_RQA0>*
*From:* Susan Payne via council <council@icann.org> *Sent:* 07 April 2026 18:23 *To:* Anne ICANN via council <council@icann.org> *Subject:* [council] SSAD Next Steps and draft Assignment Form
Dear Councilors,
As noted in the recent message <https://lists.icann.org/hyperkitty/list/council@icann.org/thread/EVFJHTBDT4G...> from GNSO Support Staff in reference to the SSAD Supplemental Recommendations Team, we are circulating a proposed draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031TneI/edit?usp=sharing>for the SSAD Supplemental Recommendations Team for the Council’s review and feedback.
Once finalised, this proposed Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, similar to previous Small Team Assignment Forms, would govern the work of the SSAD Supplemental Recommendations Team. It includes details and limitations on the scope of the work, the membership of the group, the timeline of the work, the transparency considerations of the group, et al.
Based on some of the questions and concerns Leadership has received, we have tried to answer some of the questions and address some of the concerns below.
*Reminder of how we got here*
The Council began discussing possible next steps for the SSAD recommendations beginning in November <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, following the delivery of the RDRS Standing Committee Final Finding Report. The Council continued to discuss the RDRS Standing Committee Report and next steps during the December meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the January meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...>, the SPS (where we reached agreement on the path of Supplemental Recommendations), and the February meeting <https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/...> .
In discussions with the Board, the Council agreed on this path, in part because this was also the recommendation of the RDRS Standing Committee.
Specifically, the Council discussed the ramifications of following the RDRS Standing Committee’s recommendations during the dialogue with the Board Data Privacy/Protection Caucus members and noted <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> the following:
- The RDRS Standing Committee was composed of members from across the ICANN Community and discussed the potential benefits and drawbacks of all available procedural paths before making the recommendation to not adopt the SSAD recommendations as a package; - Non-adoption and the subsequent steps in Annex A, Section 9 of the Bylaws would initiate a dialogue between the GNSO Council and the ICANN Board; - The GNSO Council would have an opportunity to provide Supplemental Recommendations, which would allow for important and necessary improvements to the existing SSAD recommendations; and, - This would provide a procedurally efficient path that recognizes the ICANN Community’s desire for this work to be completed in a timely manner.
Because we previously agreed on this Supplemental Recommendation path, and this has now been formally assigned to us by the recent Board resolution, my hope is that we can continue to refine the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, in order to incorporate additional guardrails, if these are felt to be needed, and settle on a mutually-agreeable team composition in order to progress the task efficiently.
*Remit of the Council under the Bylaws *
Annex A, Section 9 of the ICANN Bylaws <https://www.icann.org/ru/governance/bylaws> governs the process for Supplemental Recommendations. Specifically, if the Board determines GNSO policy recommendations are “not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "Board Statement"); and (ii) submit the Board Statement to the Council.” Subsequently, “at the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "Supplemental Recommendation") to the Board.”
The Bylaws do not dictate the method in which the Council produces Supplemental Recommendations. In the past, specifically for the Subsequent Procedures Supplemental Recommendations, the Council chose to use a Small Team Plus, which allowed the Council to advance its work with the inclusion of additional subject matter expertise from outside the GNSO Council.
Here, the Council has previously noted the advantage of allowing for external expertise to be included in the SSAD Supplemental Recommendations Team; specifically, some Councilors have noted the importance of including expertise from the RDRS Standing Committee, for example. In addition, some Councilors have noted the importance of including members from outside the GNSO that actively participated in the original EPDP Team and the RDRS Standing Committee, e.g., ALAC, GAC, and SSAC.
*Can the SSAD Supplemental Recommendations Team create new policy? *
The remit of the SSAD Supplemental Recommendations Team is to modify existing policy recommendations, not create new policy. The modification of existing recommendations (i.e., the eventual Supplemental Recommendations) will be expressly limited by the SSAD Supplemental Recommendations Team’s draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and its corresponding scope. In other words, the creation of Supplemental Recommendations is only an open opportunity for the Council to modify policy recommendations, grounded in previous work.
The RDRS Standing Committee, which was chartered by the GNSO Council, was tasked with, et al., providing the Council with “specific lessons learned that should be factored into the consideration of how to proceed with the SSAD (System for Standardized Access/Disclosure) Recommendations and suggestions to the Council for a proposed recommendation(s) to the ICANN Board in relation to the consideration of the SSAD recommendations.”
In providing its rationale for Recommendation 5, which advised the Council to consider asking the Board to non-adopt the 18 SSAD recommendations, the RDRS Standing Committee noted it “encourage[s] a willingness to consider modifying parts of the EPDP Phase 2 policy recommendations, if needed, as indicated in the below table. The SC considers it important to achieve a functional policy that adapts to the changed circumstances and benefits from the lessons learned of the RDRS pilot. [Accordingly,] the SC has developed the table below evaluating each of the 18 SSAD policy recommendations considering the RDRS pilot outcomes. It indicates whether each recommendation should be kept or modified along with rationale rooted in the pilot’s evidence and the Standing Committee’s considerations in [conducting its assignment from the Council.]”
In light of the above, the Standing Committee’s, ICANN Board’s, and the Council’s expectation would be that the EPDP recommendations would be modified, using the provided guidance, to allow for important and necessary improvements to the existing SSAD recommendations. For the avoidance of doubt, the SC’s guidance on the potential modifications is simply that. It serves as a valuable starting point for the SSAD Supplemental Recommendations Team, given the substantial consideration that the SC has already given to this issue, but does not determine the outcome.
*Can all GNSO Councilors participate? *
Yes, any interested and committed GNSO Councilor is invited to participate in the SSAD Supplemental Recommendations Team.
*What is the expected time commitment? *
Because the Council has committed <https://gnso.icann.org/sites/default/files/policy/2026/correspondence/payne-...> to complete the work on Supplemental Recommendations “in months, not years,” the group will be meeting regularly to progress on this work. At minimum, it is likely that the SSAD Supplemental Recommendations Team will meet once per week for up to 90 minutes, with a possibility of increasing the cadence if the need arises.
Additionally, we understand that ICANN Support Staff has been working on providing the group with dedicated face-to-face time at ICANN86. In light of this, ICANN org is currently working on organizing a *one-day in-person workshop on* *Sunday, 7 June* before ICANN86 officially begins on Monday. If you think you are interested in participating in the SSAD Supplemental Recommendations Team, please make note of this date. Councilors who choose to participate in the SSAD Supplemental Recommendations Team will be granted an early arrival date to allow for participation in this workshop. More information to follow soon.
While this task will require a time commitment from the participants, we hope that tight scoping and the limitations in place on the breadth of modification will assist in controlling this as much as possible.
*Other than the time commitment, is there anything else I should know if I would like to participate?*
Per the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, the SSAD Supplemental Recommendations Team is expected to consider several inputs as it develops Supplemental Recommendations, as these inputs serve as important boundaries on the level of modifications to the recommendations, including:
- RDRS Standing Committee Final Findings Report <https://gnso.icann.org/sites/default/files/policy/2025/draft/rdrs-sc-finding...> and the recommendations therein; - SSAD Operational Design Assessment <https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> - RDRS Policy Alignment Analysis <https://itp.cdn.icann.org/en/files/registration-data-request-service-rdrs/re...> and Public Comment Summary <https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-cou...>
Councilors interested in participating are expected to be familiar with the 18 original SSAD recommendations <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase...> as well as the above documents.
*What is the Council’s role at this stage?*
We understand the importance of scoping this work appropriately and mitigating concerns from across the Council and Community. Accordingly, we ask that Councilors closely review the draft Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...> and provide suggestions and edits *before our Council meeting on 16 April* so that we can have a fulsome discussion on any remaining questions or concerns with the Assignment Form <https://docs.google.com/document/d/1ulSvcKgCVt-C6qTsD24BpMK959n8n8LQNol5031T...>, with the goal of kicking off this work shortly after the meeting.
Thank you.
Susan
Susan Payne GNSO Council Chair
Head of Legal Policy
28 Little Russell Street, <https://www.google.com/maps/search/28+Little+Russell+Street,+%0D%0ALondon+WC...> London <https://www.google.com/maps/search/28+Little+Russell+Street,+%0D%0ALondon+WC...> WC1A 2HN, <https://www.google.com/maps/search/28+Little+Russell+Street,+%0D%0ALondon+WC...> UK <https://www.google.com/maps/search/28+Little+Russell+Street,+%0D%0ALondon+WC...> *T* +44 (0) 20 7421 8250 *D* +44 (0) 20 74218 255
*comlaude.com <http://comlaude.com/>*
*Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAAA98AADw_RQA0> and Youtube <https://t-uk.xink.io/Tracking/Index/ZxkAAA98AADw_RQA0>*
<https://www.linkedin.com/company/com-laude> <https://twitter.com/comlaude?lang=en> <https://www.facebook.com/ComLaude/> <https://www.youtube.com/@comlaude>
------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> ------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> ------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/>
_______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,%0D%0A+W...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/>
------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,%0D%0A+W...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> ------------------------------
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,%0D%0A+W...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> ------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England <https://www.google.com/maps/search/28+Little+Russell+Street,+London,+WC1A+2H...>; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland <https://www.google.com/maps/search/15+William+Street,+South+West+Lane,+Edinb...>; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2 <https://www.google.com/maps/search/Calle+Barcas+2?entry=gmail&source=g>, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com/> _______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
participants (4)
-
Anne ICANN -
farzaneh badii -
Justine Chew -
Susan Payne