<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>I think anyone who supplies someone else's email address to a
      third party without their permission is responsible for any mail
      they receive.  Unless a SWIPer has permission from their customer
      to SWIP the customer's email address, the ISP doing the SWIPing is
      responsible, not ARIN.  If they do this repeatedly or as a matter
      of course, they should be barred from SWIPing and any subnets they
      have previously SWIPed should revert to them, making them
      responsible for all network abuse and connectivity problems
      originating from those subnets.</p>
    <p>Isn't the entire point of SWIP to allow ISPs to offload the abuse
      and other points of contact to their customers, who presumably are
      more capable of dealing with the issues?  And shouldn't the
      customers expect to receive email at those POC addresses as part
      of that?  Either the ISP has explained that to their customers,
      who have agreed to this, in which case no mail sent to them as a
      consequence is SPAM, or  the ISP has not, in which case the POC
      (and SWIP) should be removed or never allowed in the first place.<br>
    </p>
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 4/17/2018 11:11 AM, Christian Tacit
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:9b66580c348c4fb1aaf1598c75724b58@S05-MBX03-12.S05.local">
      <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:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri",sans-serif;
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi
            Jason,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US">After
            discussion with staff, I can report that i</span><span
            lang="EN-US">t would be much easier to send a notification
            to the email that is swipped as the POC but to add in any
            type of ACK or NACK turns it into a very, very heavy lift
            for the organizations as it completely changes the flow.
            Furthemore, the addition of a requirement for a response
            could end up creating issues (whether real or perceived)
            that ARIN would be sending UCE (Unsolicited Commercial
            Email) (SPAM) to all of those contacts as we do not have a
            formal relationship with them.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US">Chris<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:12.0pt;font-family:"Times New
            Roman",serif"><br>
            Christian S. Tacit,<br>
            Tacit Law<br>
            <br>
            P.O. Box 24210 RPO Hazeldean<br>
            Kanata, Ontario<br>
            K2M 2C3 Canada<br>
            <br>
            Tel: +1 613 599 5345<br>
            Fax: +1 613 248 5175<br>
            E-mail: <a href="mailto:ctacit@tacitlaw.com"
              moz-do-not-send="true"><span style="color:#0563C1">ctacit@tacitlaw.com</span></a><br>
            <br>
            This message is intended only for the use of the individual
            or entity to which it is addressed and may contain
            information that is subject to copyright, privileged,
            confidential, proprietary or exempt from disclosure under
            applicable law. If you are not the intended recipient or the
            person responsible for delivering the message to the
            intended recipient, you are strictly prohibited from
            disclosing, distributing, copying or in any way using this
            message. If you have received this communication in error,
            please notify the sender and destroy or delete copies you
            may have received.</span><o:p></o:p></p>
        <p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span
            lang="EN-US"> Jason Schiller <a class="moz-txt-link-rfc2396E" href="mailto:jschiller@google.com"><jschiller@google.com></a>
            <br>
            <b>Sent:</b> April 16, 2018 3:05 PM<br>
            <b>To:</b> Christian Tacit <a class="moz-txt-link-rfc2396E" href="mailto:ctacit@tacitlaw.com"><ctacit@tacitlaw.com></a><br>
            <b>Cc:</b> ARIN-PPML List <a class="moz-txt-link-rfc2396E" href="mailto:arin-ppml@arin.net"><arin-ppml@arin.net></a><br>
            <b>Subject:</b> Re: [arin-ppml] Draft Policy 2017-12:
            Require POC Validation Upon Reassignment<o:p></o:p></span></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div>
          <p class="MsoNormal">Chris,<o:p></o:p></p>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Thanks.  <o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">One of the problems with POC validation
              is that ARIN tries to validate all POCS, and does not have
              a relationship with some.<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">There is a proposal to reduce the
              validation to only the set of POCs that ARIN has a direct
              relationship with.<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">This is problematic because it is
              through this annual validation that one finds they have
              become a POC on some resource.<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal">So without out the annual check, those
              organizations will NOT have the awareness and knowledge to
              resolve that issue between themselves.<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">The solution is a bi-directional
              check.  <o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">I think the ARIN objection is that it
              is problematic for the SWIPee to modify the record of the
              SWIPer.<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal">But I see no problem with the SWIPee
              getting notified, or even ACKing or NACKIing the SWIP.<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">__Jason<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div>
          <div>
            <p class="MsoNormal">On Sat, Apr 14, 2018 at 2:23 PM
              Christian Tacit <<a href="mailto:ctacit@tacitlaw.com"
                moz-do-not-send="true">ctacit@tacitlaw.com</a>>
              wrote:<o:p></o:p></p>
          </div>
          <blockquote style="border:none;border-left:solid #CCCCCC
            1.0pt;padding:0cm 0cm 0cm
            6.0pt;margin-left:4.8pt;margin-right:0cm">
            <div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hi
                  Jason,<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Although
                  I did look into the issue raised by your March 15
                  email promptly after receiving it. I inadvertently
                  forgot to reply to you. Please accept my apology.
                  <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Based
                  on ARIN Staff input, a major impediment to the
                  proposed Section 3.8 is that ARIN cannot be involved
                  in the contractual relationship between its customer
                  and any of the customer’s customers. The ARIN customer
                  may be submitting a simple reassignment, precisely
                  because it wants to maintain control over POC records.
                  Examples may include branches located in different
                  states of an entity that may want to use address
                  information corresponding to its  head office and or
                  other locations in which it has a presence. If there
                  is a dispute with an entity that already has an OrgID
                  with ARIN and its upstream provider on how to register
                  the entity’s reassignments, those organizations will
                  have the awareness and knowledge to resolve that issue
                  between themselves. <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Chris<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
                      lang="EN-US">From:</span></b><span lang="EN-US">
                    Jason Schiller <<a
                      href="mailto:jschiller@google.com" target="_blank"
                      moz-do-not-send="true">jschiller@google.com</a>>
                    <br>
                    <b>Sent:</b> March 15, 2018 4:29 PM<br>
                    <b>To:</b> Christian Tacit <<a
                      href="mailto:ctacit@tacitlaw.com" target="_blank"
                      moz-do-not-send="true">ctacit@tacitlaw.com</a>><br>
                    <b>Cc:</b> <a href="mailto:arin-ppml@arin.net"
                      target="_blank" moz-do-not-send="true">arin-ppml@arin.net</a><br>
                    <b>Subject:</b> Re: [arin-ppml] Draft Policy
                    2017-12: Require POC Validation Upon Reassignment</span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <div>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This
                      problem is not scoped only to with a new POC is
                      created.<o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This
                      was also supposed to be a check in 3.7 to insure a
                      resource is not<o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">randomly
                      SWIP'd to a pre-existing org.<o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">3.8
                      was intended to chatch when a resource is SWIP'd
                      to a pre-existing org, <o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">but
                      that org ID is not used, and that org's address is
                      put into a reassign simple.<o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                  </div>
                  <div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I
                        don't see how this is not implementable..<o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">-
                        If the compnay name is a match for something
                        ARIN already has a relationship with,<o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> 
                        then they should have good contact info.<o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">-
                        If the contact info is a known address of a
                        compnay that ARIN already has a <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> 
                        relationship with, then they should have good
                        contact info for that compnay.<o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">-
                        If all else fails they can send a post card to
                        the mailing address.<o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">At
                        a mimimum, if the post card is undeliverable, or
                        a holder of the the post card<o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">contacts
                        ARIN, they should revoke the SWIP.<o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">___Jason<o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                    </div>
                  </div>
                </div>
                <div>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On
                      Mon, Mar 12, 2018 at 5:47 PM, Christian Tacit <<a
                        href="mailto:ctacit@tacitlaw.com"
                        target="_blank" moz-do-not-send="true">ctacit@tacitlaw.com</a>>
                      wrote:<o:p></o:p></p>
                    <blockquote style="border:none;border-left:solid
                      #CCCCCC 1.0pt;padding:0cm 0cm 0cm
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
                      <div>
                        <div>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif">Dear
                              Community Members,</span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif">The
                              shepherds for the Draft Policy 2017-12:
                              Require POC Validation Upon Reassignment,
                              are making two changes to its text.</span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif">First,
                              the problem statement is being expanded a
                              bit to explain how POCs for reassigned
                              blocks can be assigned without the
                              knowledge of the individuals so assigned
                              under the present policy.</span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif">Second,
                              proposed section 3.8 has been deleted.
                              This is because it is unintentionally
                              misleading
                            </span><span
                              style="font-size:14.0pt;font-family:"Times
                              New Roman",serif;color:black"
                              lang="EN-US">because a simple reassignment
                              results in a customer identifier versus an
                              OrgID.   There is no contact information
                              contained in a simple reassignment other
                              than street address that could be used for
                              notification, and thus it does not appear
                              that the proposed NRPM 3.8 policy text is
                              implementable.  Even if notification were
                              possible, the “OR postal address” in this
                              section may also cause significant
                              problems for some companies as many
                              companies have the same name associated
                              with many different locations and there
                              are several locations that have many
                              companies registered there.</span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif">Based
                              on these changes, the revised text reads:</span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
                          <p
