[CPWG] [registration-issues-wg] One additional EPDP issue
Tijani BEN JEMAA
tijani.benjemaa at topnet.tn
Thu Feb 14 07:53:23 UTC 2019
LOL
A grey but still a hole….
-----------------------------------------------------------------------------
Tijani BEN JEMAA
Executive Director
Mediterranean Federation of Internet Associations (FMAI)
Phone: +216 98 330 114
+216 52 385 114
-----------------------------------------------------------------------------
> Le 14 févr. 2019 à 06:47, Alan Greenberg <alan.greenberg at mcgill.ca> a écrit :
>
> A bit late to integrate that and it is really an implementation, but will certainly use it as an example of something that could help ameliorate the issue.
>
> Then it becomes just a grey hole?
>
> Alan
>
> At 13/02/2019 08:01 PM, Olivier MJ Crépin-Leblond wrote:
>
>> Dear Alan,
>>
>> this is like lobbing correspondence over a wall... something which some of us are accustomed to. :-)
>> More seriously though, would it be possible to require that any such correspondence using an online form needs to email a copy of the form to the enquirer's email address as well as the registrant and provide both with a unique case ID? In effect, it's a CRM system. Online businesses use that all the time. I can live with a CRM system that tracks cases even without knowing who owns the domain name.
>> Kindest regards,
>>
>> Olivier
>>
>> On 13/02/2019 21:42, Alan Greenberg wrote:
>>>
>>> There was bound to be one issue that we forgot today.
>>>
>>> This is the fact that all communications with a registrant or tech
>>> contact will be via anonymized e-mail r a we form (which then is
>>> e-mail sent by the registrar).
>>>
>>> Both are what I refer to as "black hole" communications. You
>>> tow the
>>> message out and unless there is a reply, you never know if it was
>>> really forwarded on your behalf, whether it was received. If it
>>> bounced, the Registrar may know that it did, but the sender does not.
>>>
>>> With a real address, you can at least use a number of tools to try to
>>> determine if there is a path to the mail server or if the user
>>> exists. Here there is nothing.
>>>
>>> Alan
>>>
>>> _______________________________________________
>>> CPWG mailing list
>>> CPWG at icann.org <mailto:CPWG at icann.org>
>>>
>>> https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg>
>>>
>>
>> _______________________________________________
>> CPWG mailing list
>> CPWG at icann.org
>> https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg>
>>
>> _______________________________________________
>> registration-issues-wg mailing list
>> registration-issues-wg at atlarge-lists.icann.org <mailto:registration-issues-wg at atlarge-lists.icann.org>
>> https://mm.icann.org/mailman/listinfo/registration-issues-wg <https://mm.icann.org/mailman/listinfo/registration-issues-wg>_______________________________________________
> CPWG mailing list
> CPWG at icann.org <mailto:CPWG at icann.org>
> https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cpwg/attachments/20190214/b83e2e44/attachment-0001.html>
More information about the CPWG
mailing list