The group also combined its separate CORD projects.
Former COO Monika Maurer departs after just eight months on the job.
Net neutrality is defined differently in different circles. For the Internet Society, it means that an Internet service provider should not block, filter, throttle a users’ Internet usage, or give preferential treatment to one end user or content provider over another. Fundamentally, everyone should be able to access the content and services they choose without corporate or government interference. We believe this will ensure the Internet remains an engine for innovation, free expression, and economic growth. In some jurisdictions, this may require policy, regulatory, and technical measures.
On December 14, the Federal Communications Commission (FCC) is likely to vote to repeal the 2015 Open Internet Order, which classified broadband providers as common carriers under Title II of the Communications Act. Under FCC Chairman Pai’s proposal, the FCC would yield authority over broadband providers to the Federal Trade Commission (FTC).
Since the announcement of that vote, many American Internet users have been anxious that their Internet service provider may undo their commitments to provide open access to the Internet for their customers. They are right to be anxious. We are already seeing signs that ISPs may change their net neutrality commitments in light of the upcoming ruling.
American users have Continue reading
Find out why Citrix NetScaler SD-WAN was named a leading player to watch and how its solution is reshaping the modern enterprise network with improved performance reduced costs and enhanced security, with the flexibility of a hardware or virtual appliance, on-premises or in the cloud.

Six years ago when I joined Cloudflare the company had a capital F, about 20 employees, and a software stack that was mostly NGINX, PHP and PowerDNS (there was even a little Apache). Today, things are quite different.
CC BY-SA 2.0 image by Randy Merrill
The F got lowercased, there are now more than 500 people and the software stack has changed radically. PowerDNS is gone and has been replaced with our own DNS server, RRDNS, written in Go. The PHP code that used to handle the business logic of dealing with our customers’ HTTP requests is now Lua code, Apache is long gone and new technologies like Railgun, Warp, Argo and Tiered Cache have been added to our ‘edge’ stack.
And yet our servers still identify themselves in HTTP responses with
Server: cloudflare-nginx
Of course, NGINX is still a part of our stack, but the code that handles HTTP requests goes well beyond the capabilities of NGINX alone. It’s also not hard to imagine a time where the role of NGINX diminishes further. We currently run four instances of NGINX on each edge machine (one for SSL, one for non-SSL, one for caching and one Continue reading
Companies plan to ramp up their storage infrastructure, according to Interop ITX research.
So let’s learn about NETCONF, but first a bit of history and perspective. Everyone in networking business at least once heard about SNMP (Simple Network Management Protocol), which is the goto protocol for monitoring your network devices, and wondered how cool it would be if you could not only monitor your network with it, but actively configure it (sort of like “SDN wannabe”). But for that purpose the SNMP was not really useful, it supported some write operations but they were so generic and incomplete that it was not really feasible. That is where NETCONF came around 2011 as a standard (it was here before but its RFC 6241 was ratified then) and changed the game in favor of configuring any device, while not restricting vendors from declaring their own NETCONF data structures to fit their features, but lets first check the protocol first before diving into the data structures.
NETCONF is a RCP (remote procedure call) based protocol, using XML formating as payload and YAML language as data modeling (the part that explains to you what XML to send to configure something).
Ok, lets get to the point, in our excercise I will be focused on the Continue reading
Last week, I presented MANRS to the IX.BR community. My presentation was part of a bigger theme – the launch of an ambitious program in Brazil to make the Internet safer.
While there are many threats to the Internet that must be mitigated, one common point and a challenge for many of them is that the efficacy of the approaches relies on collaboration between independent and sometimes competing parties. And, therefore, finding ways to incentivize and reward such collaboration is at the core of the solutions.
MANRS tries to do that by increasing the transparency of a network operator’s security posture and its commitment to a more secure and resilient Internet. Subsequently, the operator can leverage its increased security posture, signaling it to potential customers and thus differentiating from their competitors.
MANRS also helps build a community of security-minded operators with a common purpose – an important factor that improves accountability, facilitates better peering relationships, and improves coordination in preventing and mitigating incidents.
I ran an interactive poll with four questions to provide a more quantitative answer. More than 100 people participated, which makes the results Continue reading
For the first two sessions of the Building Network Automation Solutions online course I got awesome guest speakers, and it seems we’ll have another fantastic lineup in the Spring 2018 course:
Most network automation solutions focus on device configuration based on user request – service creation or change of data model describing the network. Another very important but often ignored aspect is automatic response to external events, and that’s what David Gee will describe in his presentation.
Read more ...