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

[narten]

Total of 29 messages in the last 7 days.
 
script run at: Fri Jun  7 00:53:02 EDT 2019
 
Messages   |  Bytes| Who
+--++--+
 13.79% |4 | 18.16% |   145070 | arin-ppml@arin.net
 10.34% |3 | 11.82% |94426 | jcur...@arin.net
  6.90% |2 |  9.86% |78772 | tpru...@stratusnet.com
  3.45% |1 |  4.66% |37259 | andrew@quark.net
  3.45% |1 |  4.56% |36458 | matthew.wil...@telus.com
  3.45% |1 |  4.31% |34391 | p...@arin.net
  3.45% |1 |  4.18% |33365 | mich...@casadevall.pro
  3.45% |1 |  4.03% |32155 | steven.feld...@cbsinteractive.com
  3.45% |1 |  3.95% |31513 | lsaw...@gci.com
  3.45% |1 |  3.94% |31501 | scottleibr...@gmail.com
  3.45% |1 |  3.92% |31299 | j...@egh.com
  3.45% |1 |  3.72% |29691 | bjo...@vt.edu
  3.45% |1 |  3.37% |26899 | t...@iptrading.com
  3.45% |1 |  3.31% |26451 | o...@delong.com
  3.45% |1 |  3.29% |26289 | n...@ionswitch.com
  3.45% |1 |  2.73% |21831 | rob...@rjfc.net
  3.45% |1 |  2.42% |19365 | fhfredi...@gmail.com
  3.45% |1 |  1.93% |15455 | b...@herrin.us
  3.45% |1 |  1.49% |11868 | nar...@us.ibm.com
  3.45% |1 |  1.17% | 9358 | gary.buhrmas...@gmail.com
  3.45% |1 |  1.06% | 8504 | se...@rollernet.us
  3.45% |1 |  1.06% | 8467 | p...@rsuc.gweep.net
  3.45% |1 |  1.05% | 8392 | r...@mejac.palo-alto.ca.us
+--++--+
100.00% |   29 |100.00% |   798779 | 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] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Gary Buhrmaster]

On Thu, Jun 6, 2019 at 5:21 PM John Curran  wrote:

> To that end, at this time it would be good to know from everyone:
>
> 1.  Are you in favor of ARIN making the policy change specified in the 
> revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet 
> Requests”  ?

Support as written.

As others have said, I would like to see some future
tweaks if those changes could achieve consensus,
but this seems a good step forward today.
___
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] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Fernando Frediani]

What an absurd idea !

That's not ideal propose and although ARIN can and should not ignor
transfer market and it is the RIR function to handle the waiting list and
have it in its full control.
It is one of its main proposes to handle this waiting list and I personaly
support this fully.

Regards
Fernando


On Thu, 6 Jun 2019, 22:22 William Herrin,  wrote:

> Support, though frankly I'd prefer it if ARIN simply abolished the wait
> list and put the addresses on the transfer market.
>
> Philosophically speaking, how could you possibly *need* addresses the way
> we think of need if you can afford to wait months and months for them to
> become available on the wait list? Seems to me like there's some fudging
> going on at this point.
>
> Regards,
> Bill Herrin
>
> > Replace section 4.1.8 et. seq. as follows, then reinstate the full
> operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
> >
> > 4.1.8 ARIN Waitlist
> >
> > ARIN will only issue future IPv4 assignments/allocations (excluding 4.4
> and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
> organization may qualify for at any one time is a /22. Organizations will
> be able to elect a smaller block size than they qualify for down to a /24.
> Only organizations holding a /20 or less of IPv4 address space may apply
> and be approved. Address space distributed from the waitlist will not be
> eligible for transfer for a period of 60 months. This policy will be
> applied to all future distributions from the waitlist to include those
> currently listed.
> >
> > Repeated requests, in a manner that would circumvent 4.1.6, are not
> allowed: an organization currently on the waitlist must wait 90 days after
> receiving a distribution from the waitlist before applying for additional
> space. ARIN, at its sole discretion, may waive this requirement if the
> requester can document a change in circumstances since their last request
> that could not have been reasonably foreseen at the time of the original
> request, and which now justifies additional space. Qualified requesters
> whose request will also be advised of the availability of the transfer
> mechanism in section 8.3 as an alternative mechanism to obtain IPv4
> addresses.
> >
> > 4.1.8.1 Sequencing
> >
> > The position of each qualified request on the waiting list will be
> determined by the date it was approved. Each organization may have one
> approved request on the waiting list at a time.
> >
> > 4.1.8.2 Fulfillment
> >
> > ARIN will fulfill requests on a first-approved basis, subject to the
> size of each available address block as address blocks become available for
> distribution. A timely review of the original request may be conducted by
> ARIN staff. Requests will not be partially filled. Any requests met through
> a transfer will be considered fulfilled and removed from the waiting list
>
> --
> William Herrin
> b...@herrin.us
> https://bill.herrin.us/
> ___
> 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] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Robert Clarke]

I agree with William. It's definitely not logical to hand out free addresses.

Robert Clarke

> On Jun 6, 2019, at 6:21 PM, William Herrin  wrote:
> 
> Support, though frankly I'd prefer it if ARIN simply abolished the wait list 
> and put the addresses on the transfer market. 
> 
> Philosophically speaking, how could you possibly *need* addresses the way we 
> think of need if you can afford to wait months and months for them to become 
> available on the wait list? Seems to me like there's some fudging going on at 
> this point.
> 
> Regards,
> Bill Herrin
> 
> > Replace section 4.1.8 et. seq. as follows, then reinstate the full 
> > operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
> >
> > 4.1.8 ARIN Waitlist
> >
> > ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
> > 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an 
> > organization may qualify for at any one time is a /22. Organizations will 
> > be able to elect a smaller block size than they qualify for down to a /24. 
> > Only organizations holding a /20 or less of IPv4 address space may apply 
> > and be approved. Address space distributed from the waitlist will not be 
> > eligible for transfer for a period of 60 months. This policy will be 
> > applied to all future distributions from the waitlist to include those 
> > currently listed.
> >
> > Repeated requests, in a manner that would circumvent 4.1.6, are not 
> > allowed: an organization currently on the waitlist must wait 90 days after 
> > receiving a distribution from the waitlist before applying for additional 
> > space. ARIN, at its sole discretion, may waive this requirement if the 
> > requester can document a change in circumstances since their last request 
> > that could not have been reasonably foreseen at the time of the original 
> > request, and which now justifies additional space. Qualified requesters 
> > whose request will also be advised of the availability of the transfer 
> > mechanism in section 8.3 as an alternative mechanism to obtain IPv4 
> > addresses.
> >
> > 4.1.8.1 Sequencing
> >
> > The position of each qualified request on the waiting list will be 
> > determined by the date it was approved. Each organization may have one 
> > approved request on the waiting list at a time.
> >
> > 4.1.8.2 Fulfillment
> >
> > ARIN will fulfill requests on a first-approved basis, subject to the size 
> > of each available address block as address blocks become available for 
> > distribution. A timely review of the original request may be conducted by 
> > ARIN staff. Requests will not be partially filled. Any requests met through 
> > a transfer will be considered fulfilled and removed from the waiting list
> 
> -- 
> William Herrin
> b...@herrin.us 
> https://bill.herrin.us/ 
> ___
> 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] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[William Herrin]

Support, though frankly I'd prefer it if ARIN simply abolished the wait
list and put the addresses on the transfer market.

Philosophically speaking, how could you possibly *need* addresses the way
we think of need if you can afford to wait months and months for them to
become available on the wait list? Seems to me like there's some fudging
going on at this point.

Regards,
Bill Herrin

> Replace section 4.1.8 et. seq. as follows, then reinstate the full
operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
>
> 4.1.8 ARIN Waitlist
>
> ARIN will only issue future IPv4 assignments/allocations (excluding 4.4
and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
organization may qualify for at any one time is a /22. Organizations will
be able to elect a smaller block size than they qualify for down to a /24.
Only organizations holding a /20 or less of IPv4 address space may apply
and be approved. Address space distributed from the waitlist will not be
eligible for transfer for a period of 60 months. This policy will be
applied to all future distributions from the waitlist to include those
currently listed.
>
> Repeated requests, in a manner that would circumvent 4.1.6, are not
allowed: an organization currently on the waitlist must wait 90 days after
receiving a distribution from the waitlist before applying for additional
space. ARIN, at its sole discretion, may waive this requirement if the
requester can document a change in circumstances since their last request
that could not have been reasonably foreseen at the time of the original
request, and which now justifies additional space. Qualified requesters
whose request will also be advised of the availability of the transfer
mechanism in section 8.3 as an alternative mechanism to obtain IPv4
addresses.
>
> 4.1.8.1 Sequencing
>
> The position of each qualified request on the waiting list will be
determined by the date it was approved. Each organization may have one
approved request on the waiting list at a time.
>
> 4.1.8.2 Fulfillment
>
> ARIN will fulfill requests on a first-approved basis, subject to the size
of each available address block as address blocks become available for
distribution. A timely review of the original request may be conducted by
ARIN staff. Requests will not be partially filled. Any requests met through
a transfer will be considered fulfilled and removed from the waiting list

-- 
William Herrin
b...@herrin.us
https://bill.herrin.us/
___
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] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Brian Jones]

 I support this policy revision as written and feel it should move forward
while further discussion takes place for hashing out more details.
—
Brian Jones, CSP, CSM, CSPO
NIS Virginia Tech
bjo...@vt.edu


On Thu, Jun 6, 2019 at 5:13 PM Nick Bogle  wrote:

