<html><head><base href="x-msg://384/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><b>P3. </b> <div><br></div><div>I think Approach 3 (the TMCH sends the notice) best meets the stated business requirements of existing business relationship and verifiably of transmission. I think the Registry should advise the TMCH that the domain was registered, and the TMCH should then advise the trademark holder. I think the least attractive option is Approach 2 (Registrar provides the notice).</div><div><div><br></div><div><b>P5.</b> <br><div><br></div><div>I think Approach 1 (Registry performs the check) best meets the business requirements. Having the Registry check will simplify implementation and compliance issues (whether the Claims process is realtime or offline). It's worth noting that the applicable Registry and Registrar will be in communication for the relevant domain regardless of who is responsible for the check. As such, I don't believe making the Registry responsible for the check introduces communications inefficiencies.</div><div><br></div><div>Look forward to the next group discussion.</div><div><br></div><div>Richard Tindal</div><div>Donuts Inc.</div><div><br><div><br></div><div><br></div><div><br><div><div>On Dec 7, 2011, at 11:44 AM, Karen Lentz wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Dear Colleagues,<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Thanks again for the useful submissions and participation on the last IAG call on 30 November. <span class="Apple-converted-space"> </span><br><br>For those who were not able to attend, materials from the call are posted<br>at<span class="Apple-converted-space"> </span><a href="https://community.icann.org/display/cctrdmrkclrnghsiag/Home" style="color: blue; text-decoration: underline; ">https://community.icann.org/display/cctrdmrkclrnghsiag/Home</a>, including<br>slides, documents, chat transcript and audio recording.<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Note that any follow up submissions on the issues P1 and P2 are due by<span class="Apple-converted-space"> </span><b>Monday,</b><span class="Apple-converted-space"> </span><b>12 December</b>. We’ll provide a brief update to those 2 issues after review of all the materials.<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><b>Schedule<o:p></o:p></b></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">For the call schedule going forward, note that there are 2 tracks that will proceed in parallel: the process track (focusing on business process development, as now underway) and the technical track (focusing on technical implementation issues).<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Therefore, on 16 December, there will be 2 calls taking place:<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; "><span>1.<span style="font: normal normal normal 7pt/normal 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span>Process call (issues P3 and P5) at<span class="Apple-converted-space"> </span><b>13:00 UTC</b>.<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; "><span>2.<span style="font: normal normal normal 7pt/normal 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span>Technical call (issues T1 and T3) at<span class="Apple-converted-space"> </span><b>16:00 UTC</b>.<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Both calls are scheduled for 90 minutes and will use the existing dial-in number and Adobe Connect room.<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">You may choose to attend both calls, if you wish, or focus only on one you are interested in. The relevant documents for both are attached.<br><br><o:p></o:p></div><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 12pt; font-size: 11pt; font-family: Calibri, sans-serif; "><b>Process Track<o:p></o:p></b></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 12pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Issue# P3 (Responsibility for Trademark Holder Registration Notice)<o:p></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 12pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Issue# P5 (Responsibility to Perform Trademark Claims Checks)<o:p></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 12pt; font-size: 11pt; font-family: Calibri, sans-serif; ">We will discuss these topics, informed by your written comments, on the<span class="Apple-converted-space"> </span><b>16 Dec call</b>. Please submit your written comments to these issues by<span class="Apple-converted-space"> </span><b>13 Dec 2011</b><span class="Apple-converted-space"> </span>(23:59 UTC) to the mailing list.<br><br>As discussed previously, we are ultimately seeking your recommendations<br>for either (1) one of the proposed options in the document or (2) your<br>suggestions for alternatives that you believe to be more attractive and<br>that should be considered.<br><br>In your written comments, please make sure to indicate: (a) the issue<br>number (P3 or P5), (b) the recommended option or alternative for the issue,<br>(c) rationale (consideration of advantages and how any disadvantages could<br>be minimized) and (d) any other comments.<br><br><b>Technical Track</b><o:p></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 12pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Issue# T1 (Data Locations)<o:p></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 12pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Issue# T3 (Communication Protocols)<o:p></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 12pt; font-size: 11pt; font-family: Calibri, sans-serif; ">We will discuss these topics, informed by your written comments, on the<span class="Apple-converted-space"> </span><b>16 Dec call</b>. Please submit your written comments to these issues by<span class="Apple-converted-space"> </span><b>13 Dec 2011</b><span class="Apple-converted-space"> </span>(23:59) UTC to the mailing list.<br><br>We are ultimately seeking your recommendations for either (1) one of the<br>proposed options in the document or (2) your suggestions for alternatives<br>that you believe to be more attractive and that should be considered.<br><br>In your written comments, please make sure to indicate: (a) the issue<br>number (T1 or T3), (b) the recommended option or alternative for the issue,<br>(c) rationale (consideration of advantages and how any disadvantages could<br>be minimized) and (d) any other comments.<br><br>We look forward to hearing from you.<br><br>Karen Lentz<br>ICANN<br><br><o:p></o:p></p><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><br><br><o:p></o:p></div></div><span><IAG-issue_T1.pdf></span><span><IAG-issue_T3.pdf></span><span><IAG-issue_P5.pdf></span><span><IAG-issue_P3.pdf></span>_______________________________________________<br>tmch-iag mailing list<br><a href="mailto:tmch-iag@icann.org" style="color: blue; text-decoration: underline; ">tmch-iag@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/tmch-iag" style="color: blue; text-decoration: underline; ">https://mm.icann.org/mailman/listinfo/tmch-iag</a><br></div></span></blockquote></div><br></div></div></div></div></body></html>