<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">+1.<div class=""><br class=""></div><div class="">Well said, Andrew.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 14, 2015, at 11:25 , Andrew Dul <<a href="mailto:andrew.dul@quark.net" class="">andrew.dul@quark.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
  
    <meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
  
  <div bgcolor="#FFFFFF" text="#000000" class="">
    I don't think we want to have a policy where we give out an ipv6 /48
    per ipv4 /24.  I'm all for giving people the space they need, but v6
    is a different mindset than v4.   A /48 per site has generally been
    the goal of most ipv6 policies.<br class="">
    <br class="">
    Andrew<br class="">
    <br class="">
    <div class="moz-cite-prefix">On 8/11/2015 3:05 PM, Alfie Cleveland
      wrote:<br class="">
    </div>
    <blockquote cite="mid:408F4B53-FCC7-4ACE-B4F3-8044EC134E44@me.com" type="cite" class="">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252" class="">
      John -
      <div class=""><br class="">
      </div>
      <div class="">Apologies if I wasn’t entirely clear. As referenced
        in Section 9.3.1. of the APNIC INPP, I propose that this also
        applies to end users - allowing end users to, free of charge,
        receive a /48 for each /24 they hold.</div>
      <div class=""><br class="">
      </div>
      <div class="">Regards,</div>
      <div class="">Alfie</div>
      <div class=""><br class="">
      </div>
      <div class=""><br class="">
      </div>
      <div style="" class="">
        <blockquote type="cite" class="">
          <div class="">On 11 Aug 2015, at 23:01, John Curran <<a moz-do-not-send="true" href="mailto:jcurran@arin.net" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:jcurran@arin.net">jcurran@arin.net</a>> wrote:</div>
          <br class="Apple-interchange-newline">
          <div class="">
            <meta http-equiv="Content-Type" content="text/html;
              charset=windows-1252" class="">
            <div style="word-wrap: break-word; -webkit-nbsp-mode: space;
              -webkit-line-break: after-white-space;" class="">
              On Aug 11, 2015, at 4:43 PM, Alfie Cleveland <<a moz-do-not-send="true" href="mailto:alfeh@me.com" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:alfeh@me.com">alfeh@me.com</a>> wrote:<br class="">
              <div class="">
                <blockquote type="cite" class=""><br class="Apple-interchange-newline">
                  <div class="">
                    <div style="word-wrap: break-word;
                      -webkit-nbsp-mode: space; -webkit-line-break:
                      after-white-space;" class="">
                      Hello,
                      <div class=""><br class="">
                      </div>
                      <div class="">I’m requesting comment in regards to
                        automatically make organisations eligible for
                        IPv6 if they hold justified IPv4 space. This
                        similar to  <span style="font-family: arial,
                          helvetica, sans-serif; line-height: 18px;
                          background-color: rgb(255, 255, 255);" class="">Section 9.3.1. of the [APNIC-127]
                          APNIC Internet Number Resource Policies. I
                          feel that if organisations were able to
                          receive a /48 for each /24 they hold, then it
                          would help expedite the rollout of IPv6.
                          Organisations currently have two choices -
                          continue to use IPv4, or spend valuable time
                          on applying for IPv6 space. IPv6 space is
                          clearly in abundance - and this could
                          potentially help slow the exhaustion of IPv4.</span></div>
                    </div>
                  </div>
                </blockquote>
                <br class="">
              </div>
              <div class=""><br class="">
              </div>
              <div class="">Alfie -</div>
              <div class=""><br class="">
              </div>
              <div class="">Per NRPM 6.5.2.2, an ISP qualifies for an
                IPv6 allocation if they have a previously justified IPv4
                ISP </div>
              <div class="">allocation from ARIN (or one of its
                predecessor registries), or can qualify for an IPv4 ISP
                allocation </div>
              <div class="">under current criteria; i.e.  this means
                that they presently are automatically eligible for IPv6
                if they </div>
              <div class="">hold IPv4 space, as you suggest above.</div>
              <div class=""><br class="">
              </div>
              <div class="">Perhaps you are proposing that there be a
                default automatic size of IPv6 allocation ("a /48 for
                each</div>
              <div class="">/24 they hold”) which would allow for more
                expeditious preparation of IPv6 initial requests, for
                those </div>
              <div class="">who choose to receive this default
                allocation size rather than calculating the "smallest
                nibble-boundary </div>
              <div class="">aligned block that can provide an equally
                sized nibble-boundary aligned block to each of the
                requesters </div>
              <div class="">serving sites large enough to satisfy the
                needs of the requesters largest single serving site
                using no </div>
              <div class="">more than 75% of the available addresses”?  </div>
              <div class=""><br class="">
              </div>
              <div class="">/John</div>
              <div class=""><br class="">
              </div>
              <div class="">John Curran</div>
              <div class="">President and CEO</div>
              <div class="">ARIN</div>
              <div class=""><br class="">
              </div>
            </div>
          </div>
        </blockquote>
      </div>
      <br class="">
      <br class="">
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br class="">
      <pre wrap="" class="">_______________________________________________
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 class="">
  </div>

_______________________________________________<br class="">PPML<br class="">You are receiving this message because you are subscribed to<br class="">the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="">ARIN-PPML@arin.net</a>).<br class="">Unsubscribe or manage your mailing list subscription at:<br class=""><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" class="">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="">Please contact info@arin.net if you experience any issues.</div></blockquote></div><br class=""></div></body></html>