Thanks Scott, will update as per suggestion 😊
CLASSIFICATION:CONFIDENTIAL From: regext <[email protected]> On Behalf Of Hollenbeck, Scott Sent: November 15, 2023 11:36 AM To: [email protected]; [email protected] Cc: Don Slaunwhite <[email protected]>; [email protected] Subject: [EXT] Re: [regext] I-D draft-latour-pre-registration Thanks for this, Jack. After a quick glance, I noticed that you’re using an unusual method to define the extension. Can I suggest that you take a look at RFC 3735 for guidance on the community-agreed upon methods for extending EPP? Here’s one specific example: Section 6.1.4 of your draft describes the <pre-registration-data> extension element. If you follow RFCs 3735 and 5730, the <create> command should be extended like this: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <create> <!-- Domain creation data --> <domain:create> <!-- Domain details --> </domain:create> <!-- Pre-Registration Data --> </create> <extension> <prereg:pre-registration-data xmlns:prereg="urn:ietf:params:xml:ns:preregepp-1.0" xsi:schemaLocation="urn:ietf:params:xml:ns:preregepp-1.0 preregepp-1.0.xsd" > <!-- Pre-registration information --> </prereg:pre-registration-data> </extension> </command> </epp> Note the use of the <extension> element and the URNs for the extension namespace and schema location. RFC 5910 might also be helpful as an example of an extension that adds elements to the <create> command. Scott CLASSIFICATION:CONFIDENTIAL From: regext <[email protected]<mailto:[email protected]>> On Behalf Of Jacques Latour Sent: Wednesday, November 15, 2023 10:57 AM To: [email protected]<mailto:[email protected]> Cc: Don Slaunwhite <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: [EXTERNAL] [regext] I-D draft-latour-pre-registration Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi all, At the ICANN78 meeting and other venues, there were quite a lot of discussion on AI/ML abuse detection related discussions and presentations. * Example: https://static.sched.com/hosted_files/icann78/de/4%20%2020231023-TechDay-AI%20at%20EURid.pdf<https://secure-web.cisco.com/1NTfB4xD-peu1wmsKjsb5oRjqKlgy79kO6R4MUaEAqGWLzCXapc1ih75TFZ_PyYE3D0UA4cta4OM8FBX4snxQmkJym19OiUgg5FADk6Ex6hTFLf1FRGpFgR6KOQNNqBpJYBr0lOpmqJ9P5AKc2rvh7DiKKcaavBq63t8deMI-DvSeAKA4z7a-vPmHlPDeizq1hG8TzL3XAyrpcAJdLE4MdHW3ZrQfD7NRFrdAqkXBo-Cwe-Ggw7kvjZvb_oR4NCeLTJPjWo29dqsUepxdIxGpFBaUOKLgDplD65kWIyO6OKk/https%3A%2F%2Fstatic.sched.com%2Fhosted_files%2Ficann78%2Fde%2F4%2520%252020231023-TechDay-AI%2520at%2520EURid.pdf> But this is after the fact, after a registration is completed, so we thought of a new extension to allow the registrar to ask the registry that have this real time capabilities to analyse the pre-registration information and return a quality score to better inform the process. draft-latour-pre-registration-00 - EPP Pre-Registration Verification (ietf.org)<https://secure-web.cisco.com/1LcVfDIG2NmoEQu3NIqZW0YOU03IZwU5giqworrs5rgI6EWXtlOPcK9COZjCim5-MWLmdKqoRofBnmHAfqH02D3yptntkti1Z65Pka7CDyp3Fwh2pjRkhfdvysjdjF-NiUwYt0m5hhKYg1EWOpxrDqI1b7x7qg1u73NxghsZ3fmOSj9LksRPO7tMMJMk_OLCPXTVcZ1w2gEqswshLzPVGYdazAT_ZxyCmEEDUeelP_3DQdF3OjRRr4FhvGubYQgBRsm7uvFSkJ1j9fv0-QkiB70t8uauhH9ptYQdcDfsJ1tI/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-latour-pre-registration%2F> Have a read, Jack CLASSIFICATION:CONFIDENTIAL
_______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
