RE: Nashville

[Hiers, David]

No doubt they're good, but the best support can't overcome bad design.



From: NANOG  On Behalf Of Robert 
DeVita
Sent: Tuesday, December 29, 2020 5:17 PM
To: Eric Kuhnke ; Sean Donelan 
Cc: NANOG 
Subject: Re: Nashville

AT Disaster Recovery Team is probably the best in the business. The resources 
they can bring to the table are unmatched. This would have been 100x worse if 
it hit a carrier neutral datacenter. They don't have nearly the same resources 
to restore something like this. They usually do a road show (pre Covid). If you 
get a chance it's definitely something you should go check out. Very impressive.

Robert DeVita
Founder & CEO
Mejeticks
c. 469-441-8864
e. radev...@mejeticks.com

From: NANOG 
mailto:nanog-bounces+radevita=mejeticks@nanog.org>>
 on behalf of Eric Kuhnke mailto:eric.kuh...@gmail.com>>
Sent: Tuesday, December 29, 2020 5:06:00 PM
To: Sean Donelan mailto:s...@donelan.com>>
Cc: NANOG mailto:nanog@nanog.org>>
Subject: Re: Nashville

>From a few days ago. Obviously centralizing lots of ss7/pstn stuff all in one 
>place has a long recovery time when it's physically damaged. Something to 
>think about for entities that own and operate traditional telco COs and their 
>plans for disaster recovery.


Nv1

Here is the latest update:  6:46AM 12/27:

Work continues restoring service to the CRS routers in the Nashville Central 
Office. One router remains out of service and the other is in service with some 
links remaining out of service.

The working bridge will reconvene at 08:00 CT with the following action plan:
Additional cabling added to the first portable generator to enable full load 
capabilities (08:00 CT)
Pigtails with camlocks installed for easy swap; investigate possibility to land 
generator on the emergency service board to give the site N+1 with a manual 
ability to choose anyone. (08:00 CT)
check small power plants on floors 4 and 6 (08:00 CT)
Investigate water damage on 1st floor and energize if safe (08:00 CT
Air handlers for floors 4,5 and 6 (09:00 CT)
complete all transport work
Turn up SS7
Turn up 911 service - Approximately noon or after)
Turn up switching service.
TDM Switching team will reconvene at 09:00 CT and the Signaling team will 
reconvene at 11:00 CT on 12/27/2020.
DMS equipment on the 1st floor will be assessed for water damage. Switching 
teams will monitor power and HVAC restoration and will begin switch restoration 
as soon as the go ahead is provided by the power team.

Recovery Priorities:
1. 4th & 5th floors (Specify transport equipment needed to clear MTSO SS7 
isolation & Datakit needed for Local Switch restoration). Transport SMEs 
currently working to turn up transport equipment
2. 6th floor (ESINET Groomers)
3. 10th and 8th floors (N4E) - Trunks
4. 1st floor (DMS: DS1, 5E: DS3) - Local POTS
5. 1st floor (DMS: DS0, DS2 | 5E: DS6) - Trunks
6. 11th floor (DMS: 01T) - Trunks
7. 4th floor (STP and SCP with mates up in Donelson)

The next update will be issued at approximately 09:00 CT on December 27.



Nv2