> I support these changes as written.
>
> On Thu, Jun 6, 2019, 10:21 AM John Curran  wrote:
>
>> Folks -
>>
>> We’ve had excellent discussion of various options for the revised
>> “Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"
>>  proposed policy change – some of which is likely to have to further
>> informed folks initial views on the matter (as well as on future policy
>> proposals in this area), but at this time it is fairly important that we
>> receive focused feedback on the revised policy text as written, with due
>> consideration to the discussion that has occurred online.
>>
>> To that end, at this time it would be good to know from everyone:
>>
>> 1.  Are you in favor of ARIN making the policy change specified in the
>> revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
>> Requests”  ?
>>
>> (“Yes” obviously indicative that you’d like ARIN to proceed with its
>> adoption and resumption of wait list issuance under its revised guidelines,
>> and
>>  “No” being indicative that you’d rather have the suspension of wait list
>> issuance continue unless/until some other policy change in this area
>> reaches consensus.)
>>
>> 2.  If you are not supportive of ARIN making the change specified in the
>> revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
>> Requests”,
>> is there any modification to the proposed policy change that would enable
>> you to support it?
>>
>> I would ask that PPML participants take a moment to consider the proposed
>> policy change as written and please reply regarding the questions above.
>>
>> Thanks!
>> /John
>>
>> John Curran
>> President and CEO
>> American Registry for Internet Numbers
>>
>>
>> Begin forwarded message:
>>
>> *From: *ARIN 
>> *Subject: **[arin-ppml] Revised - Advisory Council Recommendation
>> Regarding NRPM 4.1.8. Unmet Requests*
>> *Date: *24 May 2019 at 1:04:58 PM EDT
>> *To: *
>>
>> At their 16 May meeting, the Advisory Council revised their
>> recommendation regarding NRPM 4.1.8. Unmet Requests.
>>
>> The revised recommendation is hereby submitted to the Public Policy
>> Mailing List for a second community discussion period of 14 days, to
>> conclude on 7 June.
>>
>> Once completed, the Board of Trustees will review the AC’s recommendation
>> and the PPML discussion.
>>
>> The full text of the Advisory Council's revised recommendation is below.
>>
>> Sean Hopkins
>> Policy Analyst
>> American Registry for Internet Numbers (ARIN)
>>
>>
>>
>> Advisory Council recommendation:
>>
>> This is an updated version which incorporates feedback from the ARIN
>> staff and was approved for further community consultation at the ARIN AC
>> meeting on May 16, 2019.
>>
>> In accordance with section 10.2 of the ARIN Policy Development Process,
>> the ARIN Advisory Council recommends the following actions to the Board of
>> Trustees in response to the Board’s suspension of part of the operation of
>> sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:
>>
>> Replace section 4.1.8 et. seq. as follows, then reinstate the full
>> operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
>>
>> 4.1.8 ARIN Waitlist
>>
>> ARIN will only issue future IPv4 assignments/allocations (excluding 4.4
>> and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
>> organization may qualify for at any one time is a /22. Organizations will
>> be able to elect a smaller block size than they qualify for down to a /24.
>> Only organizations holding a /20 or less of IPv4 address space may apply
>> and be approved. Address space distributed from the waitlist will not be
>> eligible for transfer for a period of 60 months. This policy will be
>> applied to all future distributions from the waitlist to include those
>> currently listed.
>>
>> Repeated requests, in a manner that would circumvent 4.1.6, are not
>> allowed: an organization currently on the waitlist must wait 90 days after
>> receiving a distribution from the waitlist before applying for additional
>> space. ARIN, at its sole discretion, may waive this requirement if the
>> requester can document a change in circumstances since their last request
>> that could not have been reasonably foreseen at the time of the original
>> request, and which now justifies additional space. Qualified requesters
>> whose request will also be advised of the availability of the transfer
>> mechanism in section 8.3 as an alternative mechanism to obtain IPv4
>> addresses.
>>
>> 4.1.8.1 Sequencing
>>
>> The position of each qualified request on the waiting list will be
>> determined by the date it was approved. Each organization may have one
>> approved request on the waiting list at a time.
>>
>> 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Nick Bogle]

I support these changes as written.

On Thu, Jun 6, 2019, 10:21 AM John Curran  wrote:

> Folks -
>
> We’ve had excellent discussion of various options for the revised
> “Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"
>  proposed policy change – some of which is likely to have to further
> informed folks initial views on the matter (as well as on future policy
> proposals in this area), but at this time it is fairly important that we
> receive focused feedback on the revised policy text as written, with due
> consideration to the discussion that has occurred online.
>
> To that end, at this time it would be good to know from everyone:
>
> 1.  Are you in favor of ARIN making the policy change specified in the
> revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
> Requests”  ?
>
> (“Yes” obviously indicative that you’d like ARIN to proceed with its
> adoption and resumption of wait list issuance under its revised guidelines,
> and
>  “No” being indicative that you’d rather have the suspension of wait list
> issuance continue unless/until some other policy change in this area
> reaches consensus.)
>
> 2.  If you are not supportive of ARIN making the change specified in the
> revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
> Requests”,
> is there any modification to the proposed policy change that would enable
> you to support it?
>
> I would ask that PPML participants take a moment to consider the proposed
> policy change as written and please reply regarding the questions above.
>
> Thanks!
> /John
>
> John Curran
> President and CEO
> American Registry for Internet Numbers
>
>
> Begin forwarded message:
>
> *From: *ARIN 
> *Subject: **[arin-ppml] Revised - Advisory Council Recommendation
> Regarding NRPM 4.1.8. Unmet Requests*
> *Date: *24 May 2019 at 1:04:58 PM EDT
> *To: *
>
> At their 16 May meeting, the Advisory Council revised their recommendation
> regarding NRPM 4.1.8. Unmet Requests.
>
> The revised recommendation is hereby submitted to the Public Policy
> Mailing List for a second community discussion period of 14 days, to
> conclude on 7 June.
>
> Once completed, the Board of Trustees will review the AC’s recommendation
> and the PPML discussion.
>
> The full text of the Advisory Council's revised recommendation is below.
>
> Sean Hopkins
> Policy Analyst
> American Registry for Internet Numbers (ARIN)
>
>
>
> Advisory Council recommendation:
>
> This is an updated version which incorporates feedback from the ARIN staff
> and was approved for further community consultation at the ARIN AC meeting
> on May 16, 2019.
>
> In accordance with section 10.2 of the ARIN Policy Development Process,
> the ARIN Advisory Council recommends the following actions to the Board of
> Trustees in response to the Board’s suspension of part of the operation of
> sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:
>
> Replace section 4.1.8 et. seq. as follows, then reinstate the full
> operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
>
> 4.1.8 ARIN Waitlist
>
> ARIN will only issue future IPv4 assignments/allocations (excluding 4.4
> and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
> organization may qualify for at any one time is a /22. Organizations will
> be able to elect a smaller block size than they qualify for down to a /24.
> Only organizations holding a /20 or less of IPv4 address space may apply
> and be approved. Address space distributed from the waitlist will not be
> eligible for transfer for a period of 60 months. This policy will be
> applied to all future distributions from the waitlist to include those
> currently listed.
>
> Repeated requests, in a manner that would circumvent 4.1.6, are not
> allowed: an organization currently on the waitlist must wait 90 days after
> receiving a distribution from the waitlist before applying for additional
> space. ARIN, at its sole discretion, may waive this requirement if the
> requester can document a change in circumstances since their last request
> that could not have been reasonably foreseen at the time of the original
> request, and which now justifies additional space. Qualified requesters
> whose request will also be advised of the availability of the transfer
> mechanism in section 8.3 as an alternative mechanism to obtain IPv4
> addresses.
>
> 4.1.8.1 Sequencing
>
> The position of each qualified request on the waiting list will be
> determined by the date it was approved. Each organization may have one
> approved request on the waiting list at a time.
>
> 4.1.8.2 Fulfillment
>
> ARIN will fulfill requests on a first-approved basis, subject to the size
> of each available address block as address blocks become available for
> distribution. A timely review of the original request may be conducted by
> ARIN staff. Requests will not be partially filled. Any requests met through
> a transfer will be considered fulfilled and removed 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Steve Feldman]

I also support this policy change as written and encourage future policy
proposals to refine the details.
Steve


On Thu, Jun 6, 2019 at 10:26 AM Leif Sawyer  wrote:

> +1 support the policy change as currently written
>
>
>
>
>
> Also, as a general reminder, we don’t have to get this **perfect**  out
> of the gates, and we -the community-  can suggest follow-up policy changes
>
> if things start looking strange.   But if we wait to try to find a perfect
> balance between all parties, we’ll never resume issuance.
>
>
>
> Leif
>
>
>
> *From:* ARIN-PPML  *On Behalf Of *John Curran
> *Sent:* Thursday, June 6, 2019 9:21 AM
> *To:* ARIN-PPML List 
> *Subject:* [arin-ppml] Looking for final show of support on revised
> Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
> *Importance:* High
>
>
>
> [*EXTERNAL EMAIL* - CAUTION: Do not open unexpected attachments or links.]
>
> Folks -
>
>
>
> We’ve had excellent discussion of various options for the revised
> “Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"
>  proposed policy change – some of which is likely to have to further
> informed folks initial views on the matter (as well as on future policy
> proposals in this area), but at this time it is fairly important that we
> receive focused feedback on the revised policy text as written, with due
> consideration to the discussion that has occurred online.
>
>
>
> To that end, at this time it would be good to know from everyone:
>
>
>
> 1.  Are you in favor of ARIN making the policy change specified in the
> revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
> Requests”  ?
>
>
>
> (“Yes” obviously indicative that you’d like ARIN to proceed with its
> adoption and resumption of wait list issuance under its revised guidelines,
> and
>
>  “No” being indicative that you’d rather have the suspension of wait list
> issuance continue unless/until some other policy change in this area
> reaches consensus.)
>
>
>
> 2.  If you are not supportive of ARIN making the change specified in the
> revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
> Requests”,
>
> is there any modification to the proposed policy change that would enable
> you to support it?
>
>
>
> I would ask that PPML participants take a moment to consider the proposed
> policy change as written and please reply regarding the questions above.
>
>
>
> Thanks!
>
> /John
>
>
>
> John Curran
>
> President and CEO
>
> American Registry for Internet Numbers
>
>
>
>
>
> Begin forwarded message:
>
>
>
> *From: *ARIN 
>
> *Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding
> NRPM 4.1.8. Unmet Requests*
>
> *Date: *24 May 2019 at 1:04:58 PM EDT
>
> *To: *
>
>
>
> At their 16 May meeting, the Advisory Council revised their recommendation
> regarding NRPM 4.1.8. Unmet Requests.
>
> The revised recommendation is hereby submitted to the Public Policy
> Mailing List for a second community discussion period of 14 days, to
> conclude on 7 June.
>
> Once completed, the Board of Trustees will review the AC’s recommendation
> and the PPML discussion.
>
> The full text of the Advisory Council's revised recommendation is below.
>
> Sean Hopkins
> Policy Analyst
> American Registry for Internet Numbers (ARIN)
>
>
>
> Advisory Council recommendation:
>
> This is an updated version which incorporates feedback from the ARIN staff
> and was approved for further community consultation at the ARIN AC meeting
> on May 16, 2019.
>
> In accordance with section 10.2 of the ARIN Policy Development Process,
> the ARIN Advisory Council recommends the following actions to the Board of
> Trustees in response to the Board’s suspension of part of the operation of
> sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy
> Manual:
>
> Replace section 4.1.8 et. seq. as follows, then reinstate the full
> operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
>
> 4.1.8 ARIN Waitlist
>
> ARIN will only issue future IPv4 assignments/allocations (excluding 4.4
> and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
> organization may qualify for at any one time is a /22. Organizations will
> be able to elect a smaller block size than they qualify for down to a /24.
> Only organizations holding a /20 or less of IPv4 address space may apply
> and be approved. Address space distributed from the waitlist will not be
> eligible for transfer for a period of 60 months. This policy will be
> applied to all future distributions from the waitlist to include those
> currently listed.
>
> Repeated requests, in a manner that would circumvent 4.1.6, are not
> allowed: an organization currently on the waitlist must wait 90 days after
> receiving a distribution from the waitlist before applying for additional
> space. ARIN, at its sole discretion, may waive this requirement if the
> requester can document a change in circumstances since their last request
> that could not have been 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Andrew Dul]

I support the AC's recommendation as written.

While this policy will limit the organizations that are eligible to 
receive a block, I believe it strikes the right balance.  The smaller 
block size (/22) is generally in line with the final block size 
allocations of the other RIRs.


Furthermore, I would ask the the board consider adopting a fee to 
receive any block from the wait-list.  I believe this fee would be 
beneficial for two purposes.  One, it would help ARIN recover the costs 
associated with managing the wait-list and two, the fee would slightly 
close the gap between the the windfall from receiving a wait-list block 
and the market price of receiving a block via transfer.


Andrew

On 6/6/2019 10:29 AM, Owen DeLong wrote:
Yes. I favor the AC’s revised recommendation. The changes address 
certain staff concerns we hadn’t previously considered while 
maintaining a structure which I believe is widely supported within the 
community.


Even if this isn’t the perfect solution, I believe it is a good way 
forward and additional modification should be done through the 
standard policy process.


Owen


On Jun 6, 2019, at 10:20, John Curran > wrote:



Folks -

We’ve had excellent discussion of various options for the revised 
“Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet 
Requests"  proposed policy change – some of which is likely to have 
to further informed folks initial views on the matter (as well as on 
future policy proposals in this area), but at this time it is fairly 
important that we receive focused feedback on the revised policy text 
as written, with due consideration to the discussion that has 
occurred online.


To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in 
the revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. 
Unmet Requests”  ?


(“Yes” obviously indicative that you’d like ARIN to proceed with its 
adoption and resumption of wait list issuance under its revised 
guidelines, and
 “No” being indicative that you’d rather have the suspension of wait 
list issuance continue unless/until some other policy change in this 
area reaches consensus.)


2.  If you are not supportive of ARIN making the change specified in 
the revised "Advisory Council Recommendation Regarding NRPM 4.1.8. 
Unmet Requests”,
is there any modification to the proposed policy change that would 
enable you to support it?


I would ask that PPML participants take a moment to consider the 
proposed policy change as written and please reply regarding the 
questions above.


Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers



Begin forwarded message:

*From: *ARIN mailto:i...@arin.net>>
*Subject: **[arin-ppml] Revised - Advisory Council Recommendation 
Regarding NRPM 4.1.8. Unmet Requests*

*Date: *24 May 2019 at 1:04:58 PM EDT
*To: *mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their 
recommendation regarding NRPM 4.1.8. Unmet Requests.


The revised recommendation is hereby submitted to the Public Policy 
Mailing List for a second community discussion period of 14 days, to 
conclude on 7 June.


Once completed, the Board of Trustees will review the AC’s 
recommendation and the PPML discussion.


The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN 
staff and was approved for further community consultation at the 
ARIN AC meeting on May 16, 2019.


In accordance with section 10.2 of the ARIN Policy Development 
Process, the ARIN Advisory Council recommends the following actions 
to the Board of Trustees in response to the Board’s suspension of 
part of the operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the 
Numbering Resource Policy Manual:


Replace section 4.1.8 et. seq. as follows, then reinstate the full 
operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.


4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 
4.4 and 4.10 space) from the ARIN Waitlist. The maximum size 
aggregate that an organization may qualify for at any one time is a 
/22. Organizations will be able to elect a smaller block size than 
they qualify for down to a /24. Only organizations holding a /20 or 
less of IPv4 address space may apply and be approved. Address space 
distributed from the waitlist will not be eligible for transfer for 
a period of 60 months. This policy will be applied to all future 
distributions from the waitlist to include those currently listed.


Repeated requests, in a manner that would circumvent 4.1.6, are not 
allowed: an organization currently on the waitlist must wait 90 days 
after receiving a distribution from the waitlist before applying for 
additional 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Joe Provo]

On Thu, Jun 06, 2019 at 05:20:40PM +, John Curran wrote:
> Folks -
> 
> We???ve had excellent discussion of various options for the revised
> ???Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
> Requests"  proposed policy change ??? some of which is likely to
> have to further informed folks initial views on the matter (as well
> as on future policy proposals in this area), but at this time it
> is fairly important that we receive focused feedback on the revised
> policy text as written, with due consideration to the discussion
> that has occurred online.
> 
> To that end, at this time it would be good to know from everyone:
> 
> 1.  Are you in favor of ARIN making the policy change specified
> in the revised  "Advisory Council Recommendation Regarding NRPM
> 4.1.8. Unmet Requests???  ?

Yes, as the conservative resumption of distribution is to the 
benefit of the community at large.

I also look forward to near-future policy proposals refining
the unmet requests policy.

Cheers,

Joe


-- 
Posted from my personal account - see X-Disclaimer header.
Joe Provo / Gweep / Earthling 
___
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] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[John Santos]

Support.

On 6/6/2019 1:20 PM, John Curran wrote:

Folks -

We’ve had excellent discussion of various options for the revised 
“Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests" 
 proposed policy change – some of which is likely to have to further 
informed folks initial views on the matter (as well as on future 
policy proposals in this area), but at this time it is fairly 
important that we receive focused feedback on the revised policy text 
as written, with due consideration to the discussion that has occurred 
online.


To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the 
revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet 
Requests”  ?


(“Yes” obviously indicative that you’d like ARIN to proceed with its 
adoption and resumption of wait list issuance under its revised 
guidelines, and
 “No” being indicative that you’d rather have the suspension of wait 
list issuance continue unless/until some other policy change in this 
area reaches consensus.)


2.  If you are not supportive of ARIN making the change specified in 
the revised "Advisory Council Recommendation Regarding NRPM 4.1.8. 
Unmet Requests”,
is there any modification to the proposed policy change that would 
enable you to support it?


I would ask that PPML participants take a moment to consider the 
proposed policy change as written and please reply regarding the 
questions above.


Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers



Begin forwarded message:

*From: *ARIN mailto:i...@arin.net>>
*Subject: **[arin-ppml] Revised - Advisory Council Recommendation 
Regarding NRPM 4.1.8. Unmet Requests*

*Date: *24 May 2019 at 1:04:58 PM EDT
*To: *mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their 
recommendation regarding NRPM 4.1.8. Unmet Requests.


The revised recommendation is hereby submitted to the Public Policy 
Mailing List for a second community discussion period of 14 days, to 
conclude on 7 June.


Once completed, the Board of Trustees will review the AC’s 
recommendation and the PPML discussion.


The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN 
staff and was approved for further community consultation at the ARIN 
AC meeting on May 16, 2019.


In accordance with section 10.2 of the ARIN Policy Development 
Process, the ARIN Advisory Council recommends the following actions 
to the Board of Trustees in response to the Board’s suspension of 
part of the operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the 
Numbering Resource Policy Manual:


Replace section 4.1.8 et. seq. as follows, then reinstate the full 
operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.


4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 
4.4 and 4.10 space) from the ARIN Waitlist. The maximum size 
aggregate that an organization may qualify for at any one time is a 
/22. Organizations will be able to elect a smaller block size than 
they qualify for down to a /24. Only organizations holding a /20 or 
less of IPv4 address space may apply and be approved. Address space 
distributed from the waitlist will not be eligible for transfer for a 
period of 60 months. This policy will be applied to all future 
distributions from the waitlist to include those currently listed.


Repeated requests, in a manner that would circumvent 4.1.6, are not 
allowed: an organization currently on the waitlist must wait 90 days 
after receiving a distribution from the waitlist before applying for 
additional space. ARIN, at its sole discretion, may waive this 
requirement if the requester can document a change in circumstances 
since their last request that could not have been reasonably foreseen 
at the time of the original request, and which now justifies 
additional space. Qualified requesters whose request will also be 
advised of the availability of the transfer mechanism in section 8.3 
as an alternative mechanism to obtain IPv4 addresses.


