Re: few big monolithic PEs vs many small PEs

On 28/Jun/19 01:23, Mike Hammett wrote: > I've ran into many providers where they had routers in the top 10 or > 15 markets...  and that was it. If you wanted a connection in South > Bend or Indianapolis or New Orleans or Ohio or...  you were backhauled > potentially hundreds of miles to a nearb

Re: Crowdfunding critical infrastructure

> You know how to help. Take the Loadsharers pleadge and spread the word. > Or maybe suggest to some of these BDFL that they loosen their self imposed requirements to maintain absolute control of the code, and share the workload. It's not hard to work 50 hours a week for free. Don't! On Thu, Jun

Re: Crowdfunding critical infrastructure

Jon Lewis : > This may have been an anomaly made possible by early .com $, but I'm pretty > sure at one point, companies like VA Research / VA Linux employed developers > who in various cases worked part or full time on the Linux kernel and other > Open Source projects "as their job". I was on the

Re: few big monolithic PEs vs many small PEs

Big routers also mean they're a lot more expensive. You have to squeeze more life out of them because they cost you hundreds of thousands of dollars. You run them longer than you really should. If you run more, smaller, $20k or $30k routers, you'll replace them on a more reasonable cycle.

Re: few big monolithic PEs vs many small PEs

I've ran into many providers where they had routers in the top 10 or 15 markets... and that was it. If you wanted a connection in South Bend or Indianapolis or New Orleans or Ohio or... you were backhauled potentially hundreds of miles to a nearby big market. More smaller POPs reduces the tro

Re: Crowdfunding critical infrastructure

Once upon a time, Jon Lewis said: > This may have been an anomaly made possible by early .com $, but I'm > pretty sure at one point, companies like VA Research / VA Linux > employed developers who in various cases worked part or full time on > the Linux kernel and other Open Source projects "as th

Re: Crowdfunding critical infrastructure

Once upon a time, Eric S. Raymond said: > Chris Adams : > > Once upon a time, Eric S. Raymond said: > > > Tell it to Patrick Volkerding, who sweated to created the first Linux > > > distribution > > > > No, he didn't. > > Can you be more specific? Are we possibly having some definitional issue

Re: Crowdfunding critical infrastructure

Eric, Not to go too far afield, but I’m also not on anyone’s payroll, so I buy my own individual-plan health insurance. Yes, it’s more expensive, but that’s the price of not having just one boss :) -mel beckman > On Jun 27, 2019, at 10:46 AM, Eric S. Raymond wrote: > > Mehmet Akcin : >>> On

Re: OFFTRACK - Re: 1st Linux Distro [was:Re: Crowdfunding critical infrastructure]

Eric S. Raymond : > Miles Fidelman : > > Now, if you mean, the oldest EXTANT distribution, that WOULD be Slackware. > > I will revise appropriately. And ask my informants some pointed questions. > > This is, by tge why, an exemplar of why LBIP evaluation should be > crowdsourced. I can't know ev

Re: Crowdfunding critical infrastructure

Jan Schaumann : > Perhaps an opportunity to collaborate with > https://www.coreinfrastructure.org/ ? I am unfortunately constrained in what I can say about CII. The temptation to rant is extreme, but I would be revealing confidences that are not mine if I did so. I'll just suggest that if you thi

Re: AS16509 (Amazon) peering contact

Hi Kody, Please don't share a person's e-mail account on a mailing list.  Role accounts are one thing, but not this.  If you want to, send it privately.  Cheers, Stephen On 2019-06-27 17:47, Kody Vicknair wrote: > I've always worked with Tim Bates. They were exceptionally quick with > standing

Re: OFFTRACK - Re: 1st Linux Distro [was:Re: Crowdfunding critical infrastructure]

Miles Fidelman : > Now, if you mean, the oldest EXTANT distribution, that WOULD be Slackware. I will revise appropriately. And ask my informants some pointed questions. This is, by tge why, an exemplar of why LBIP evaluation should be crowdsourced. I can't know eveything relevant. No other singl

