[address-policy-wg] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)

On Wed, Nov 8, 2017 at 3:29 AM, Nick Hilliard <nick at foobar.org> wrote:

> Gert Doering wrote:
> > So:
> >
> >>> We encourage you to read the proposal, impact analysis and draft
> >>> document and send any comments to <address-policy-wg at ripe.net>
> >>> before 17 November 2017.
> >
> > Please speak up *here* if you have opinions on this proposal.
>
> Looks sensible.  I support the proposal.
>
> Nick


I agree;

It seems to me that the extreme position that WiFi hotspot type use of PI
is in violation because you are sub-assigning addresses for use by outside
parties, is missing the point that from a policy perspective a
sub-assignment has to have some level of permanence and dedication to it.
The transient or temporary use of some addresses by a customer, a business
partner, or even the general public, does not rise to the point of making a
sub-assignment from a policy perspective, because it lacks permanence and
in most cases is not dedicated to a specific external use, or in other
words its dynamic or changing.

To count as a sub-assignment from a policy perspective the use number
resources by an outside party (a customer, a business partner, the general
public, etc...) has to be dedicated to the use by a specific external
individual or entity for a substantive period of time, like months or
years, not just a few hours or days.

While I support the concept of this policy, because of the
unique-prefix-per-host work nearing completion in the IETF, I like to see
language about prefixes and subnets removed from the policy and maybe
replaced with language based on the temporary non-dedicated (dynamic) use
instead.

Thanks.





-- 
===============================================
David Farmer               Email:farmer at umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20171108/6f9c1fa3/attachment.html>