[arin-ppml] Weekly posting summary for p...@arin.net

2019-12-26 Thread narten
Total of 16 messages in the last 7 days.
 
script run at: Fri 27 Dec 2019 12:53:06 AM EST
 
Messages   |  Bytes| Who
+--++--+
 25.00% |4 | 18.06% |38020 | i...@arin.net
 12.50% |2 | 18.88% |39741 | arin-ppml@arin.net
 12.50% |2 | 12.90% |27157 | fhfredi...@gmail.com
 12.50% |2 | 11.90% |25045 | scottleibr...@gmail.com
  6.25% |1 | 14.59% |30713 | far...@umn.edu
 12.50% |2 |  7.87% |16557 | gary.buhrmas...@gmail.com
  6.25% |1 |  6.77% |14245 | jcur...@arin.net
  6.25% |1 |  5.19% |10923 | nar...@us.ibm.com
  6.25% |1 |  3.84% | 8081 | o...@delong.com
+--++--+
100.00% |   16 |100.00% |   210482 | Total
___
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.


Re: [arin-ppml] Draft Policy ARIN-2019-21: Reserved Pool Replenishment

2019-12-26 Thread David Farmer
Responses are inline;

On Thu, Dec 26, 2019 at 6:38 PM Fernando Frediani 
wrote:

> There are two points to analyze in this proposal:
>
> - Any returned, reclaimed or revoked addresses that belong originally to
> the reserved pools to be returned to them. I think this was pretty
> obvious and was already done this way and wouldn't be necessary to state
> it again. Could the author show that this is not the way it is currently
> done then I am fine to support this part.
>

I'm not sure how ARIN staff does this now. However, if this is what we
want, it is usually better for it to be clearly stated in the policy.


> - With regards returning any other returned, reclaimed or revoke
> resources that were not from the reserved pools to them, although I see
> the good intent of it I find it difficult to support it as we don't know
> numbers related to this at the present. The numbers of assignments from
> these reserved pools, the amount available and the forecast for it are
> necessary for this analysis.
> Also it seems that three-year supply a long time for it to be kept. If
> the numbers mentioned point to the direction of the need of replenishing
> for these pools then the it may be necessary to review and discuss the
> supply time better. Without this information I cannot support this part
> of the proposal yet.
>

The idea of this policy is to have a default action of replenishing these
reserved pools only when or if they get down to a three-year or less
supply. Until then, other recovered resources go to the waiting list. Even
then the idea is to only replenish them to or maintain a three year supply
in the reserved pools, any resources recovered beyond that would still go
to the waiting list.

Without this policy, when or if these reserved pools get low, we will just
let them run out unless we have a consensus for a policy to change things
at that time. However, I would like default action to be to replenish the
reserved pools when or if they get low unless there is consensus at that
time to let them run out, requiring policy action at that time if we want
them to let them run out.

As for the current status of these pools; the following is from the ARIN 44
meeting report, at the beginning of November, in response to a question
during the discussion of ARIN-2019-17;

John Sweeting:  John Sweeting, ARIN staff. I think I'm going to answer
Joe's question. So in the 4.10 pool, the IP pool -- sorry, Cathy -- there
are 15,727 /24s left. 657 have been used over the time since it was
implemented. And it puts about an average between 10 and 15 a month.

On the 4.4, there's 123 issued. 389 left and about 1.5 per month. So maybe
15, 18 a year.

4.10 pool;
   15,727 /24s left
   15 /24s a month
   This is more than 80 years worth at that rate of use, but I expect the
rate of use will increase for this pool.

4.4 pool;
   389 /24s left
   1.5 /24s a month
   This is more than 20 years worth at that rate of use.

So this policy is not expected to have any effect for many years unless
there is a dramatic increase in the use of these pools.

Regards
> Fernando
>
> On 24/12/2019 11:41, ARIN wrote:
> >
> > On 19 December 2019, the ARIN Advisory Council (AC) accepted
> > "ARIN-prop-281: Reserved Pool Replenishment" as a Draft Policy.
> >
> > Draft Policy ARIN-2019-21 is below and can be found at:
> >
> > https://www.arin.net/participate/policy/drafts/2019_21/
> >
> > 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/participate/policy/pdp/
> >
> > Draft Policies and Proposals under discussion can be found at:
> > https://www.arin.net/participate/policy/drafts/
> >
> > Regards,
> >
> > Sean Hopkins
> > Policy Analyst
> > American Registry for Internet Numbers (ARIN)
> >
> >
> > Draft Policy ARIN-2019-21: Reserved Pool Replenishment
> >
> > Problem Statement:
> >
> > While the current level of resources in the reserve pools created in
> > Sections 4.4 and 4.10 presently seem more than adequate for their
> > intended purposes. Nevertheless, even these well-resourced pools will
> > eventually run out. Therefore, we should make arrangements for their
> > replenishment, if or when necessary.
> >
> > Policy Statement:
> >
> > Add a new subsection in IPv4 General Principles, Section 4.1;
> >
> > 4.1.X Reserved Pool Replenishment
> >
> > Any resources allocated from a reserved pool created in Sections 4.4
> > or 4.10, or any other reserved pools created in the future, that are
> > returned, reclaimed, or revoked will be returned to the reserved pool
> > they were originally allocated from, 