As of 09:00 CT: Teams worked through the night to restore service and improve 
conditions at the Nashville 2nd Ave Central Office. Since the initial service 
impact, over 75% of the Out of Service Mobility Sites have been restored. 
Certain call flows may be limited and should improve as additional restoration 
activities complete.
The generator that is currently powering equipment on the 2nd and 3rd floor, 
was refueled and ran with no issues through the night. Overnight, the batteries 
connected to it, continued to charge. Teams have placed additional power 
cables, which once connected, will allow the working generator, to better 
handle the load in the building. In order to accomplish this, the generator 
will need to be shut down for 15-30 minutes this morning, so teams can connect 
the new cables to the system. The power team reports they are still on target 
to restore power and cooling to the 5th and 6th floor by approximately 12:00 
CT. Also, a portable chiller will be delivered this morning and strategically 
placed, in case it is needed to assist in cooling the office.
There is a Call Center at 333 Commerce, in Nashville that does not have network 
or phone services available. Corporate Real Estate (CRE) reports there is some 
damage to that office, but the extent of the damage will not be known until 
they can gain access to the site. Because of this, the impacted Call Center 
ceased operations until further notice.
DMS switching equipment on the 1st floor will be assessed for water damage. 
Switching teams will monitor power and HVAC restoration. Equipment power ups 
will begin, as soon as the go ahead is provided by the power team.
Two SatCOLTs remain positioned on the East and West sides of the NSVLTNMT 
Central Office providing critical communication for teams working restoration 
efforts. There are 17 assets deployed in the field- 15 are on air (the 2 at the 
CO 

RE: Backhoe season?

[Hiers, David]

Backhoes In Space!

https://www.nasa.gov/feature/jpl/nasas-mars-insight-lander-to-push-on-top-of-the-mole



From: NANOG [mailto:nanog-bounces+david.hiers=cdk@nanog.org] On Behalf Of 
Kaiser, Erich
Sent: Thursday, March 26, 2020 2:26 PM
To: Aaron Gould 
Cc: NANOG list ; Darron Legnon 
Subject: Re: Backhoe season?

The outages in Texas are not uncommon at all. Its probably the worst vs other 
areas of the country.  One other problem area is between Ashburn and Atlanta.  
We have been seeing more underlying LH carrier equipment failures  vs fiber 
cuts in the last year.


Erich Kaiser
The Fusion Network
er...@gotfusion.net



On Thu, Mar 26, 2020 at 3:22 PM Aaron Gould 
mailto:aar...@gvtc.com>> wrote:
Yeah Darron, we lost some san Antonio connectivity to Houston via dallas or 
somewhere twice in the past few days, affecting different things for us

-Aaron

-Original Message-
From: Darron Legnon [mailto:dar...@commzoom.com]
Sent: Thursday, March 26, 2020 1:11 PM
To: Aaron Gould; 'William Herrin'; nanog@nanog.org
Subject: RE: Backhoe season?

I've had contractors for Zayo hitting multiple fiber routes over the past 3 
months numerous times affecting us, AT, CenturyLink, Windstream, Fiberlight, 
etc in south Texas. Actually had one cut yesterday around 3pm and lasted till 
1am.

-Original Message-
From: NANOG mailto:nanog-boun...@nanog.org>> On Behalf 
Of Aaron Gould
Sent: Thursday, March 26, 2020 1:03 PM
To: 'William Herrin' mailto:b...@herrin.us>>; 
nanog@nanog.org
Subject: RE: Backhoe season?

CAUTION: This email originated from outside your organization. Exercise caution 
when opening attachments or clicking links, especially from unknown senders.

I heard, and am seeing that construction type jobs don't seem to be affected 
much with the virus shutdown.  I mean I see guys building homes and working on 
roads all around me...  furthermore, we've heard of a couple fiber cuts that 
have brought portions of our network down a couple times in the last week or so.

-Aaron

-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On 
Behalf Of William Herrin
Sent: Thursday, March 26, 2020 12:57 PM
To: nanog@nanog.org
Subject: Backhoe season?

Howdy,

With so much work shut down, I'm curious how backhoe season is shaping up this 
year? How do the circuit and fiber outage numbers look?

Regards,
Bill Herrin


--
William Herrin
b...@herrin.us
https://bill.herrin.us/


This e-mail and any files transmitted with it are the property of COMMZOOM, are 
confidential, and are intended solely for the use of the individual or
entity to which this e-mail is addressed. Any other use, retention, 
dissemination, forwarding, printing, or copying of this e-mail is strictly 
prohibited.

--
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.

SD-WAN Operators Group

[Hiers, David]

Hi,
If you’re interested in SD-WAN, I’ve started a NANOG-knockoff over on groups.io.

https://groups.io/g/sdwanoperators

it has all the usual SMTP controls:

  *   Post: sdwanoperat...@groups.io
  *   Subscribe: 
sdwanoperators+subscr...@groups.io
  *   Unsubscribe: 
sdwanoperators+unsubscr...@groups.io
  *   Group Owner: 
sdwanoperators+ow...@groups.io
  *   Help: sdwanoperators+h...@groups.io



Regards,

David


--
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.

RE: DHS letters for fuel and facility access

[Hiers, David]

Good reminder to test, test, test...


-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Warren Kumari
Sent: Tuesday, March 17, 2020 10:08 AM
To: Paul Nash 
Cc: Untitled 3 
Subject: Re: DHS letters for fuel and facility access

On Tue, Mar 17, 2020 at 12:44 PM Paul Nash  wrote:
>
> September 2001.  Just after the 9/11 attacks, all of lower Manhattan was shut 
> down.  Out link (IIRC) was to a satellite farm on Staten island, across the 
> bay to 60 Hudson.  Power went off, diesels kicked in, fuel trucks was not 
> allowed in, and a few days later we lost all international connectivity.

We had some interesting failures during 9/11 as well -- for some reason, the 
UPS didn't kick in, so everything went down - and then came back a few minutes 
later as the generators came online -- and then went down again ~2 hours later 
-- turns out that the genset air filters got clogged with dust, and suffocated 
the diesel.
This was "fixed" a few days later by brushing them off with brooms and 
paintbrushes -- by this point they had completely discharged the 24V starter 
batteries, and so someone (not me!) had to lug a pair of car batteries and 
jumper cables. They restarted, and ran for a while, and then stopped again.

It turns out that getting a permit to store lots of diesel on the roof is hard 
(fair enough), and so there was only a small holding tank on the roof, and the 
primary tanks were in the basement -- and the transfer pump from the basement 
to roof storage was not, as we had been told, on generator power

We had specified that the transfer pump be on the generator feed, there was a 
schematic showing at is being on the generator feed, there was even a breaker 
with a cable marked  "Transfer Pump (HP4,5)" --- but it turned out to just be a 
~3ft piece of cable stuffed into a conduit, and not actually, you know, running 
all the way down to the basement and connected to the transfer pump.

W



>
> Lots of important people lost power as well, so the feds decided to let the 
> diesel tankers in after a few days’ deliberations.
>
> paul
>
> > On Mar 17, 2020, at 11:21 AM, Mark Tinka  wrote:
> >
> >
> >
> > On 17/Mar/20 17:15, Paul Nash wrote:
> >
> >> That same fuel shortage killed all Internet traffic to sub-Saharan Africa. 
> >>  Took us a while to figure out what was wrong with the satellite link to 
> >> the US.
> >
> > What year was that :-)?
> >
> > Mark.
>