style="margin:0cm;margin-bottom:.0001pt;line-height:18.0pt;background:white"><strong><span
style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:black;border:none
                                windowtext 1.0pt;padding:0cm">Version
                                Date: March 12, 2018</span></strong><o:p></o:p></p>
                          <p
style="margin:0cm;margin-bottom:.0001pt;line-height:18.0pt;background:white"><strong><span
style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:black;border:none
                                windowtext 1.0pt;padding:0cm"> </span></strong><o:p></o:p></p>
                          <p
style="margin:0cm;margin-bottom:.0001pt;line-height:18.0pt;background:white"><strong><span
style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:black;border:none
                                windowtext 1.0pt;padding:0cm">Problem
                                Statement:</span></strong><o:p></o:p></p>
                          <p
style="margin-bottom:6.0pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><span
                              style="font-size:14.0pt;color:black">Some
                              large ISPs assign individuals to be POCs
                              for reassigned blocks without consultation
                              of the individual they are inserting into
                              Whois. For example, during</span><span
                              style="font-size:14.0pt;color:black">
                              <span lang="EN-US">the
                                reassignment/reallocation process, some
                                large ISPs automatically create POCs
                                from their customer’s order form. This
                                process is automated for many ISPs and
                                therefore the resulting POCs are not
                                validated prior to being created in the
                                ARIN Whois database. This creates
                                unknowing POCs that have no idea what
                                Whois is or even who ARIN is at the time
                                they receive the annual POC validation
                                email. It can also create multiple POCs
                                per email address causing that same
                                person to receive a multitude of POC
                                Validation emails each year.</span></span><o:p></o:p></p>
                          <p
                            style="margin-bottom:6.0pt;line-height:18.0pt;background:white"><span
                              style="font-size:14.0pt;color:black">This
                              policy proposal seeks to improve the
                              situation where a POC is unwittingly and
                              unintentionally inserted into Whois.</span><o:p></o:p></p>
                          <p
