
During a few recent chats with my friends in the industry, I’ve heard a common refrain coming up about technologies or products being offered for sale. Typically these are advanced ideas given form that are then positioned as products for sale in the market. Overwhelmingly the feedback comes down to one phrase:
This is a solution in search of a problem.
We’ve probably said this a number of times about a protocol or a piece of hardware. Something that seems to be built to solve a problem we don’t have and couldn’t conceive of. But why does this seem to happen? And what can we do to fix this kind of mentality?
If I told you today that I was creating software that would revolutionize the way your autonomous car delivers music to the occupants on their VR headsets you’d probably think I was crazy, right? Every one of the technologies I mentioned in the statement is a future thing that we expect may be big down the road. We love the idea of autonomous vehicles and VR headsets and such.
Now, let’s change the statement. I’m working on a new algorithm for HD-DVD players to produce Continue reading
Internet Exchange Points (IXPs) are a vital element of Internet infrastructure. They can be found at physical and neutral locations where different IP networks meet to exchange local traffic via a switch. Implementing an IXP within a country helps bring faster, more affordable, and better performing Internet to people.
Frustrated by poor quality of service and high-cost connectivity, local Internet stakeholders started off the process of setting up an IXP in Pakistan. With the adoption of the 2015 telecoms policy, there was a new drive to foster interconnection and keep local traffic within the country.
Led by the Pakistan Telecom Authority (PTA), the telecom regulator, the government-initiated consultations on how to set up an IXP. To develop an informed opinion about IXPs, PTA reached out to the Internet Society, the Asia Pacific Network Information Center (APNIC), the local Internet community, and civil society.
The consultations led to the formation of an IXP board; comprised of all stakeholders. The new board decided to establish IXPs at Islamabad, Karachi, and Lahore. The IXP board first set up an IXP in Pakistan at a neutral venue, the Higher Education Commission of Pakistan (HEC), Islamabad in 2016. HEC was ideal because it provided a Continue reading
The second part of the Cisco SD-WAN webinar focused on design considerations and trade-offs in several scenarios. David Penaloza briefly reviewed the types of policies and their capabilities before discussing what to keep in mind when designing the solution.
The second part of the Cisco SD-WAN webinar focused on design considerations and trade-offs in several scenarios. David Penaloza briefly reviewed the types of policies and their capabilities before discussing what to keep in mind when designing the solution.
In this Day Two Cloud podcast clip, we discuss consulting and MONEY. To hear the entire episode, go here. Hosts Ned Bellavance and Ethan Banks are joined by Michael Jenkins, Sr. Systems Reliability Engineer at Managed Kaos; and Anthony Nocentino, Enterprise Architect at Centino Systems and Pluralsight author. If you like engineering discussions like this, […]
The post What Should A Consultant Charge Clients? – Video appeared first on Packet Pushers.
Latin America boasts impressive growth in IPv6 adoption. In today's podcast we speak with Alejandro Acosta, Innovation and Development Engineer at Latin America's Regional Internet Registry, LACNIC, to find out how the region is achieving its deployments.
The post IPv6 Buzz 069: IPv6 And LACNIC In Latin America appeared first on Packet Pushers.
FR Routing is a widely used and supported open source routing stack. In this episode of the Hedge, Alistair Woodman, Quentin Young, Donald Sharp, Tom Ammon, and Russ White discuss recent updates, additions to the CI/CD system, the release process, and operating system support. If you’re looking for a good open source, containerized routing stack for everything from route servers to DC fabrics and labbing to production, you should check out FR Routing.
I made a flippant remark in a blog comment…
While it’s academically stimulating to think about forwarding small packets (and applicable to large-scale VoIP networks), most environments don’t have to deal with those. Looks like it’s such a non-issue that I couldn’t find recent data; in the good old days ~50% of the packets were 1500 byte long.
… and Minh Ha (by now a regular contributor to my blog) quickly set me straight with a lengthy comment that’s too good to be hidden somewhere at the bottom of a page. Here it is (slightly edited). Also, you might want to read other comments to the original blog post for context.