Worth Reading: Email optimization

In Part 1 of this series, we introduced the problem of email volume optimization. We showed that on the one hand, email is among the principal drivers of engagement, but on the other hand, excessive email volume results in increased negative responses such as members unsubscribing from an email type or reporting emails as spam. We discussed an approach for email volume optimization that minimizes email volume while maximizing downstream sessions and minimizing the number of member complaints (unsubscribes and spam reports). In this post, we’ll discuss our learnings from this approach and describe our new, improved approach that has resulted. —LinkedIn Engineering Blog

The post Worth Reading: Email optimization appeared first on 'net work.

In Flight

The post In Flight appeared first on 'net work.

Worth Reading: NTP is still a security risk

The Network Time Protocol (NTP) has been in the news a number of times over the past couple of years because of attacks on the protocol, vulnerabilities in the daemon, and the use of NTP in DDoS attacks. In each case, the developers of NTP have responded quickly with fixes or recommendations for remediating these attacks. Additionally, the development team has continued to look ahead and has worked to enhance the security of NTP. —CircleID

The post Worth Reading: NTP is still a security risk appeared first on 'net work.

Worth Reading: Living in an age of cyber extortion

One of the most famous examples of DDoS attacks used for extortion was attributed to an attacker using the moniker “DD4BC,” which stands for “DDoS for Bitcoin.” ASERT wrote about this in June. Due to DD4BC’s success copy cats emerged and these types of attacks spread quickly around the world. In fact, there have been stories reported of “copy cats of copy cats,” simply threatening to launch DDoS attacks in exchange for bitcoin – even though they had no such botnet at their disposal. —Arbor

The post Worth Reading: Living in an age of cyber extortion appeared first on 'net work.

Worth Reading: Physics and distributed systems

If you squint hard enough, many of the challenges of distributed computing appear similar to the work done by the great physicists. Dang, those fellows were smart! Here, we examine some of the most important physics breakthroughs and draw some whimsical parallels to phenomena in the world of computing… just for fun. —ACM Queue

The post Worth Reading: Physics and distributed systems appeared first on 'net work.

Worth Reading: Hacking wireless keyboards

You should be able to trust your wireless keyboard. And yet security researchers have been warning people to be suspicious of wireless computer accessories using sketchy radio protocols for years. Those warnings peaked five months ago, when hackers at the security firm Bastille found that millions of cheap keyboard and mouse dongles let hackers inject keystrokes onto your machine from hundreds of yards away. Now, in case you missed that message, the same researchers have extended their attack to millions more devices—and this time, they can not only inject keystrokes, but also read yours, too. —Wired

The post Worth Reading: Hacking wireless keyboards appeared first on 'net work.

DC Fabric Segment Routing Use Case (3)

In the second post in this series, we considered the use of IGP-Prefix segments to carry a flow along a specific path in a data center fabric. Specifically, we looked at pulling the green flow in this diagram—

—along the path [A,F,G,D,E]. Let’s assume this single flow is an elephant flow that we’re trying to separate out from the rest of the traffic crossing the fabric. So—we’ve pulled the elephant flow onto its own path, but this still leaves other flows to simple ECMP forwarding through the fabric. This means some number of other flows are still going to follow the [A,F,G,D,E] path. The flows that are randomly selected (or selected by the ECMP has) to follow the same path as the elephant flow are still going to contend with the elephant flow for queue space, etc.

So we need more than just a way to pull an elephant flow onto a specific path. In fact, we also need a way to pull a specific set of flows off a particular path in the ECMP set. Returning to our diagram, assume we want all the traffic other than the elephant flow to be load shared between H and B, and Continue reading

Worth Reading: Exploiting man in the middle against HTTPS

A key guarantee provided by HTTPS encryption is that the addresses of visited websites aren’t visible to attackers who may be monitoring an end user’s network traffic. Now, researchers have devised an attack that breaks this protection. The attack can be carried out by operators of just about any type of network, including public Wi-Fi networks, which arguably are the places where Web surfers need HTTPS the most. It works by abusing a feature known as WPAD—short for Web Proxy Autodisovery—in a way that exposes certain browser requests to attacker-controlled code. —ARS Technica

The post Worth Reading: Exploiting man in the middle against HTTPS appeared first on 'net work.

Worth reading: The making of algorithm markets

Algorithmia’s approach is to containerize algorithms, packaging them as microservices and hosting on their scalable and serverless cloud infrastructure, and which are called up through their API, via a few lines of code. … Since the company’s launch in 2013, it has amassed over 2,200 algorithms from 19,000 authors — some of them hailing from the finest research universities in the world — in its online libraries. —New Stack

The post Worth reading: The making of algorithm markets appeared first on 'net work.

Reaction: Standardization versus Innovation

Should the Docker container image format be completely standardized? Or should Docker not be held back from evolving the format ahead of the open specification? This was the topic of a heated Twitter tussle last week between Google evangelist Kelsey Hightower and the creator of the Docker itself, Solomon Hykes. —New Stack

What is at stake here is the standardization versus innovation. Should Docker standardize their container technology or not?

On the one side is the belief that standardizing squashes innovation. Once you’ve standardized something, and other people start building on it, you can’t change the standard without a lot of agreement and effort—after all, other people are now depending on your product remaining the same across many cycles of development. This certainly kills innovation, as implementing new things both exposes your ideas to public view before you can implement them, and slows down the pace at which new ideas can be deployed in the real world.

On the other side is the belief that standardizing is necessary for the market to mature, and for a healthy ecosystem to develop that’s better for the entire community. How can customers and other vendors build products around a particular product if the Continue reading

Worth Reading: Routing Area Director’s thoughts on IETF Berlin

Kicking off IETF 96 in Berlin, Germany was the weekend’s IETF Hackathon. There is growing engagement between the Open Source communities and the IETF. The IETF Hackathon had more participants than ever and we experimented with having a place for it in the IETF Lounge all week. —IETF

The post Worth Reading: Routing Area Director’s thoughts on IETF Berlin appeared first on 'net work.

Worth Reading: The geeks guide to the Barton Aquaduct

The Grade II-listed Barton Swing Aqueduct in Salford was built to solve the knotty problem of how to get the Bridgewater Canal across the proposed Manchester Ship Canal. And bar some routine maintenance, the odd lick of paint and a change of power source from steam to electricity, it has been doing the same job on a daily basis for over 120 years. What makes the Barton Aqueduct even more interesting is that not only was it the first swing aqueduct to be built but it was also the last. To this day it is unique. And not just in the UK. Scour the globe and you’ll not find another one. —the Register

The post Worth Reading: The geeks guide to the Barton Aquaduct appeared first on 'net work.

snaproute Go BGP Code Dive (7): Moving to Connect

In last week’s post, we looked at how snaproute’s implementation of BGP in Go moves into trying to connect to a new peer—we chased down the connectRetryTimer to see what it does, but we didn’t fully work through what the code does when actually moving to connect. To jump back into the code, this is where we stopped—

func (st *ConnectState) processEvent(event BGPFSMEvent, data interface{}) {
  switch event {
  ....
    case BGPEventConnRetryTimerExp:
      st.fsm.StopConnToPeer()
      st.fsm.StartConnectRetryTimer()
      st.fsm.InitiateConnToPeer()
....

When the connectRetryTimer timer expires, it is not only restarted, but a new connection to the peer is attempted through st.fsm.InitiateConnToPeer(). This, then, is the next stop on the road to figuring out how this implementation of BGP brings up a peer. Before we get there, though, there’s an oddity here that needs to be addressed. If you look through the BGP FSM code, you will only find this call to initiate a connection to a peer in a few places. There is this call, and then one other call, here—

func (st *ConnectState) enter() {
  ....
  st.fsm.AcceptPeerConn()
  st.fsm.InitiateConnToPeer()
}

The rest of the instances of InitiateConnToPeer() are related to the definition of the function. Continue reading

Worth Reading: The languages that almost became CSS

When HTML was announced by Tim Berners-Lee in 1991 there was no method of styling pages. How given HTML tags were rendered was determined by the browser, often with significant input from the user’s preferences. It seemed, however, like a good idea to create a standard way for pages to ‘suggest’ how they might prefer to be rendered stylistically. —Eager

The post Worth Reading: The languages that almost became CSS appeared first on 'net work.

Worth Reading: Top performance items to watch

What’s eating your network? What is (quietly) killing performance? What performance items should you be watching, but probably are not? I’m a big fan of appropriate network management data, with the right tool(s). If you don’t monitor absolutely every interface, and capture historical data, you’re flying blind. —Netcraftsmen

The post Worth Reading: Top performance items to watch appeared first on 'net work.

Buenos Aires

The post Buenos Aires appeared first on 'net work.

Worth Reading: Hot Commodities

A Booz Allen Hamilton Industrial Cybersecurity Threat Briefing reports that cyber incidents targeting Integrated Control Systems (ICS), like the ones used to run the nation’s electric grid, reached an all-time high in 2015. The briefing also predicted that the number of these incidents will likely continue to increase, and cited nation-state backed groups as a key threat. —Lawfare

The post Worth Reading: Hot Commodities appeared first on 'net work.

Worth Reading: Real world security and the Internet of Things

Right now, the only way to patch most home routers is to throw them away and buy new ones. And the security that comes from replacing your computer and phone every few years won’t work with your refrigerator and thermostat: on the average, you replace the former every 15 years, and the latter approximately never. A recent Princeton survey found 500,000 insecure devices on the Internet. That number is about to explode. —Schneier on Security

The post Worth Reading: Real world security and the Internet of Things appeared first on 'net work.

On the ‘net: The future of networking

Lately I have been thinking a lot about the future of networking and the career paths in this domain. As you probably know I like to guide and mentor people and with everything going on in the industry it can be confusing to find your way and to know what skills to work on to stay ahead of the curve. —Lost in Transit

The post On the ‘net: The future of networking appeared first on 'net work.

Worth Reading: Ten years of Cisco Live

Technology changes every day. We change from hardware to software and back again. Routers give way to switches. Fabrics rise. Analytics tell all. But all this technology still has people behind it. Those people make the difference. People learn and grow and change. They figure out how to make SDN work today after learning ISDN and Frame Relay yesterday. They have the power to expand beyond their station and be truly amazing. —Networking Nerd

The post Worth Reading: Ten years of Cisco Live appeared first on 'net work.