style="margin-bottom:6.0pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><span
                              style="font-size:14.0pt;color:black">It
                              also seeks to mitigate the significant
                              amount of time that ARIN staff reports
                              that they spend fielding phone calls from
                              POCs who have no idea they are in Whois.</span><o:p></o:p></p>
                          <p
style="margin-bottom:6.0pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><span
                              style="font-size:14.0pt;color:black">Finally,
                              it is hopeful that this proposal will
                              improve the overall POC validation
                              situation, by forcing ISPs and customers
                              to work together to insert proper
                              information into Whois at the time of
                              sub-delegation.</span><o:p></o:p></p>
                          <p
style="margin:0cm;margin-bottom:.0001pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><strong><span
style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:black;border:none
                                windowtext 1.0pt;padding:0cm"> </span></strong><o:p></o:p></p>
                          <p
style="margin:0cm;margin-bottom:.0001pt;line-height:18.0pt;background:white"><strong><span
style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:black;border:none
                                windowtext 1.0pt;padding:0cm">Policy
                                statement:</span></strong><o:p></o:p></p>
                          <p
style="margin-bottom:6.0pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><span
                              style="font-size:14.0pt;color:black">Insert
                              one new section into NRPM 3:</span><o:p></o:p></p>
                          <p
style="margin-bottom:6.0pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><span
                              style="font-size:14.0pt;color:black">3.7
                              New POC Validation Upon Reassignment</span><o:p></o:p></p>
                          <p