4.1.8.1 Sequencing

The position of each qualified request on the waiting list will be 
determined by the date it was approved. Each organization may have 
one approved request on the waiting list at a time.


4.1.8.2 Fulfillment

ARIN will fulfill requests on a first-approved basis, subject to the 
size of each available address block as address blocks become 
available for distribution. A timely review of the original request 
may be conducted by ARIN staff. Requests will not be partially 
filled. Any requests met through a transfer will be considered 
fulfilled and removed from the waiting list.

___
ARIN-PPML
You are receiving this message 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Steven Ryerse via ARIN-PPML]

I would add that the current wait list is the best view we have of what the 
marketplace needs, so if a minimum is to be established it should take into 
account the actual requests for resources that are in the queue.  Also 2 year 
hold is the compromise.  My two cents.


Steven Ryerse
President
100 Ashford Center North, Suite 110, Atlanta, GA  30338
www.eclipse-networks.com
770.656.1460 - Cell
770.399.9099- Office

[Description: Description: Eclipse Networks Logo_small.png]℠ Eclipse Networks, 
Inc.
Conquering Complex Networks℠

From: ARIN-PPML  On Behalf Of Tom Pruitt
Sent: Thursday, June 6, 2019 3:39 PM
To: John Curran 
Cc: ARIN-PPML List 
Subject: Re: [arin-ppml] Looking for final show of support on revised Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

That would be correct.

What to do with the people already on the current list need to be addressed 
clearly.


Thanks,
Tom Pruitt
Network Engineer
Stratus Networks


From: John Curran mailto:jcur...@arin.net>>
Sent: Thursday, June 6, 2019 2:34 PM
To: Tom Pruitt mailto:tpru...@stratusnet.com>>
Cc: ARIN-PPML List mailto:arin-ppml@arin.net>>
Subject: Re: Looking for final show of support on revised Advisory Council 
Recommendation Regarding NRPM 4.1.8. Unmet Requests

Tom -

To be clear, if the only choices are status quo (no wait list issuance for 
foreseeable future) or resume under the AC proposed change, you are 
recommending status quo - correct?

/John

John Curran
President and CEO
American Registry for Internet Numbers


On 6 Jun 2019, at 3:01 PM, Tom Pruitt 
mailto:tpru...@stratusnet.com>> wrote:

No  -- I cannot support the new policy if applied to the current waiting list.

--  I don’t support applying the new restriction (only Orgs holding a /20 or 
less can get on the waiting list) to Orgs that were on the list prior to the 
suspension.


--I also would rather see those same Orgs get their requested allocation as 
long as they were approved for it initially.  (yes I think a /15 is excessive, 
but if they were approved for it before the rules changed….).

--At the very least Orgs that were on the list prior to the suspension should 
get either their requested allocation, or if their request was larger than the 
new Max allocation they should get the Max allocation.


I could support the suggested changes if they did not get applied to the Orgs 
on the waiting list prior to the suspension.  Once the suspension took affect 
Orgs knew changes were coming, and it is reasonable to change the policy, prior 
to that, they in good faith applied and were approved properly using the set 
policy.  Prudent or not, some Orgs counted on the list for the future, many of 
these Orgs don’t the deep pockets necessary to go to the secondary market.  I 
don’t think we should “punish” those orgs.

Thanks,
Tom Pruitt
Network Engineer
Stratus Networks

From: ARIN-PPML mailto:arin-ppml-boun...@arin.net>> 
On Behalf Of John Curran
Sent: Thursday, June 6, 2019 12:21 PM
To: ARIN-PPML List mailto:arin-ppml@arin.net>>
Subject: [arin-ppml] Looking for final show of support on revised Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
Importance: High

Folks -

We’ve had excellent discussion of various options for the revised “Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change – some of which is likely to have to further informed folks initial 
views on the matter (as well as on future policy proposals in this area), but 
at this time it is fairly important that we receive focused feedback on the 
revised policy text as written, with due consideration to the discussion that 
has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and
 “No” being indicative that you’d rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.)

2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”,
is there any modification to the proposed policy change that would enable you 
to support it?

I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers



Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: mailto:arin-ppml@arin.net>>

At their 16 May 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Tom Pruitt]

That would be correct.

What to do with the people already on the current list need to be addressed 
clearly.


Thanks,
Tom Pruitt
Network Engineer
Stratus Networks


From: John Curran 
Sent: Thursday, June 6, 2019 2:34 PM
To: Tom Pruitt 
Cc: ARIN-PPML List 
Subject: Re: Looking for final show of support on revised Advisory Council 
Recommendation Regarding NRPM 4.1.8. Unmet Requests

Tom -

To be clear, if the only choices are status quo (no wait list issuance for 
foreseeable future) or resume under the AC proposed change, you are 
recommending status quo - correct?

/John

John Curran
President and CEO
American Registry for Internet Numbers



On 6 Jun 2019, at 3:01 PM, Tom Pruitt 
mailto:tpru...@stratusnet.com>> wrote:

No  -- I can not support the new policy if applied to the current waiting list.

--  I don’t support applying the new restriction (only Orgs holding a /20 or 
less can get on the waiting list) to Orgs that were on the list prior to the 
suspension.


--I also would rather see those same Orgs get their requested allocation as 
long as they were approved for it initially.  (yes I think a /15 is excessive, 
but if they were approved for it before the rules changed….).

--At the very least Orgs that were on the list prior to the suspension should 
get either their requested allocation, or if their request was larger than the 
new Max allocation they should get the Max allocation.


I could support the suggested changes if they did not get applied to the Orgs 
on the waiting list prior to the suspension.  Once the suspension took affect 
Orgs knew changes were coming, and it is reasonable to change the policy, prior 
to that, they in good faith applied and were approved properly using the set 
policy.  Prudent or not, some Orgs counted on the list for the future, many of 
these Orgs don’t the deep pockets necessary to go to the secondary market.  I 
don’t think we should “punish” those orgs.

Thanks,
Tom Pruitt
Network Engineer
Stratus Networks

From: ARIN-PPML mailto:arin-ppml-boun...@arin.net>> 
On Behalf Of John Curran
Sent: Thursday, June 6, 2019 12:21 PM
To: ARIN-PPML List mailto:arin-ppml@arin.net>>
Subject: [arin-ppml] Looking for final show of support on revised Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
Importance: High

Folks -

We’ve had excellent discussion of various options for the revised “Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change – some of which is likely to have to further informed folks initial 
views on the matter (as well as on future policy proposals in this area), but 
at this time it is fairly important that we receive focused feedback on the 
revised policy text as written, with due consideration to the discussion that 
has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and
 “No” being indicative that you’d rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.)

2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”,
is there any modification to the proposed policy change that would enable you 
to support it?

I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers




Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their recommendation 
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing 
List for a second community discussion period of 14 days, to conclude on 7 June.

Once completed, the Board of Trustees will review the AC’s recommendation and 
the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff and 
was approved for further community consultation at the ARIN AC meeting on May 
16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the 
ARIN Advisory Council recommends the following actions to the Board of Trustees 
in response to the Board’s suspension of part 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[John Curran]

Tom -

To be clear, if the only choices are status quo (no wait list issuance for 
foreseeable future) or resume under the AC proposed change, you are 
recommending status quo - correct?

/John

John Curran
President and CEO
American Registry for Internet Numbers


On 6 Jun 2019, at 3:01 PM, Tom Pruitt 
mailto:tpru...@stratusnet.com>> wrote:

No  -- I can not support the new policy if applied to the current waiting list.

--  I don’t support applying the new restriction (only Orgs holding a /20 or 
less can get on the waiting list) to Orgs that were on the list prior to the 
suspension.


--I also would rather see those same Orgs get their requested allocation as 
long as they were approved for it initially.  (yes I think a /15 is excessive, 
but if they were approved for it before the rules changed….).

--At the very least Orgs that were on the list prior to the suspension should 
get either their requested allocation, or if their request was larger than the 
new Max allocation they should get the Max allocation.


I could support the suggested changes if they did not get applied to the Orgs 
on the waiting list prior to the suspension.  Once the suspension took affect 
Orgs knew changes were coming, and it is reasonable to change the policy, prior 
to that, they in good faith applied and were approved properly using the set 
policy.  Prudent or not, some Orgs counted on the list for the future, many of 
these Orgs don’t the deep pockets necessary to go to the secondary market.  I 
don’t think we should “punish” those orgs.

Thanks,
Tom Pruitt
Network Engineer
Stratus Networks

From: ARIN-PPML mailto:arin-ppml-boun...@arin.net>> 
On Behalf Of John Curran
Sent: Thursday, June 6, 2019 12:21 PM
To: ARIN-PPML List mailto:arin-ppml@arin.net>>
Subject: [arin-ppml] Looking for final show of support on revised Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
Importance: High

Folks -

We’ve had excellent discussion of various options for the revised “Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change – some of which is likely to have to further informed folks initial 
views on the matter (as well as on future policy proposals in this area), but 
at this time it is fairly important that we receive focused feedback on the 
revised policy text as written, with due consideration to the discussion that 
has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and
 “No” being indicative that you’d rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.)

2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”,
is there any modification to the proposed policy change that would enable you 
to support it?

I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers



Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their recommendation 
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing 
List for a second community discussion period of 14 days, to conclude on 7 June.

Once completed, the Board of Trustees will review the AC’s recommendation and 
the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff and 
was approved for further community consultation at the ARIN AC meeting on May 
16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the 
ARIN Advisory Council recommends the following actions to the Board of Trustees 
in response to the Board’s suspension of part of the operation of sections 
4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full operation of 
sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
4.10 space) from the ARIN Waitlist. The maximum size 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Steven Ryerse via ARIN-PPML]

