100% IPv6 deployment is an utopia and will not happen not even in the next decade for various reasons, therefore IPv4 is still needed for for basic CGNAT, 464XLAT and other techniques that allows an ISPs or End Users to exist in the Internet, therefore it is always better for more people can receive the bare minimum IPv4 to operate during this long interim.

I like the idea of demonstrate IPv6 deployment in order to receive a new IPv4 allocation, but not sure what is the most appropriate way the RIR can do that. Perhaps having a way is something to be taken with high consideration.

Regards
Fernando

On 16/05/2019 11:48, Jimmy Hess wrote:
On Thu, May 16, 2019 at 9:27 AM John Curran <[email protected]> wrote:

Perhaps, one could say: that both the Marketplace and the Waitlist
are harmful to exist, since they discourage using IPv6 instead
by providing a "tempting solution" to the run-out situation that is not really a
solution --- the registry operating in an abnormal way where a major
set of number resources can only be transferred from existing holders...
not "freshly allocated" likely encourages fraud.

100% IPv6 deployment should alleviate the v4 registry issues
(by eliminating the utility for v4 space) and thus remove
potential incentives for bad actors.

Perhaps it would make sense to have a requirement such
as "Demonstrate matching IPv6 deployment for all previous
allocations,  and materialized plans for IPv6 deployment in
all  future/applied for allocations"   as

A required condition for receiving resources, whether by marketplace
or by wait list.

...
Some have argued that no such policy is needed at all, and ARIN should simply 
monetize
the number resources and use the proceeds in a manner aligned with its mission 
and
productive to the community, whereas others have indicated that the policy 
provides an
important option for smaller ISPs and organizations who may not be aware of 
IPv4 runout
and are not readily positioned to go the marketplace.   (Neither of these views 
supports
the waiting list policy which was suspended, as it served far more than simply 
smaller entities.)

John Curran
--
-JH
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to