ZTE Replaces Its Chairman and Entire Board of Directors
The sudden absence of a major telecom vendor has caused some big ripple effects. For instance, ZTE pulled out of Mobile World Congress in Shanghai this week.
The sudden absence of a major telecom vendor has caused some big ripple effects. For instance, ZTE pulled out of Mobile World Congress in Shanghai this week.

My good friend and colleague Rich Stroffolino (@MrAnthropology) is collecting Tales from the Trenches about times when we did things that we didn’t expect to cause problems. I wanted to share one of my own here about the time I knocked a school offline with a debug command.
The setup for this is pretty simple. I was deploying a CallManager setup for a multi-site school system deployment. I was using local gateways at every site to hook up fax lines and fire alarms with FXS/FXO ports for those systems to dial out. Everything else got backhauled to a voice gateway at the high school with a PRI running MGCP.
I was trying to figure out why the station IDs that were being send by the sites weren’t going out over caller ID. Everything was showing up as the high school number. I needed to figure out what was being sent. I was at the middle school location across town and trying to debug via telnet. I logged into the router and figured I would make a change, dial my cell phone from the VoIP phone next to me, and see what happened. Simple troubleshooting, Continue reading
Today is an exciting day for the Internet Society. It gives me great pleasure to announce, on behalf of the Internet Society’s Board of Trustees, that Andrew Sullivan has been selected as the Internet Society’s new President and Chief Executive Officer (CEO). He will formally take up his position on September 1, 2018.
This selection now successfully concludes the CEO search process we began last November.
The CEO selection process involved extensive work on the part of the Board but gave us much food for thought. We received a wealth of extremely impressive applications from more than a hundred internal and external candidates covering a huge range of talent and experience. We had some thought-provoking conversations as part of the process and I would like to express my sincere appreciation to everybody who applied for the position.
I believe Andrew’s success in being selected for this crucial role represents an enormous opportunity for the Internet Society and the global Internet.
Andrew brings a wealth of Internet industry and technology experience with him. He has served in a number of past roles, including time at Dyn, now a Global Business Unit of the Oracle Corporation, managing Domain Name System (DNS) development Continue reading
Hey, it's HighScalability time:
Rockets. They're big. You won't believe how really really big they are. (Corridor Crew)
Do you like this sort of Stuff? Please lend me your support on Patreon. It would mean a great deal to me. And if you know anyone looking for a simple book that uses lots of pictures and lots of examples to explain the cloud, then please recommend my new book: Explain the Cloud Like I'm 10. They'll love you even more.
Following the precedent set by other modern technologies in India, SD-WAN will render MPLS obsolete before it even gets a foothold.
Two weeks ago was our eighth DockerCon in just four years. Our community of contributors, developers, IT users, enterprises and ecosystem partners has grown exponentially into the millions, anchored on our founder Solomon Hykes’ simple premise of democratizing the use of the software container. Today as was from the beginning, Docker creates simple tooling and a universal packaging approach that bundles up all application dependencies inside the container. Docker Engine enables applications to run anywhere consistently on any infrastructure, solving “dependency hell” for developers and operations teams, and eliminating the “it works on my laptop!” problem.
In the past 2 years, Docker Engine’s codebase has been refactored into several reusable components, the most important being containerd, the core container runtime, and BuildKit, the part of Docker Engine used to build images. In the contribute and collaborate track at DockerCon, Michael Crosby and Tonis Tiigli gave an update on these two projects (video, slides)
containerd, the core container runtime in Docker Engine has been leveraged by millions of users and is run in production by tens of thousands of organizations. Eighteen months ago, Docker spun out containerd from Docker Engine; donated Continue reading
In today’s Network Collective Short Take, Russ White discusses his take on the intersection of culture and technology.
The post Short Take – Culture and Technology appeared first on Network Collective.
If you followed part one, I have an environment setup where I can write Typescript with tests and deploy to the Cloudflare Edge with npm run upload. For this post, I want to take one of the Worker Recipes further.
I'm going to build a mini HTTP request routing and handling framework, then use it to build a gateway to multiple cryptocurrency API providers. My point here is that in a single file, with no dependencies, you can quickly build pretty sophisticated logic and deploy fast and easily to the Edge. Furthermore, using modern Typescript with async/await and the rich type structure, you also write clean, async code.
OK, here we go...
My API will look like this:
| Verb | Path | Description |
|---|---|---|
| GET | /api/ping |
Check the Worker is up |
| GET | /api/all/spot/:symbol |
Aggregate the responses from all our configured gateways |
| GET | /api/race/spot/:symbol |
Return the response of the provider who responds fastest |
| GET | /api/direct/:exchange/spot/:symbol |
Pass through the request to the gateway. E.g. gdax or bitfinex |
OK, this is Typescript, I get interfaces and I'm going to use them. Here's my ultra-mini-http-routing framework definition:
export interface IRouter {
route(req: RequestContextBase): IRouteHandler;
}
/**
* A route
*/
export interface IRoute Continue readingEthernet Virtual Private Network (EVPN) solution is becoming pervasive for Network Virtualization Overlay (NVO) services in data center (DC) networks and as the next generation VPN services in service provider (SP) networks. As a result of this popularity a lot of work is going on in IETF in this area. In this post I collect links to some of the interesting IETF drafts in this area.
All this information is relevant for 1H 2018 timeframe. Keep in mind to pay attention to which version of draft you’re reading – this drafts are frequently updated.
Service Chaining using Virtual Networks with BGP VPNs
This document describes how service function chains (SFC) can be applied to traffic flows using routing in a virtual (overlay) network to steer traffic between service nodes. Chains can include services running in routers, on physical appliances or in virtual machines. Two techniques are described: in one the service chain is implemented as a sequence of distinct VPNs between sets of service nodes that apply each service function; in the other, the routes within a VPN are modified through the use of special route targets and modified next-hop resolution to achieve the desired result.
As telecom operators roll out 5G, the US should steer clear of the heavy-handed regulation like that of the EU in order to ensure all citizens gain access to the speedier mobile technology.
The largest chunk of bytes that a transport protocol can forward across specific medium is called MTU – Maximum Transmission Unit. If we speak about Ethernet, which is today the most common, he has by default 1522 bytes MTU. The story about MTU is that the MTU of specific protocol basically defines how much payload (or highest protocols headers + their payload) it can carry in its biggest packet, not counting his own headers. Putting more payload into single packet than the MTU allows will result in fragmentation, the process of slicing the frame into more smaller frames so that
The post MTU and TCP MSS appeared first on How Does Internet Work.
Debugging data flows in reactive programs Banken et al., ICSE’18
To round off our look at papers from ICSE, here’s a really interesting look at the challenges of debugging reactive applications (with a certain Erik Meijer credited among the authors).
… in recent years the use of Reactive Programming (RP) has exploded. Languages such as Elm and libraries such as Reactor, Akka, and Rx are being used by companies such as Netflix, Microsoft, and Google, to build highly responsive and scalable systems.
The rise of reactive programming fits well with the increasing need to process streams of data. In a reactive program, you set up a data processing pipeline and then wait for input to arrive.
Many RP implementations share a notion of a collection that abstracts over time, in contrast to space like standard collections. This collection comes in different flavors, such as Observable (Rx)… the implementations differ in the precise semantics of their collections, their execution model (push/pull) , and the set of available operators.
While in theory events and threads are duals, in practice the RP abstraction works very well for expressing streaming pipelines. If you have an abstraction over time though, Continue reading