+1 for toms comments

Sent from my iPhone

On Jun 6, 2019, at 3:03 PM, Tom Pruitt 
mailto:tpru...@stratusnet.com>> wrote:

No  -- I can not support the new policy if applied to the current waiting list.

--  I don’t support applying the new restriction (only Orgs holding a /20 or 
less can get on the waiting list) to Orgs that were on the list prior to the 
suspension.


--I also would rather see those same Orgs get their requested allocation as 
long as they were approved for it initially.  (yes I think a /15 is excessive, 
but if they were approved for it before the rules changed….).

--At the very least Orgs that were on the list prior to the suspension should 
get either their requested allocation, or if their request was larger than the 
new Max allocation they should get the Max allocation.


I could support the suggested changes if they did not get applied to the Orgs 
on the waiting list prior to the suspension.  Once the suspension took affect 
Orgs knew changes were coming, and it is reasonable to change the policy, prior 
to that, they in good faith applied and were approved properly using the set 
policy.  Prudent or not, some Orgs counted on the list for the future, many of 
these Orgs don’t the deep pockets necessary to go to the secondary market.  I 
don’t think we should “punish” those orgs.

Thanks,
Tom Pruitt
Network Engineer
Stratus Networks

From: ARIN-PPML mailto:arin-ppml-boun...@arin.net>> 
On Behalf Of John Curran
Sent: Thursday, June 6, 2019 12:21 PM
To: ARIN-PPML List mailto:arin-ppml@arin.net>>
Subject: [arin-ppml] Looking for final show of support on revised Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
Importance: High

Folks -

We’ve had excellent discussion of various options for the revised “Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change – some of which is likely to have to further informed folks initial 
views on the matter (as well as on future policy proposals in this area), but 
at this time it is fairly important that we receive focused feedback on the 
revised policy text as written, with due consideration to the discussion that 
has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and
 “No” being indicative that you’d rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.)

2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”,
is there any modification to the proposed policy change that would enable you 
to support it?

I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers



Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their recommendation 
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing 
List for a second community discussion period of 14 days, to conclude on 7 June.

Once completed, the Board of Trustees will review the AC’s recommendation and 
the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff and 
was approved for further community consultation at the ARIN AC meeting on May 
16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the 
ARIN Advisory Council recommends the following actions to the Board of Trustees 
in response to the Board’s suspension of part of the operation of sections 
4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full operation of 
sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an 
organization may qualify for at any one time is a /22. Organizations will be 
able to elect a smaller block size than they qualify for down to a /24. Only 
organizations holding a /20 or less of IPv4 address 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Tom Pruitt]

No  -- I can not support the new policy if applied to the current waiting list.

--  I don’t support applying the new restriction (only Orgs holding a /20 or 
less can get on the waiting list) to Orgs that were on the list prior to the 
suspension.


--I also would rather see those same Orgs get their requested allocation as 
long as they were approved for it initially.  (yes I think a /15 is excessive, 
but if they were approved for it before the rules changed….).

--At the very least Orgs that were on the list prior to the suspension should 
get either their requested allocation, or if their request was larger than the 
new Max allocation they should get the Max allocation.


I could support the suggested changes if they did not get applied to the Orgs 
on the waiting list prior to the suspension.  Once the suspension took affect 
Orgs knew changes were coming, and it is reasonable to change the policy, prior 
to that, they in good faith applied and were approved properly using the set 
policy.  Prudent or not, some Orgs counted on the list for the future, many of 
these Orgs don’t the deep pockets necessary to go to the secondary market.  I 
don’t think we should “punish” those orgs.

Thanks,
Tom Pruitt
Network Engineer
Stratus Networks

From: ARIN-PPML  On Behalf Of John Curran
Sent: Thursday, June 6, 2019 12:21 PM
To: ARIN-PPML List 
Subject: [arin-ppml] Looking for final show of support on revised Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
Importance: High

Folks -

We’ve had excellent discussion of various options for the revised “Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change – some of which is likely to have to further informed folks initial 
views on the matter (as well as on future policy proposals in this area), but 
at this time it is fairly important that we receive focused feedback on the 
revised policy text as written, with due consideration to the discussion that 
has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and
 “No” being indicative that you’d rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.)

2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”,
is there any modification to the proposed policy change that would enable you 
to support it?

I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers



Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their recommendation 
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing 
List for a second community discussion period of 14 days, to conclude on 7 June.

Once completed, the Board of Trustees will review the AC’s recommendation and 
the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff and 
was approved for further community consultation at the ARIN AC meeting on May 
16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the 
ARIN Advisory Council recommends the following actions to the Board of Trustees 
in response to the Board’s suspension of part of the operation of sections 
4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full operation of 
sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an 
organization may qualify for at any one time is a /22. Organizations will be 
able to elect a smaller block size than they qualify for down to a /24. Only 
organizations holding a /20 or less of IPv4 address space may apply and be 
approved. Address space distributed from the waitlist will not be eligible for 
transfer for a period of 60 months. This policy will be applied to all future 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Paul Andersen]

Michael,

Given the timing of the next ARIN Advisory Council and Board Meeting(s) and the 
next scheduled allocation of resources by staff — it is the only option if the 
community does not want to delay resumption of the waiting list. If the 
community feels that we need to go back to the drawing board that is fully an 
option; however, it may involve delaying resumption of the waiting list. 

Cheers,

Paul



> On Jun 6, 2019, at 1:33 PM, Michael Williams via ARIN-PPML 
>  wrote:
> 
> If the only choice is to not issue or issue /22, I suppose resuming.
> 
> Sent from my iPhone
> 
> On 6 Jun 2019, at 13:30, John Curran  > wrote:
> 
>> Michael - 
>> 
>> To be clear, if the only choices are status quo (no wait list issuance for 
>> foreseeable future) or resume under the AC proposed change, you are 
>> recommending status quo - correct?
>> 
>> /John
>> 
>> p.s.  The reason we ask in this particular manner is because we can’t 
>> accurately gauge support or lack thereof of this particular change, if those 
>> indicating “No” are  predicated on future conditions that may be different 
>> or may not occur (consensus on a different size, or additional constraints, 
>> etc.)   - Thanks! 
>> 
>> 
>>> On 6 Jun 2019, at 1:24 PM, Michael Williams >> > wrote:
>>> 
>>> No. I do not support the policy as written. I believe the request size 
>>> should be increased to a /21.
>>> 
>>> Furthermore either in this policy or a seperate one should require any IP 
>>> issuances coming from the waitlist to be returned to ARIN if they are no 
>>> longer used. We should not allow IPs acquired from waitlist to be 
>>> transferred unless the company is fully acquired.
>>> 
>>> I represent ARIN member organisation GLEXI-3.
>>> 
>>> Sent from my iPhone
>>> 
>>> On 6 Jun 2019, at 13:20, John Curran >> > wrote:
>>> 
 Folks - 
 
 We’ve had excellent discussion of various options for the revised 
 “Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  
 proposed policy change – some of which is likely to have to further 
 informed folks initial views on the matter (as well as on future policy 
 proposals in this area), but at this time it is fairly important that we 
 receive focused feedback on the revised policy text as written, with due 
 consideration to the discussion that has occurred online. 
 
 To that end, at this time it would be good to know from everyone: 
 
 1.  Are you in favor of ARIN making the policy change specified in the 
 revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet 
 Requests”  ?
 
 (“Yes” obviously indicative that you’d like ARIN to proceed with its 
 adoption and resumption of wait list issuance under its revised 
 guidelines, and 
  “No” being indicative that you’d rather have the suspension of wait list 
 issuance continue unless/until some other policy change in this area 
 reaches consensus.) 
 
 2.  If you are not supportive of ARIN making the change specified in the 
 revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet 
 Requests”,
 is there any modification to the proposed policy change that would enable 
 you to support it?
 
 I would ask that PPML participants take a moment to consider the proposed 
 policy change as written and please reply regarding the questions above. 
 
 Thanks!
 /John
 
 John Curran
 President and CEO
 American Registry for Internet Numbers
 
 
> Begin forwarded message:
> 
> From: ARIN mailto:i...@arin.net>>
> Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding 
> NRPM 4.1.8. Unmet Requests
> Date: 24 May 2019 at 1:04:58 PM EDT
> To: mailto:arin-ppml@arin.net>>
> 
> At their 16 May meeting, the Advisory Council revised their 
> recommendation regarding NRPM 4.1.8. Unmet Requests.
> 
> The revised recommendation is hereby submitted to the Public Policy 
> Mailing List for a second community discussion period of 14 days, to 
> conclude on 7 June.
> 
> Once completed, the Board of Trustees will review the AC’s recommendation 
> and the PPML discussion.
> 
> The full text of the Advisory Council's revised recommendation is below.
> 
> Sean Hopkins
> Policy Analyst
> American Registry for Internet Numbers (ARIN)
> 
> 
> 
> Advisory Council recommendation:
> 
> This is an updated version which incorporates feedback from the ARIN 
> staff and was approved for further community consultation at the ARIN AC 
> meeting on May 16, 2019.
> 
> In accordance with section 10.2 of the ARIN Policy Development Process, 
> the ARIN Advisory Council recommends the following actions to the Board 
> of Trustees in response to the Board’s 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Brian Reid]

> 1.  Are you in favor of ARIN making the policy change specified in the 
> revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet 
> Requests"  ?

Yes.___
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] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Michael Williams via ARIN-PPML]

If the only choice is to not issue or issue /22, I suppose resuming.

Sent from my iPhone

On 6 Jun 2019, at 13:30, John Curran  wrote:

Michael -

To be clear, if the only choices are status quo (no wait list issuance for
foreseeable future) or resume under the AC proposed change, you are
recommending status quo - correct?

/John

