Yes, I respectfully disagree with Sara's statement, Chuck. (With a small qualification.) I don't think you have consensus around that point, in my view. The qualification I'd make is: where there are specific regulatory reasons to either require or permit a change to existing Whois/RDS policy, provided that it's done in the most conservative way possible, I think that's reasonable to discuss. (The obvious example here is the GDPR.) Beyond that, I believe that one of the best alternatives that's (implicitly) presented so far is no change, as many (all?) of the proposed changes I've heard so far would be worse than the status quo. 

So do I believe it "must" change? No, aside from a very limited tweak due to some specific regulatory issues. Do I believe it could be improved, and that improvements are worth discussing? Yes.  But the answer to your question is: Yes, there is someone on this working group who respectfully disagrees with Sara's statement. 

John Horton
President and CEO, LegitScript


Follow LegitScript: LinkedIn  |  Facebook  |  Twitter  |  Blog  |  Newsletter




On Wed, Feb 14, 2018 at 11:08 AM, Chuck <consult@cgomes.com> wrote:

Is there anyone in this WG who disagrees with Sara’s statement that ‘RDS must change’, understanding that we still have large differences of opinion regarding how to change it?

 

Chuck

 

From: gnso-rds-pdp-wg [mailto:gnso-rds-pdp-wg-bounces@icann.org] On Behalf Of Sara Bockey
Sent: Wednesday, February 14, 2018 9:22 AM
To: Steve Crocker <steve@shinkuro.com>; gnso-rds-pdp-wg@icann.org
Subject: Re: [gnso-rds-pdp-wg] Using the GDPR as a basis for RDS Policy is backwards

 

I agree with Steve and look forward to additional feedback from him. 

 

RDS must change.  Discussions to the contrary are a waste of time.

 

Sara

 

sara bockey

sr. policy manager | GoDaddy™

sbockey@godaddy.com  480-366-3616

skype: sbockey

 

This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.

 

 

From: gnso-rds-pdp-wg <gnso-rds-pdp-wg-bounces@icann.org> on behalf of Steve Crocker <steve@shinkuro.com>
Date: Wednesday, February 14, 2018 at 9:27 AM
To: "gnso-rds-pdp-wg@icann.org" <gnso-rds-pdp-wg@icann.org>
Subject: [gnso-rds-pdp-wg] Using the GDPR as a basis for RDS Policy is backwards

 

I am only partially up to speed on the state of discussion within this WG, but I have been following the RDS situation for several years.  In my view, the current focus on GDPR, while understandable because of the looming deadline, is logically backwards.  The challenge, which we tried to address forcefully in 2012, is to rethink the RDS from the ground up.  In my view, this is:

 

o necessary

 

o feasible

 

o will lead to a much cleaner model

 

o will make it relatively straightforward to satisfy the GDPR and all similar regulations around the world.

 

There are also some issues such as the relationship of name server operators that also need to be addressed.

 

There is obviously much more that needs to be said.  I will contribute as much and as quickly as I can.

 

Steve

 


_______________________________________________
gnso-rds-pdp-wg mailing list
gnso-rds-pdp-wg@icann.org
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg