Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2018-4: Clarification on Temporary Sub-Assignments

[hostmaster]

I also have no problem with the Clarification.

I also note that in 2017-5, the registration requirements for IPv6 was 
changed to more than a /48.  Thus, unless someone is handing out BYOD or 
public use IPv6 address blocks larger than this, or with unique routing 
applied, that act should never trigger a registration requirement.  I 
asked for this change because of issues in obtaining static IPv6 address 
space for use in public transit busses since they no longer offered static 
IPv4 due to shortage of address space. The mobile provider insisted that 
the ARIN policy at the time required SWIP registration of /64 or more of 
space. They were insisting on registration of each bus, complete with a 
unique "Street Address" for each one.  Now that 2017-5 has been adopted, I 
no longer have any issue with the State contract wireless provider, and I 
can SWIP them all to the main office IT department.

The issue being addressed here is a NEW problem that did not exist in most 
networks running IPv4.  This is because in most cases, addresses assigned 
by DHCP or otherwise in the IPv4 enviroment were not ARIN assigned 
addresses, but were instead NAT addresses assigned from RFP1918 space and 
not subject to the restrictions contained in the NRPM since only the NAT 
device had a public IP address subject to ARIN rules, and this device was 
under the control of the network owner. Very few networks actually handed 
out actual public IPv4 addresses, and those who did were also technically 
in violation of ARIN rules.

In IPv6, NAT is not normally used, and addresses assigned for both BYOD 
and public use are in fact public IP addresses which are part of address 
space regulated by ARIN. Technically under the current NRPM, this 
assignment of address space issued under ARIN for BYOD or public use 
(wifi) networks is not permitted without these changes.  This would 
include both DHCP assigned or even SLAAC assigned addresses.  This is why 
we need to change the NRPM to make clear that this current routine 
practice in networks with IPv6 is proper.

Albert Erdmann
Network Administrator
Paradise On Line Inc.

On Tue, 14 Aug 2018, Owen DeLong wrote:

This also works for me.

Owen


On Aug 14, 2018, at 09:20 , David Farmer <far...@umn.edu> wrote:

Yes, moving the sentence to the end of the section is probably even a better 
solution.

However, looking at the sentence a little more closely. Using reassignment, or 
assignment for that matter, twice in the same sentence sounds a little circular 
or possibly self-contradictory to me. Also, incidental seems like a good 
additional word for describing what we mean in this situation.

in??ci??den??tal
1. accompanying but not a major part of something.
    ?? occurring by chance in connection with something else.
2. liable to happen as a consequence of (an activity).

tem??po??rar??y
1.
lasting for only a limited period of time; not permanent.

The point is even a permanent but incidental use should not be considered a 
reassignment.

So, how about;

Note that the incidental or temporary use of address space by third parties 
shall not be considered a reassignment or a violation of the exclusive use 
criterion.

Thanks.

On Tue, Aug 14, 2018 at 9:52 AM, JORDI PALET MARTINEZ <jordi.pa...@consulintel.es 
<mailto:jordi.pa...@consulintel.es>> wrote:
Unless I???m missing anything (in other regions we have ???sub-assignment???), 
I think it works for me.



May be a way to shorten it is to use the proposed sentence, but after all the 
definitions:





2.5. Allocation, Assignment, Reallocation, Reassignment



Allocation - Address space delegated to an organization directly by ARIN for 
the purpose of subsequent distribution by the recipient organization to other 
parties.



Assignment - Address space delegated to an organization directly by ARIN for 
the exclusive use of the recipient organization.



Reallocation - Address space sub-delegated to an organization by an upstream 
provider for the purpose of subsequent distribution by the recipient 
organization to other parties.



Reassignment - Address space sub-delegated to an organization by an upstream 
provider for the exclusive use of the recipient organization.



Note that a temporary reassignment of address space provided to third parties 
shall not be considered a reassignment or a violation of the exclusive use 
criterion.

 Regards,

Jordi

De: ARIN-PPML <arin-ppml-boun...@arin.net <mailto:arin-ppml-boun...@arin.net>> en nombre de 
David Farmer <far...@umn.edu <mailto:far...@umn.edu>>
Fecha: martes, 14 de agosto de 2018, 8:44
Para: ARIN <i...@arin.net <mailto:i...@arin.net>>
CC: ARIN-PPML List <arin-ppml@arin.net <mailto:arin-ppml@arin.net>>
Asunto: Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2018-4: 
Clarification on Temporary Sub-Assignments



Because of recent changes, editorial if I remember correctly, section 2.5 now 
reads as;



2.5. Allocation, Assignment, Reallocation, Reassignment



Allocation - Address space delegated to an organization directly by ARIN for 
the purpose of subsequent distribution by the recipient organization to other 
parties.



Assignment - Address space delegated to an organization directly by ARIN for 
the exclusive use of the recipient organization.



Reallocation - Address space sub-delegated to an organization by an upstream 
provider for the purpose of subsequent distribution by the recipient 
organization to other parties.



Reassignment - Address space sub-delegated to an organization by an upstream 
provider for the exclusive use of the recipient organization.



This proposal essentially adds the following sentence to "Assignment" above.



A temporary assignment of address space provided to third parties shall not be 
considered a reassignment or a violation of the exclusive use criterion.



However, I propose the following minor change to that;



A temporary reassignment of address space provided to third parties shall not 
be considered a reassignment or a violation of the exclusive use criterion.



