[arin-ppml] Draft Policy ARIN-2018-2 :Clarification to ISP Initial Allocation and Permit Renumbering (Language improvement)

[Kerrie Vassall-Richards]

1. *Clarification to ISP initial allocation and permit renumbering*
2. Proposal Originator
- name: Jason Schiller
- email: ***@google.com
- telephone: [phone]
- organization: Google LLC
3. Date: 02/01/2017
4. *Problem Statement:*

As discussed in more detail in ARIN-2017-9 and noted in the ARIN 40 Policy
Experience Report, the criteria to qualify for an initial block of address
space in 4.2.2 and 8.5.4 are seeming at odds with each other. At ARIN 41
the community seemed to prefer the approach contained in this policy over
the approach in ARIN-2017-9, which was subsequently abandoned.

Moreover, as the NRPM (2018-1) currently sits, 4.2.2 appears to state that
an initial allocation of up to a /21 could be granted without any more
justification than needed to qualify for a /24. Therefore, 4.2.2 should be
modified, allowing an initial allocation of only a /24 without any
additional justification and allowing an initial allocation of up to a /21
when justified by a 24-month allocation plan.

*Policy Statement:*

Replace the current Section 4.2.2 with:

4.2.2. Initial allocation to ISPs

All ISP organizations without direct assignments or allocations from ARIN
qualify for an initial allocation of up to a /21, subject to ARIN's minimum
allocation size.

All ISP organizations without direct allocations, direct assignments,
re-allocations or reassignments automatically qualify for a /24. These
organizations are exempt from requirements of showing the efficient
utilization of previously held IPv4 space. These organizations may qualify
for a larger than a /24 by documenting how the requested allocation will be
utilized within the request size specified in 4.2.4.3

ISPs holding re-allocations and/or reassignments must show the efficient
utilization of their resources consistent with the requirements in sections
4.2.3 and 4.2.4


*Comments:*

The timetable for Implementation: Immediate

*Anything Else:*

This is an attempt to clarify the changes that came about from 2016-4.
It also aligns section 4.2 with current transfer policy.
It also re-established the understanding that ISP can renumber and return,
but putting the last section 4.2.2.1.4 into the ISP additional requests
section. This text is slightly modified to include returns to ARIN in
addition to returns to the upstream.

[Andrew Dul]

The AC has recently been discussing this draft policy and noted that we
have not heard from the community since this new text has been posted. 
We would like to hear from you on if we should move this policy to
recommended.


I believe the new text fixes the discrepancy, for initial ISP
allocations, which depends on if the organization initially applies
under section4 or section8.  This policy fixes this issue in section4 by
requiring the same documentation (as required under the section8
transfer policy) for a new ISP requesting a block larger than a /24.

I support this draft policy.


Thanks,

Andrew

Post by Kerrie Vassall-Richards
1. *Clarification to ISP initial allocation and permit renumbering*
2. Proposal Originator
* name: Jason Schiller
* telephone: [phone]
* organization: Google LLC
3. Date: 02/01/2017
4. *Problem Statement:*
As discussed in more detail in ARIN-2017-9 and noted in the ARIN 40
Policy Experience Report, the criteria to qualify for an initial block
of address space in 4.2.2 and 8.5.4 are seeming at odds with each
other. At ARIN 41 the community seemed to prefer the approach
contained in this policy over the approach in ARIN-2017-9, which was
subsequently abandoned.
Moreover, as the NRPM (2018-1) currently sits, 4.2.2 appears to state
that an initial allocation of up to a /21 could be granted without any
more justification than needed to qualify for a /24. Therefore, 4.2.2
should be modified, allowing an initial allocation of only a /24
without any additional justification and allowing an initial
allocation of up to a /21 when justified by a 24-month allocation plan.
*Policy Statement:*
4.2.2. Initial allocation to ISPs
All ISP organizations without direct assignments or allocations from
ARIN qualify for an initial allocation of up to a /21, subject to
ARIN's minimum allocation size.
All ISP organizations without direct allocations, direct assignments,
re-allocations or reassignments automatically qualify for a /24. These
organizations are exempt from requirements of showing the efficient
utilization of previously held IPv4 space. These organizations may
qualify for a larger than a /24 by documenting how the requested
allocation will be utilized within the request size specified in 4.2.4.3
ISPs holding re-allocations and/or reassignments must show the
efficient utilization of their resources consistent with the
requirements in sections 4.2.3 and 4.2.4
*Comments:*
The timetable for Implementation: Immediate
*Anything Else:*
This is an attempt to clarify the changes that came about from 2016-4.
It also aligns section 4.2 with current transfer policy.
It also re-established the understanding that ISP can renumber and
return, but putting the last section 4.2.2.1.4 into the ISP additional
requests section. This text is slightly modified to include returns to
ARIN in addition to returns to the upstream.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
https://lists.arin.net/mailman/listinfo/arin-ppml

[David Farmer]

