+1 on the work done. Will be good to know if reasons where provided for the NO as I expect it won't be an outright "no"
Regards
Sent from my Asus Zenfone2
Kindly excuse brevity and typos.
Thanks Padmini,Excellent work! This is very useful information.I note that some of the requests are very broad in nature and would pose a challenge to comply eg those requests for "All communications from ..."," all documents from..". In some jurisdictions this can be a legitimate reason for denial if the request is too burdensome.ICANN must provide a reason(s) to support why it denies a request - merely stating "No" does not engender trust as the decision may not have any merit. Providing clear reasons would ensure that ICANN is in fact following the DIDP , it would provide legal guidance for future applicants and would comfort disappointed applicants who would be better informed on whether to pursue a re-consideration of the decision.regardsKarelOn Tue, Oct 6, 2015 at 8:55 AM, Padmini <[log in to unmask]> wrote:Warm regardsPlease read the two together. Since this was a massive manual data compiling project, I may have inadvertently made some small errors; in the event that you do find any, please leave a comment, and I will follow it up. Hope this comes of use.Dear allPlease find two links, which contain a comprehensive breakdown of all the DIDP requests ever filed and responded to by ICANN as of today.
https://docs.google.com/spreadsheets/d/1M1gWBpa7tlxGPMWyB6xJryddahyZzjVIarSz0RJswDM/edit?usp=sharing
https://docs.google.com/document/d/1x1vG23FdIAzo4ro80eEieaokBpAeNVtYXjds6mHt2DE/edit?usp=sharingPadmini BaruahProgramme Associate, Internet GovernanceCenter for Internet and Society, Bangalore