--
I don't think the execution is relevant when it was obviously a bad idea in the 
first place.
This is like putting rabid weasels in your pants, and later expressing regret 
at having chosen those particular rabid weasels and that pair of pants.
   ---maf

--
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.

RE: Quagga for production?

[Hiers, David]

Quagga is built into one of our core products, works great.   That particular 
vendor a sponsor of frr, and is replacing quagga with frr soon.

Maybe look at the vendor/partner list for quagga and frr, and decide which 
project has better long-term prospects.

David


From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Nathan Brookfield
Sent: Sunday, February 23, 2020 4:41 AM
To: Dmitry Sherman 
Cc: nanog@nanog.org
Subject: Re: Quagga for production?

Hi Mate,

Yep on and off for about 15 years, very solid, very reliable.  I tend to use 
Bird this hmorning we rays for this task but Zebra and Quagga are rock solid.
Kindest Regards,


Nathan Brookfield (VK2NAB)
Simtronic Technologies Pty Ltd



On 23 Feb 2020, at 23:29, Dmitry Sherman 
mailto:dmi...@interhost.net>> wrote:


Hello,

Anybody working with Quagga for production peering with multiple peers and 
dynamic eBGP/iBGP announcement?



Thanks.

Dmitry


--
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.

RE: QUIC traffic throttled on AT residential

[Hiers, David]

We find that they usually impose pretty harsh QOS on a link that has an ATT 
voice service.

David



-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Jay Hennigan
Sent: Thursday, February 20, 2020 12:13 AM
To: nanog@nanog.org
Subject: Re: QUIC traffic throttled on AT residential

