[195440] in North American Network Operators' Group
Re: US/Canada International border concerns for routing
daemon@ATHENA.MIT.EDU (Dave Cohen)
Tue Aug 8 20:52:46 2017
X-Original-To: nanog@nanog.org
From: Dave Cohen <craetdave@gmail.com>
Date: Tue, 8 Aug 2017 20:52:43 -0400
To: Bill Woodcock <woody@pch.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
It seems to me the original question was asking about it more from a legal p=
erspective, in other words does Canadian traffic have to stay in Canada. IAN=
AL (or a Canadian), but the answer is "mostly, no, especially as related to p=
ublicly routed traffic" as should be evidenced based on what's already been d=
iscussed here. In other words, there is restricted traffic but unless you're=
making a play for MAN/WAN type service on owned infrastructure, those requi=
rements are unlikely to arise.=20
To support the macro point, there is some big-boy level peering in Toronto b=
ut not really much else outside that, but there are plenty of routes that do=
n'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 networ=
k, 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 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, 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
