>
> In your fair proposal, MSA is related to network architecture as a way
> to standardise pluggable (optics). But as always standards are
> incomplete, ambiguous and do not guarantee interoperability, so it
> will take some time for industry to decide what is 'correct'
> interpretation of MSA. Im
We could also add an explanation to our proposals for the acronym. :)
In your fair proposal, MSA is related to network architecture as a way
to standardise pluggable (optics). But as always standards are
incomplete, ambiguous and do not guarantee interoperability, so it
will take some time for ind
Just to add a bit of fun to the mix - perhaps multi-source agreement was
intended :)
Cheers,
Etienne
On Wed, May 18, 2022 at 3:59 AM Martin Hannigan wrote:
>
>
> All,
>
> Why do MSA’s matter as related to network architecture?
>
> Thanks all —
>
> -M<
>
>
>
>
--
Ing. Etienne-Victor Depasqual
Asking good questions is much harder than answering good questions.
You could have improved the quality of question here by staging what
MSA is and in what context you've run into this.
I am assuming MSA here is a metro statistical area, and if so, I can
answer for the context of my employer, whe
On 5/18/22 03:55, Martin Hannigan wrote:
All,
Why do MSA’s matter as related to network architecture?
As in "Master Services Agreement"?
Mark.
All,
Why do MSA’s matter as related to network architecture?
Thanks all —
-M<
Juniper added sFlow support to MX routers in Junos 18.1R1,
https://blog.sflow.com/2018/04/sflow-available-on-juniper-mx-series.html
You might want to consider deploying sFlow instead of IPFIX, particularly
if you are interested in DDoS mitigation where low latency and visibility
into packet header
The ELK stack does a good job of collecting netflow records with the addition
of Filebeat. Check out my tattle-tale tool that collects netflow data:
https://github.com/racompton/tattle-tale It has numerous rules in
logstash/conf.d to try to just look for spoofed DDoS amplification requests but
8 matches
Mail list logo