Further, the sentence should also apply to "Reassignment". So, does the sentence also need to be 
added to "Reassignment"?  Or maybe add the following sentence to "Reassignment";




Excluding temporary reassignments, as discussed in the definition Assignment 
above.




Thanks



On Mon, Aug 13, 2018 at 12:39 PM, ARIN <i...@arin.net <mailto:i...@arin.net>> 
wrote:


The following has been revised and retitled:

* Draft Policy ARIN-2018-4: Clarification on Temporary Sub-Assignments

Formerly:

* Draft Policy ARIN-2018-4: Clarification on IPv6 Sub-Assignments

Revised text is below and can be found at:
https://www.arin.net/policy/proposals/2018_4.html 
<https://www.arin.net/policy/proposals/2018_4.html>

You are encouraged to discuss all Draft Policies on PPML. The AC will evaluate 
the discussion in order to assess the conformance of this draft policy with 
ARIN's Principles of Internet number resource policy as stated in the Policy 
Development Process (PDP). Specifically, these principles are:

* Enabling Fair and Impartial Number Resource Administration
* Technically Sound
* Supported by the Community

The PDP can be found at:
https://www.arin.net/policy/pdp.html <https://www.arin.net/policy/pdp.html>

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/policy/proposals/index.html 
<https://www.arin.net/policy/proposals/index.html>

Regards,

Sean Hopkins
Policy Analyst
American Registry for Internet Numbers (ARIN)



Draft Policy ARIN-2018-4: Clarification on Temporary Sub-Assignments

Problem Statement:

When the policy was drafted, the concept of assignments/sub-assignments did not 
consider the use of IP addresses in hotspots, or the use of IP addresses by 
guests or employees in Bring Your Own Device (BYOD) and many other similar 
cases.

Additionally, the IETF has recently approved the use of a unique IPv6 /64 prefix per 
interface/host (RFC8273) instead of a unique address. This, for example, allows users to 
connect to a hotspot, receive a /64 such that they are "isolated" from other 
users (for reasons of security, regulatory requirements, etc.) and they can also use 
multiple virtual machines on their devices with a unique address for each one (within the 
same /64).

Section 2.5 (Definitions/Allocate and Assign), explicitly prohibits such assignments, 
stating that "Assignments... are not to be sub-assigned to other parties".

This proposal clarifies this situation in this regard and better define the 
concept, particularly considering new uses of IPv6 (RFC8273), by means of 
additional language added to the definition of an Assignment.

Note that the proposal text also incorporates changes made under an Editorial Change 
currently awaiting Board of Trustees review, available here: 
https://www.arin.net/policy/proposals/2017_11.html 
<https://www.arin.net/policy/proposals/2017_11.html>

Policy Statement:

Actual Text, Section 2.5:

??? Assign - To assign means to delegate address space to an ISP or end-user, 
for specific use within the Internet infrastructure they operate. Assignments 
must only be made for specific purposes documented by specific organizations 
and are not to be sub-assigned to other parties.

New Text:

??? Assignment - Address space delegated to an organization directly by ARIN 
for the exclusive use of the recipient organization. A temporary assignment of 
address space provided to third parties shall not be considered an assignment 
or a violation of the exclusive use criterion.

Comments

Timetable for implementation:

Immediate

Anything else:

Situation in other regions:

This situation, has already been corrected in RIPE, and the policy was updated 
in a similar way, even if right now there is a small discrepancy between the 
policy text that reached consensus and the RIPE NCC Impact Analysis. A new 
policy proposal has been submitted to amend that, and the text is the same as 
presented by this proposal at ARIN. Same text has also been submitted to 
AfriNIC, LACNIC and APNIC.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net 
<mailto:ARIN-PPML@arin.net>).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml 
<https://lists.arin.net/mailman/listinfo/arin-ppml>
Please contact i...@arin.net <mailto:i...@arin.net> if you experience any 
issues.






--

===============================================
David Farmer               Email:far...@umn.edu <mailto:email%3afar...@umn.edu>
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE 
<https://maps.google.com/?q=2218+University+Ave+SE&entry=gmail&source=g>        
Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

_______________________________________________ ARIN-PPML You are receiving this message because 
you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML@arin.net 
<mailto:ARIN-PPML@arin.net>). Unsubscribe or manage your mailing list subscription at: 
https://lists.arin.net/mailman/listinfo/arin-ppml 
<https://lists.arin.net/mailman/listinfo/arin-ppml> Please contact i...@arin.net 
<mailto:i...@arin.net> if you experience any issues.


**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es <http://www.consulintel.es/>
The IPv6 Company

This electronic message contains information which may be privileged or 
confidential. The information is intended to be for the exclusive use of the 
individual(s) named above and further non-explicilty authorized disclosure, 
copying, distribution or use of the contents of this information, even if 
partially, including attached files, is strictly prohibited and will be 
considered a criminal offense. If you are not the intended recipient be aware 
that any disclosure, copying, distribution or use of the contents of this 
information, even if partially, including attached files, is strictly 
prohibited, will be considered a criminal offense, so you must reply to the 
original sender to inform about this communication and delete it.




--
===============================================
David Farmer               Email:far...@umn.edu <mailto:email%3afar...@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
===============================================
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net 
<mailto:ARIN-PPML@arin.net>).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml 
<https://lists.arin.net/mailman/listinfo/arin-ppml>
Please contact i...@arin.net <mailto:i...@arin.net> if you experience any 
issues.

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