[ALAC] Community Feedback on Proposed models for RDS - by the end of January

Alan Greenberg alan.greenberg at mcgill.ca
Mon Jan 15 04:36:17 UTC 2018

In my mind, there is no question that we need to respond.

The models are NOT what I was expecting, but that 
is not particularly relevant at this point. 
ICANN's challenge is to attempt to saitisfy data 
commissioners, who will not likely tell us ahead 
of time that they agree with us or not, But to do 
that while to the extent prossible, maintaining 
WHOIS so it can at least partially satisfy the 
ongoing important uses of WHOIS, particularly 
with respect to fighting DNS abuse and malicious activities.

So for example, Model 3 certainly satisfies 
privacy concerns (although we could endlessly 
debate whether the expiration date is private 
information or not), but it shuts down virtually 
all other uses of WHOIS (including trade mark 
protection and the UDRP) and I find including it 
as one of the proposed models rather ludicrous. 
It is certainly easy to implement. And cheap.


At 14/01/2018 03:24 PM, Holly Raiche wrote:

>So you do support responding - whatever it is called?
>On 15 Jan 2018, at 7:15 am, Sebicann Bachollet 
><<mailto:sebicann at bachollet.fr>sebicann at bachollet.fr> wrote:
>>Yes Holly
>>It is exactly what I was pointing out.
>>>Le 14 janv. 2018 à 20:35, Holly Raiche 
>>><<mailto:h.raiche at internode.on.net>h.raiche at internode.on.net> a écrit :
>>>Hi Sebastian
>>>I did read the words.  But seriously, he is 
>>>asking for a response - whatever it 
>>>is  called.  And given the importance of the 
>>>issue, we should respond - whatever we call it.
>>>On 15 Jan 2018, at 3:05 am, Sebicann Bachollet 
>>><<mailto:sebicann at bachollet.fr>sebicann at bachollet.fr> wrote:
>>>>No comment but feedback ;)
>>>>"To help inform this, please provide your 
>>>>feedback by 29 January 2018. Please send your 
>>>>feedback to <mailto:gdpr at icann.org>gdpr at icann.org. »
>>>>>Le 14 janv. 2018 à 16:39, Glenn McKnight 
>>>>><<mailto:mcknight.glenn at gmail.com>mcknight.glenn at gmail.com> a écrit :
>>>>>Hi Holly
>>>>>Interesting you mentioned this issue, two things to share with you
>>>>>1.  NCUC did a session at the IGF and 
>>>>>curious if anyone followed their tread. they 
>>>>>had a good google doc on the issues
>>>>>2. NARALO is having monthly hot topics 
>>>>>during the second half of our monthly 
>>>>>membership calls. I was thinking of this 
>>>>>issue as a topic for March since I have 
>>>>>Cybersecurity as the February topic.   I 
>>>>>will need someone to level set the issue.  We had Net Neutrality for January
>>>>>Glenn McKnight
>>>>>NARALO Secretariat
>>>>><mailto:mcknight.glenn at gmail.com>mcknight.glenn at gmail.com
>>>>>skype  gmcknight
>>>>>twitter gmcknight
>>>>>289-830 6259
>>>>>On Sun, Jan 14, 2018 at 1:07 AM, Holly 
>>>>>Raiche <<mailto:h.raiche at internode.on.net>h.raiche at internode.on.net> wrote:
>>>>>Two days ago, Goran’s blog posted ICANN’s 
>>>>>proposed there models for addressing the 
>>>>>issue of RDS information and the EU Data 
>>>>>Protection rules.  According to the blog, 
>>>>>'community input' is being sought - by the end of January.
>>>>>Given the significance of this discussion on 
>>>>>the information that registries/registrars 
>>>>>collect and display, I am assuming that ALAC 
>>>>>will be making comments? We should, at the 
>>>>>least, have a page on the wiki for comments???
>>>>>ALAC mailing list
>>>>><mailto:ALAC at atlarge-lists.icann.org>ALAC at atlarge-lists.icann.org
>>>>>At-Large Online: 
>>>>>ALAC Working Wiki: 
>>>>>ALAC mailing list
>>>>><mailto:ALAC at atlarge-lists.icann.org>ALAC at atlarge-lists.icann.org
>>>>>At-Large Online: 
>>>>>ALAC Working Wiki: 
>Content-Type: text/plain; charset="us-ascii"
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline
>ALAC mailing list
>ALAC at atlarge-lists.icann.org
>At-Large Online: http://www.atlarge.icann.org
>ALAC Working Wiki: 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20180114/a00cd102/attachment.html>

More information about the ALAC mailing list