The U.S. Cybersecurity & Infrastructure Security Agency (DHS) has released
version 2.0 of its advisory memorandum on identification of essential
critical infrastructure workers during COVID-19 response.
A lot of wordsmithing, and extensive lobbying by certain industries. Its
easy to pick
On 3/29/20 1:46 PM, Joe Greco wrote:
On Sun, Mar 29, 2020 at 07:46:28PM +0100, Nick Hilliard wrote:
Joe Greco wrote on 29/03/2020 15:56:
The concept of flooding isn't problematic by itself.
Flood often works fine until you attempt to scale it. Then it breaks,
just like Bj??rn admitted.
On Sun, Mar 29, 2020 at 07:46:28PM +0100, Nick Hilliard wrote:
> Joe Greco wrote on 29/03/2020 15:56:
> >On Sun, Mar 29, 2020 at 03:01:04PM +0100, Nick Hilliard wrote:
> >>because it uses flooding and can't guarantee reliable message
> >>distribution, particularly at higher traffic levels.
> >
>
On Sun, Mar 29, 2020 at 03:01:04PM +0100, Nick Hilliard wrote:
> Bj??rn Mork wrote on 29/03/2020 13:44:
> >How is nntp non-scalable?
>
> because it uses flooding and can't guarantee reliable message
> distribution, particularly at higher traffic levels.
That's so hideously wrong. It's like
> I heard, and am seeing that construction type jobs don't seem to be affected
> much with the virus shutdown. I mean I see guys building homes and working
> on roads all around me... furthermore, we've heard of a couple fiber cuts
> that have brought portions of our network down a couple
I have a customer in eastern Europe accessing a SAAS application hosted in
one of Azure's north America datacenters. for the past few days every
morning between 3am and 6am est performance slows to crawl. This is person
is like 8am to 11am locally so they cant get much done.
The local ISP is
Hi Harlan,
I am quite sure that we actually generally agree and are just talking
past each other, and so are you judging from your mail below.
Let’s move this discussion from the list.
Regards,
Ragnar
> On 29 Mar 2020, at 03:06, Harlan Stenn wrote:
>
>
>
> On 3/28/2020 5:35 PM, Ragnar
> On 29 Mar 2020, at 01:18, Harlan Stenn wrote:
>
> Ragnar,
>
> On 3/28/2020 4:59 PM, Ragnar Sundblad wrote:
>>
>>
>>> On 29 Mar 2020, at 00:35, Harlan Stenn wrote:
>>>
>>> Ragnar,
>>>
>>> On 3/28/2020 4:09 PM, Ragnar Sundblad wrote:
> On 28 Mar 2020, at 23:58, Harlan Stenn
> On 29 Mar 2020, at 00:35, Harlan Stenn wrote:
>
> Ragnar,
>
> On 3/28/2020 4:09 PM, Ragnar Sundblad wrote:
>>
>>> On 28 Mar 2020, at 23:58, Harlan Stenn wrote:
>>>
Steven Sommars said:
> The secure time transfer of NTS was designed to avoid
amplification attacks.
>>>
> On 28 Mar 2020, at 23:58, Harlan Stenn wrote:
>
>> Steven Sommars said:
>>> The secure time transfer of NTS was designed to avoid
>>amplification attacks.
>
> Uh, no.
Yes, it was.
As Steven said, “The secure time transfer of NTS was designed to
avoid amplification attacks”. I would
On Sun, Mar 29, 2020 at 10:31:50PM +0100, Nick Hilliard wrote:
> Joe Greco wrote on 29/03/2020 21:46:
> >On Sun, Mar 29, 2020 at 07:46:28PM +0100, Nick Hilliard wrote:
> >>>That's so hideously wrong. It's like claiming web forums don't
> >>>work because IP packet delivery isn't reliable.
> >>
>
> On 28 Mar 2020, at 23:29, Bottiger wrote:
...
> Broken protocols need to be removed and blacklisted at every edge.
A protocol isn’t broken just because it can be abused when spoofed,
it is abused. Even TCP can be abused in that way.
Should we blacklist and remove TCP?
> Pushing the
> On 27 Mar 2020, at 18:54, Saku Ytti wrote:
>
> On Fri, 27 Mar 2020 at 19:48, Ragnar Sundblad wrote:
>
>> Is this really what the ISP community wants - to kill off port 123,
>> and force NTP to move to random ports?
>
> Make NST attenuation vector, so that reply is guaranteed to be
>
Joe Greco wrote on 29/03/2020 21:46:
On Sun, Mar 29, 2020 at 07:46:28PM +0100, Nick Hilliard wrote:
That's so hideously wrong. It's like claiming web forums don't
work because IP packet delivery isn't reliable.
Really, it's nothing like that.
Sure it is. At a certain point you can get web
Hello all.
As you are aware, the world is facing the ongoing challenge of the
spread of the Coronavirus (COVID-19), which has had a material impact on
a number of local, regional and global events and businesses across
various industries.
Unfortunately, the preparation for SAFNOG-6, initially
Joe Greco wrote on 29/03/2020 15:56:
On Sun, Mar 29, 2020 at 03:01:04PM +0100, Nick Hilliard wrote:
because it uses flooding and can't guarantee reliable message
distribution, particularly at higher traffic levels.
That's so hideously wrong. It's like claiming web forums don't
work because
I did error somewhere, yes. If I didn't read that part, didn't send the right
link, etc. Not sure.
Yeah, single-homed on Cogent IPv6 is a problem.
Maybe I just assumed that if you had transit from someone, that you got IPv4
and IPv6 service with them. Who doesn't do that?
-
Mike
Bjørn Mork wrote on 29/03/2020 13:44:
How is nntp non-scalable?
because it uses flooding and can't guarantee reliable message
distribution, particularly at higher traffic levels.
The fact that it ended up having to implement TAKETHIS is only one
indication of what a truly awful protocol it
Nick Hilliard writes:
> nntp is a non-scalable protocol which broke under its own
> weight.
How is nntp non-scalable? It allows an infinite number of servers
connected in a tiered network, where you only have to connect to a few
other peers and carry whatever part of the traffic you want.
On Wed, Mar 25, 2020 at 05:27:41PM +, Nick Hilliard wrote:
> nntp is a non-scalable protocol which broke under its own weight. Threaded
> news-readers are a great way of catching up with large mailing lists if
> you're prepared to put in the effort to create a bidirectional gateway. But
>
20 matches
Mail list logo
