<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Don,<br>
      Has anyone circulated a U.S. DMCA form so that people in the PPSAI
      can see one before adopting this recommendation?<br>
      Best,<br>
      Kathy<br>
      :<br>
    </div>
    <blockquote cite="mid:CFC7342A.605A7%25dblumenthal@pir.org"
      type="cite">
      <meta http-equiv="Context-Type" content="text/html;
        charset=Windows-1252">
      <div>
        <p class="MsoNormal">I shortened the description but didn&#8217;t make
          substantive changes.</p>
        <p class="MsoNormal"><span><br>
          </span></p>
        <p class="MsoNormal"><span>The WG recommends that the
            requirements concerning forms of alleged malicious conduct
            that would be covered by a providers's designated published
            point of contact should include a list of forms of conduct
            that would need to be covered. At the same time these
            requirements should&nbsp;</span><span>allow for the flexibility
            to accommodate new types of malicious conduct. Section 3 of
            the Public Interest Commitments (PIC) Specification in the
            New gTLD Registry Agreement<a moz-do-not-send="true"
              name="_ftnref1" title=""><span
                class="MsoFootnoteReference"><span
                  class="MsoFootnoteReference">[1]</span></span></a>&nbsp;or
            Safeguard 2, Annex 1 of the GAC&#8217;s Beijing Communique<a
              moz-do-not-send="true" name="_ftnref2" title=""><span
                class="MsoFootnoteReference"><span
                  class="MsoFootnoteReference">[2]</span></span></a>&nbsp;could
            serve as examples for how this could be achieved.</span><span></span></p>
        <span>Furthermore, the WG recommends standardizing reporting
          forms, which would nonetheless continue to include space for
          free form text. A starting point for such a form could be that
          used under the Digital Millennium Copyright Act (DMCA) in the
          United States. At a minimum such a form should include: [<span>to
            be completed</span>]. It was also suggested that providers
          have the ability to &#8220;categorize&#8221; reports received, in order to
          facilitate responsiveness.</span>
        <div><br>
          <hr width="33%">
          <div id="ftn1">
            <p class="MsoFootnoteText"><a moz-do-not-send="true"
                name="_ftn1" title=""><span class="MsoFootnoteReference"><span><span
                      class="MsoFootnoteReference"><span>[1]</span></span></span></span></a><span>&nbsp;Registry

                Operator will include a provision in its
                Registry-Registrar Agreement that requires Registrars to
                include in their Registration Agreements a provision
                prohibiting Registered Name Holders from distributing
                malware, abusively operating botnets, phishing, piracy,
                trademark or copyright infringement, fraudulent or
                deceptive practices, counterfeiting or otherwise
                engaging in activity contrary to applicable law, and
                providing (consistent with applicable law and any
                related procedures) consequences for such activities
                including suspension of the domain name.</span></p>
          </div>
          <div id="ftn2">
            <p class="MsoFootnoteText">
              <a moz-do-not-send="true" name="_ftn2" title=""><span
                  class="MsoFootnoteReference"><span><span
                      class="MsoFootnoteReference"><span>[2]</span></span></span></span></a><span>&nbsp;Registry

                Operator will include a provision in its
                Registry-Registrar Agreement that requires Registrars to
                include in their Registration Agreements a provision
                prohibiting Registered Name Holders from distributing
                malware, abusively operating botnets, phishing, piracy,
                trademark or copyright infringement, fraudulent or
                deceptive practices, counterfeiting or otherwise
                engaging in activity contrary to applicable law, and
                providing (consistent with applicable law and any
                related procedures) consequences for such activities
                including suspension of the domain name.</span></p>
            <p class="MsoFootnoteText">
              <span>===================</span></p>
          </div>
        </div>
      </div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <div>
          <span>From: </span>Marika Konings &lt;<a
            moz-do-not-send="true"
            href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>&gt;<br>
          <span>Date: </span>Wednesday, June 18, 2014 at 10:09 AM<br>
          <span>To: </span>PPSAI &lt;<a moz-do-not-send="true"
            href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>&gt;<br>
          <span>Subject: </span>[Gnso-ppsai-pdp-wg] For your review -
          updated template Cat D - Q4<br>
        </div>
        <div><br>
        </div>
        <div>
          <meta name="Title" content="">
          <meta name="Keywords" content="">
          <meta name="ProgId" content="Word.Document">
          <meta name="Generator" content="Microsoft Word 14">
          <meta name="Originator" content="Microsoft Word 14">
          <div>
            <div>Dear All,</div>
            <div><br>
            </div>
            <div>Following yesterday's meeting, please find attached the
              updated template for Cat D &#8211; Q 4 attached for your review.
              Based on our discussions, the proposed preliminary
              recommendation has been updated as follows:</div>
            <div><br>
            </div>
            <div>===============</div>
            <div>
              <p class="MsoNormal"><span>The WG recommends that the
                  requirements in relation to which forms of alleged
                  malicious conduct would be covered by the designated
                  published point of contact at an ICANN-accredited
                  privacy/proxy service provider include an indicative
                  list of forms of malicious conduct that would need to
                  be covered while at the same time these requirements
                  should
                </span><span>allow for enough flexibility to accommodate
                  new types of malicious conduct being covered. Section
                  3 of the Public Interest Commitments (PIC)
                  Specification in the New gTLD Registry Agreement<a
                    moz-do-not-send="true" name="_ftnref1" title=""><span
                      class="MsoFootnoteReference"><span
                        class="MsoFootnoteReference">[1]</span></span></a>
                  or Safeguard 2, Annex 1 of the GAC&#8217;s Beijing
                  Communique<a moz-do-not-send="true" name="_ftnref2"
                    title=""><span class="MsoFootnoteReference"><span
                        class="MsoFootnoteReference">[2]</span></span></a>
                  could serve as examples for how this could be
                  achieved.</span><span></span></p>
              <span>Furthermore, the WG recommends standardizing
                reporting forms, which would nonetheless continue to
                include space for free form text. A starting point for
                such a form could be that used under the Digital
                Millennium Copyright Act (DMCA) in the United States. At
                a minimum such a form should include: [<span>to be
                  completed</span>]. It was also suggested that
                providers have the ability to &#8220;categorize&#8221; reports
                received, in order to facilitate responsiveness.
              </span>
              <div><br>
                <hr width="33%">
                <div id="ftn1">
                  <p class="MsoFootnoteText"><a moz-do-not-send="true"
                      name="_ftn1" title=""><span
                        class="MsoFootnoteReference"><span><span
                            class="MsoFootnoteReference"><span>[1]</span></span></span></span></a><span>
                      Registry Operator will include a provision in its
                      Registry-Registrar Agreement that requires
                      Registrars to include in their Registration
                      Agreements a provision prohibiting Registered Name
                      Holders from distributing malware, abusively
                      operating botnets, phishing, piracy, trademark or
                      copyright infringement, fraudulent or deceptive
                      practices, counterfeiting or otherwise engaging in
                      activity contrary to applicable law, and providing
                      (consistent with applicable law and any related
                      procedures) consequences for such activities
                      including suspension of the domain name.</span></p>
                </div>
                <div id="ftn2">
                  <p class="MsoFootnoteText">
                    <a moz-do-not-send="true" name="_ftn2" title=""><span
                        class="MsoFootnoteReference"><span><span
                            class="MsoFootnoteReference"><span>[2]</span></span></span></span></a><span>
                      Registry Operator will include a provision in its
                      Registry-Registrar Agreement that requires
                      Registrars to include in their Registration
                      Agreements a provision prohibiting Registered Name
                      Holders from distributing malware, abusively
                      operating botnets, phishing, piracy, trademark or
                      copyright infringement, fraudulent or deceptive
                      practices, counterfeiting or otherwise engaging in
                      activity contrary to applicable law, and providing
                      (consistent with applicable law and any related
                      procedures) consequences for such activities
                      including suspension of the domain name.</span></p>
                  <p class="MsoFootnoteText">
                    <span>===================</span></p>
                  <p class="MsoFootnoteText">
                    <br>
                  </p>
                  <p class="MsoFootnoteText">You are encouraged to share
                    any comments / edits you may have with the mailing
                    list.</p>
                  <p class="MsoFootnoteText"><br>
                  </p>
                  <p class="MsoFootnoteText">Best regards,</p>
                  <p class="MsoFootnoteText"><br>
                  </p>
                  <p class="MsoFootnoteText">Marika</p>
                </div>
              </div>
            </div>
          </div>
        </div>
      </span>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></pre>
    </blockquote>
    <br>
  </body>
</html>