I very much support fixing the problem that ARIN Staff has brought to our
attention. I don't have a strong opinion as to if this is the preferred
solution to the problem. However, there did seem to be a slight
preference by the community for this solution over ARIN-2017-9 at the Maimi
meeting.

Therefore, I support this draft policy and encourage others to make
their opinions known.

Thanks.

Post by Andrew Dul
The AC has recently been discussing this draft policy and noted that we
have not heard from the community since this new text has been posted. We
would like to hear from you on if we should move this policy to
recommended.
I believe the new text fixes the discrepancy, for initial ISP allocations,
which depends on if the organization initially applies under section4 or
section8. This policy fixes this issue in section4 by requiring the same
documentation (as required under the section8 transfer policy) for a new
ISP requesting a block larger than a /24.
I support this draft policy.
Thanks,
Andrew
1. *Clarification to ISP initial allocation and permit renumbering*
2. Proposal Originator
- name: Jason Schiller
- telephone: [phone]
- organization: Google LLC
3. Date: 02/01/2017
4. *Problem Statement:*
As discussed in more detail in ARIN-2017-9 and noted in the ARIN 40 Policy
Experience Report, the criteria to qualify for an initial block of address
space in 4.2.2 and 8.5.4 are seeming at odds with each other. At ARIN 41
the community seemed to prefer the approach contained in this policy over
the approach in ARIN-2017-9, which was subsequently abandoned.
Moreover, as the NRPM (2018-1) currently sits, 4.2.2 appears to state that
an initial allocation of up to a /21 could be granted without any more
justification than needed to qualify for a /24. Therefore, 4.2.2 should be
modified, allowing an initial allocation of only a /24 without any
additional justification and allowing an initial allocation of up to a /21
when justified by a 24-month allocation plan.
*Policy Statement:*
4.2.2. Initial allocation to ISPs
All ISP organizations without direct assignments or allocations from ARIN
qualify for an initial allocation of up to a /21, subject to ARIN's minimum
allocation size.
All ISP organizations without direct allocations, direct assignments,
re-allocations or reassignments automatically qualify for a /24. These
organizations are exempt from requirements of showing the efficient
utilization of previously held IPv4 space. These organizations may qualify
for a larger than a /24 by documenting how the requested allocation will be
utilized within the request size specified in 4.2.4.3
ISPs holding re-allocations and/or reassignments must show the efficient
utilization of their resources consistent with the requirements in sections
4.2.3 and 4.2.4
*Comments:*
The timetable for Implementation: Immediate
*Anything Else:*
This is an attempt to clarify the changes that came about from 2016-4.
It also aligns section 4.2 with current transfer policy.
It also re-established the understanding that ISP can renumber and return,
but putting the last section 4.2.2.1.4 into the ISP additional requests
section. This text is slightly modified to include returns to ARIN in
addition to returns to the upstream.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
Unsubscribe or manage your mailing list subscription at:https://lists.arin.net/mailman/listinfo/arin-ppml
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
https://lists.arin.net/mailman/listinfo/arin-ppml

[Brian Jones]

I support this policy. It aligns with the transfer policy better and clarifies initial allocation in section 4.2.2.

--
Brian E Jones

Post by Kerrie Vassall-Richards
Clarification to ISP initial allocation and permit renumbering
Proposal Originator
name: Jason Schiller
telephone: [phone]
organization: Google LLC
Date: 02/01/2017
As discussed in more detail in ARIN-2017-9 and noted in the ARIN 40 Policy Experience Report, the criteria to qualify for an initial block of address space in 4.2.2 and 8.5.4 are seeming at odds with each other. At ARIN 41 the community seemed to prefer the approach contained in this policy over the approach in ARIN-2017-9, which was subsequently abandoned.
Moreover, as the NRPM (2018-1) currently sits, 4.2.2 appears to state that an initial allocation of up to a /21 could be granted without any more justification than needed to qualify for a /24. Therefore, 4.2.2 should be modified, allowing an initial allocation of only a /24 without any additional justification and allowing an initial allocation of up to a /21 when justified by a 24-month allocation plan.
4.2.2. Initial allocation to ISPs
All ISP organizations without direct assignments or allocations from ARIN qualify for an initial allocation of up to a /21, subject to ARIN's minimum allocation size.
All ISP organizations without direct allocations, direct assignments, re-allocations or reassignments automatically qualify for a /24. These organizations are exempt from requirements of showing the efficient utilization of previously held IPv4 space. These organizations may qualify for a larger than a /24 by documenting how the requested allocation will be utilized within the request size specified in 4.2.4.3
ISPs holding re-allocations and/or reassignments must show the efficient utilization of their resources consistent with the requirements in sections 4.2.3 and 4.2.4
The timetable for Implementation: Immediate
This is an attempt to clarify the changes that came about from 2016-4.
It also aligns section 4.2 with current transfer policy.
It also re-established the understanding that ISP can renumber and return, but putting the last section 4.2.2.1.4 into the ISP additional requests section. This text is slightly modified to include returns to ARIN in addition to returns to the upstream.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
https://lists.arin.net/mailman/listinfo/arin-ppml

