Re: [gnso-thickwhoispdp-wg] Feedback concerning legal review
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">hi all,<div><br></div><div>i'm with Don (although i'm connecting the dots on a few of his typos) ;-)</div><div><br></div><div>i've attached the latest "state of the proposal" draft to this note. i was kinda holding off until Marika had a chance to talk to Legal, but now seems like the time to push it along.</div><div><br></div><div>in this draft, we're asking that (what is probably a routine) legal review be conducted during the implementation project. we're also specifying that the legal review include a focused look at issues that arise from the transition from thin to thick (implied meaning -- we couldn't find any, but we would like another set of eyes). we're also specifying that they consult with heavy-duty experts, again to ensure that the review is rigorous. finally, and this is the new bit, we are specifying that **IF** policy issues turn up, that staff hands them back to the GNSO (in the form of the Implementation Review Team) to be addressed, rather than trying to solve them on their own. </div><div><br></div><div>i think there will be a day when we won't have to be so specific about these things, or to Alan's point even have to mention them. but given the recent issues in the new gTLD implementation -- some of which led to the Policy and Implementation PDP, i think it's prudent that we are very specific in our instructions in this case. i agree with Don, we're not asking for individual advice -- we are asking for a certain level of rigor and followthrough on behalf of ICANN, not individuals.</div><div><br></div><div>i'm also a bit underwhelmed by the EWG language, but that's a topic for another setting.</div><div><br></div><div>thanks again Marika,</div><div><br></div><div>mikey</div><div><br></div><div></div></body></html> Attachment:
Thick Whois -- Proposal - WG 10-Oct v1.doc <html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div></div><div><br></div><div><br></div><div><br></div><div><div><div>On Oct 9, 2013, at 5:50 PM, Don Blumenthal <<a href="mailto:dblumenthal@xxxxxxx";>dblumenthal@xxxxxxx</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "> <div>Marika,</div> <div><br> </div> <div>Thanks very much. I really appreciate your follow up.</div> <div><br> </div> <div>I'm concerned that the GC's office misunderstands what the WG is considering, or at least what I think is on the table. What's needed is a systematic analysis of how data protection legal regimes might affect transition decisions, not detailed legal analyses of laws as they apply to individual parties. For example, are there are aren't there enough potential roadblocks to transition to affect any decisions? Will so many parties use the ICANN procedures that transition becomes pointless (that assumes that the processes listed are relevant to our issues at all. I'm not sure that they are but need more time to ponder).</div> <div><br> </div> <div>It has been clear that privacy has been a big part of the EWG's focus, and having the memo is very useful. It generally is the type of document that I see coming out of the legal review that we have discussed. I would focus the issues more on WG matters, obviously. More importantly in a way, I expect a product that takes advantage of data protection law expertise outside GC and that also does a much more thorough cataloguing of different national and international approaches. It does the usual pass through the US, EU, and Canada. How about APEC (Asia Pacific Economic Cooperation), Brazil, India, the Philippines, China, and many more DP regimes that I could mention? In fairness, the memo mentions "Asia" briefly but gives no details on the reference.</div> <div><br> </div> <div>Don</div> <div><br> </div> <span id="OLK_SRC_BODY_SECTION"> <div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223); "> <span style="font-weight:bold">From: </span>Marika Konings <<a href="mailto:marika.konings@xxxxxxxxx";>marika.konings@xxxxxxxxx</a>><br> <span style="font-weight:bold">Date: </span>Wednesday, October 9, 2013 4:38 PM<br> <span style="font-weight:bold">To: </span>Thick Thin PDP <<a href="mailto:gnso-thickwhoispdp-wg@xxxxxxxxx";>gnso-thickwhoispdp-wg@xxxxxxxxx</a>><br> <span style="font-weight:bold">Subject: </span>[gnso-thickwhoispdp-wg] Feedback concerning legal review<br> </div> <div><br> </div> <div> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "> <div>Dear All,</div> <span id="OLK_SRC_BODY_SECTION"> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; "> <div><br> </div> <div>Following our meeting yesterday, I spoke to my colleagues in the legal team and wanted to clarify some things in relation to the possible 'legal review'. As I've mentioned before, they are kept in the loop throughout the working group discussions which already allows them to raise any potential red flags during that part of the process as well as during the implementation process. However, their main focus is on assuring that any policy recommendations do not conflict or contradict any existing ICANN policies or legal requirements applicable to ICANN. They are not in a position to provide advice to individual parties in different jurisdictions on whether or not the proposed policy recommendations are in potential violation of local laws. This is the responsibility of the party affected and as most of you know there are several mechanisms in place by which the affected party can work with ICANN to request an exemption (see for example <a href="http://www.icann.org/en/resources/registrars/whois-policies-provisions#2";>http://www.icann.org/en/resources/registrars/whois-policies-provisions#2</a> and <a href="http://www.icann.org/en/resources/registrars/updates/retention/waiver-request-process";>http://www.icann.org/en/resources/registrars/updates/retention/waiver-request-process</a>).</div> <div><br> </div> <div>Separately, I wanted to share with you the attached memo that has been prepared for the EWG concerning data protection considerations applicable for the collection of gTLD registration data in the Proposed Centralized and Federated Database Systems. Although this is not specific to our discussion on thick vs. thin, it does hopefully show that data protection and privacy considerations are seriously considered in other efforts that are dealing with Whois. Also, there is a specific section on restrictions on personal data transfer which may help inform the development of the implementation plan and any potential safeguards that may need to be considered.</div> <div><br> </div> <div>Best regards,</div> <div><br> </div> <div>Marika</div> </div> </span><link rel="File-List" href="file:///Users/marika/Library/Caches/TemporaryItems/msoclip/0/clip_filelist.xml"><link rel="themeData" href="file:///Users/marika/Library/Caches/TemporaryItems/msoclip/0/clip_themedata.xml"><style> <!-- /* Font Definitions */ @font-face {font-family:Arial; panose-1:2 11 6 4 2 2 2 2 2 4; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:-536859905 -1073711037 9 0 511 0;} @font-face {font-family:Arial; panose-1:2 11 6 4 2 2 2 2 2 4; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:-536859905 -1073711037 9 0 511 0;} @font-face {font-family:"Arial Unicode MS"; panose-1:2 11 6 4 2 2 2 2 2 4; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:-134238209 -371195905 63 0 4129279 0;} @font-face {font-family:DFKai-SB; mso-font-charset:136; mso-generic-font-family:script; mso-font-pitch:fixed; mso-font-signature:3 135135232 22 0 1048577 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; mso-bidi-font-size:10.0pt; font-family:"Times New Roman"; mso-fareast-font-family:DFKai-SB; mso-fareast-language:ZH-CN;} p.Letterhead, li.Letterhead, div.Letterhead {mso-style-name:Letterhead; mso-style-unhide:no; margin:0cm; margin-bottom:.0001pt; text-align:right; line-height:12.0pt; mso-line-height-rule:exactly; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Arial Unicode MS"; mso-fareast-language:ZH-CN;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt; mso-fareast-language:ZH-CN;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 90.0pt 72.0pt 90.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} --> </style></div> </div> </span> </div> </blockquote></div><br><div apple-content-edited="true"> <br class="Apple-interchange-newline"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">PHONE: 651-647-6109, FAX: 866-280-2356, WEB: <a href="http://www.haven2.com";>www.haven2.com</a>, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)</span> </div> <br></div></body></html> Attachment:
smime.p7s
|