Re: [arin-ppml] Draft Policy ARIN-2019-21: Reserved Pool Replenishment

2019-12-26 Thread Michael B. Williams via ARIN-PPML
Agreed. Support this for the time being.

--

*Michael B. Williams*
Glexia, Inc. - An IT Company
USA Direct: +1 978 477 6797
USA Toll Free: +1 800 675 0297 x101
AUS Direct: +61 3 8594 2265
AUS Toll Free: +61 1800 931 724 x101
Fax: +1.815-301-5570
michael.willi...@glexia.com
https://www.glexia.com/
https://www.glexia.com.au/

*Legal Notice:*
The information in this electronic mail message is the sender's
confidential business and may be legally privileged. It is intended solely
for the addressee(s). Access to this internet electronic mail message by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it is prohibited and may be unlawful.



On Thu, Dec 26, 2019 at 8:39 PM Gary Buhrmaster 
wrote:

> Support.  At some future point it may make sense to
> eliminate (or reduce the size of) the reserved pools,
> but until we have consensus as to how to right-size
> those pools, they should have priority to top them
> off.
> ___
> 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.
>
___
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.


Re: [arin-ppml] Draft Policy ARIN-2019-21: Reserved Pool Replenishment

2019-12-26 Thread Gary Buhrmaster
Support.  At some future point it may make sense to
eliminate (or reduce the size of) the reserved pools,
but until we have consensus as to how to right-size
those pools, they should have priority to top them
off.
___
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.


Re: [arin-ppml] Draft Policy ARIN-2019-20: Harmonization of Maximum Allocation Requirements under Sections 4.1.8 (ARIN Waitlist) and 4.2.2 (Initial Allocation to ISPs)

2019-12-26 Thread Michael B. Williams via ARIN-PPML
Support. Because I don’t ever see us allocating directly; instead
everything will be placed on the wait list. It’s a bit annoying joining
thinking you qualify for a /21 then have to submit significant
justification to get a second /22 (bringing you to a /21).

Michael

On Fri, Dec 27, 2019 at 11:18 Fernando Frediani 
wrote:

> Support this proposal.
> Make sense to harmonize given the current scenario. In other RIRs it
> works or is planned to work in the same way.
>
> Regards
> Fernando Frediani
>
> On 24/12/2019 11:38, ARIN wrote:
> >
> > On 19 December 2019, the ARIN Advisory Council (AC) accepted
> > "ARIN-prop-279: Harmonization of Maximum Allocation Requirements under
> > Sections 4.1.8 (ARIN Waitlist) and 4.2.2 (Initial Allocation to ISPs)"
> > as a Draft Policy.
> >
> > Draft Policy ARIN-2019-20 is below and can be found at:
> >
> > https://www.arin.net/participate/policy/drafts/2019_20/
> >
> > 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/participate/policy/pdp/
> >
> > Draft Policies and Proposals under discussion can be found at:
> > https://www.arin.net/participate/policy/drafts/
> >
> > Regards,
> >
> > Sean Hopkins
> > Policy Analyst
> > American Registry for Internet Numbers (ARIN)
> >
> >
> >
> > Draft Policy ARIN-2019-20: Harmonization of Maximum Allocation
> > Requirements under Sections 4.1.8 (ARIN Waitlist) and 4.2.2 (Initial
> > Allocation to ISPs)
> >
> > Problem Statement:
> >
> > Under the current ARIN waitlist policy (section 4.1.8), ARIN now only
> > issues IPv4 assignments/allocations (excluding section 4.4 and 4.10
> > space) from the ARIN waitlist. The maximum size aggregate for which an
> > organization may qualify at any one time is a /22. On the other hand,
> > the current initial allocations to ISPs policy (section 4.2.2)
> > provides that direct assignments or allocations from ARIN qualify for
> > an initial allocation of up to a /21, subject to ARIN’s minimum
> > allocation size. This proposal seeks to resolve the conflict in the
> > maximum allocation size requirements between the two sections in
> > favour of the requirement in the waitlist policy, since that is the
> > one that is intended to govern at the present time. Reconciling the
> > policy language as proposed herein will avoid confusion by readers of
> > the NRPM.
> >
> > Policy statement:
> >
> > Change the first sentence of section 4.2.2 to read:
> >
> > “All ISP organizations without direct assignments or allocations from
> > ARIN qualify for an initial allocation of up to a /22, subject to
> > ARIN’s minimum allocation size.”
> >
> > Timetable for Implementation: Immediate
> >
> > ___
> > 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.
> ___
> 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.
>
-- 
Sent from Gmail Mobile
___
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.


