AT&T CEO Weighs In on Huawei: ‘Our Government Is Asking the Right Questions’
The CEO said that the issue for European operators in banning Huawei has less to do with security...
Ericsson Firms Up 5G Standing in Korea
Korean mobile operators look set to beat Verizon by a matter of days in the race to a 5G network...
The Serverlist Newsletter: Serverless Benchmarks, Workers.dev, security implications of serverless cloud computing, and more
Check out our third edition of The Serverlist below. Get the latest scoop on the serverless space, get your hands dirty with new developer tutorials, engage in conversations with other serverless developers, and find upcoming meetups and conferences to attend.
Sign up below to have The Serverlist sent directly to your mailbox.
Dell EMC, HPE Still Lead Server Market, But Watch Out for Inspur
Inspur set a goal to be the top server market vendor by 2023, and it’s got a plan to steal market...
Migration Strategy: Moving From MPLS/LDP to Segment Routing
MPLS core networks that use Label Distribution Protocol (LDP) are common in SP core networks and have served us well. So, the thought of pulling the guts out of the core is pretty daunting and invites the question why you would want to perform open-heart surgery on such critical infrastructure. This article attempts to explain the benefits that would accrue from such a move and gives a high-level view of a migration strategy.
Why Do I Need Segment Routing?
- Simplicity: LDP was invented as a label distribution protocol for MPLS because nobody wanted to go back to the standards bodies to re-invent OSPF or IS-IS so that they could carry labels. A pragmatic decision, but one that results in networks having to run two protocols. Two protocols means twice the complexity.
Segment Routing simplifies things by allowing you to turn off LDP. Instead it carries label (or Segment ID) information in extensions to the IGP. This then leaves you with only IS-IS or OSPF to troubleshoot. As Da Vinci reportedly said, ‘simplicity is the ultimate sophistication’.
- Scale: LDP scales, but for fast convergence RSVP-TE is often used to tunnel LDP across a core. RSVP requires core routers to Continue reading
Computer Networks: A Systems Approach – free textbook
Free (as in Freedom) Computer Textbook for Computer Networking
The post Computer Networks: A Systems Approach – free textbook appeared first on EtherealMind.
IPv6 Buzz 022: Critical Security Differences Between IPv4 And IPv6
There are a few critical security differences between IPv4 and IPv6, including host addressing and extension headers. In today's IPv6 Buzz episode, we examine these differences, and other v6 security issues, with guest Eric Vyncke, a Distinguished Engineer at Cisco and co-author of the book "IPv6 Security."
The post IPv6 Buzz 022: Critical Security Differences Between IPv4 And IPv6 appeared first on Packet Pushers.
IPv6 Buzz 022: Critical Security Differences Between IPv4 And IPv6
There are a few critical security differences between IPv4 and IPv6, including host addressing and extension headers. In today's IPv6 Buzz episode, we examine these differences, and other v6 security issues, with guest Eric Vyncke, a Distinguished Engineer at Cisco and co-author of the book "IPv6 Security."Writing an API at the Edge with Workers and Cloud Firestore
We’re super stoked about bringing you Workers.dev, and we’re even more stoked at every opportunity we have to dogfood Workers. Using what we create keeps us tuned in to the developer experience, which takes a good deal of guesswork out of drawing our roadmaps.
Our goal with Workers.dev is to provide a way to deploy JavaScript code to our network of 165 data centers without requiring developers to register a domain with Cloudflare first. While we gear up for general availability, we wanted to provide users an opportunity to reserve their favorite subdomain in a fair and consistent way, so we built a system to allow visitors to reserve a subdomain where their Workers will live once Workers.dev is released. This is the story of how we wrote the system backing that submission process.
Requirements
Of course, we always want to use the best tool for the job, so designing the Workers that would back Workers.dev started with an inventory of constraints and user experience expectations:
Constraints
- We want to limit reservations to one per email address. It’s no fun if someone writes a bot to claim every good Workers subdomain in ten seconds; they Continue reading
Is ONAP Stone Soup? Reflections From the Open Source Leadership Summit
Schrödinger’s cat or stone soup, pick your favorite ONAP analogy.
Buzzword bingo: NetDevOps edition
Looking at the marketing landscape for IT, you could be forgiven for thinking that the current strategy was to dynamite a word factory and use the resulting debris as marketing content. DevSecOps. NetDevOps. Ops, ops, spam, eggs, spam, and DevSpamOps.
The naming trend lends itself easily to parody, but it began as shorthand for an attempt to solve real IT problems. And its iterations have more in common than a resemblance to alphabet salad. What lies beneath the buzzwords? And do you need to care?
Countless companies have jumped on the NetDevOps bandwagon, all with their own way of doing things; and most are utterly incompatible with everyone else. Some may have already abandoned the NetDevOps craze, believing it to be nothing but marketing hype wrapped around a YAML parser and some scripts. Others might have found a system that works for them and swear by it, using nothing else for provisioning.
Regardless of views, a system that allows for rapid provisioning and re-provisioning of applications, containers, virtual machines, and network infrastructure is paramount.
Ministry of Silly Names: A History
The modern era of namesmashing started with DevOps. This made a sort of sense because, before this, IT had Continue reading
The Blogging Mirror
Writing isn’t always the easiest thing in the world to do. Coming up with topics is hard, but so too is making those topics into a blog post. I find myself getting briefings on a variety of subjects all the time, especially when it comes to networking. But translating those briefings into blog posts isn’t always straight forward. When I find myself stuck and ready to throw in the towel I find it easy to think about things backwards.
A World Of Pure Imagination
When people plan blog posts, they often think about things in a top-down manner. They come up with a catchy title, then an amusing anecdote to open the post. Then they hit the main idea, find a couple of supporting arguments, and then finally they write a conclusion that ties it all together. Sound like a winning formula?
Except when it isn’t. How about when the title doesn’t reflect the content of the post? Or the anecdote or lead in doesn’t quite fit with the overall tone? How about when the blog starts meandering away from the main idea halfway through with a totally separate argument? Or when the conclusion is actually the place where the Continue reading
Wachter Saves $200K Annually With MNJ Technologies’ Managed SD-WAN
The electrical contractor and technology integrator deployed a Silver Peak-based managed SD-WAN...
Creating Automation Source-of-Truth from Device Configurations
Remember the previous blog post in this sequence in which I explained the need for single source-of-truth used in your network automation solution? No? Please read it first ;)
Ready for the next step? Assuming your sole source-of-truth is the actual device configuration, is there a magic mechanism we can use to transform it into something we could use in network automation?
TL&DR: No.
Read more ...