[195453] in North American Network Operators' Group
RE: US/Canada International border concerns for routing
daemon@ATHENA.MIT.EDU (Hiers, David)
Wed Aug 9 09:22:48 2017
X-Original-To: nanog@nanog.org
From: "Hiers, David" <David.Hiers@cdk.com>
To: Dave Cohen <craetdave@gmail.com>, Bill Woodcock <woody@pch.net>
Date: Wed, 9 Aug 2017 01:11:13 +0000
In-Reply-To: <6FB948C4-EF91-4726-ABDD-A3B40DE99BCA@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
I can't thank everyone enough for their input and insight!
It sounds like my discovery didn't miss some glaringly obvious form, checkb=
ox, agreement or community (NO-US-EH, for instance <snark> ) to keep traffi=
c from crossing the border.
Data *storage*, on the other hand, is a very different thing, and even a dr=
unk intern can find the rules around that kind of thing.
Thanks again,
David
=20
-----Original Message-----
From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Dave Cohen
Sent: Tuesday, August 08, 2017 5:53 PM
To: Bill Woodcock <woody@pch.net>
Cc: nanog@nanog.org
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. I=
ANAL (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, tho=
se requirements are unlikely to arise.=20
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 destinati=
on, for example going to an AWS on ramp in Canada using a native partner ne=
twork, especially in the Toronto-Ottawa-Montreal.=20
Dave Cohen
craetdave@gmail.com
> On Aug 8, 2017, at 8:41 PM, Bill Woodcock <woody@pch.net> wrote:
>=20
>=20
> --Apple-Mail=3D_8DA28412-F6D0-43D8-A90F-5E151E54468E
> Content-Transfer-Encoding: quoted-printable
> Content-Type: text/plain;
> charset=3Dus-ascii
>=20
>=20
>> On Aug 8, 2017, at 5:33 PM, Clayton Zekelman <clayton@MNSi.Net> wrote:
>> =3D20
>> =3D20
>> =3D20
>> With the peering policies of the major Canadian ISPs, you're=20
>> virtually =3D
> guaranteed to hairpin through the US on most paths.
>> =3D20
>> Robellus (Rogers, Bell & Telus) will peer with you at any of their =3D
> major Canadian peering points, such as NYC, Chicago or LA.
>=20
> To be fair, Rogers does peer in Toronto. Along with New York,=20
> Chicago, =3D Seattle, and Ashburn.
>=20
> -Bill
>=20
>=20
>=20
>=20
>=20
> --Apple-Mail=3D_8DA28412-F6D0-43D8-A90F-5E151E54468E
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
> filename=3Dsignature.asc
> Content-Type: application/pgp-signature;
> name=3Dsignature.asc
> Content-Description: Message signed with OpenPGP
>=20
> -----BEGIN PGP SIGNATURE-----
>=20
> iQIcBAEBCAAGBQJZilooAAoJEG+kcEsoi3+HgNsQAIPkgL/lVL/j1sdPyiyQsepE
> TCyHm4bsAq6m085kXoRj/IWn+KsVwmAq8ZGKnKEAiozmrSeyxAa2vmw5Kfs57l1/
> crBima+EOOlPT4VcD7tv9e8yEiVdjDuMp5tnLI238qCfIlHeHRtuU7CClzWPv6uD
> 3jCNIBEcScrLWz37Ofm/D2AkYRAhhK5H8I417Y/39TH4MIoIKFsGbvWwpl30Fv8r
> 5phO0MrTP6mB8niHne6HTxyMED5TGQpVEL2Qgh6qgaI9vzAs5/47KwwY57tZpxaL
> v9GjkPJ4Ql7QVWbsSkXnFmHxXzqaHXAfg8SR+gsCN42Jyn99AIyAAwdALhqc4RuZ
> ydi+lOlEutAMndA01CnrI81Eu/RpWrN+q/vi37W2rb6EPTPcCz2196JDlpC6VVW6
> tJOMNuP6Pa/ee52Cxu6RWwA4QZ6QVIT9fbDcRFXTGNuohwP8XVpujcsPLChzsFXA
> Y2nt+TliL697lTZNbTZEzQ0f9w2rpCDpcLjTMCR8MNWZ4MjQHL3eDgO5ZIWHPTQf
> ggR1Dz2EhPSXXZdvN7KPh1q9rhRb2VUPSn3EeEDo2TjgUVeUlunsDg/ILpf8lxUY
> RTsXe5Nky7YqXKDG4HSlLF3R/RtfaVqKJfjljYg351cs40rzivzjD2TJ8r35RQeW
> btKUtEvrcU28g15nOhLG
> =3DMTUG
> -----END PGP SIGNATURE-----
>=20
> --Apple-Mail=3D_8DA28412-F6D0-43D8-A90F-5E151E54468E--
>=20
----------------------------------------------------------------------
This message and any attachments are intended only for the use of the addre=
ssee and may contain information that is privileged and confidential. If th=
e reader of the message is not the intended recipient or an authorized repr=
esentative of the intended recipient, you are hereby notified that any diss=
emination of this communication is strictly prohibited. If you have receive=
d this communication in error, notify the sender immediately by return emai=
l and delete the message and any attachments from your system.