On 2/18/20 18:40, nanog-l...@contactdaniel.net wrote:

> Growing prevalence of IPv6-only
> sites is probably the only thing that will get a lot of access 
> networks to support v6.

I recall a similar idea called "The Great IPv6 Experiment" back in 2007. ;-)


--
Jay Hennigan - j...@west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV

--
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.

RE: Backup over 4G/LTE

[Hiers, David]

VeloCloud’s 510-LTE is one option.



From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Colton Conor
Sent: Wednesday, January 29, 2020 6:44 PM
To: K. Scott Helms 
Cc: NANOG list 
Subject: Re: Backup over 4G/LTE

Does Velcloud make an actual LTE box?

On Wed, Jan 29, 2020 at 6:44 AM K. Scott Helms 
mailto:kscott.he...@gmail.com>> wrote:
There are lots of options to solve that problem.

Peplink, 128T, Viptela (Cisco), Velocloud (VMWare), etc.

Scott Helms


On Tue, Jan 28, 2020 at 6:31 PM K MEKKAOUI 
mailto:amekka...@mektel.ca>> wrote:
Dear NANOG Community,

Can anyone help with any device information that provides redundancy for 
business internet access? In other words when the internet provided through the 
cable modem fails the 4G/LTE takes over automatically to provide internet 
access to the client.

Thank you

KARIM M.


--
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.

RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest

[Hiers, David]

Excessive cold killed us once when the air exit vents froze shut.


From: NANOG [mailto:nanog-bounces+david.hiers=cdk@nanog.org] On Behalf Of 
Naslund, Steve
Sent: Wednesday, January 30, 2019 9:43 AM
To: nanog@nanog.org
Subject: RE: Effects of Cold Front on Internet Infrastructure - U.S. Midwest

Ironically you don’t really save a lot of energy when it’s this cold because 
the loops are running at high speed and the humidification coils are working 
overtime to keep the RH up in the room.

People think we can bring in all the outside cold we want but the issue then is 
humidity stability.

Steven Naslund
Chicago IL

--
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.

RE: Feedback - SBC Vendors.

[Hiers, David]

You might want to drop this question on the VoiceOps list:

voice...@voiceops.org

It runs at a good signal-to-noise ratio, so you'll get some useful responses.


David


-Original Message-
From: NANOG [mailto:nanog-bounces+david.hiers=cdk@nanog.org] On Behalf Of 
James Milko
Sent: Thursday, August 09, 2018 7:06 AM
To: Ryan Finnesey 
Cc: nanog@nanog.org
Subject: Re: Feedback - SBC Vendors.

 Which Ribbon product are you looking at?  There are quite a few now and they 
have different code bases/features.

JM

On Wed, Aug 8, 2018 at 7:56 PM, Ryan Finnesey  wrote:

> I am going to have to install a series of SBCs for a  voice offering 
> connected to Microsoft Teams.  We are going to pass the SIP traffic 
> off to a larger number of SIP providers.  I would like  to get some 
> feedback from the group on SBC vendors.  I have two options for 
> vendors Ribbon or AudioCodes.  I am leaning towards a software based SBC over 
> an appliance.
>
> Would be helpful to get the other members feedback on Ribbon or 
> AudioCodes deployments within their networks.
>
> Cheers
> Ryan
>
>

--
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.

RE: Security team objectives

[Hiers, David]

The Big Goal of security can be stated something like this:

"To bend all of the cost and benefit curves to most closely align with the 
organization's security goals"

If the Board of Directors can't articulate the goals, your pretty much doomed.

David


-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of John Kristoff
Sent: Monday, July 30, 2018 5:00 AM
To: nanog@nanog.org
Subject: Re: Security team objectives

On Mon, 30 Jul 2018 04:43:35 +
Ramy Hashish  wrote:

> If you are going to start a security team in a newly founded IT 
> organization, what will the objectives/results be?

Hello Ramy,

Management and organization buy-in is important.  Initially I would say it 
would be helpful to do some internal education and awareness, which helps with 
the first point.  Identify a few things you can improve upon right away.  Some 
small obtainable achievements would help justify the team if the team can point 
to some early success.  Then build up that.

