On Wed, May 18, 2022 at 01:59 Mark Tinka wrote:
>
>
> 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"?
Admittedly vague, but deliberate. Perhaps the thread answered the question.
Hi list,
If anyone has a valid contact for or is lurking from Wave/Astound
(AS11404), would you please contact me off list? I'm having trouble
getting a response from any of the ARIN addresses about stale PTR records
causing issues, which I'd really like to get resolved.
Thanks in advance
//
Since yesterday, I've started to see an increase in latency between my
self in NJ on Verizon FIOS and Hetzner in DE. Even using Verizon:s
looking glass is giving me 250ms. This is an increase of about 150ms
(Seems to be true for most of the US East Coast)
A traceroute seems to tell me that the
On Wed, May 18, 2022 at 2:29 PM Tomas Jonsson wrote:
> Since yesterday, I've started to see an increase in latency between my
> self in NJ on Verizon FIOS and Hetzner in DE. Even using Verizon:s
> looking glass is giving me 250ms. This is an increase of about 150ms
> (Seems to be true for most
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,
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
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
>
> 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.
On 5/18/22 08:39, Saku Ytti wrote:
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
>
> Considered that, but that would be obvious - we need optics :-).
>
Agreed - but wouldn't it be fair to say that, nonetheless, the availability
of an MSA
supports the development of network architecture?
With an MSA, there is some limited, common basis for a discussion in
an ecosystem of
On 5/18/22 08:28, Etienne-Victor Depasquale via NANOG wrote:
Just to add a bit of fun to the mix - perhaps multi-source agreement
was intended :)
Considered that, but that would be obvious - we need optics :-).
Mark.
On Wed, 18 May 2022 at 11:35, Mark Tinka wrote:
> Unless you are truly desperate and/or happy to get stuck in vendor-land,
> always wise to be slightly behind the curve when it comes to optics.
Agreed, if possible do boring things and get boring results.
Even in vendor land, a boring result is
12 matches
Mail list logo
