[gnso-rds-pdp-wg] Discussion Topics

[Rod Rasmussen]

Chuck,

Please consider it “put forward” then. :-)

I too have been experimenting a bit with registration-specific phone numbers and distressingly find the same issue - call upon call that only started to the number once the data was published in whois *AND* in the hands of the registrar of course (hard to tell who the real villain is given that, probably both).  Many of these are the Indian boiler rooms pretending to be “Microsoft support” for example.

This fits in with the concepts we were discussing last week on “preferred contact methods” for a particular contact object (person/legal entity).  For example, we could still mandate collecting a phone number, but only publishing it for particular purposes and providing a “preferred public contact” method that is less intrusive depending upon the preferences of that contact.  Not saying I endorse that approach or not, just saying that we need to be thinking along those directions.  For example, I could provide my e-mail address as my preferred “public” contact method since I can spam filter it far more effectively than phone calls, but still be reachable via phone for important technical issues or abuse problems with some sort of vetting.

At the end of the day we’re talking about a “directory service” here and we need to be approaching it from how we would engineer one at the end of the second decade of the 21st century rather than the beginning of the last decade of the 20th.  A long list of fixed field parameters tied to a single primary database key (domain name) that are one-size-fits-all for collection and public publication are definitely “old school”.  Object-oriented data with relational pointers and flexible context that allow for differentiated publication are a bit more modern...

Cheers,

Rod

> On Jul 20, 2017, at 7:20 AM, Chuck Gomes Consulting <consult at cgomes.com> wrote:
> 
> Johtan,
>  
> I suggest that you either become a member of the WG and then submit this request or find a member who would put this suggestion forward.
>  
> Chuck
>   <>
> From: Jothan Frakes [mailto:jothan at jothan.com <mailto:jothan at jothan.com>] 
> Sent: Wednesday, July 19, 2017 1:58 PM
> To: Chuck Gomes Consulting <consult at cgomes.com <mailto:consult at cgomes.com>>
> Cc: RDS WG <gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>>
> Subject: Re: [gnso-rds-pdp-wg] Discussion Topics
>  
> Hi-
>  
> I am an observer on this group, but wanted to ask if it is possible to inject an explicit 'do not call for marketing' field into the whois which would be opt-out while we are under the hood.
>  
> I realize such a thing is likely to be unenforceable, as there have been disclaimers and directions on use of the whois data within the output for years that gets completely disregarded by marketers, but it seems like it could be a hook upon which legislative efforts could be added.
>  
> After receiving my 15th call today from aggressive telemarketers calling me on a telephone number that I created specifically for a new domain registration made less than 36 hours ago, it is clear to me that we MUST do something about this predatory behaviour if we can, and the information is clearly being sourced from whois.
>  
> -Jothan
> 
> 
> Jothan Frakes
> Tel: +1.206-355-0230
> 
>  
> On Wed, Jul 19, 2017 at 10:49 AM, Chuck Gomes Consulting <consult at cgomes.com <mailto:consult at cgomes.com>> wrote:
>> Here are the list discussion topics in preparation for next week’s WG meeting:
>> Any topics related to the survey that will be distributed later today.
>> Collecting the data element ‘Registrant’ for the RDS
>> Collecting the data element ‘Registrant Organization’ for the RDS
>> Collecting the data element ‘Registrant Country’ for the RDS
>> Collecting the data element ‘Registrant Contact’ in the RDS.
>> Any topics related to collecting the following data elements* for the RDS:
>> Admin Contact & Contact ID
>> Technical Contact & Contact ID
>> Privacy/Proxy Provider Contact & Contact ID
>> Reseller
>> Registrar Abuse Contact Email Address
>> Registrar Abuse Contact Phone
>> URL of Internic Complaint Site (ICANN Whois Data Problem Reporting System)
>> Original Registration Date
>>  
>> * Note that most WG members who responded to last week’s poll supported collecting these data elements for the RDS.
>>  
>> If you have any questions, please ask them.
>>  
>> Chuck
>> 
>> _______________________________________________
>> gnso-rds-pdp-wg mailing list
>> gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>
>> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg <https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg>
>  
> _______________________________________________
> gnso-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg <https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20170720/88e2230e/attachment.html>