…are better at building TCP stacks than we are. i came across the track of an interesting project - RemyCC, providing greater efficiency and at the same time a better division and lower delays (on average). it is worth to look.
for a moment, let’s assume those are rumblings of man worn out by pulling couple of all-nighters in one row. we have to assume that security intelligence services will want to listen to everything and everywhere. that includes NSA sniffing all traffic in major interconnection points at largest service providers. and, obviously - we don’t like it. why we can’t get back to original idea, that all point to point communication should be protected by IPsec (ALL COMMUNICATION). widely deployed IPv6 with devices that will support it makes this possible. the fact that nowadays even small devices can encrypt traffic at very high speeds helps. one of the less known IPsec discussions before standarization, was idea that nodes using IPsec should constantly generate traffic - but not exceeding available link bandwidth (to avoid buffer bloat). service providers generally removed data caps (apart from mobile operators - which may change after migration to LTE). our sniffers can’t record all of this traffic, and decrypting IPsec traffic is unfeasible to say the least. you can’t also selectively record, as all is encrypted. will intelligence agencies have money and power to break AES? well, not now, but let’s say it will be possible in near future. but your idle device is anyway generating gigabytes of random connections to fill up the link (of course there’s question of how analytics and statistical traffic monitoring can help select only interesting pairs, but given programmers invention i bet it’s doable with some level of effort). ...
i’ve stumbled upon an article of Michael Leonard from Juniper. he decided to take a stab at LISP. i usually call such articles with the title of this post, and the article mentioned is all about it. while we’re discussing in open forums with engineers and architects from Juniper, and in most of them we actually do cooperate - including in LISP, which author doesn’t seem to even know about - it’s sad to look at people who believe attacking competition is everything they should do in life. his comments are misguided, and willingness to be visible sad. it also doesn’t show juniper as a company in good light. ...
amazing sweet photo. you can watch this until you drop dead, looking for all details. and this landscape in the background…
very interesting experiment (it’s worth looking other from the series!). it basically shows how people react to very tricky move while walking freely on the street. i bet in Poland the behavior observed would be different… or maybe i’m wrong? will you try? :) (by the way, can you point to movie from which title of this post comes from without looking at google?)
i highly recommend this article from Wired. while we have to live with situation where such wealthy people like Kaspersky himself can influence ITU decisions, we still can stand up and work to make internet free and independent. it’s kind of naive of course, but consequences of having too much money and power - frighten me again every day.
using our new blogging platform, i just published short piece about just announced onePK. i’m watching live discussions for over two years now about network control capabilities. i was one of those distanced guys when it comes to OpenFlow “explosion” in popularity. and as time did show - I was right. today even hardware vendors suddenly slowed down a bit and distance themselves from new standard versions, and development tempo also falls down. more and more of these that believed supporting OpenFlow will suddenly change their support model and feature set - start to understand thats hardly true. some of them even decided to abandon this direction altogether. ...
there’s a lot of wisdom in books, presentations and trainings covering “how to achieve success” (however we choose to define it). this can be applied to working with people, managing them - or companies. one of great books helps reader achieve the success by simply structuring it in a simple, three-step program: decide what you want to achieve prepare plan, that will help you achieving what you want execute the plan simple, isn’t it? what’s really interesting, it’s actually that easy. but people tend to get lost very quickly around point number 2, and spend most of their lives around number 1. ...
FreeBSD 9.0 did an unannounced appearance lately. it introduces a bunch of different features, two of which are of great interest to me. firstly, we can select different mechanisms to fight traffic congestion for TCP. to do that, you need to change sysctl net.inet.tcp.cc.algorithm from the list available under net.inet.tcp.cc.available. NewRENO, the default one, works quite OK, but in some specific configurations you can select others and check if they’d behave better. ...
there’s a lot of discussions around the net neutrality, as obviously the subject is currently still pretty hot. from the one side we have enormous amount of money from advertising business, spend in interesting, devious and - tempting way. from the other side, we have the ideal information society, in which all information are free from filtering, and available for all willing to read. we point to China, Iran or Saudi Arabia as bad examples, filtering all that their citizens can view using the Internet - but we all use google. the same Google, that for the two PCs, depending on their source IP, browser, operating system - and what’s more interesting - depending on your cookies and your google profile (you logged off, right?) - show different answers for the same query. personalization? but using your own money, dear internet user :) i highly recommend reading this book, and before it arrives, read this and this. ...