[195456] in North American Network Operators' Group
Re: US/Canada International border concerns for routing
daemon@ATHENA.MIT.EDU (Rod Beck)
Wed Aug 9 09:32:59 2017
X-Original-To: nanog@nanog.org
From: Rod Beck <rod.beck@unitedcablecompany.com>
To: "Constantine A. Murenin" <mureninc@gmail.com>, "Hiers, David"
<David.Hiers@cdk.com>
Date: Wed, 9 Aug 2017 13:25:09 +0000
In-Reply-To: <CAPKkNb6cfYfywgvCaBB7DHydgKti4N1kP-57g9zuo1tdX6FBbA@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
I am not sure that this answers your question, but carriers are looking for=
more diversity on cross border traffic. Right now virtually all Toronto/NY=
C runs through Buffalo and 350 Main, Buffalo. May be Montreal/NYC has more =
options.
There have been huge network builds in the US Northeast by Unite and Firstl=
ight, which are providing optical backhaul from cell towers. So more routin=
g options may be available than in the past.
An issue that no one discussed in the age of the fiber. The big carriers an=
d the Web Giants do not want to 1998 manufactured fiber. And some of the We=
b Giants are only putting 4x 100 gig waves per fiber pair. So the incentive=
to create new diverse routes with new large fiber builds is growing.
- R.
________________________________
From: NANOG <nanog-bounces@nanog.org> on behalf of Constantine A. Murenin <=
mureninc@gmail.com>
Sent: Wednesday, August 9, 2017 1:54 AM
To: Hiers, David
Cc: nanog@nanog.org
Subject: Re: US/Canada International border concerns for routing
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 =97 there's been quite a few new IX
POPs that popped up =97 but I doubt the scenario is a thing of the past.
P.S. Just for the giggles =97 checked http://lg.he.net/ routing from
Looking Glass - Hurricane Electric (AS6939)<http://lg.he.net/>
lg.he.net
Hurricane Electric (AS6939) Network Looking Glass
core1.tor1.he.net to www.bell.ca<http://www.bell.ca> =97 still goes through=
Chicago, to
[http://upload.wikimedia.org/wikipedia/commons/thumb/9/91/Bell_logo.svg/120=
px-Bell_logo.svg.png]<http://www.bell.ca/>
Bell Canada - Mobile phones, TV, Internet and Home phone ...<http://www.bel=
l.ca/>
www.bell.ca
Bell is Canada's largest telecommunications company, providing Mobile phone=
, TV, high speed and wireless Internet, and residential Home phone services=
.
Montreal, from Toronto. :-) Going straight to Montreal,
core1.ymq1.he.net, will route you to www.bell.ca<http://www.bell.ca> (still=
in Montreal)
[http://upload.wikimedia.org/wikipedia/commons/thumb/9/91/Bell_logo.svg/120=
px-Bell_logo.svg.png]<http://www.bell.ca/>
Bell Canada - Mobile phones, TV, Internet and Home phone ...<http://www.bel=
l.ca/>
www.bell.ca
Bell is Canada's largest telecommunications company, providing Mobile phone=
, TV, high speed and wireless Internet, and residential Home phone services=
.
through the peering at NYC.
P.P.S. In other words =97 if someone wants guarantees, they better
explicitly ask you for it.
Cheers,
Constantine.
http://cm.su/
cm.su. =97 Constantine Murenin is Super User<http://cm.su/>
cm.su
Constantine Murenin is Super User Yes, it's true! Constantine.SU; BXR.SU; m=
doc.su; nginx.conf 2016; GitHub; StackOverflow =A9 2016 Constantine A. Mure=
nin (cnst)
