On Tue, Feb 26, 2019 at 10:33:45PM -0800, Ronald F. Guilmette wrote:
>
> In message ,
> John Curran wrote:
>
> >If you wish complete transparency regarding fraudulent requests, that can
> >be accommodated, but first requires the community to come to consensus that
> >requests for number
I appreciate the humour and agree with your statements but could we
keep the political commentary to a minimum? Your messages would have
the same affect.
Sent from my iPhone
> On 27 Feb 2019, at 01:53, Ronald F. Guilmette wrote:
>
>
> In message ,
> Robert Clarke wrote:
>
>> My proposal is
I agree it’s the endgame, stops all abuse.
In regards to what can be done with the money, there are a lot of creative
solutions that I’m sure the community can come up with. Better in the hands of
ARIN rather than fraudsters though.
Robert Clarke
CubeMotion LLC
rob...@cubemotion.com
M: +1
In message ,
Robert Clarke wrote:
>My proposal is that ARIN auctions off all available IPv4 ranges reserved
>for allocations under 4.2 policy and pockets the proceeds.
This was always and inevitably going to be the end game anyway... a true
and unfettered free market, where money talks and
Unfortunately that doesn’t solve any problems Michael. It would encourage
“off-ARIN” transfers more heavily and still lead to sales if a bit more
informal. Not only does this cause logistical problems for those with
legitimate M transactions but would still lead to fraudsters abusing the
In message ,
John Curran wrote:
>If you wish complete transparency regarding fraudulent requests, that can
>be accommodated, but first requires the community to come to consensus that
>requests for number resource activities (issuance/transfers/updates) should
>be made publicly. To my
Easy. Eliminate transfers. If you obtain a block you use it yourself
or it goes back to ARIN for redistribution. Seems easy enough to me.
We’ve been waiting years to get any available IP address as we have an
immediate need. I’m actually not sure why we even allow for private
transfers of blocks
On 26 Feb 2019, at 9:06 PM, Kevin Blumberg
mailto:kev...@thewire.ca>> wrote:
The problem statement is pretty damning in the abuse described. The BoT minutes
while mentioning misuse and abuse was void of the information described by the
policy author. While I would like to take the problem
On 26 Feb 2019, at 5:51 PM, Ronald F. Guilmette wrote:
> ...
> I see rampant abuse of the Internet, day in and day out, every bit of which
> involves number resources, said resources having been obtained, by hook or
> by crook, and virtually all of this online evil that I see is the proverbial
>
The problem statement is pretty damning in the abuse described. The BoT minutes
while mentioning misuse and abuse was void of the information described by the
policy author. While I would like to take the problem statement at face value,
it would be helpful, based on the current discussion, to
Concur with these statements. If resource issuance is going to be suspended
there should be documented evidence presented to the community. Asking for
a solution without truly explaining or illustrating the problem may yield
fruitless or less than desirable results.
Michael Williams
Glexia, Inc.
I agree with Ronald’s comments here. It is a disservice to the community to
cite abuse in previous waiting list requests and not publicize said abuse for
scrutiny.
Best Regards,
Robert Clarke
CubeMotion LLC
rob...@cubemotion.com
M: +1 (844) 244-8140 ex. 512
300 Lenora Street #454, Seattle, WA,
On 21 February 2019, the ARIN Advisory Council (AC) accepted
"ARIN-prop-261: Waiting List Block Size Restriction" as a Draft Policy.
Draft Policy ARIN-2019-2 is below and can be found at:
https://www.arin.net/policy/proposals/2019_2.html
You are encouraged to discuss all Draft Policies on
On 21 February 2019, the ARIN Advisory Council (AC) accepted
"ARIN-prop-260: Clarify Section 4 IPv4 Request Requirements" as a Draft
Policy.
Draft Policy ARIN-2019-1 is below and can be found at:
https://www.arin.net/policy/proposals/2019_1.html
You are encouraged to discuss all Draft
The following has been revised:
* Recommended Draft Policy ARIN-2018-2: Clarification to ISP Initial
Allocation
Revised text is below and can be found at:
https://www.arin.net/policy/proposals/2018_2.html
You are encouraged to discuss all Draft Policies on PPML. The AC will
evaluate the
The following has been revised:
* Draft Policy ARIN-2017-12: POC Notification and Validation Upon
Reassignment or Reallocation
Revised text is below and can be found at:
https://www.arin.net/policy/proposals/2017_12.html
You are encouraged to discuss all Draft Policies on PPML. The AC will
In accordance with the Policy Development Process, the Advisory Council
met on 21 February 2019.
The AC has advanced the following Proposals to Draft Policy Status (each
will be posted separately for discussion):
* ARIN-prop-260: Clarify Section 4 IPv4 Request Requirements
* ARIN-prop-261:
17 matches
Mail list logo