RE: AS16509 (Amazon) peering contact

I've always worked with Tim Bates. They were exceptionally quick with standing up my session. like same day quick... t...@amazon.com Kody Vicknair Network Engineer Tel:985.536.1214 Fax:985.536.0300 Email: kvickn...@reservetele.com Reserve Telecommunications 100 RTC Dr Reserve, LA

Re: Crowdfunding critical infrastructure

On Thu, 27 Jun 2019, Eric S. Raymond wrote: I think many of us assume that doing the sort of work you're referring to will definitely result in the regular receipt of many prestigious, high-paying job offers. When that happens, it's actually a problem. Let's suppose that someone were to judge

Re: AS16509 (Amazon) peering contact

On 27/06/2019 20:55, Andras Toth wrote: > Including at least an ASN in the peering request usually helps to > expedite the process :) & keeping your peeringdb entry up-to-date is usually helpful, too. Depending on who you want to peer with(!) Some networks require you to have up-to-date peeringd

Re: few big monolithic PEs vs many small PEs

On 27 June 2019 16:26:03 BST, Mark Tinka wrote: > > >On 27/Jun/19 10:58, James Bensley wrote: > >> Hi Adam, >> >> Over the years I have been bitten multiple times by having fewer big >> routers with either far too many services/customers connected to them >> or too much traffic going through th

Re: Crowdfunding critical infrastructure

Miles Fidelman wrote: > I think it would be a grand thing if someone put together a visible list of > critical Internet infrastructure, who maintains it, and perhaps "click to > support" buttons for those that need support. Perhaps an opportunity to collaborate with https://www.coreinfrastructure

Re: few big monolithic PEs vs many small PEs

On 27 June 2019 16:31:27 BST, Mark Tinka wrote: > > >On 27/Jun/19 14:48, James Bensley wrote: > >> That to me is a simple scenario, and it can be mapped with a >> dependency tree. But in my experience, and maybe it's just me, things >> are usually a lot more complicated than this. The root cause i

OFFTRACK - Re: 1st Linux Distro [was:Re: Crowdfunding critical infrastructure]

On 6/27/19 3:21 PM, Eric S. Raymond wrote: Chris Adams : Once upon a time, Eric S. Raymond said: Tell it to Patrick Volkerding, who sweated to created the first Linux distribution No, he didn't. Can you be more specific? Are we possibly having some definitional issue about what constitutes

Re: Crowdfunding critical infrastructure

Chris Adams : > Once upon a time, Eric S. Raymond said: > > Tell it to Patrick Volkerding, who sweated to created the first Linux > > distribution > > No, he didn't. Can you be more specific? Are we possibly having some definitional issue about what constitutes a Linux distribution? It is cer

Re: Crowdfunding critical infrastructure

Once upon a time, Eric S. Raymond said: > Tell it to Patrick Volkerding, who sweated to created the first Linux > distribution No, he didn't. -- Chris Adams

Re: AS16509 (Amazon) peering contact

Hey Francois, Including at least an ASN in the peering request usually helps to expedite the process :) Best regards, Andras > On 27 Jun 2019, at 19:01, Darin Steffl wrote: > > It took us over a year before peering was established. Just keep trying until > they reply. > >> On Thu, Jun 27, 2

Re: Crowdfunding critical infrastructure

Jeff Shultz : > As is, one thing that grates a bit personally is that the two advisor > pages do not share a common structure - If I'm doing a comparison, > even unconsciously, I'm going to want to be looking at like objects. > Instead, I have your page, which matches the rest of the formatting of

Re: AS16509 (Amazon) peering contact

It took us over a year before peering was established. Just keep trying until they reply. On Thu, Jun 27, 2019 at 11:13 AM Francois Lecavalier < francois.lecaval...@mindgeek.com> wrote: > Hi nanog, > > > > We just joined a IXP (QiX – Montreal) in the hope to offload >4Gbps of > traffic to AWS, ho

