US/Canada International border concerns for routing

Hiers, David David.Hiers at
Wed Aug 9 01:11:13 UTC 2017

I can't thank everyone enough for their input and insight!

It sounds like my discovery didn't miss some glaringly obvious form, checkbox, agreement or community (NO-US-EH, for instance <snark> ) to keep traffic from crossing the border.

Data *storage*, on the other hand, is a very different thing, and even a drunk intern can find the rules around that kind of thing.

Thanks again,


-----Original Message-----
From: NANOG [mailto:nanog-bounces at] On Behalf Of Dave Cohen
Sent: Tuesday, August 08, 2017 5:53 PM
To: Bill Woodcock <woody at>
Cc: nanog at
Subject: Re: US/Canada International border concerns for routing

It seems to me the original question was asking about it more from a legal perspective, in other words does Canadian traffic have to stay in Canada. IANAL (or a Canadian), but the answer is "mostly, no, especially as related to publicly routed traffic" as should be evidenced based on what's already been discussed here. In other words, there is restricted traffic but unless you're making a play for MAN/WAN type service on owned infrastructure, those requirements are unlikely to arise. 

To support the macro point, there is some big-boy level peering in Toronto but not really much else outside that, but there are plenty of routes that don't cross the border if you don't have to jump networks to your destination, for example going to an AWS on ramp in Canada using a native partner network, especially in the Toronto-Ottawa-Montreal. 

Dave Cohen
craetdave at

> On Aug 8, 2017, at 8:41 PM, Bill Woodcock <woody at> wrote:
> --Apple-Mail=_8DA28412-F6D0-43D8-A90F-5E151E54468E
> Content-Transfer-Encoding: quoted-printable
> Content-Type: text/plain;
>    charset=us-ascii
>> On Aug 8, 2017, at 5:33 PM, Clayton Zekelman <clayton at MNSi.Net> wrote:
>> =20
>> =20
>> =20
>> With the peering policies of the major Canadian ISPs, you're 
>> virtually =
> guaranteed to hairpin through the US on most paths.
>> =20
>> Robellus (Rogers, Bell & Telus) will peer with you at any of their =
> major Canadian peering points, such as NYC, Chicago or LA.
> To be fair, Rogers does peer in Toronto.  Along with New York, 
> Chicago, = Seattle, and Ashburn.
>                                -Bill
> --Apple-Mail=_8DA28412-F6D0-43D8-A90F-5E151E54468E
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
>    filename=signature.asc
> Content-Type: application/pgp-signature;
>    name=signature.asc
> Content-Description: Message signed with OpenPGP
> iQIcBAEBCAAGBQJZilooAAoJEG+kcEsoi3+HgNsQAIPkgL/lVL/j1sdPyiyQsepE
> TCyHm4bsAq6m085kXoRj/IWn+KsVwmAq8ZGKnKEAiozmrSeyxAa2vmw5Kfs57l1/
> crBima+EOOlPT4VcD7tv9e8yEiVdjDuMp5tnLI238qCfIlHeHRtuU7CClzWPv6uD
> 3jCNIBEcScrLWz37Ofm/D2AkYRAhhK5H8I417Y/39TH4MIoIKFsGbvWwpl30Fv8r
> 5phO0MrTP6mB8niHne6HTxyMED5TGQpVEL2Qgh6qgaI9vzAs5/47KwwY57tZpxaL
> v9GjkPJ4Ql7QVWbsSkXnFmHxXzqaHXAfg8SR+gsCN42Jyn99AIyAAwdALhqc4RuZ
> ydi+lOlEutAMndA01CnrI81Eu/RpWrN+q/vi37W2rb6EPTPcCz2196JDlpC6VVW6
> tJOMNuP6Pa/ee52Cxu6RWwA4QZ6QVIT9fbDcRFXTGNuohwP8XVpujcsPLChzsFXA
> ggR1Dz2EhPSXXZdvN7KPh1q9rhRb2VUPSn3EeEDo2TjgUVeUlunsDg/ILpf8lxUY
> RTsXe5Nky7YqXKDG4HSlLF3R/RtfaVqKJfjljYg351cs40rzivzjD2TJ8r35RQeW
> btKUtEvrcU28g15nOhLG
> --Apple-Mail=_8DA28412-F6D0-43D8-A90F-5E151E54468E--

This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.

More information about the NANOG mailing list