FIRST.org, which is the original security team community, has a wealth of very 
detailed guides and information you might look over:

  

John

--
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.

RE: US/Canada International border concerns for routing

[Hiers, David]

That is what our lawyers are starting to figure out, too.  Very glad to see 
them converging on the tribal wisdom.

Cheers,

David


-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Andrew Kerr
Sent: Tuesday, August 08, 2017 6:03 PM
To: nanog@nanog.org
Subject: 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 never be stored in the US.

On Tue, 8 Aug 2017 at 17:52 Dave Cohen  wrote

> 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
> craetd...@gmail.com
>
> > On Aug 8, 2017, at 8:41 PM, Bill Woodcock  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  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
> >
> > -BEGIN PGP SIGNATURE-
> >
> > 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
> > =MTUG
> > -END PGP SIGNATURE-
> >
> > --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.

RE: US/Canada International border concerns for routing

[Hiers, David]

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  ) 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,

David
 

-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Dave Cohen
Sent: Tuesday, August 08, 2017 5:53 PM
To: Bill Woodcock 
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. 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
craetd...@gmail.com

> On Aug 8, 2017, at 8:41 PM, Bill Woodcock  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  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
> 
> -BEGIN PGP SIGNATURE-
> 
> 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
> =MTUG
> -END PGP SIGNATURE-
> 
> --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.

US/Canada International border concerns for routing

[Hiers, David]

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 York?

I'm asking network operators about packet routing; data storage is a very 
different matter, of course.

Thanks,

David

--
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.

Ready to get your federal computer license?

[Hiers, David]

Governments already license stock brokers, pilots, commercial drivers, 
accountants, engineers, all sorts of people whose mistakes can be measured in 
the loss of hundreds of lives and millions of dollars. 

http://sip-trunking.tmcnet.com/topics/security/articles/63218-bill-give-president-emergency-power-internet-raises-concerns.htm


Good times



David Hiers

CCIE (R/S, V), CISSP
ADP Dealer Services
2525 SW 1st Ave.
Suite 300W
Portland, OR 97201
o: 503-205-4467
f: 503-402-3277 



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, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

RE: FCCs RFC for the Definition of Broadband

[Hiers, David]

We're way past the time in which broadband meant more bits than baud, huh?  Was 
it the other way around?  I forget...

:)

Anyway:

Broadband could be defined as a duplex channel that is some positive multiple 
of the BW needed to carry the lowest resolution, full-power, public broadcast 
TV channel currently permitted by FCC regulation.

As technology and regulation changes, we'd always have a definition of 
broadband that is implementation independent, technology agnostic, and easy 
to grasp for most people.



David Hiers

CCIE (R/S, V), CISSP
ADP Dealer Services
2525 SW 1st Ave.
Suite 300W
Portland, OR 97201
o: 503-205-4467
f: 503-402-3277 


-Original Message-
From: Dorn Hetzel [mailto:dhet...@gmail.com] 
Sent: Wednesday, August 26, 2009 1:16 PM
To: nanog@nanog.org
Subject: FCCs RFC for the Definition of Broadband

not to mention all the lightning-blasted-routers that will be prevented by
FTTH :)  even with several layers of protection I still accumulate about one
dead interface of some sort each year on my very rural T-1...


