Their lawyers probably explained to them that they can "block" the call "after"
accepting it and thus can get the best of both world -- the revenue from
terminating the call while still preventing it from bothering their customers
...
--
The fact that there's a Highway to Hell but only a
On Wed, Jul 10, 2019 at 11:56 PM Sean Donelan wrote:
>
> On Tue, 9 Jul 2019, Sean Donelan wrote:
> > The agenda looks like lots of happy, happy talk from industry
> > representatives.
>
> In advance of the SHAKEN/STIR robocall summit, AT has issued a press
> release announcing plans to
On Tue, 9 Jul 2019, Sean Donelan wrote:
The agenda looks like lots of happy, happy talk from industry
representatives.
In advance of the SHAKEN/STIR robocall summit, AT has issued a press
release announcing plans to automatically block robocalls for its
customers.
On Mon, 8 Jul 2019, Keith Medcalf wrote:
The solution is to disallow spoofing. If the "pretty overlay
information" does not equal the "billing information" then do not permit
the call to be made. Easy Peasy.
This assumes that all calls from a phone number originate from the carrier
of
Over the past decade, numerous tools have been developed to check the
correctness of router configurations. However, there seems to be a gap
between the information these tools provide and the information required to
fix the configurations.
As part of an ongoing research project at Colgate
hi,
use Direct Access PAC file for clients to get the right endpoints.
Apply QoS to that traffic - and use that same PAC file to feed the IP
ranges into your QoS
rules on the firewall/router ?
alan
On Mon, 8 Jul 2019 at 17:15, Joe Yabuki wrote:
>
> Hi all,
>
> How do you deal with QoS for
On Tue, 9 Jul 2019, Mike O'Connor wrote:
:How do you deal with QoS for Office365, since the IPs are subject to changes ?
How often is the data in:
https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges
I was always taught that “if you can't say anything nice, don't say nothing at
all”—That being said, my last CenturyLink turnup was worse than my last AT
turnup. Take that for what it is worth.
/chris
We run a network over dark fiber originally gotten from Level3. Some of the
fiber they provided us they were getting from CL (formerly Qwest). Since L3
was the CL customer, not us, we needed L3 to escort us for access to our
equipment in several sites. Now that everyone's one big happy CL
They're not going to do anything unless there is a warrant, especially
considering that it's not a customer of theirs. Of course "illegal" traffic
is going to flow over Tier I equipment, public internet is public internet.
- Mike Bolitho
On Wed, Jul 10, 2019 at 6:30 AM ecdhe via NANOG wrote:
Some of your resources are being used for organized crime and attacks (but not
originating from your network).
I would appreciate an off-list contact if anyone knows of one. Thank you.
On Mon, Jul 08, 2019 at 06:54:51PM -0600, Keith Medcalf wrote:
> This is because DKIM was a solution to a problem that did not exist.
This is correct. We have always known the IP address of the connecting
MTA, therefore we have always known the network it resides in, therefore
we have always
Dear Community
we have extended the
Deadlines
=
Presentation Abstract Deadline 29/07/2019 12:00 UTC
Final Selection of Speakers 09/08/2019
Presentation Slides Submission Deadline 02/09/2019 12:00 UTC
Best regards
Arnold
On 23.04.2019
13 matches
Mail list logo
