<div dir="ltr"><div dir="ltr">On Mon, Jan 13, 2020 at 9:06 AM Andrew Dul <<a href="mailto:andrew.dul@quark.net">andrew.dul@quark.net</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Happy New Year everyone...</p>
<p>We had a robust discussion on this list before the New Year, but
it was clear that we don't have consensus on the current draft.
Thus to help move this draft forward... I'm proposing a couple of
questions to see if we can find middle ground here to update the
text of the draft policy. <br>
</p>
<p>The policy as written today would require organizations who wish
to obtain an IPv4 transfer to complete a limited scope IPv6
deployment.</p>
<p>Do you support any IPv6 requirements on an IPv4 transfer?</p></div></blockquote><div><br></div><div>Most definitely not. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<p>Would you support IPv6 requirements for receiving a block via the
ARIN wait-list?</p>
<p>Do you support different IPv6 deployment criteria that would
qualify an organization for a IPv4 transfer? (Such as, just
requiring the org to have an IPv6 allocation or assignment from
ARIN) Please propose different IPv6 criteria that you would
support if the current criteria is unacceptable. <br></p></div></blockquote><div><br></div><div>I'm not categorically opposed to IPv6 requirements tied to waitlist allocations, but I'm skeptical that there is any set of requirements that ARIN could impose that would be fully enforceable, meaningful in enough cases to drive adoption, and not onerous.</div><div><br></div><div>Requiring an IPv6 allocation/assignment, or even requiring someone to route an IPv6 block, wouldn't drive adoption enough to be meaningful.</div><div><br></div><div>-Scott</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><p>
</p>
<p><br>
</p>
<p>Thanks for your comments on this draft,</p>
<p>Andrew</p>
<p><br>
</p>
<p>=== <br>
</p>
<p><strong>Current Policy Statement:</strong></p>
<p>In section 8.5.2, add the following language to the end of the
paragraph entitled “Operational Use”:</p>
<p>Such operational network must at minimum include an allocation or
assignment by ARIN of IPv6 address space under the same Org ID
receiving the transferred IPv4 space. Such Org must be able to
prove this IPv6 space is being routed by using it to communicate
with ARIN.</p>
<p>In the event the receiver provides a written statement from its
upstream that IPv6 connectivity is unavailable, the IPv6
requirement may be waived.</p>
<p>===<br>
</p>
</div>
_______________________________________________<br>
ARIN-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">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div></div>