Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Hi Ren et al., Thanks for pointing out that some peers do not use the route servers. This group can be subdivided in a group of peers not sending any IP prefixes to the route servers while maintaining a route server BGP session, and a group of peers not even connecting to the route server. The

Re: BGP Experiment

On 23/01/2019 19:40, Job Snijders wrote: I agree with Job. Continue the experiment and warn us in advance. -Hank Dear Ben, all, I'm not sure this experiment should be canceled. On the public Internet we MUST assume BGP speakers are compliant with the BGP-4 protocol. Broken BGP-4 speakers

Re: DNS Flag Day, Friday, Feb 1st, 2019

Don’t forget the reverse tree as well. > On 31 Jan 2019, at 5:40 pm, Hank Nussbacher wrote: > > On 31/01/2019 07:18, Mark Andrews wrote: > > There is some secret, silent block on my postings to NANOG that the admins > have not yet discovered. In the interim can one of you please proxy to the

Re: DNS Flag Day, Friday, Feb 1st, 2019

The only ones that could potentially make a “breaking change” on the Feb 1 are Google, Cloudflare and Quad9. They are the public DNS recursive server operators that have committed to removing work arounds. Google has already stated publicly that it will be introducing changes gradually and I

Re: DNS Flag Day, Friday, Feb 1st, 2019

On Wed, Jan 30, 2019 at 9:51 PM Christopher Morrow wrote: > you do realize you are proposing to make a breaking change (breaking change to > a global system) on a friday. delaying until the following monday would not > have There are reasons to prefer a Friday over other days as well, but the

Re: DNS Flag Day, Friday, Feb 1st, 2019

On Wed, Jan 30, 2019 at 8:10 PM Keith Medcalf wrote: > > The best time is usually a Wednesday at Noon or 11:00 in the impacted > timezone. Of course, if the impact is worldwide then that would probably > be UT1 :) that still sounds like: "not friday" right? >

Calling Jason Lixfeld @ DE-CIX NY

Greetings Jason, Do you see your new IPv4 session UP at DE-CIX NY with LinkedIn? Thanks ! Kind regards, Mara

RE: DNS Flag Day, Friday, Feb 1st, 2019

The best time is usually a Wednesday at Noon or 11:00 in the impacted timezone. Of course, if the impact is worldwide then that would probably be UT1 :) --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-Original

Re: DNS Flag Day, Friday, Feb 1st, 2019