style="margin-bottom:6.0pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><span
                              style="font-size:14.0pt;color:black">When
                              an ISP submits a valid reallocation or
                              detailed reassignment request to ARIN
                              which would result in a new POC object
                              being created, ARIN must (before otherwise
                              approving the request) contact the new POC
                              by email for validation. ARIN's
                              notification will, at a minimum, notify
                              the POC of:</span><o:p></o:p></p>
                          <p
style="margin-bottom:6.0pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><span
                              style="font-size:14.0pt;color:black">- the
                              information about the organization
                              submitting the record; and<br>
                              - the resource(s) to which the POC is
                              being attached; and<br>
                              - the organization(s) to which the POC is
                              being attached.</span><o:p></o:p></p>
                          <p
style="margin-bottom:6.0pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><span
                              style="font-size:14.0pt;color:black">If
                              the POC validates the request, the request
                              shall be accepted by ARIN and the new
                              objects inserted into Whois.  If the POC
                              does not validate the request within 10
                              days, ARIN must reject the request.</span><o:p></o:p></p>
                          <p
style="margin:0cm;margin-bottom:.0001pt;line-height:18.0pt;background:white;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px"><strong><span
style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:black;border:none
                                windowtext 1.0pt;padding:0cm"> </span></strong><o:p></o:p></p>
                          <p
style="margin:0cm;margin-bottom:.0001pt;line-height:18.0pt;background:white"><strong><span
style="font-size:14.0pt;font-family:"Calibri",sans-serif;color:black;border:none
                                windowtext 1.0pt;padding:0cm">Timetable
                                for implementation:</span></strong><span
                              style="font-size:14.0pt;color:black"> Immediate</span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif">Comments
                              from the community are welcome!</span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif"> </span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span
style="font-size:14.0pt;font-family:"Times New Roman",serif"><br>
                              Christian S. Tacit</span><o:p></o:p></p>
                          <p class="MsoNormal"
                            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                        </div>
                      </div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
                        _______________________________________________<br>
                        PPML<br>
                        You are receiving this message because you are
                        subscribed to<br>
                        the ARIN Public Policy Mailing List (<a
                          href="mailto:ARIN-PPML@arin.net"
                          target="_blank" moz-do-not-send="true">ARIN-PPML@arin.net</a>).<br>
                        Unsubscribe or manage your mailing list
                        subscription at:<br>
                        <a
                          href="http://lists.arin.net/mailman/listinfo/arin-ppml"
                          target="_blank" moz-do-not-send="true">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
                        Please contact <a href="mailto:info@arin.net"
                          target="_blank" moz-do-not-send="true">info@arin.net</a>
                        if you experience any issues.<o:p></o:p></p>
                    </blockquote>
                  </div>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
                    <br clear="all">
                    <o:p></o:p></p>
                  <div>
                    <p class="MsoNormal"
                      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                  </div>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                    <o:p></o:p></p>
                  <div>
                    <div>
                      <p class="MsoNormal"
                        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                          style="font-family:"Courier
                          New";color:#555555">_______________________________________________________</span><o:p></o:p></p>
                      <div>
                        <p class="MsoNormal"
                          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                            style="font-family:"Courier
                            New";color:black">Jason
                            Schiller|NetOps|<a
                              href="mailto:jschiller@google.com"
                              target="_blank" moz-do-not-send="true">jschiller@google.com</a>|571-266-0006</span><o:p></o:p></p>
                      </div>
                      <div>
                        <p class="MsoNormal"
                          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-family:"Arial",sans-serif;color:black"> </span><o:p></o:p></p>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <p class="MsoNormal"><br clear="all">
          <o:p></o:p></p>
        <div>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
        <p class="MsoNormal">-- <o:p></o:p></p>
        <div>
          <div>
            <p class="MsoNormal"><span style="font-family:"Courier
                New";color:#555555">_______________________________________________________</span><span
style="font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
            <div>
              <p class="MsoNormal"><span
                  style="font-family:"Courier
                  New";color:black">Jason Schiller|NetOps|<a
                    href="mailto:jschiller@google.com" target="_blank"
                    moz-do-not-send="true">jschiller@google.com</a>|571-266-0006</span><span
style="font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
            </div>
            <div>
              <p class="MsoNormal"><span
                  style="font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
John Santos
Evans Griffiths & Hart, Inc.
781-861-0670 ext 539
</pre>
  </body>
</html>