<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle35
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Dear Sub Team Members,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Please see below the action items and discussion notes captured by staff from the meeting on 01 June. <i>These high-level notes are designed to help Work Track Sub Team members navigate through the content of the call and are not a substitute for the chat room or the recording.</i> See the chat room and recording on the meetings pages at: <a href="https://community.icann.org/display/NGSPP/Work+Track+2+Meetings">https://community.icann.org/display/NGSPP/Work+Track+2+Meetings</a>. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Please also see the attached slides and the excerpts from the chat room below.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Julie<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Julie Hedlund, Policy Director<o:p></o:p></span></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Action Items/Discussion Notes 01 June</span></b><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><i><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Discussion on Global Public Interest<o:p></o:p></span></i></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>See the slides at: https://community.icann.org/download/attachments/64950794/SubPro%20Track%202_GPI.pdf?version=1&modificationDate=1496351569155&api=v2<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Slide 2: Explanation of the Subject<o:p></o:p></span></u></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p><span style='text-decoration:none'> </span></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Definition of Global Public Interest "introducing and promoting competition in the registration of domain names where practicable and beneficial to the public interest as identified through the bottom-up, multi-stakeholder policy development process.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Slide 3: GAC Toronto Communique October 2012<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- AGB: Specific role for the GAC to provide early warnings and advice on new gTLD applications that raise public policy issues.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- GAC requested a written briefing from the Board -- how to modify applications as a result of early warnings; how overseen and enforced by ICANN.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Slide 4: Introducing Public Interest Commitments<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- February 2013: PIC Spec -- PICs posted in March 2013 -- 499 PIC specs where received. See: https://newgtlds.icann.org/en/announcements-and-media/announcement-06mar13-en.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Slide 5: Specification 11: Mandatory PICs<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Registry Operator use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Registry Operator agrees to perform the following specific public interest commitments enforceable by ICANN and through the PICDRP.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>[Reading through sections of the PICDRP. See slides 5 and 6.]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Slide 7: Specification 11: Voluntary PICs<o:p></o:p></span></u></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p><span style='text-decoration:none'> </span></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Section 4 of Spec 11.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Were "voluntary" in nature.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- No guidance on what should be in or not.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Types:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Anti-abuse<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Additional RPMs<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Geographic Protections<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Many reserved the right at sole discretion to modify or even eliminate PICs.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Slide 8: Questions and Concerns Related to the Subject<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Global Public Interest wasn't explored that well.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Could be an area of policy development.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Slide 9: Relevant Guidance<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Annex A to the ICANN Board resolution on Planning for Future gTLD Application Rounds (17 November 2014): https://www.icann.org/en/system/files/files/resolutions-annex-a-17nov14-en.pdf.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Slide 10: Rationale for Policy Development<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Not a lot to work with respect to the definition of Global Public Interest.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Slide 11: Questions<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- PICs are not incorporated into policy. Determine what is an adequate "application of 'public interest' analysis as a guideline for evaluation determinations on individual applications."<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>[Reading questions from Slide 11.]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Question: Can someone remind us how the PICs came about? <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- After the GAC issued its early warning -- how to put these obligations in the contract. Fadi suggested PICs as a way to address the GAC's Toronto Communique asking for a mechanism. Beijing Communique had more detail. 499 TLDs submitted PICs so the majority did not. It was top down and that is one of the reasons we are addressing it, whether it should be incorporated into policy.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- The concept was created by ICANN staff/Board to address the issue of how to address concerns raised by some TLDs. The Beijing communique specific TLDs that had public interest issues. That resulted in the mandatory PICs that were applicable to some TLDs. The GAC asked for 8 specific constraints on some TLDs. The Board implemented a subset of that. GAC and ALAC are still taking the position that those were not complete and some TLDs deserved more protection than others. One of the requirements for this PDP to look at. The GAC and ALAC agreed to not take action on existing TLDs with the understanding that it would be considered for subsequent TLDs.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Initially when we heard about the PICs it appeared to be intended to be some time of response to the GAC. That there should be a place to codify it as part of the contract. It went way beyond the GAC. The voluntary PICs had other elements -- apparently the voluntary PICs were open for a very short amount of time and anyone could put anything in there.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Put yourself in the applicant's mindset at the time. Applications are just starting to get evaluated. Some were scared that the GAC would have advice against their TLDs. So they put things in their PICs so governments would view them more favorably. Some of these might not be included in future TLDs. It depends on how we do PICs. Should address the issue of how to respond to GAC early warning and to amend your application as a binding commitment, or should we not?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Share examples of intellectual property rights being enhanced?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- One could argue whether some of these things are "public interest commitments". Don't see anything wrong to have a list and putting them into the contract.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- If the PICs are voluntary how do you evaluate whether they are in the public interest? Address both mandatory and voluntary. Are the mandatory PICs sufficient in protecting the public interest and should they be included in policy?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- GAC and ALAC have stated that there are certain classes of TLDs based on the category numbers the GAC assigned where the current PICs are no sufficient.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- On the mandatory PICs there is work going on to talk about some of these in Spec 11 3b -- conversations between the Public Safety Working Group and the Registries. Clarification on what is required on some of these PICs. 4th one on generic strings (slide 6) depends on where we come out on closed generics. One PICDRP case filed to date. Although they found fraudulent activity by the registry there wasn't much under the contract for ICANN to open a breech notice based on the contract. How the PIC works is more for Work Track 3.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>[Looking back at slides 5-6 -- mandatory PICs.]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Several sessions at ICANN meetings where Tony Harris has expressed concerns about the Spec 11 requirement about only using ICANN-accredited registrars.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- The requirement in the PIC is not to use ICANN-accredited registrars but the ones on the 2013 RAA -- controls that were not in prior RAAs. 2013 RAA added some other requirements on registrars, some of which are relatively expensive. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- In terms of are these mandatory PICs necessary, I don't think we can get rid of #1 -- prohibiting Registered Name Holders from distributing malware, etc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- #1 of Mandatory PICs [reading from the slide]: This was done before the new ICANN Bylaws. May need to evaluate them in light of the new Bylaws. Is this legal or otherwise and consistent with the new ICANN mission.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>-- Believe that the existing PICs were grandfathered into the Bylaws.. See: Section 1.1.d.ii of the Bylaws. Doesn't apply to new contracts or in the process of being signed. Also: 1.1.d.iv is the provision that says "ICANN shall have the ability to negotiate, enter into and enforce agreements, including public interest commitments, with any party in service of its Mission." Action: Should still confirm with Legal.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Rubens Kuhl: Actually, some registries considered including PICs that contradicted parts of the agreement they didn't like, like sunrise protection only for brands. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Rubens Kuhl: Having such a list in a PIC allows people that dislike it to challenge it in a PDDRP. So for any stakeholders, it's better than being listed as a Registry Service. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Jeff Neuman 2: Just TLD Commitments<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Kathy Kleiman 2: And perhaps GAC Commitments<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Rubens Kuhl: Some PICs tried to address ALAC or IO concerns... <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>hil Marano: “The Panel notes that PIC (3)(a) of Specification 11 imposes no obligation on Respondent as the Registry Operator itself to avoid fraudulent and deceptive practices.” See https://www.icann.org/uploads/compliance_notice/attachment/911/serad-to-westerdal-16mar17.pdf <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Kiran Malancharuvil: The PICDRP functionality may be for WT3, but there is a LOT to be learned about the PICs generally from the PICDRP result. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Kiran Malancharuvil: And there have been multiple, filed, only one made it to the panel. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Jeff Neuman 2: @Kiran - Right......when we talk about how the dispute process works, that is for WT3. But the PICs themselves (which are the subject of the dispute) is for us in WT2.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri",sans-serif'>Kurt Pritz: Now that new TLDs are in use: Can anyone point to a potential abusive behavior that was prevented by a PIC? (I.e., has there been an abuse in a TLD (that didn’t receive Type 1 GAC Advice) that might have been replicated by a GAC Advice Type 1 TLD?) - or - Can anyone point to an abuse by a GAC Advice Type 1 TLD that could be avoided by enhanced PIC Specs? If the answer to both of these is no, we should question the benefit of having the PIC Specs.<o:p></o:p></span></p></div></body></html>