Re: [arin-ppml] Draft Policy ARIN-2019-21: Reserved Pool Replenishment

2019-12-26 Thread Fernando Frediani

There are two points to analyze in this proposal:

- Any returned, reclaimed or revoked addresses that belong originally to 
the reserved pools to be returned to them. I think this was pretty 
obvious and was already done this way and wouldn't be necessary to state 
it again. Could the author show that this is not the way it is currently 
done then I am fine to support this part.


- With regards returning any other returned, reclaimed or revoked 
resources that were not from the reserved pools to them, although I see 
the good intent of it I find it difficult to support it as we don't know 
numbers related to this at the present. The numbers of assignments from 
these reserved pools, the amount available and the forecast for it are 
necessary for this analysis.
Also it seems that three-year supply a long time for it to be kept. If 
the numbers mentioned point to the direction of the need of replenishing 
for these pools then the it may be necessary to review and discuss the 
supply time better. Without this information I cannot support this part 
of the proposal yet.


Regards
Fernando

On 24/12/2019 11:41, ARIN wrote:


On 19 December 2019, the ARIN Advisory Council (AC) accepted 
"ARIN-prop-281: Reserved Pool Replenishment" as a Draft Policy.


Draft Policy ARIN-2019-21 is below and can be found at:

https://www.arin.net/participate/policy/drafts/2019_21/

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/participate/policy/pdp/

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/participate/policy/drafts/

Regards,

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


Draft Policy ARIN-2019-21: Reserved Pool Replenishment

Problem Statement:

While the current level of resources in the reserve pools created in 
Sections 4.4 and 4.10 presently seem more than adequate for their 
intended purposes. Nevertheless, even these well-resourced pools will 
eventually run out. Therefore, we should make arrangements for their 
replenishment, if or when necessary.


Policy Statement:

Add a new subsection in IPv4 General Principles, Section 4.1;

4.1.X Reserved Pool Replenishment

Any resources allocated from a reserved pool created in Sections 4.4 
or 4.10, or any other reserved pools created in the future, that are 
returned, reclaimed, or revoked will be returned to the reserved pool 
they were originally allocated from, regardless of the current level 
of each pool. Further, any other resources returned, reclaimed, or 
revoked will be prioritized for the replenishment of any reserved pool 
that falls below a running three-year supply, which is based on the 
previous three years of allocations from each pool.


Timetable for Implementation: Immediate

Anything Else:

ARIN Staff should regularly report on the levels and projected 
run-times for each reserved pool and immediately report when any 
reserved pool falls below a three-year running supply.


A three-year running supply was chosen to provide the ARIN Policy 
Community adequate time to react through policy, as deemed appropriate 
at that time, to an imminent run out event for one of the reserved pools.

___
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.

___
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.


Re: [arin-ppml] Draft Policy ARIN-2019-20: Harmonization of Maximum Allocation Requirements under Sections 4.1.8 (ARIN Waitlist) and 4.2.2 (Initial Allocation to ISPs)

2019-12-26 Thread Fernando Frediani

Support this proposal.
Make sense to harmonize given the current scenario. In other RIRs it 
works or is planned to work in the same way.


Regards
Fernando Frediani

On 24/12/2019 11:38, ARIN wrote:


On 19 December 2019, the ARIN Advisory Council (AC) accepted 
"ARIN-prop-279: Harmonization of Maximum Allocation Requirements under 
Sections 4.1.8 (ARIN Waitlist) and 4.2.2 (Initial Allocation to ISPs)" 
as a Draft Policy.


Draft Policy ARIN-2019-20 is below and can be found at:

https://www.arin.net/participate/policy/drafts/2019_20/

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/participate/policy/pdp/

Draft Policies and Proposals under discussion can be found at:
https://www.arin.net/participate/policy/drafts/

Regards,

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



Draft Policy ARIN-2019-20: Harmonization of Maximum Allocation 
Requirements under Sections 4.1.8 (ARIN Waitlist) and 4.2.2 (Initial 
Allocation to ISPs)


Problem Statement:

Under the current ARIN waitlist policy (section 4.1.8), ARIN now only 
issues IPv4 assignments/allocations (excluding section 4.4 and 4.10 
space) from the ARIN waitlist. The maximum size aggregate for which an 
organization may qualify at any one time is a /22. On the other hand, 
the current initial allocations to ISPs policy (section 4.2.2) 
provides that direct assignments or allocations from ARIN qualify for 
an initial allocation of up to a /21, subject to ARIN’s minimum 
allocation size. This proposal seeks to resolve the conflict in the 
maximum allocation size requirements between the two sections in 
favour of the requirement in the waitlist policy, since that is the 
one that is intended to govern at the present time. Reconciling the 
policy language as proposed herein will avoid confusion by readers of 
the NRPM.


Policy statement:

Change the first sentence of section 4.2.2 to read:

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


Timetable for Implementation: Immediate

___
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.

___
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.