All

With thanks to Sam, I am circulating her suggested path, which is something of a hybrid of 1 and 3 below, for consideration:  https://docs.google.com/document/d/122suSucvCc-PWfee9cJBFo1e8R-t-gO4Lf6-R4G_Ky8/edit?usp=sharing

 

When considering the next steps on urgent requests with your groups, please also include this proposal together with the original three options.  Please share feedback as soon as possible, ideally in advance of our next Council 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 and Youtube

From: Caitlin Tubergen via council <council@icann.org>
Sent: 08 March 2026 06:34
To: council@icann.org
Subject: [council] Summary of options from urgent requests discussion re: authentication

 

Dear Councilors,

 

Further to the discussion this morning on urgent requests, please find the below summary of options:

 

To ensure consistency with Recommendation 18, the work to develop an authentication mechanism could be integrated with the Urgent Request timeline through either:

 

    1. GNSO Council confirmation that implementation of the response timeline language incorporating the authentication mechanism would be consistent with Recommendation 18

OR

    1. Board un-adoption of Recommendation 18 and GNSO Council development of a supplemental Consensus Policy recommendation integrating authentication and the response timeline language

OR

    1. Council incorporates the authentication mechanism as part of the work on supplemental recommendations for the EPDP Phase 2 Policy Recommendations.

 

References

 

EPDP Phase 1 Final Report

EPDP Phase 2 Final Report

Public Comment on proposed Urgent Request timeline language

Public Comment on Proposed GNSO Process for ICANN Board to Reverse Adoption of GNSO Policy Recommendations

Public Comment on Registration Data Request Service (RDRS) Policy Alignment Analysis

 

Thank you.

 

Best regards,

 

Caitlin

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