[195431] in North American Network Operators' Group
Re: US/Canada International border concerns for routing
daemon@ATHENA.MIT.EDU (Constantine A. Murenin)
Tue Aug 8 19:55:00 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <CFEC2ABD93715E4B96AAD927F5AAB44C011C828E2B@DSXMBX2HE.ds.ad.adp.com>
From: "Constantine A. Murenin" <mureninc@gmail.com>
Date: Tue, 8 Aug 2017 17:54:56 -0600
To: "Hiers, David" <David.Hiers@cdk.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On 20/07/2017, Hiers, David <David.Hiers@cdk.com> wrote:
> Hi,
> We're looking to extend some services into Canada. While our lawyers dig
> into it, I thought that I'd ask the hive mind about border restrictions.
>
> For traffic routing, is anyone constraining cross-border routing between
> Canada and the US? IOW, if you are routing from Toronto to Montreal, do =
you
> have to guarantee that the path cannot go through, say, Syracuse, New Yor=
k?
Guarantee to whom?
Back a few years ago when I looked into it, most of the traffic within
Canada went through the US, e.g., since Bell didn't want to peer with
anyone in Canada, you'd go something like YYZ - ORD - YYZ, clearly
visible through the traceroute.
Possibly somewhat better nowadays =E2=80=94 there's been quite a few new IX
POPs that popped up =E2=80=94 but I doubt the scenario is a thing of the pa=
st.
P.S. Just for the giggles =E2=80=94 checked http://lg.he.net/ routing from
core1.tor1.he.net to www.bell.ca =E2=80=94 still goes through Chicago, to
Montreal, from Toronto. :-) Going straight to Montreal,
core1.ymq1.he.net, will route you to www.bell.ca (still in Montreal)
through the peering at NYC.
P.P.S. In other words =E2=80=94 if someone wants guarantees, they better
explicitly ask you for it.
Cheers,
Constantine.
http://cm.su/
