[188540] in North American Network Operators' Group
Re: What services does Microsoft AS8075 provide when peering at IXPs?
daemon@ATHENA.MIT.EDU (Eric A Louie via NANOG)
Sun Apr 3 20:22:09 2016
X-Original-To: nanog@nanog.org
Date: Mon, 4 Apr 2016 00:22:05 +0000 (UTC)
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
In-Reply-To: <171099.1459724654@turing-police.cc.vt.edu>
From: Eric A Louie via NANOG <nanog@nanog.org>
Reply-To: Eric A Louie <elouie@yahoo.com>
Cc: NANOG List <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
My direct peering is within my control, the traffic has to follow basically=
the same path internally to Internet and IXP.=C2=A0 Internet path is defin=
itely variable.=C2=A0 IXP path is definitely fixed.=C2=A0 It's already ther=
e, just needed to know what Microsoft provided (if anyone knew).=C2=A0 Actu=
ally, a MS peering engineer answered the question for me privately.
My marketing people aren't terribly concerned with security, that wasn't th=
e issue.=C2=A0 The issue was shorter path/better performance.=C2=A0 I'm sti=
ll not clear if it's public or private Azure that the customer is trying to=
access.
=20
On Sunday, April 3, 2016 4:04 PM, "Valdis.Kletnieks@vt.edu" <Valdis.Kle=
tnieks@vt.edu> wrote:
=20
=20
On Fri, 01 Apr 2016 18:02:56 -0000, Eric A Louie via NANOG said:
> I suppose we have a customer who is an Azure customer that wants to know =
if=20
> their Azure traffic will stay in our network or still go through the Inte=
rnet.
As a practical matter, if they're using the answer for a security baseline,
they're doing it wrong - they should be planning that based on the assumpti=
on
that their traffic *will* ride the rails of the commodity Internet (due to
outages or whatever).
Similarly, if they're looking at it for performance/latency, they need to
fix their assumptions - your direct peering can be slow and congested, whil=
e
there's actually a longer but faster path through someplace else....
=20