p.s.  The reason we ask in this particular manner is because we can’t
accurately gauge support or lack thereof of this particular change, if
those indicating “No” are  predicated on future conditions that may be
different or may not occur (consensus on a different size, or additional
constraints, etc.)   - Thanks!


On 6 Jun 2019, at 1:24 PM, Michael Williams 
wrote:

No. I do not support the policy as written. I believe the request size
should be increased to a /21.

Furthermore either in this policy or a seperate one should require any IP
issuances coming from the waitlist to be returned to ARIN if they are no
longer used. We should not allow IPs acquired from waitlist to be
transferred unless the company is fully acquired.

I represent ARIN member organisation GLEXI-3.

Sent from my iPhone

On 6 Jun 2019, at 13:20, John Curran  wrote:

Folks -

We’ve had excellent discussion of various options for the revised “Advisory
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed
policy change – some of which is likely to have to further informed folks
initial views on the matter (as well as on future policy proposals in this
area), but at this time it is fairly important that we receive focused
feedback on the revised policy text as written, with due consideration to
the discussion that has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the
revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its
adoption and resumption of wait list issuance under its revised guidelines,
and
 “No” being indicative that you’d rather have the suspension of wait list
issuance continue unless/until some other policy change in this area
reaches consensus.)

2.  If you are not supportive of ARIN making the change specified in the
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
Requests”,
is there any modification to the proposed policy change that would enable
you to support it?

I would ask that PPML participants take a moment to consider the proposed
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers


Begin forwarded message:

*From: *ARIN 
*Subject: **[arin-ppml] Revised - Advisory Council Recommendation Regarding
NRPM 4.1.8. Unmet Requests*
*Date: *24 May 2019 at 1:04:58 PM EDT
*To: *

At their 16 May meeting, the Advisory Council revised their recommendation
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing
List for a second community discussion period of 14 days, to conclude on 7
June.

Once completed, the Board of Trustees will review the AC’s recommendation
and the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff
and was approved for further community consultation at the ARIN AC meeting
on May 16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the
ARIN Advisory Council recommends the following actions to the Board of
Trustees in response to the Board’s suspension of part of the operation of
sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full
operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
organization may qualify for at any one time is a /22. Organizations will
be able to elect a smaller block size than they qualify for down to a /24.
Only organizations holding a /20 or less of IPv4 address space may apply
and be approved. Address space distributed from the waitlist will not be
eligible for transfer for a period of 60 months. This policy will be
applied to all future distributions from the waitlist to include those
currently listed.

Repeated requests, in a manner that would circumvent 4.1.6, are not
allowed: an organization currently on the waitlist must wait 90 days after
receiving a distribution from the waitlist before applying for additional
space. ARIN, at its sole discretion, may waive this requirement if the
requester can document a change in circumstances 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Tom Fantacone]

No - oppose.  But I would support it if the 60 month waiting period was reduced 
to 12 or 24 months.  60 months means companies who no longer need the resources 
will just sit on them till they can sell them.  Not an efficient way to get 
them into the hands of those who need them.

And also that it shouldn't affect current waiting list participants who planned 
their networks based on prior policy.


 On Thu, 06 Jun 2019 13:20:40 -0400 John Curran  
wrote 


Folks - 



We’ve had excellent discussion of various options for the revised “Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change – some of which is likely to have to further informed folks initial 
views on the matter
 (as well as on future policy proposals in this area), but at this time it is 
fairly important that we receive focused feedback on the revised policy text as 
written, with due consideration to the discussion that has occurred online. 



To that end, at this time it would be good to know from everyone: 



1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”  ?



(“Yes” obviously indicative that you’d like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and 

 “No” being indicative that you’d rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.) 



2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”,

is there any modification to the proposed policy change that would enable you 
to support it?



I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above. 



Thanks!

/John



John Curran

President and CEO

American Registry for Internet Numbers



Begin forwarded message:


From: ARIN 

Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests

Date: 24 May 2019 at 1:04:58 PM EDT

To: 


At their 16 May meeting, the Advisory Council revised their recommendation 
regarding NRPM 4.1.8. Unmet Requests.
 
 The revised recommendation is hereby submitted to the Public Policy Mailing 
List for a second community discussion period of 14 days, to conclude on 7 June.
 
 Once completed, the Board of Trustees will review the AC’s recommendation and 
the PPML discussion.
 
 The full text of the Advisory Council's revised recommendation is below.
 
 Sean Hopkins
 Policy Analyst
 American Registry for Internet Numbers (ARIN)
 
 
 
 Advisory Council recommendation:
 
 This is an updated version which incorporates feedback from the ARIN staff and 
was approved for further community consultation at the ARIN AC meeting on May 
16, 2019.
 
 In accordance with section 10.2 of the ARIN Policy Development Process, the 
ARIN Advisory Council recommends the following actions to the Board of Trustees 
in response to the Board’s suspension of part of the operation of sections 
4.1.8, 4.1.8.1 and 4.1.8.2
 of the Numbering Resource Policy Manual:
 
 Replace section 4.1.8 et. seq. as follows, then reinstate the full operation 
of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
 
 4.1.8 ARIN Waitlist
 
 ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an 
organization may qualify for at any one time is a /22. Organizations will be 
able to elect a smaller block size
 than they qualify for down to a /24. Only organizations holding a /20 or less 
of IPv4 address space may apply and be approved. Address space distributed from 
the waitlist will not be eligible for transfer for a period of 60 months. This 
policy will be applied
 to all future distributions from the waitlist to include those currently 
listed.
 
 Repeated requests, in a manner that would circumvent 4.1.6, are not allowed: 
an organization currently on the waitlist must wait 90 days after receiving a 
distribution from the waitlist before applying for additional space. ARIN, at 
its sole discretion, may
 waive this requirement if the requester can document a change in circumstances 
since their last request that could not have been reasonably foreseen at the 
time of the original request, and which now justifies additional space. 
Qualified requesters whose request
 will also be advised of the availability of the transfer mechanism in section 
8.3 as an alternative mechanism to obtain IPv4 addresses.
 
 4.1.8.1 Sequencing
 
 The position of each qualified request on the waiting list will be determined 
by the date it was approved. Each organization may have one approved request on 
the waiting list at a time.
 
 4.1.8.2 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Matthew Wilder]

+1, I also support ARIN adopting the changes recommended by the AC.

Having followed discussion on the mailing list and in person (at ARIN 43) I was 
able to see first-hand the good faith discussions and rationale which led to 
the CIDR size limitation and timing for wait list issuance.  Better to have 
more organization have limited access to IPv4 resources for the foreseeable 
future than to reward fewer organizations with larger IPv4 allocations when 
they instead should be looking to IPv6.

Matthew Wilder

From: ARIN-PPML  On Behalf Of Leif Sawyer
Sent: June 6, 2019 10:26 AM
To: 'ARIN-PPML List' 
Subject: Re: [arin-ppml] Looking for final show of support on revised Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

+1 support the policy change as currently written


Also, as a general reminder, we don't have to get this *perfect*  out of the 
gates, and we -the community-  can suggest follow-up policy changes
if things start looking strange.   But if we wait to try to find a perfect 
balance between all parties, we'll never resume issuance.

Leif

From: ARIN-PPML mailto:arin-ppml-boun...@arin.net>> 
On Behalf Of John Curran
Sent: Thursday, June 6, 2019 9:21 AM
To: ARIN-PPML List mailto:arin-ppml@arin.net>>
Subject: [arin-ppml] Looking for final show of support on revised Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
Importance: High

[EXTERNAL EMAIL - CAUTION: Do not open unexpected attachments or links.]
Folks -

We've had excellent discussion of various options for the revised "Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change - some of which is likely to have to further informed folks initial 
views on the matter (as well as on future policy proposals in this area), but 
at this time it is fairly important that we receive focused feedback on the 
revised policy text as written, with due consideration to the discussion that 
has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  ?

("Yes" obviously indicative that you'd like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and
 "No" being indicative that you'd rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.)

2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests",
is there any modification to the proposed policy change that would enable you 
to support it?

I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers


Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their recommendation 
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing 
List for a second community discussion period of 14 days, to conclude on 7 June.

Once completed, the Board of Trustees will review the AC's recommendation and 
the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff and 
was approved for further community consultation at the ARIN AC meeting on May 
16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the 
ARIN Advisory Council recommends the following actions to the Board of Trustees 
in response to the Board's suspension of part of the operation of sections 
4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering 
Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full operation of 
sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an 
organization may qualify for at any one time is a /22. Organizations will be 
able to elect a smaller block size than they qualify for down to a /24. Only 
organizations holding a /20 or less of IPv4 address space may apply and be 
approved. Address space distributed from the waitlist will not be eligible for 
transfer for a period of 60 months. This policy will be 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Seth Mattinen]

On 6/6/19 10:20 AM, John Curran wrote:
1.  Are you in favor of ARIN making the policy change specified in the 
revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet 
Requests”  ?



Yes, I support this policy.

~Seth
___
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] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Michael Casadevall]

+1 support from here as well

On Thu, Jun 6, 2019, 17:29 Scott Leibrand  wrote:

> +1 support for the draft policy as written, and to Leif's other points.
>
> -Scott
>
> On Thu, Jun 6, 2019 at 10:26 AM Leif Sawyer  wrote:
>
>> +1 support the policy change as currently written
>>
>>
>>
>>
>>
>> Also, as a general reminder, we don’t have to get this **perfect**  out
>> of the gates, and we -the community-  can suggest follow-up policy changes
>>
>> if things start looking strange.   But if we wait to try to find a
>> perfect balance between all parties, we’ll never resume issuance.
>>
>>
>>
>> Leif
>>
>>
>>
>> *From:* ARIN-PPML  *On Behalf Of *John Curran
>> *Sent:* Thursday, June 6, 2019 9:21 AM
>> *To:* ARIN-PPML List 
>> *Subject:* [arin-ppml] Looking for final show of support on revised
>> Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
>> *Importance:* High
>>
>>
>>
>> [*EXTERNAL EMAIL* - CAUTION: Do not open unexpected attachments or
>> links.]
>>
>> Folks -
>>
>>
>>
>> We’ve had excellent discussion of various options for the revised
>> “Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"
>>  proposed policy change – some of which is likely to have to further
>> informed folks initial views on the matter (as well as on future policy
>> proposals in this area), but at this time it is fairly important that we
>> receive focused feedback on the revised policy text as written, with due
>> consideration to the discussion that has occurred online.
>>
>>
>>
>> To that end, at this time it would be good to know from everyone:
>>
>>
>>
>> 1.  Are you in favor of ARIN making the policy change specified in the
>> revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
>> Requests”  ?
>>
>>
>>
>> (“Yes” obviously indicative that you’d like ARIN to proceed with its
>> adoption and resumption of wait list issuance under its revised guidelines,
>> and
>>
>>  “No” being indicative that you’d rather have the suspension of wait list
>> issuance continue unless/until some other policy change in this area
>> reaches consensus.)
>>
>>
>>
>> 2.  If you are not supportive of ARIN making the change specified in the
>> revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
>> Requests”,
>>
>> is there any modification to the proposed policy change that would enable
>> you to support it?
>>
>>
>>
>> I would ask that PPML participants take a moment to consider the proposed
>> policy change as written and please reply regarding the questions above.
>>
>>
>>
>> Thanks!
>>
>> /John
>>
>>
>>
>> John Curran
>>
>> President and CEO
>>
>> American Registry for Internet Numbers
>>
>>
>>
>>
>>
>> Begin forwarded message:
>>
>>
>>
>> *From: *ARIN 
>>
>> *Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding
>> NRPM 4.1.8. Unmet Requests*
>>
>> *Date: *24 May 2019 at 1:04:58 PM EDT
>>
>> *To: *
>>
>>
>>
>> At their 16 May meeting, the Advisory Council revised their
>> recommendation regarding NRPM 4.1.8. Unmet Requests.
>>
>> The revised recommendation is hereby submitted to the Public Policy
>> Mailing List for a second community discussion period of 14 days, to
>> conclude on 7 June.
>>
>> Once completed, the Board of Trustees will review the AC’s recommendation
>> and the PPML discussion.
>>
>> The full text of the Advisory Council's revised recommendation is below.
>>
>> Sean Hopkins
>> Policy Analyst
>> American Registry for Internet Numbers (ARIN)
>>
>>
>>
>> Advisory Council recommendation:
>>
>> This is an updated version which incorporates feedback from the ARIN
>> staff and was approved for further community consultation at the ARIN AC
>> meeting on May 16, 2019.
>>
>> In accordance with section 10.2 of the ARIN Policy Development Process,
>> the ARIN Advisory Council recommends the following actions to the Board of
>> Trustees in response to the Board’s suspension of part of the operation of
>> sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy
>> Manual:
>>
>> Replace section 4.1.8 et. seq. as follows, then reinstate the full
>> operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
>>
>> 4.1.8 ARIN Waitlist
>>
>> ARIN will only issue future IPv4 assignments/allocations (excluding 4.4
>> and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
>> organization may qualify for at any one time is a /22. Organizations will
>> be able to elect a smaller block size than they qualify for down to a /24.
>> Only organizations holding a /20 or less of IPv4 address space may apply
>> and be approved. Address space distributed from the waitlist will not be
>> eligible for transfer for a period of 60 months. This policy will be
>> applied to all future distributions from the waitlist to include those
>> currently listed.
>>
>> Repeated requests, in a manner that would circumvent 4.1.6, are not
>> allowed: an organization currently on the waitlist must wait 90 days after
>> receiving a distribution from the 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[John Curran]

Michael -

To be clear, if the only choices are status quo (no wait list issuance for 
foreseeable future) or resume under the AC proposed change, you are 
recommending status quo - correct?

/John

p.s.  The reason we ask in this particular manner is because we can’t 
accurately gauge support or lack thereof of this particular change, if those 
indicating “No” are  predicated on future conditions that may be different or 
may not occur (consensus on a different size, or additional constraints, etc.)  
 - Thanks!


On 6 Jun 2019, at 1:24 PM, Michael Williams 
mailto:michael.willi...@glexia.com>> wrote:

No. I do not support the policy as written. I believe the request size should 
be increased to a /21.

Furthermore either in this policy or a seperate one should require any IP 
issuances coming from the waitlist to be returned to ARIN if they are no longer 
used. We should not allow IPs acquired from waitlist to be transferred unless 
the company is fully acquired.

I represent ARIN member organisation GLEXI-3.

Sent from my iPhone

On 6 Jun 2019, at 13:20, John Curran 
mailto:jcur...@arin.net>> wrote:

Folks -

We’ve had excellent discussion of various options for the revised “Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change – some of which is likely to have to further informed folks initial 
views on the matter (as well as on future policy proposals in this area), but 
at this time it is fairly important that we receive focused feedback on the 
revised policy text as written, with due consideration to the discussion that 
has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and
 “No” being indicative that you’d rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.)

2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”,
is there any modification to the proposed policy change that would enable you 
to support it?

I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers


Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their recommendation 
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing 
List for a second community discussion period of 14 days, to conclude on 7 June.

Once completed, the Board of Trustees will review the AC’s recommendation and 
the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff and 
was approved for further community consultation at the ARIN AC meeting on May 
16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the 
ARIN Advisory Council recommends the following actions to the Board of Trustees 
in response to the Board’s suspension of part of the operation of sections 
4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full operation of 
sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an 
organization may qualify for at any one time is a /22. Organizations will be 
able to elect a smaller block size than they qualify for down to a /24. Only 
organizations holding a /20 or less of IPv4 address space may apply and be 
approved. Address space distributed from the waitlist will not be eligible for 
transfer for a period of 60 months. This policy will be applied to all future 
distributions from the waitlist to include those currently listed.

Repeated requests, in a manner that would circumvent 4.1.6, are not allowed: an 
organization currently on the waitlist must wait 90 days after receiving a 
distribution from the waitlist before applying for additional space. ARIN, at 
its sole discretion, may waive this requirement if the requester can document a 
change in 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Owen DeLong]

Yes. I favor the AC’s revised recommendation. The changes address certain staff 
concerns we hadn’t previously considered while maintaining a structure which I 
believe is widely supported within the community.

Even if this isn’t the perfect solution, I believe it is a good way forward and 
additional modification should be done through the standard policy process. 

Owen


> On Jun 6, 2019, at 10:20, John Curran  wrote:
> 
> Folks - 
> 
> We’ve had excellent discussion of various options for the revised “Advisory 
> Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
> change – some of which is likely to have to further informed folks initial 
> views on the matter (as well as on future policy proposals in this area), but 
> at this time it is fairly important that we receive focused feedback on the 
> revised policy text as written, with due consideration to the discussion that 
> has occurred online. 
> 
> To that end, at this time it would be good to know from everyone: 
> 
> 1.  Are you in favor of ARIN making the policy change specified in the 
> revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet 
> Requests”  ?
> 
> (“Yes” obviously indicative that you’d like ARIN to proceed with its adoption 
> and resumption of wait list issuance under its revised guidelines, and 
>  “No” being indicative that you’d rather have the suspension of wait list 
> issuance continue unless/until some other policy change in this area reaches 
> consensus.) 
> 
> 2.  If you are not supportive of ARIN making the change specified in the 
> revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet 
> Requests”,
> is there any modification to the proposed policy change that would enable you 
> to support it?
> 
> I would ask that PPML participants take a moment to consider the proposed 
> policy change as written and please reply regarding the questions above. 
> 
> Thanks!
> /John
> 
> John Curran
> President and CEO
> American Registry for Internet Numbers
> 
> 
>> Begin forwarded message:
>> 
>> From: ARIN 
>> Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding 
>> NRPM 4.1.8. Unmet Requests
>> Date: 24 May 2019 at 1:04:58 PM EDT
>> To: 
>> 
>> At their 16 May meeting, the Advisory Council revised their recommendation 
>> regarding NRPM 4.1.8. Unmet Requests.
>> 
>> The revised recommendation is hereby submitted to the Public Policy Mailing 
>> List for a second community discussion period of 14 days, to conclude on 7 
>> June.
>> 
>> Once completed, the Board of Trustees will review the AC’s recommendation 
>> and the PPML discussion.
>> 
>> The full text of the Advisory Council's revised recommendation is below.
>> 
>> Sean Hopkins
>> Policy Analyst
>> American Registry for Internet Numbers (ARIN)
>> 
>> 
>> 
>> Advisory Council recommendation:
>> 
>> This is an updated version which incorporates feedback from the ARIN staff 
>> and was approved for further community consultation at the ARIN AC meeting 
>> on May 16, 2019.
>> 
>> In accordance with section 10.2 of the ARIN Policy Development Process, the 
>> ARIN Advisory Council recommends the following actions to the Board of 
>> Trustees in response to the Board’s suspension of part of the operation of 
>> sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:
>> 
>> Replace section 4.1.8 et. seq. as follows, then reinstate the full operation 
>> of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
>> 
>> 4.1.8 ARIN Waitlist
>> 
>> ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
>> 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an 
>> organization may qualify for at any one time is a /22. Organizations will be 
>> able to elect a smaller block size than they qualify for down to a /24. Only 
>> organizations holding a /20 or less of IPv4 address space may apply and be 
>> approved. Address space distributed from the waitlist will not be eligible 
>> for transfer for a period of 60 months. This policy will be applied to all 
>> future distributions from the waitlist to include those currently listed.
>> 
>> Repeated requests, in a manner that would circumvent 4.1.6, are not allowed: 
>> an organization currently on the waitlist must wait 90 days after receiving 
>> a distribution from the waitlist before applying for additional space. ARIN, 
>> at its sole discretion, may waive this requirement if the requester can 
>> document a change in circumstances since their last request that could not 
>> have been reasonably foreseen at the time of the original request, and which 
>> now justifies additional space. Qualified requesters whose request will also 
>> be advised of the availability of the transfer mechanism in section 8.3 as 
>> an alternative mechanism to obtain IPv4 addresses.
>> 
>> 4.1.8.1 Sequencing
>> 
>> The position of each qualified request on the waiting list will be 
>> determined by the date it was 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Leif Sawyer]