On Wed, Jan 30, 2019 at 6:23 PM Mark Andrews wrote: > You do realise that when the day was chosen it was just the date after > which new versions of name servers by the original group of Open Source DNS > you do realize you are proposing to make a breaking change (breaking change to a global

Re: DNS Flag Day, Friday, Feb 1st, 2019

You do realise that when the day was chosen it was just the date after which new versions of name servers by the original group of Open Source DNS developers would not have the work arounds incorporated? For ISC that will be BIND 9.14.0 and no that will not be available Feb 1 but you can use

Re: DNS Flag Day, Friday, Feb 1st, 2019

On January 31, 2019 1:55:26 AM UTC, Christopher Morrow wrote: >On Wed, Jan 30, 2019 at 5:41 PM Jim Popovitch via NANOG > >wrote: > >> On Wed, 2019-01-30 at 17:22 -0800, Matthew Petach wrote: >> > Any chance this could wait until say the Tuesday >> > *after* the Superbowl, when we aren't cutting

Re: DNS Flag Day, Friday, Feb 1st, 2019

This basically affects sites using really old Windows DNS servers (Microsoft decided to make them only respond once with FORMERR so if that message is lost they appear to be dead until the timer clears) and those using firewalls that block EDNS queries. If you use such firewalls they are

Re: DNS Flag Day, Friday, Feb 1st, 2019

On Wed, Jan 30, 2019 at 5:41 PM Jim Popovitch via NANOG wrote: > On Wed, 2019-01-30 at 17:22 -0800, Matthew Petach wrote: > > Any chance this could wait until say the Tuesday > > *after* the Superbowl, when we aren't cutting an > > entire religion's worth of potential workers out of > > the

Re: DNS Flag Day, Friday, Feb 1st, 2019

On Wed, 2019-01-30 at 17:22 -0800, Matthew Petach wrote: > Any chance this could wait until say the Tuesday  > *after* the Superbowl, when we aren't cutting an  > entire religion's worth of potential workers out of  > the workforce available to fix issues in case it  > turns out to be a bigger

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Some companies just don't join route servers as a policy. It can be annoying if you want to talk to them, but I understand there can be various reasons why. It gets very annoying when the peering department isn't responsive to manual peering requests when they're not on the route server because

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

On Wed, 30 Jan 2019 23:55:40 +, "i3D.net - Martijn Schmidt" said: > Here: all networks that didn't already change their peering IP are not > yet connected to the updated route-server. Some networks are not > connected to any route-server. Therefore, those networks did not yet > change

Re: DNS Flag Day, Friday, Feb 1st, 2019

On Wed, Jan 23, 2019 at 4:12 PM Brian Kantor wrote: > Quoting from the web site at https://dnsflagday.net/ > [...] > The current DNS is unnecessarily slow and suffers from inability > to deploy new features. To remediate these problems, vendors of > DNS software and also big public DNS

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

On 1/31/19 12:36 AM, Töma Gavrichenkov wrote: > On Thu, Jan 30, 2019 at 23:10 AM Ren Provo wrote: >> You probably should remove sessions with networks >> explicitly *not* participating in route servers versus >> displaying them on a global shame list. > And so it begins — yet another discussion

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

On Thu, Jan 30, 2019 at 23:10 AM Ren Provo wrote: > You probably should remove sessions with networks > explicitly *not* participating in route servers versus > displaying them on a global shame list. And so it begins — yet another discussion on what does the word "responsibility" really mean.

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

On Wed, Jan 30, 2019 at 9:07 AM Christopher Morrow wrote: > And here I always figured it was bespoke knit caps for all the packets in > cold-weather climes? > learn something new every day! (also, now I wonder what the people who > told me they were too busy knitting caps are ACTUALLY doing??) >

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

Re: Fire Also fire dept response. I've ridden with the Boston Fire Dept, extreme cold is a major PITA, hydrants freeze, you have to work in it going from the heat of the fire to sub-zero air temps over and over, all while getting soaking wet, and wind-chill is certainly a factor. There were

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Hi Thomas, You probably should remove sessions with networks explicitly *not* participating in route servers versus displaying them on a global shame list. Cheers, -ren On Wed, Jan 30, 2019 at 5:06 PM Thomas King wrote: > Hi all, > > > > Thanks for your support! This helps us getting all

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Hi all, Thanks for your support! This helps us getting all peers on the new IPv4 space. Our looking glass shows which peers already have changed the IP settings (see section “BGP session established”) and which peers are still working on it (see section “BGP sessions down”):

Re: Amazon Peering

I'm sure ~ $20k/yr in time cost alone per 10G has nothing to do with that... :p Although to be fair, the individual from Amazon who my peering group has been working with after my first message has been really, really great. As with many things, the people are great, just not enough resources I'm

Re: Amazon Peering

> Yup, super professional of them. > Have you tried to order a port on DirectConnect to check if it was hassleless ? :p

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Greetings Jason, Thank you for your kind feedback, we have CM planned for today to do the needed change. Kind regards, Mara From: NANOG on behalf of Mike Hammett Sent: Wednesday, January 30, 2019 8:41 AM To: Jason Lixfeld Cc: North American Network

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Microsoft an Edgecast has not yet made there changes. On Wed, Jan 30, 2019 at 12:20 PM Jared Mauch wrote: > Akamai is working on doing our part. Apologies. > > Sent from my iCar > > On Jan 30, 2019, at 12:02 PM, Mehmet Akcin wrote: > > Pinged my contacts in each > > On Wed, Jan 30, 2019 at

RE: Amazon Peering

AKA Too Big To Care. Happens a lot. Steven Naslund Chicago IL On Wed, Jan 30, 2019 at 11:36 AM Mike Hammett mailto:na...@ics-il.net>> wrote: Oh, you ordered cross connects for a PNI and they stopped responding mid-project? Isn't that nice! - Mike Hammett Intelligent Computing Solutions

Re: Amazon Peering

Yup, super professional of them. On Wed, Jan 30, 2019 at 11:36 AM Mike Hammett wrote: > Oh, you ordered cross connects for a PNI and they stopped responding > mid-project? Isn't that nice! > > > > - > Mike Hammett > Intelligent Computing Solutions > http://www.ics-il.com > > Midwest-IX >

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

Well said. The electrical load shifts, hydraulic systems, airflows constrained by ice cover, etc, etc, etc. All kinds of things being asked to do stuff outside or at the edge of specifications. Hug your local facilities guys when these things happen. (Or bring them booze.) On Wed, Jan 30, 2019

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

>And apparently fire. I wasn’t going to chime in but one of my >providers >*just* alerted us to an electrical fire in a Minneapolis pop >causing loads to >failover to ups. Unknown whether weather >conditions contributed to the >incident. Yes, in Chicago we will see an increase in home fires

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.

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

On 30/Jan/19 19:37, Naslund, Steve wrote: > >   > > A good HVAC team is critical because we have noted that the building > management systems often are not flexible enough to automatically deal > with super extremes and require some human intervention to tell them > to do things like run heat

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

And apparently fire. I wasn’t going to chime in but one of my providers *just* alerted us to an electrical fire in a Minneapolis pop causing loads to failover to ups. Unknown whether weather conditions contributed to the incident. PZ On Wed, Jan 30, 2019 at 09:25 Naslund, Steve wrote: > >To the

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

>Exactly what he said. We actually run cooling and supplemental heating >in >extreme cold. We need to keep the chiller pulling heat into itself and >pumps >moving on high to keep the outdoor components from freezing >up. During the >summer you might run close to or slightly below freezing

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

>To the 'infrastructure' question, I think the biggest concerns would >be power >related. Although we have a DC in Buffalo that is cooled >on ambient outside >air that has the opposite problem ; it's TOO cold >at the moment, so we are >cycling most of the hot server exhaust >back into the

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Akamai is working on doing our part. Apologies. Sent from my iCar > On Jan 30, 2019, at 12:02 PM, Mehmet Akcin wrote: > > Pinged my contacts in each > >> On Wed, Jan 30, 2019 at 05:52 Jason Lixfeld wrote: >> Hi, >> >> In late October 2018, DE-CIX announced that they would be renumbering

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

The main issue is infrastructure like power, cable damage, and heating/cooling systems. Power lines tend to go down because anything weak becomes brittle and any accident involving a pole tends to cause them to break rather than absorb impact. Also, conduits and manholes that normally might

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

To be fair, reporting the the wind chill factor is very meaningful for health and safety reasons almost everywhere so proper warning is given about people spending time outside. Minneapolis, and the bigger Canadian cities have those inside walkways and pedestrian pathways, but they're not that

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

And here I always figured it was bespoke knit caps for all the packets in cold-weather climes? learn something new every day! (also, now I wonder what the people who told me they were too busy knitting caps are ACTUALLY doing??) On Wed, Jan 30, 2019 at 8:55 AM Bryan Holloway wrote: >

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Pinged my contacts in each On Wed, Jan 30, 2019 at 05:52 Jason Lixfeld wrote: > Hi, > > In late October 2018, DE-CIX announced that they would be renumbering > their IPv4 address block in New York between 01-28-19 and 01-30-19. > > This was followed by numerous reminders in months, weeks and

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

Approximately 3 hrs ago we lost B-feed at Minneapolis Cologix. Apparently the local utility requested that they move one side to generator due to the weather and high-utilization, and the ATS failed. But we're up ... On 1/30/19 10:50 AM, Mel Beckman wrote: Being a Minnesota native, I can

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

Being a Minnesota native, I can tell you that while it is indeed cold, this is nothing new i the Great White North :) I am amaze a how consistently the media overplays the severity of Midwest cold weather as some kind of unique phenomenon. They amplify this by reporting the wind-chill factor,

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

