[gnso-rds-pdp-wg] possible requirements from GAC / law enforcement recommended documents

Thu Jul 14 20:12:41 UTC 2016

Team,

I would suggest that instead of continuing this particular thread that seems to be a back-and-forth about the interpretation and motivations of the LEA “recommended possible requirements” document (note the title), that all members of the work party simply read the very straight-forward two page document and come to their own conclusions about its contents.  It should take no more than a couple minutes.  I’m sure that we can discuss further the reasons/goals/uses cases for the particular asks the LEA team made in that document as part of our further deliberative process down the line, but for now, this document is very succinct in naming various POTENTIAL data gathering/maintenance and display requirements that involve RDS elements plus some others likely unrelated to the RDS, but with impact on domain registrars.  As such it is a very good example of a list of potential requirements, but due to its brevity doesn’t supply the reasoning/use cases behind the requests.  That’s fine, since we have members of this WP who either helped draft this document or provided advice and input into it who we can tap to flesh out the stories behind the requests once that time arrives.  That goes for almost all the requirements and documents we are gathering right now - the whole point in having a diverse WP membership is to bring perspective to the often dry or sparse documentation we do have to work with to better inform our understanding of what different requirements and requests are trying to accomplish.  Understanding those needs may lead to accepting the need/recommendation, accepting the need but providing a different approach, or rejecting the need and thus the recommended actions.  Ascribing motives and/or accepting/rejecting needs/requirements/requests at this stage of the game is thus premature and counter-productive to our overall work plan, so I would respectfully request that we refrain from doing so until we reach the part of our work plan where we actually can shed full light on various issues so we can weigh them fully and with as little bias as possible, and go through that part of the process in an orderly fashion.

Best,

Rod Rasmussen
VP, Cybersecurity

-  <http://www.infoblox.com/>-
 <http://www.infoblox.com/>
> On Jul 14, 2016, at 10:02 AM, Catalyst-Vaibhav Aggarwal <va at bladebrains.com> wrote:
> 
> Rob
> 
> I hope you reply to Mine, Terri’s & Kiran’s Mail ?
> 
> Regards
> -VA
> 
> From: <gnso-rds-pdp-wg-bounces at icann.org <mailto:gnso-rds-pdp-wg-bounces at icann.org>> on behalf of Terri Stumme <terri.stumme at legitscript.com <mailto:terri.stumme at legitscript.com>>
> Date: Thursday, July 14, 2016 at 10:08 PM
> To: Rob Golding <rob.golding at astutium.com <mailto:rob.golding at astutium.com>>
> Cc: <gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>>
> Subject: Re: [gnso-rds-pdp-wg] possible requirements from GAC / law enforcement recommended documents
> 
> Law enforcement never requested "personal details, home address etc of senior STAFF of a Registrar listed on a website." Law enforcement requested only that the names of the executives be posted on the registrar's website, and that contact information for the registrar; i.e., company address and telephone number, not the home address of senior staff.
> 
> On Thu, Jul 14, 2016 at 1:35 AM, Rob Golding <rob.golding at astutium.com <mailto:rob.golding at astutium.com>> wrote:
>> On 2016-07-14 08:58, Catalyst-Vaibhav Aggarwal wrote:
>>> So now v agree to say that GAC / Law enforcement is over reaching
>>> and suggestions, pants made are baseless and have no argument.
>> 
>> You appear to turn many ideas / comments you don't understand into some sort of personal attack.
>> 
>> Perhaps if you had
>> * read the document
>> * understood the document
>> * attended any of the multiple Registrar&LEA meetings where some of their wants (most of which they never expected to get and many of which they couldn't provide any reason for asking for)
>> you wouldn't be jumping so quickly to these weird conclusions.
>> 
>>> YET we come back to the table and talk of Privacy and other related
>>> factors. How can it be ?
>> 
>> One (of many) examples ..
>> 
>> LEAs wanted the personal details, home address etc of senior STAFF of a Registrar listed on a website.
>> 
>> Not simply provided (as is law in most locales) to the company regulating authority in that region - most of whom DO NOT make that information public without a warrant for very valid reasons
>> 
>> Not even just submitted to ICANN (as indeed much information about the management of a registrar already is) for them to know / leak
>> 
>> But published for anyone and everyone on the registration website
>> 
>> If someone LEA or otherwise wants to to talk to my Registrar, they can do so at the office (by appointment) or by phone or by email or through the ticket system or any number of other *appropriate* and *documented* methods - they DO NOT need to know about and turn up at my HOME address
>> 
>> Rob
>> --
>> Rob Golding   rob.golding at astutium.com <mailto:rob.golding at astutium.com>
>> Astutium Ltd, Number One Poultry, London. EC2R 8JR
>> 
>> * domains * hosting * vps * servers * cloud * backups *
>> 
>> _______________________________________________
>> 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>
> 
> 
> 
> --
> Terri Stumme
> Investigative Analyst
> _______________________________________________ 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
> 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/20160714/95c87dfc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 45B46C56-BE39-4932-8286-164C8D050227[3].png
Type: image/png
Size: 17183 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160714/95c87dfc/45B46C56-BE39-4932-8286-164C8D0502273.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160714/95c87dfc/signature.asc>