On Wed, Aug 26, 2009 at 1:57 PM, jim deleskie deles...@gmail.com wrote:

 I agree we should all be telling the FCC that broadband is fiber to
 the home.  If we spend all kinds of $$ to build a 1.5M/s connection to
 homes, it's outdated before we even finish.



 On Wed, Aug 26, 2009 at 1:38 PM, Fred Bakerf...@cisco.com wrote:
  If it's about stimulus money, I'm in favor of saying that broadband
 implies
  fiber to the home. That would provide all sorts of stimuli to the economy
 -
  infrastructure, equipment sales, jobs digging ditches, and so on. I could
  pretty quickly argue myself into suggesting special favors for deployment
 of
  DNSSEC, multicast, and IPv6. As in, use the stimulus money to propel a
 leap
  forward, not just waste it.
 
  On Aug 26, 2009, at 9:44 AM, Carlos Alcantar wrote:
 
  I think the big push to get the fcc to define broadband is highly based
  on the rus/ntia setting definitions of what broadband is.  If any anyone
  has been fallowing the rus/ntia they are the one handing out all the
  stimulus infrastructure grant loan money.  So there are a lot of
  political reasons to make the definition of broadband a bit slower than
  one would think.  I guess it doesn't hurt that the larger lec's with the
  older infrastructure are shelling out the money to lobby to make sure
  the definition stays as low as can be.  They don't want to see the gov
  funding there competition.  Just my 2 cents.
 
  -carlos
 
  -Original Message-
  From: Ted Fischer [mailto:t...@fred.net]
  Sent: Wednesday, August 26, 2009 8:50 AM
  To: nanog@nanog.org
  Subject: Re: FCCs RFC for the Definition of Broadband
 
 
 
  Paul Timmins wrote:
 
  Fred Baker wrote:
 
  On Aug 24, 2009, at 9:17 AM, Luke Marrott wrote:
 
  What are your thoughts on what the definition of Broadband should be
 
  going
  forward? I would assume this will be the standard definition for a
  number of
  years to come.
 
 
  Historically, narrowband was circuit switched (ISDN etc) and
 
  broadband
 
  was packet switched. Narrowband was therefore tied to the digital
  signaling hierarchy and was in some way a multiple of 64 KBPS. As the
 
  term was used then, broadband delivery options of course included
  virtual circuits bearing packets, like Frame Relay and ATM.
 
  of or relating to or being a communications network in which the
  bandwidth can be divided and shared by multiple simultaneous signals
 
  (as
 
  for voice or data or video)
 
  That's my humble opinion. Let them use a new term, like High Speed
  Internet.
 
 
  Seconded
 
 
 
 
 
 




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, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

RE: cisco.com

[Hiers, David]

 
FACEBOOK:   UP
CISCO:  UP
LOCATION:   PORTLAND, OR




David Hiers

CCIE (R/S, V), CISSP
ADP Dealer Services
2525 SW 1st Ave.
Suite 300W
Portland, OR 97201
o: 503-205-4467
f: 503-402-3277 


-Original Message-
From: Scott Wolfe [mailto:scott.wo...@cybera.net] 
Sent: Tuesday, August 04, 2009 7:04 AM
To: nanog@nanog.org
Subject: RE: cisco.com

No route for 198.133.219.0/24 in 22820 from our upstream (3356 and 174).

-Scott W


-Original Message-
From: sjk [mailto:s...@sleepycatz.com]
Sent: Tuesday, August 04, 2009 8:49 AM
To: Dominic J. Eidson
Cc: nanog@nanog.org
Subject: Re: cisco.com

We have seen the route for cisco withdrawn from 208 and 2828. Facebook seems 
fine

Dominic J. Eidson wrote:
 
 Both work from Austin, TX.
 
 
 
  - d.
 
 On Tue, 4 Aug 2009, Alex Nderitu wrote:
 
 Facebook seems to also be affected.


 -Original Message-
 From: R. Benjamin Kessler r...@mnsginc.com
 To: nanog@nanog.org
 Subject: cisco.com
 Date: Tue, 4 Aug 2009 09:34:46 -0400


 Hey Gang -

 I'm unable to get to cisco.com from multiple places on the 'net 
 (including downforeveryoneorjustme.com); any ideas on the cause and ETR?

 Thanks,

 Ben




 



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, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

Voice Operators' Group: voiceops.org

[Hiers, David]

Hi Everyone,
I'm pleased to announce that the Voice Operators' Group has found an excellent 
home.

Our web site, www.voiceops.org has a good home (thanks Scott!), while Jared, 
Daniel, and all the great folks over at nether.net are hosting our list server.

If VoiceOps can do for voice anything close to what NANOG has done for IP, 
we'll all owe much to the people that are making this happen.



email: voiceops-subscr...@voiceops.org
web:   https://puck.nether.net/mailman/listinfo/voiceops 





