<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>The AC has recently been discussing this draft policy and noted
      that we have not heard from the community since this new text has
      been posted.  We would like to hear from you on if we should move
      this policy to recommended.  <br>
    </p>
    <p><br>
    </p>
    <p>I believe the new text fixes the discrepancy, for initial ISP
      allocations, which depends on if the organization initially
      applies under section4 or section8.  This policy fixes this issue
      in section4 by requiring the same documentation (as required under
      the section8 transfer policy) for a new ISP requesting a block
      larger than a /24.<br>
    </p>
    <p>I support this draft policy.<br>
    </p>
    <p><br>
    </p>
    <p>Thanks,</p>
    <p>Andrew<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 6/23/2018 1:18 PM, Kerrie
      Vassall-Richards wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGPa=cfkUFF3DonoFBGR7jjvMF+QOLAqqgvaA2hd0QM7wec3zw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div dir="ltr">
        <ol>
          <li><b>Clarification to ISP initial allocation and permit
              renumbering</b><br>
          </li>
          <li>Proposal Originator<br>
          </li>
          <ul>
            <li>name: Jason Schiller</li>
            <li>email: <a rel="nofollow" class="external gmail-text"
                href="mailto:jschiller@google.com"
style="background:url("data:image/gif;base64,R0lGODlhEAAQAKUlAE5OTmSh5e43IPBEL/JhT6Ojo4Kz6o298LHQ8rbT87nV873X9L7Y9MLa9cXc9cne9srf9tDj99Hj99bm+Nrp+dzq+d3q+d/s+uHt+uTu+ujx++ny++vz/O30/PD2/PL3/fX5/fn7/vz9/v7+/+0XF////////////////////////////////////////////////////////////////////////////////////////////////////////////yH5BAEAAD8ALAAAAAAQABAAAAZewJ9wSCwaj8gkscBsOpsAYaFEpYpAnUwlcoj+ptVRyKO5EAZdaSlgCLg5mMlAkP5Wr1lKxLGoT9luBhYSDwwJfiViHxsXExANCgh+B5SVlpReBQCbnJ2cSqChoqNFQQA7")
                100% 50%
no-repeat;text-decoration-line:none;color:rgb(51,102,187);padding-right:18px"
                moz-do-not-send="true">jschiller@google.com</a></li>
            <li>telephone: 202-258-8863</li>
            <li>organization: Google LLC</li>
          </ul>
          <li>Date: 02/01/2017<br>
          </li>
          <li><b>Problem Statement:</b><br>
          </li>
        </ol>
        <p style="margin:1em
0px;color:rgb(0,0,0);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial">As
          discussed in more detail in ARIN-2017-9 and noted in the ARIN
          40 Policy Experience Report, the criteria to qualify for an
          initial block of address space in 4.2.2 and 8.5.4 are seeming
          at odds with each other. At ARIN 41 the community seemed to
          prefer the approach contained in this policy over the approach
          in ARIN-2017-9, which was subsequently abandoned.  <br>
          <br>
          Moreover, as the NRPM (2018-1) currently sits, 4.2.2 appears
          to state that an initial allocation of up to a /21 could be
          granted without any more justification than needed to qualify
          for a /24. Therefore, 4.2.2 should be modified, allowing an
          initial allocation of only a /24 without any additional
          justification and allowing an initial allocation of up to a
          /21 when justified by a 24-month allocation plan.</p>
        <p style="margin:1em
0px;color:rgb(0,0,0);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial"><b>Policy
            Statement:</b></p>
        <p style="margin:1em
0px;color:rgb(0,0,0);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial">Replace
          the current Section 4.2.2 with:<br>
          <br>
          4.2.2. Initial allocation to ISPs<br>
          <br>
          All ISP organizations without direct assignments or
          allocations from ARIN qualify for an initial allocation of up
          to a /21, subject to ARIN's minimum allocation size.<br>
          <br>
          All ISP organizations without direct allocations, direct
          assignments, re-allocations or reassignments automatically
          qualify for a /24. These organizations are exempt from
          requirements of showing the efficient utilization of
          previously held IPv4 space. These organizations may qualify
          for a larger than a /24 by documenting how the requested
          allocation will be utilized within the request size specified
          in 4.2.4.3</p>
        <p style="margin:1em
0px;color:rgb(0,0,0);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial">ISPs
          holding re-allocations and/or reassignments must show the
          efficient utilization of their resources consistent with the
          requirements in sections 4.2.3 and 4.2.4<br>
           </p>
        <p style="margin:1em
0px;color:rgb(0,0,0);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial"><b>Comments:</b></p>
        <p style="margin:1em
0px;color:rgb(0,0,0);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial">The
          timetable for Implementation: Immediate</p>
        <p style="margin:1em
0px;color:rgb(0,0,0);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial"><b>Anything
            Else:</b></p>
        <p style="margin:1em
0px;color:rgb(0,0,0);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial">This
          is an attempt to clarify the changes that came about from
          2016-4.<br>
          It also aligns section 4.2 with current transfer policy.<br>
          It also re-established the understanding that ISP can renumber
          and return, but putting the last section 4.2.2.1.4 into the
          ISP additional requests section. This text is slightly
          modified to include returns to ARIN in addition to returns to
          the upstream.</p>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
ARIN-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="https://lists.arin.net/mailman/listinfo/arin-ppml">https://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>
  </body>
</html>