William,
> Don't get me wrong. You can cure this fraud without going to extremes.
> An open peering policy doesn't require you to buy hardware for the
> other guy's convenience. Let him reimburse you or procure the hardware
> you spec out if he wants to peer. Nor do you have to extend your
> netwo
"I've said it before and I'll say it again: an ISP's refusal to
maintain a settlement-free open peering policy is directly linked with
said company's fraudulent double-billing for services."
aaannnddd.. I'm done with that post.
-
Mike Hammett
Intelligent Computing Solutions
http://
WHo cares? TOG (your third party shooting what you loosly call un-authorized
video) is not a party to the contract and therefore does not give a flying fuck
what it says. Nor do the parties to the contract have anything to say about
the matter.
So in other words, TOG is free to do whatever h
NTT also seemed to suffer, I wonder if it's the same issue there...
Rubens
On Sat, Jan 23, 2016 at 3:42 AM, Larry J. Blunk wrote:
>
>Service for the RADb whois protocol has now been restored. We were
> experiencing
> extensive DDOS activity directed at the whois service host(s).
>
> Reg
On 23 January 2016 at 02:43, Tore Anderson wrote:
> William,
>
>> Don't get me wrong. You can cure this fraud without going to extremes.
>> An open peering policy doesn't require you to buy hardware for the
>> other guy's convenience. Let him reimburse you or procure the hardware
>> you spec out i
People do prefix filtering based on *DB may think twice...
On 23.01.16 07:42, Larry J. Blunk wrote:
>
>Service for the RADb whois protocol has now been restored. We were
> experiencing
> extensive DDOS activity directed at the whois service host(s).
>
> Regards,
>Larry Blunk
>Meri
How come? What situations would you run into that are so urgent about updating
prefix lists that the task can’t be put off for a few hours?
> On Jan 23, 2016, at 1:50 PM, Max Tulyev wrote:
>
> People do prefix filtering based on *DB may think twice...
>
> On 23.01.16 07:42, Larry J. Blunk wr
On Sat, Jan 23, 2016 at 12:42:07AM -0500, Larry J. Blunk wrote:
> Service for the RADb whois protocol has now been restored. We were
> experiencing extensive DDOS activity directed at the whois service
> host(s).
The whois.radb.net IPv4 address changed earlier today, the new IP is
129.250.120.86.
On Sat, 23 Jan 2016 14:02:52 -0500, Daniel Corbe said:
> How come? What situations would you run into that are so urgent about
> updating
> prefix lists that the task canât be put off for a few hours?
Those of you who have cron jobs doing an automatic pull can be quite surprised
by scenarios l
On 01/23/2016 02:43 AM, Tore Anderson wrote:
William,
Don't get me wrong. You can cure this fraud without going to extremes.
An open peering policy doesn't require you to buy hardware for the
other guy's convenience. Let him reimburse you or procure the hardware
you spec out if he wants to peer
>> How come? What situations would you run into that are so urgent
>> about updating prefix lists that the task can’t be put off
>> for a few hours?
> Those of you who have cron jobs doing an automatic pull can be quite
> surprised by scenarios like this.
doing it from cron, smart. installing re
11 matches
Mail list logo