A lot of huge companies apparently find it tough to find the $75k to hire one more peering person. Not all, though. For many, everything just runs like clockwork. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com -

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

For anyone running IP networks in the Midwest, are you having to do anything special to keep your networks up? For the data centres, is this cold front a chance to reduce air conditioning costs, or is it actually straining the infrastructure? I'm curious, from a +27-degree C summer's day here in

Re: Amazon Peering

Oh, you ordered cross connects for a PNI and they stopped responding mid-project? Isn't that nice! - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com - Original Message - From: "Luca Salvatore via NANOG" To: "North

Re: Amazon Peering

Similar experiences here with Amazon. Initially had semi-regular responses from their peering team, they issued LOAs, I ordered the x-connects and then radio silence for months. At the point now where I'm disconnecting x-connects since it's a waste of money. On Tue, Jan 29, 2019 at 10:49 AM

Re: AT Fiber Outage in Holmdel, NJ

Hi Mehmet, Commercial; forgot to mention fiber issues related to AVPN service, specifically peering to ASN 13979. Best Regards, Amauris Get Outlook for iOS From: Mehmet Akcin Sent: Tuesday, January 29, 2019 12:43 To: Amauris Rodriguez

Re: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

On 1/30/19 7:52 AM, Jason Lixfeld wrote: Hi, In late October 2018, DE-CIX announced that they would be renumbering their IPv4 address block in New York between 01-28-19 and 01-30-19. This was followed by numerous reminders in months, weeks and even days leading up to the renumbering

Calling LinkedIn, Amazon and Akamai @ DE-CIX NY

Hi, In late October 2018, DE-CIX announced that they would be renumbering their IPv4 address block in New York between 01-28-19 and 01-30-19. This was followed by numerous reminders in months, weeks and even days leading up to the renumbering activity. The renumbering activity has come and