Re: Crowdfunding critical infrastructure

On Thu, Jun 27, 2019 at 10:31 AM Eric S. Raymond wrote: > > Jeff Shultz : > > It will be interesting to see, should this get off the ground to any > > significant amount, if it turns into a bit of a popularity contest - > > where a few get the lions share of the donations and the rest a > > pittan

Re: Crowdfunding critical infrastructure

Miles Fidelman : > I think it would be a grand thing if someone put together a visible list of > critical Internet infrastructure, who maintains it, and perhaps "click to > support" buttons for those that need support.  Then again, such a list might > present a wonderful target list for those who m

Re: Crowdfunding critical infrastructure

Mehmet Akcin : > On Thu, Jun 27, 2019 at 08:41 Eric S. Raymond wrote: > > > The members of this list are, I think, much more aware tham most that > > a lot of critical Internet software is maintained by unfunded > > volunteers, and of the systemic risks that result from this. > > Please explain.

Re: Crowdfunding critical infrastructure

Jeff Shultz : > It will be interesting to see, should this get off the ground to any > significant amount, if it turns into a bit of a popularity contest - > where a few get the lions share of the donations and the rest a > pittance. I'm aware of that possible failure mode. It's why I designed in

Re: Crowdfunding critical infrastructure

Tom Beecher > > Adding an organization in front of that whose sole reason for existence is > > to decide who gets what % of the money doesn't make a lot of sense, mostly > > because it is just creating another layer of people who are then going to > > feel entitled to be compensated for taking the

Re: Crowdfunding critical infrastructure

Matt Harris : > Interesting concept, and seems like a good idea. What's the end goal look > like? Depends on timescale. What I want is for a growing number of skilled engineers to be able to both (a) work shared-infrastructure problems full time, and (b) be able to feed themselves and pay rent an

Re: Crowdfunding critical infrastructure

I think it would be a grand thing if someone put together a visible list of critical Internet infrastructure, who maintains it, and perhaps "click to support" buttons for those that need support.  Then again, such a list might present a wonderful target list for those who might want to do ill.

Re: Crowdfunding critical infrastructure

On Thu, Jun 27, 2019 at 9:34 AM Tom Beecher wrote: >> >> Encouraging folks to contribute to specific individuals directly may be a >> little more difficult though, compared to, say, getting a legitimate >> organization going that provides (likely objectively-determined merit-based) >> payouts t

Re: Crowdfunding critical infrastructure

On Thu, Jun 27, 2019 at 11:32 AM Tom Beecher wrote: > Encouraging folks to contribute to specific individuals directly may be a >> little more difficult though, compared to, say, getting a legitimate >> organization going that provides (likely objectively-determined >> merit-based) payouts to the

Re: Crowdfunding critical infrastructure

> > Encouraging folks to contribute to specific individuals directly may be a > little more difficult though, compared to, say, getting a legitimate > organization going that provides (likely objectively-determined > merit-based) payouts to the sort of folks you're talking about. > Adding an organ

Caching infrastructure

Hello! If you have experience building and operating small caching boxes for cdns, or other type of dns services Please contact me offlist as i have some simple questions about them Thank you -- Mehmet +1-424-298-1903

Call for Presentations: 31st DNS-OARC Workshop, Austin, Texas, Oct 31 - Nov 01 2019

The 31st DNS-OARC Workshop will take place at the JW Marriott Austin in Austin, Texas, USA on October 31st and November 1st 2019. It is co-located with and will take place right after NANOG 77 (Oct 27th to Oct 30th 2019). The Workshop's Program Committee is now requesting proposals for presentatio

Re: Anyone from AT&T/AS7018 available?

