Documentary Information Disclosure Policy: Difference between revisions

JP (talk | contribs)
No edit summary
JP (talk | contribs)
Line 573: Line 573:
| After [https://www.icann.org/en/system/files/files/acharya-response-19feb15-en.pdf initially responding] that it needed to consult with the parties to the contract to get consensus on making the plan publicly available, staff provided an update that the [https://www.icann.org/resources/pages/20150120-1-2015-02-24-en document was published in March]
| After [https://www.icann.org/en/system/files/files/acharya-response-19feb15-en.pdf initially responding] that it needed to consult with the parties to the contract to get consensus on making the plan publicly available, staff provided an update that the [https://www.icann.org/resources/pages/20150120-1-2015-02-24-en document was published in March]
| Initial response cited 1, 2, 3, & 9
| Initial response cited 1, 2, 3, & 9
|
|-
| 6 February 2015
| Centre for Internet and Society
| Details of contract fees paid by the [[Regional Internet Registry|RIRs]] from 1999-2014, including a breakdown of contributions from each.
| [https://www.icann.org/en/system/files/files/cis-response-08mar15-en.pdf Pointed to published financial information], no other documents released
| No
| The response noted that NRO only published breakdowns of contributions by RIR for three years from 2003-2005
|-
| 11 February 2015
| Kin Sun
| Documents related to allegedly unauthorized transfer(s) of a domain name
| [https://www.icann.org/en/system/files/files/didp-response-13mar15-en.pdf Declined]
| 3 & 5
|
|-
| 12 March 2015
| [[James Gannon]]
| Disclosure of Root Zone KSK Operator Function Termination Plan specified in Section C.7.3 of the IANA Functions Contract between ICANN and the NTIA
| After [https://www.icann.org/en/system/files/files/didp-response-20150312-1-gannon-25mar15-en.pdf initially responding] that it needed to consult with the parties to the contract to get consensus on making the plan publicly available, staff provided an update that the [https://www.icann.org/resources/pages/20150312-1-2015-03-25-en document was published in March]
| Initial response cited 1, 2, 3, 9, & 10
| Essentially the same request as Guru Archarya, above
|-
| 14 March 2015
| [[James Gannon]]
| Disclosure of Contingency and Continuity of Operations Plan as specified in Section C.7.2 in the IANA Functions contract between ICANN and the NTIA
| [https://www.icann.org/en/system/files/files/didp-response-20150314-1-gannon-25mar15-en.pdf Declined]
| 1, 3, 6, 10, & 11
| Response notes that disclosure of the plan "could pose a threat to the stability and security of the Internet and domain name system," because the plan includes details of response & recovery planning in the event of targeted disruption of the Internet.
|-
| 7 April 2015
| [[Paul Kane]]
| Workflow process documents with statistics for each stage of the IANA Root Zone Management Function
| After [https://www.icann.org/en/system/files/files/didp-response-20150407-1-kane-07may15-en.pdf initially responding] that staff would have to consult with all involved parties regarding publication of the information, staff later [https://www.icann.org/resources/pages/20150407-1-2015-05-08-en updated the record] to note that the information had been published
| Initial response cited 1, 2, 3, 6, 8, 9, 10, & 11
|
|-
| 27 April 2015
| James Bridle
| Documents relating to the delegation and operation of [[.io]], including correspondence between ICANN and the delegated authority
| [https://www.icann.org/en/system/files/files/didp-response-20150427-1-bridle-27may15-en.pdf Provided context] but did not produce documents
| 1, 2, 3, 9, & 10
| [[.io]] is an [[Open Use ccTLD]] that was delegated by IANA in 1997, prior to the formation of ICANN, and using IANA's standard procedure for assigning operation of [[ccTLD]]s, as described in [[RFC 1591]]
|-
| 5 June 2015
| [[Flip Petillion]]
| Information & documents regarding the data exposure issues in the new gTLD application and GDD portals that exposed the data of [[.hotel]] applicants and others.
| [https://www.icann.org/en/system/files/files/didp-response-20150605-1-petillion-05jul15-en.pdf Provided a narrative] of the data exposure incident as related through ICANN's public announcements and updates on the issue; did not produce new documents
| 2, 5, 6, 8, & 9
|  
|  
|}
|}


==References==
==References==