<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div dir="ltr">Hi Alan - </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Given the absurd level of spam and abuse currently taking place on web forms, we could not support this recommendation.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">J.</div>
<div dir="ltr"><br>
<blockquote type="cite">On May 24, 2021, at 17:45, Alan Greenberg via Gnso-epdp-team <gnso-epdp-team@icann.org> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="background-color: #f2dede; padding-left: .5cm; border-left-width: 5px; border-left-style: solid; border-left-color: #b94a48;">
<span style="font-size: 11pt; line-height: 16pt; font-family: Tahoma, Verdana, Segoe, sans-serif; color: #b94a48;">Caution:</span>
<span style="font-size: 11pt; line-height: 16pt; font-family: Tahoma, Verdana, Segoe, sans-serif; color: #b94a48;">
This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@.</span></div>
<p> </p>
<div>Unfortunately, Mark and I did not get this in prior to the Friday deadline, but we still believe that it is crucial to include in the Initial Report.<br>
<br>
Although some form of email address is a far preferable solution for many on this EPDP, it appears that this will not be a recommendation.<br>
<br>
As it stands, the EPDP Recommendation #13 which is supposed to facilitate communications with the registrant does not achieve its goal. Many registrars are using web forms, and in many cases, they are effectively useless. As an example, one common example is
a form that simply lets the requestor select one of three messages (Domain name or content is being used in malware, or for spam or abuse; Domain name or content is infringing on a trademark or violating local laws or regulations; or Research or other purpose).<br>
<br>
It has been suggested that this matter be referred to the Phase 1 IRT, but without a recommendation saying that the policy may set web form content, there is no way for the IRT to establish such enforceable rules.<br>
<br>
Accordingly, the Initial Report must include a new Recommendation:<br>
<br>
<font color="#0000FF"><b>Recommendation<br>
<br>
The Phase 1 Recommendation 13 should be amended to include: Should a Registrar choose to use a web form, that form must allow at the requester to specify the Subject of the email to be send (up to 64 characters) and a free-form text message of up to 512 characters
to be included in the communication to the registrant.<br>
<br>
</b></font>Alan & Mark </div>
<span>_______________________________________________</span><br>
<span>Gnso-epdp-team mailing list</span><br>
<span>Gnso-epdp-team@icann.org</span><br>
<span>https://mm.icann.org/mailman/listinfo/gnso-epdp-team</span><br>
<span>_______________________________________________</span><br>
<span>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.</span></div>
</blockquote>
</body>
</html>