Re: US/Canada International border concerns for routing

On 2017-08-09 10:11, Hiers, David wrote: > That is what our lawyers are starting to figure out, too. Very glad to see > them converging on the tribal wisdom. late to discussion. You might get some organisations which require you to provide intra-canada routes for privacy reasons. But at the

Re: US/Canada International border concerns for routing

You mean ROBALLOFUS right? :-) On August 8, 2017 5:33:28 PM PDT, Clayton Zekelman wrote: > > >With the peering policies of the major Canadian ISPs, you're >virtually guaranteed to hairpin through the US on most paths. > >Robellus (Rogers, Bell & Telus) will peer with you at

RE: US/Canada International border concerns for routing

: Re: US/Canada International border concerns for routing Canadian here who's evaluated service providers and dealt with legal requirements for our customers... Generally we weren't worried about data travelling through the US based on normal internet routes, as long as it was encrypted

Re: US/Canada International border concerns for routing

Sorta, kinda. The various ASs operated by Zayo are more interconnected than that description would imply. The traditional mode of operation on an "acquired AS" has been to turn down any upstream transit as quickly as contractually possible and upgrade NNI capacity between that AS and 6461 to

Re: US/Canada International border concerns for routing

sday, 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.hi...@cdk.com> wrote: > Hi, > We're looking to extend some services into Canada. While our lawyers dig > into it, I th

Re: US/Canada International border concerns for routing

g-boun...@nanog.org> on behalf of Keenan Tims <kt...@stargate.ca> Sent: Wednesday, August 9, 2017 2:48 AM To: nanog@nanog.org Subject: Re: US/Canada International border concerns for routing On 2017-08-08 17:10, Bill Woodcock wrote: > No. In fact, Bell Canada / Bell Aliant a

RE: US/Canada International border concerns for routing

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 publ

Re: US/Canada International border concerns for routing

David Generally speaking, when customers have concerns about their traffic crossing borders, they do ask upfront. As a multinational operator you can only guarantee traffic if customers asks and offcours pays the fee for special class of service. Ahad On Wed, 9 Aug 2017 at 9:21 am, Hiers,

Re: US/Canada International border concerns for routing

Canadian here who's evaluated service providers and dealt with legal requirements for our customers... Generally we weren't worried about data travelling through the US based on normal internet routes, as long as it was encrypted. The thing we usually specified in RFPs was that the data could

Re: US/Canada International border concerns for routing

to and no one selling dark on this route today. - R. From: NANOG <nanog-boun...@nanog.org> on behalf of Eric Kuhnke <eric.kuh...@gmail.com> Sent: Wednesday, August 9, 2017 4:13 AM To: Stephen Fulton; nanog@nanog.org list Subject: Re: US/Canada Internat

Re: US/Canada International border concerns for routing

Re: US/Canada International border concerns for routing

It is worth noting, however, that the former AllStream ASN (formerly AT Canada) AS15290 is a completely different thing, and has distinct infrastructure and routing from the AboveNet ASN which is operated by Zayo. Although they are probably using "Free" Zayo transport by now. If I am grossly

Re: US/Canada International border concerns for routing

> On Aug 8, 2017, at 5:48 PM, Keenan Tims wrote: > While they do practice peering protectionism and only purchase transit out of > country, the situation is not *quite* so bad that all traffic round-trips > through the US. No, not all, 64%. By comparison, only 0.27% of

Re: US/Canada International border concerns for routing

OK, Maybe I was a bit overly dramatic. One of the big 3 peered with us in a US location, but refused to peer in Canada. I can't recall if we actually did specifically ask Rogers at one point or not. I know we haven't asked recently. At 08:41 PM 08/08/2017, Bill Woodcock wrote: > On

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

Re: US/Canada International border concerns for routing

On 2017-08-08 17:10, Bill Woodcock wrote: No. In fact, Bell Canada / Bell Aliant and Telus guarantee that you_will_ go through Chicago, Seattle, New York, or Ashburn, since none of them peer anywhere in Canada at all. The major national networks (Bell, Rogers, Telus, Shaw, Zayo/Allstream)

Re: US/Canada International border concerns for routing

> On Aug 8, 2017, at 5:33 PM, Clayton Zekelman wrote: > > > > With the peering policies of the major Canadian ISPs, you're virtually > guaranteed to hairpin through the US on most paths. > > Robellus (Rogers, Bell & Telus) will peer with you at any of their major >

Re: US/Canada International border concerns for routing

With the peering policies of the major Canadian ISPs, you're virtually guaranteed to hairpin through the US on most paths. Robellus (Rogers, Bell & Telus) will peer with you at any of their major Canadian peering points, such as NYC, Chicago or LA. At 10:01 AM 20/07/2017, Hiers, David

Re: US/Canada International border concerns for routing

TR, MTS Allstream is no longer a combined entity. MTS was purchased by Bell Canada and Allstream was purchased by Zayo. -- Stephen On 2017-08-08 8:19 PM, TR Shaw wrote: Bill, What does Bell buying MTS do? Does it change your statement or will the MTS portion of Bell still peer locally?

Re: US/Canada International border concerns for routing

> On Aug 8, 2017, at 5:19 PM, TR Shaw wrote: > > Bill, > > What does Bell buying MTS do? Does it change your statement or will the MTS > portion of Bell still peer locally? I’d have to go back and look at the actual ASNs in our analysis. I think what we called “MTS

Re: US/Canada International border concerns for routing

Bill, What does Bell buying MTS do? Does it change your statement or will the MTS portion of Bell still peer locally? Tom > On Aug 8, 2017, at 8:10 PM, Bill Woodcock wrote: > > >> On Jul 20, 2017, at 7:01 AM, Hiers, David wrote: >> For traffic routing,

Re: US/Canada International border concerns for routing

> On Jul 20, 2017, at 7:01 AM, Hiers, David wrote: > 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,

Re: US/Canada International border concerns for routing

On 20/07/2017, Hiers, David 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 >