Thanks,



David Hiers

CCIE (R/S, V), CISSP
ADP Dealer Services
2525 SW 1st Ave.
Suite 300W
Portland, OR 97201
o: 503-205-4467
f: 503-402-3277 



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, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

RE: OT: Voice Operators' Group forming

[Hiers, David]

 
Hi All,

We're making progress...

I registered the domains voiceops.org and voiceops.net.  No matter what the 
final name becomes, at least we've got some domains that aren't too hard on the 
eyes.

Some noble souls have already volunteered to host it on a proper mailman server.

Nothing is set up yet, but it's coming together.



Thanks,



David Hiers




-Original Message-
From: Charles Wyble [mailto:char...@thewybles.com] 
Sent: Tuesday, July 28, 2009 3:17 PM
To: nanog@nanog.org
Subject: Re: OT: Voice Operators' Group forming



jamie wrote:
 puck.nether.net http://puck.nether.net.

Right. That's what I meant.

 
 way to volunteer someone else's box :-)

Good point. My apologies.

Google groups then. :)




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, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

OT: Voice Operators' Group forming

[Hiers, David]

Hi NANOG,
I'd like to announce the formation of a NANOG-knockoff group for voice 
operators, the Voice Operators' Group.

Voice network operators share many of the same challenges as IP network 
operators; we register with registrars (CILLI, OCN, and ACNA as well as ASN and 
DNS), route traffic (point codes as well as IP addresses), resolve names (CNAM 
as well as DNS), manage reachability (to countries, LATAs and NPA/NXXs as well 
as  to IP networks), and deal with equipment issues.

NANOG has been so useful at the IP layer that it seems like a good idea to try 
to duplicate it a little further up the stack.  

For now, the group is on Yahoo:

http://tech.groups.yahoo.com/group/voip_operators_group/

Of course, we're looking for a better place, name, and charter.


Regards,


David Hiers

CCIE (R/S, V), CISSP
ADP Dealer Services
2525 SW 1st Ave.
Suite 300W
Portland, OR 97201
o: 503-205-4467
f: 503-402-3277 

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, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

RE: XO - a Tier 1 or not?

[Hiers, David]

 
If you limit your consideration to how things look at IP and AP/AR, then the 
Tier-N discussion is solvable.

If you care about actual physical facilities, all bets are off.  Taking a 
tangent from the diversity concept:

http://www.atis.org/ndai/ATIS_NDAI_Final_Report_2006.pdf


war-story
I worked at a CLEC that purchased two SS7 links, one each from two Very Big 
Carriers.  Both wound up going through the same fiber bundle in one particular 
market, on which both big guys leased bandwidth from A Minor Carrier.  I've 
never seen a VP run as fast as when that backhoe hit us in Illinois; turns out 
they only *look* slow.
/war-story


You never really know...



David Hiers

CCIE (R/S, V), CISSP
ADP Dealer Services
2525 SW 1st Ave.
Suite 300W
Portland, OR 97201
o: 503-205-4467
f: 503-402-3277 



-Original Message-
From: Patrick W. Gilmore [mailto:patr...@ianai.net] 
Sent: Tuesday, July 28, 2009 8:26 AM
To: NANOG list
Subject: Re: XO - a Tier 1 or not?

On Jul 28, 2009, at 11:18 AM, Pekka Savola wrote:
 On Tue, 28 Jul 2009, Charles Mills wrote:
 Is XO Communications a Tier 1 ISP?
 ...
 Any help here?  Thanks as always.

 http://en.wikipedia.org/wiki/Tier_1_network

Having written a good portion of that page, in the interest of full disclosure, 
I would like to point out some of the comments made while I was editing (and 
re-editing) the page.

I do not _know_ XO has settlement agreements with Sprint  L3.  Such contracts 
are covered by NDA, so (supposedly) only certain people inside Sprint, L3, and 
XO know whether XO is paying settlements.

That said, does it matter?  Settlement-Based may actually have a slight benefit 
over Settlement Free, as links which generate revenue may get upgraded faster 
than links which do not.