+1 support the policy change as currently written


Also, as a general reminder, we don't have to get this *perfect*  out of the 
gates, and we -the community-  can suggest follow-up policy changes
if things start looking strange.   But if we wait to try to find a perfect 
balance between all parties, we'll never resume issuance.

Leif

From: ARIN-PPML  On Behalf Of John Curran
Sent: Thursday, June 6, 2019 9:21 AM
To: ARIN-PPML List 
Subject: [arin-ppml] Looking for final show of support on revised Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests
Importance: High

[EXTERNAL EMAIL - CAUTION: Do not open unexpected attachments or links.]
Folks -

We've had excellent discussion of various options for the revised "Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change - some of which is likely to have to further informed folks initial 
views on the matter (as well as on future policy proposals in this area), but 
at this time it is fairly important that we receive focused feedback on the 
revised policy text as written, with due consideration to the discussion that 
has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  ?

("Yes" obviously indicative that you'd like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and
 "No" being indicative that you'd rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.)

2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests",
is there any modification to the proposed policy change that would enable you 
to support it?

I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers



Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their recommendation 
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing 
List for a second community discussion period of 14 days, to conclude on 7 June.

Once completed, the Board of Trustees will review the AC's recommendation and 
the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff and 
was approved for further community consultation at the ARIN AC meeting on May 
16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the 
ARIN Advisory Council recommends the following actions to the Board of Trustees 
in response to the Board's suspension of part of the operation of sections 
4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering 
Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full operation of 
sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an 
organization may qualify for at any one time is a /22. Organizations will be 
able to elect a smaller block size than they qualify for down to a /24. Only 
organizations holding a /20 or less of IPv4 address space may apply and be 
approved. Address space distributed from the waitlist will not be eligible for 
transfer for a period of 60 months. This policy will be applied to all future 
distributions from the waitlist to include those currently listed.

Repeated requests, in a manner that would circumvent 4.1.6, are not allowed: an 
organization currently on the waitlist must wait 90 days after receiving a 
distribution from the waitlist before applying for additional space. ARIN, at 
its sole discretion, may waive this requirement if the requester can document a 
change in circumstances since their last request that could not have been 
reasonably foreseen at the time of the original request, and which now 
justifies additional space. Qualified requesters whose request will also be 
advised of the availability of the transfer mechanism in section 8.3 as an 
alternative mechanism to obtain IPv4 addresses.

4.1.8.1 Sequencing

The position of each 

Re: [arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[Michael Williams via ARIN-PPML]

No. I do not support the policy as written. I believe the request size
should be increased to a /21.

Furthermore either in this policy or a seperate one should require any IP
issuances coming from the waitlist to be returned to ARIN if they are no
longer used. We should not allow IPs acquired from waitlist to be
transferred unless the company is fully acquired.

I represent ARIN member organisation GLEXI-3.

Sent from my iPhone

On 6 Jun 2019, at 13:20, John Curran  wrote:

Folks -

We’ve had excellent discussion of various options for the revised “Advisory
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed
policy change – some of which is likely to have to further informed folks
initial views on the matter (as well as on future policy proposals in this
area), but at this time it is fairly important that we receive focused
feedback on the revised policy text as written, with due consideration to
the discussion that has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the
revised  "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its
adoption and resumption of wait list issuance under its revised guidelines,
and
 “No” being indicative that you’d rather have the suspension of wait list
issuance continue unless/until some other policy change in this area
reaches consensus.)

2.  If you are not supportive of ARIN making the change specified in the
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet
Requests”,
is there any modification to the proposed policy change that would enable
you to support it?

I would ask that PPML participants take a moment to consider the proposed
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers


Begin forwarded message:

*From: *ARIN 
*Subject: **[arin-ppml] Revised - Advisory Council Recommendation Regarding
NRPM 4.1.8. Unmet Requests*
*Date: *24 May 2019 at 1:04:58 PM EDT
*To: *

At their 16 May meeting, the Advisory Council revised their recommendation
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing
List for a second community discussion period of 14 days, to conclude on 7
June.

Once completed, the Board of Trustees will review the AC’s recommendation
and the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff
and was approved for further community consultation at the ARIN AC meeting
on May 16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the
ARIN Advisory Council recommends the following actions to the Board of
Trustees in response to the Board’s suspension of part of the operation of
sections 4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full
operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
organization may qualify for at any one time is a /22. Organizations will
be able to elect a smaller block size than they qualify for down to a /24.
Only organizations holding a /20 or less of IPv4 address space may apply
and be approved. Address space distributed from the waitlist will not be
eligible for transfer for a period of 60 months. This policy will be
applied to all future distributions from the waitlist to include those
currently listed.

Repeated requests, in a manner that would circumvent 4.1.6, are not
allowed: an organization currently on the waitlist must wait 90 days after
receiving a distribution from the waitlist before applying for additional
space. ARIN, at its sole discretion, may waive this requirement if the
requester can document a change in circumstances since their last request
that could not have been reasonably foreseen at the time of the original
request, and which now justifies additional space. Qualified requesters
whose request will also be advised of the availability of the transfer
mechanism in section 8.3 as an alternative mechanism to obtain IPv4
addresses.

4.1.8.1 Sequencing

The position of each qualified request on the waiting list will be
determined by the date it was approved. Each organization may have one
approved request on the waiting list at a time.

4.1.8.2 Fulfillment

ARIN will fulfill requests on a first-approved basis, subject to the size
of each available address block as address blocks become available for

[arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

[John Curran]

Folks -

We’ve had excellent discussion of various options for the revised “Advisory 
Council Recommendation Regarding NRPM 4.1.8. Unmet Requests"  proposed policy 
change – some of which is likely to have to further informed folks initial 
views on the matter (as well as on future policy proposals in this area), but 
at this time it is fairly important that we receive focused feedback on the 
revised policy text as written, with due consideration to the discussion that 
has occurred online.

To that end, at this time it would be good to know from everyone:

1.  Are you in favor of ARIN making the policy change specified in the revised  
"Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”  ?

(“Yes” obviously indicative that you’d like ARIN to proceed with its adoption 
and resumption of wait list issuance under its revised guidelines, and
 “No” being indicative that you’d rather have the suspension of wait list 
issuance continue unless/until some other policy change in this area reaches 
consensus.)

2.  If you are not supportive of ARIN making the change specified in the 
revised "Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests”,
is there any modification to the proposed policy change that would enable you 
to support it?

I would ask that PPML participants take a moment to consider the proposed 
policy change as written and please reply regarding the questions above.

Thanks!
/John

John Curran
President and CEO
American Registry for Internet Numbers


Begin forwarded message:

From: ARIN mailto:i...@arin.net>>
Subject: [arin-ppml] Revised - Advisory Council Recommendation Regarding NRPM 
4.1.8. Unmet Requests
Date: 24 May 2019 at 1:04:58 PM EDT
To: mailto:arin-ppml@arin.net>>

At their 16 May meeting, the Advisory Council revised their recommendation 
regarding NRPM 4.1.8. Unmet Requests.

The revised recommendation is hereby submitted to the Public Policy Mailing 
List for a second community discussion period of 14 days, to conclude on 7 June.

Once completed, the Board of Trustees will review the AC’s recommendation and 
the PPML discussion.

The full text of the Advisory Council's revised recommendation is below.

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



Advisory Council recommendation:

This is an updated version which incorporates feedback from the ARIN staff and 
was approved for further community consultation at the ARIN AC meeting on May 
16, 2019.

In accordance with section 10.2 of the ARIN Policy Development Process, the 
ARIN Advisory Council recommends the following actions to the Board of Trustees 
in response to the Board’s suspension of part of the operation of sections 
4.1.8, 4.1.8.1 and 4.1.8.2 of the Numbering Resource Policy Manual:

Replace section 4.1.8 et. seq. as follows, then reinstate the full operation of 
sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.

4.1.8 ARIN Waitlist

ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 
4.10 space) from the ARIN Waitlist. The maximum size aggregate that an 
organization may qualify for at any one time is a /22. Organizations will be 
able to elect a smaller block size than they qualify for down to a /24. Only 
organizations holding a /20 or less of IPv4 address space may apply and be 
approved. Address space distributed from the waitlist will not be eligible for 
transfer for a period of 60 months. This policy will be applied to all future 
distributions from the waitlist to include those currently listed.

Repeated requests, in a manner that would circumvent 4.1.6, are not allowed: an 
organization currently on the waitlist must wait 90 days after receiving a 
distribution from the waitlist before applying for additional space. ARIN, at 
its sole discretion, may waive this requirement if the requester can document a 
change in circumstances since their last request that could not have been 
reasonably foreseen at the time of the original request, and which now 
justifies additional space. Qualified requesters whose request will also be 
advised of the availability of the transfer mechanism in section 8.3 as an 
alternative mechanism to obtain IPv4 addresses.

4.1.8.1 Sequencing

The position of each qualified request on the waiting list will be determined 
by the date it was approved. Each organization may have one approved request on 
the waiting list at a time.

4.1.8.2 Fulfillment

ARIN will fulfill requests on a first-approved basis, subject to the size of 
each available address block as address blocks become available for 
distribution. A timely review of the original request may be conducted by ARIN 
staff. Requests will not be partially filled. Any requests met through a 
transfer will be considered fulfilled and removed from the waiting list.
___
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List