[Carlton Samuels]

I can support this policy. Perfectly rational.

-Carlton

==============================
*Carlton A Samuels*

*Mobile: [phone]Strategy, Process, Governance, Assessment & Turnaround*
=============================


On Sat, Jun 23, 2018 at 3:19 PM Kerrie Vassall-Richards <

Post by Kerrie Vassall-Richards
1. *Clarification to ISP initial allocation and permit renumbering*
2. Proposal Originator
- name: Jason Schiller
- telephone: [phone]
- organization: Google LLC
3. Date: 02/01/2017
4. *Problem Statement:*
As discussed in more detail in ARIN-2017-9 and noted in the ARIN 40 Policy
Experience Report, the criteria to qualify for an initial block of address
space in 4.2.2 and 8.5.4 are seeming at odds with each other. At ARIN 41
the community seemed to prefer the approach contained in this policy over
the approach in ARIN-2017-9, which was subsequently abandoned.
Moreover, as the NRPM (2018-1) currently sits, 4.2.2 appears to state that
an initial allocation of up to a /21 could be granted without any more
justification than needed to qualify for a /24. Therefore, 4.2.2 should be
modified, allowing an initial allocation of only a /24 without any
additional justification and allowing an initial allocation of up to a /21
when justified by a 24-month allocation plan.
*Policy Statement:*
4.2.2. Initial allocation to ISPs
All ISP organizations without direct assignments or allocations from ARIN
qualify for an initial allocation of up to a /21, subject to ARIN's minimum
allocation size.
All ISP organizations without direct allocations, direct assignments,
re-allocations or reassignments automatically qualify for a /24. These
organizations are exempt from requirements of showing the efficient
utilization of previously held IPv4 space. These organizations may qualify
for a larger than a /24 by documenting how the requested allocation will be
utilized within the request size specified in 4.2.4.3
ISPs holding re-allocations and/or reassignments must show the efficient
utilization of their resources consistent with the requirements in sections
4.2.3 and 4.2.4
*Comments:*
The timetable for Implementation: Immediate
*Anything Else:*
This is an attempt to clarify the changes that came about from 2016-4.
It also aligns section 4.2 with current transfer policy.
It also re-established the understanding that ISP can renumber and return,
but putting the last section 4.2.2.1.4 into the ISP additional requests
section. This text is slightly modified to include returns to ARIN in
addition to returns to the upstream.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
https://lists.arin.net/mailman/listinfo/arin-ppml

[Blaise Arbouet]

I also support the policy.

Blaise Arbouet

Post by Carlton Samuels
I can support this policy. Perfectly rational.
-Carlton
==============================
*Carlton A Samuels*
*Mobile: [phone]Strategy, Process, Governance, Assessment & Turnaround*
=============================
On Sat, Jun 23, 2018 at 3:19 PM Kerrie Vassall-Richards <

Post by Kerrie Vassall-Richards
1. *Clarification to ISP initial allocation and permit renumbering*
2. Proposal Originator
- name: Jason Schiller
- telephone: [phone]
- organization: Google LLC
3. Date: 02/01/2017
4. *Problem Statement:*
As discussed in more detail in ARIN-2017-9 and noted in the ARIN 40
Policy Experience Report, the criteria to qualify for an initial block of
address space in 4.2.2 and 8.5.4 are seeming at odds with each other. At
ARIN 41 the community seemed to prefer the approach contained in this
policy over the approach in ARIN-2017-9, which was subsequently abandoned.
Moreover, as the NRPM (2018-1) currently sits, 4.2.2 appears to state
that an initial allocation of up to a /21 could be granted without any more
justification than needed to qualify for a /24. Therefore, 4.2.2 should be
modified, allowing an initial allocation of only a /24 without any
additional justification and allowing an initial allocation of up to a /21
when justified by a 24-month allocation plan.
*Policy Statement:*
4.2.2. Initial allocation to ISPs
All ISP organizations without direct assignments or allocations from ARIN
qualify for an initial allocation of up to a /21, subject to ARIN's minimum
allocation size.
All ISP organizations without direct allocations, direct assignments,
re-allocations or reassignments automatically qualify for a /24. These
organizations are exempt from requirements of showing the efficient
utilization of previously held IPv4 space. These organizations may qualify
for a larger than a /24 by documenting how the requested allocation will be
utilized within the request size specified in 4.2.4.3
ISPs holding re-allocations and/or reassignments must show the efficient
utilization of their resources consistent with the requirements in sections
4.2.3 and 4.2.4
*Comments:*
The timetable for Implementation: Immediate
*Anything Else:*
This is an attempt to clarify the changes that came about from 2016-4.
It also aligns section 4.2 with current transfer policy.
It also re-established the understanding that ISP can renumber and
return, but putting the last section 4.2.2.1.4 into the ISP additional
requests section. This text is slightly modified to include returns to ARIN
in addition to returns to the upstream.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
https://lists.arin.net/mailman/listinfo/arin-ppml

_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
https://lists.arin.net/mailman/listinfo/arin-ppml