Perhaps more importantly, does Transit Free matter?  A network which has two 
diverse transit providers is orders of magnitude less likely to be affected by 
bifurcation events than transit free networks.

Not to mention many non-transit free networks have better quality and service, 
IMHO, than some transit free networks.

But hey, your money, your bits, so your decision.   You want to buy  
from XO because they are Transit Free, or not buy from them because they are 
not Tier One, so be it.  What's that line about competitors and 
encouragement... ? =)

-- 
TTFN,
patrick




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, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

RE: ATT. Layer 6-8 needed.

[Hiers, David]

Im not a lawyer, but I think that the argument goes something like this...

The common carriers want to be indemnified from the content they carry. In 
other words, the phone company doesn't want to be held liable for the Evil Plot 
planned over their phone lines.  The price they pay for indemnification is that 
they must not care about ANY content (including content that competes with 
content offered by a non-carrier division of the common carrier).  If they edit 
SOME content, then they are acting in the role of a newspaper editor, and have 
assumed the mantle of responsibility for ALL content. 

Carriers can, however, do what they need to do to keep their networks running, 
so they are permitted disrupt traffic that is damaging to the network.

The seedy side of all of this is that if a common carrier wants to block a 
particular set of content from a site/network, all they need to do is point out 
some technical badness that comes from the same general direction.  Since the 
background radiation of technical badness is fairly high from every direction, 
it's not too hard to find a good excuse when you want one.




David Hiers

CCIE (R/S, V), CISSP
ADP Dealer Services
2525 SW 1st Ave.
Suite 300W
Portland, OR 97201
o: 503-205-4467
f: 503-402-3277 


-Original Message-
From: Jon Lewis [mailto:jle...@lewis.org] 
Sent: Monday, July 27, 2009 6:58 AM
To: William Pitcock
Cc: nanog - n. am. network ops group list
Subject: Re: ATT. Layer 6-8 needed.

On Mon, 27 Jul 2009, William Pitcock wrote:

 It is widely known that ATT loves censorship.  They love censorship 
 because it is profitable for them to love censorship, and this isn't 
 the first time they have enmasse blocked access to a website they 
 didn't like.  This has nothing at all to do with forged ACK responses, 
 and everything to do with content.

How does breaking things (censorship) make them more money?

http://njabl.org/faq.html#Q12

 ATT does not have the right to filter what their users can access, 
 period.  You can put all the spin on it that you want, but in the end 
 it's about content.

Whatever happened to My network, my rules?  If ATT blocks something, and as 
an ATT customer, you don't like it, get your connectivity from someone else.

--
  Jon Lewis   |  I route
  Senior Network Engineer |  therefore you are
  Atlantic Net|
_ http://www.lewis.org/~jlewis/pgp for PGP public key_



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, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

RE: Verio taking twitter down during Iran Election Riots?

[Hiers, David]

This is a useful reminder that nanog creates a large part of the battlefield on 
which state and non-state players constantly prosecute their Information 
Warfare agendas.

What will you do when you get a call from Khamenei, and then one from Obama?

Armor up, boys and girls.


David Hiers

CCIE (R/S, V), CISSP



-Original Message-
From: Steven M. Bellovin [mailto:s...@cs.columbia.edu] 
Sent: Tuesday, June 16, 2009 4:46 PM
To: Jack Bates
Cc: Erik Fichtner; nanog@nanog.org
Subject: Re: Verio taking twitter down during Iran Election Riots?

On Tue, 16 Jun 2009 09:48:07 -0500
Jack Bates jba...@brightok.net wrote:

 Erik Fichtner wrote:
  
  And yet, all upgrades can be postponed with the right... motivation.
  
 
 
 Hmmm, you do know that motivation may have strictly been, Your 
 maintenance corresponds with a major event, can you put it off for a 
 day?
 
According to
http://feeds.arstechnica.com/~r/arstechnica/index/~3/k32Wx4r_vew/twitter-from-statedept-delay-upgrade-to-aid-iran-protests.ars
the delay was requested by the U.S. State Department.


--Steve Bellovin, http://www.cs.columbia.edu/~smb



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, please notify us immediately by e-mail and delete the message and any 
attachments from your system.