If it's to turn up a circuit I would say try these: I turned up BGP with Anthony once: ag2...@att.com And the next circuit I had to turn up I was stuck in a hurricane too, reached back to him, was away but was redirecting to his manager: mm2...@us.att.com

AS16509 (Amazon) peering contact

Hi nanog, We just joined a IXP (QiX - Montreal) in the hope to offload >4Gbps of traffic to AWS, however it's been 2 weeks we sent a request to peer...@amazon.com without any reply. Are they usually taking long to reply? Anyone have a direct contact? Thanks, -Frank

Re: Crowdfunding critical infrastructure

On Thu, Jun 27, 2019 at 08:41 Eric S. Raymond wrote: > The members of this list are, I think, much more aware tham most that > a lot of critical Internet software is maintained by unfunded > volunteers, and of the systemic risks that result from this. > Please explain. This is not true. > I'm

Re: Crowdfunding critical infrastructure

On Thu, Jun 27, 2019 at 10:41 AM Eric S. Raymond wrote: > The members of this list are, I think, much more aware tham most that > a lot of critical Internet software is maintained by unfunded > volunteers, and of the systemic risks that result from this. > > I'm attacking the problem at the root,

Crowdfunding critical infrastructure

The members of this list are, I think, much more aware tham most that a lot of critical Internet software is maintained by unfunded volunteers, and of the systemic risks that result from this. I'm attacking the problem at the root, applying what the Internet has taught us about decentralization an

Re: few big monolithic PEs vs many small PEs

On 27/Jun/19 14:48, James Bensley wrote: > That to me is a simple scenario, and it can be mapped with a > dependency tree. But in my experience, and maybe it's just me, things > are usually a lot more complicated than this. The root cause is > probably a bad design introducing too much complexi

Re: few big monolithic PEs vs many small PEs

On 27/Jun/19 14:03, adamv0...@netconsultings.com wrote: > I believe it would, for a time, but it would require SW upgrade -testing > etc.. even newer SW in itself gave us better resource management and > performance optimizations. > However even with powerful CP and streamlined SW we'd be sti

Re: few big monolithic PEs vs many small PEs

On 27/Jun/19 10:58, James Bensley wrote: > Hi Adam, > > Over the years I have been bitten multiple times by having fewer big > routers with either far too many services/customers connected to them > or too much traffic going through them. These days I always go for > more smaller/more routers t

Comcast Outage - East Coast?

I just saw a 40% traffic drop on my routing core (East Coast based) across all my BGP peers. None of my transit peers flapped or had any issues other than the traffic drop. Almost all the complaints of connectivity issues were people using Comcast, so right now thats the only common thread. Any

Re: few big monolithic PEs vs many small PEs

On Thu, 27 Jun 2019 at 12:46, wrote: > > > From: James Bensley > > Sent: Thursday, June 27, 2019 9:56 AM > > > > One experience I have made is that when there is an outage on a large PE, > > even when it still has spare capacity, is that the business impact can be > > too > > much to handle (the

Re: few big monolithic PEs vs many small PEs

On Wed, 19 Jun 2019 at 21:23, wrote: > > Hi folks, > > Recently I ran into a peculiar situation where we had to cap couple of PE > even though merely a half of the rather big chassis was populated with > cards, reason being that the central RE/RP was not able to cope with the > combined number of

RE: few big monolithic PEs vs many small PEs

> From: Mark Tinka > Sent: Friday, June 21, 2019 1:27 PM > > > > On 21/Jun/19 10:32, adamv0...@netconsultings.com wrote: > > > So this particular case, the major POPs, is actually where we ran into the > problem of RE/RP becoming full (too many VRFs/Routes/BGP sessions) > halfway through the c

RE: few big monolithic PEs vs many small PEs

> From: James Bensley > Sent: Thursday, June 27, 2019 9:56 AM > > One experience I have made is that when there is an outage on a large PE, > even when it still has spare capacity, is that the business impact can be too > much to handle (the support desk is overwhelmed, customers become irate > i