Jacoba Urist @ The Atlantic No Taxes, No Travel: Why the IRS Wants the Right to Seize Your Passport:
“It all started last fall, when Senator Barbara Boxer introduced the “Moving Ahead for Progress in the 21st Century Act” (or “MAP-21” as it’s now called), to reauthorize funds for federal highway and transportation programs. While that doesn’t sound like anything having to do with your taxes, the bill includes a little-noticed section that allows the State Department to “deny, revoke or limit” passport rights for any taxpayers with “serious delinquencies.”
Here’s how it would work. If someone owed more than $50,000 in back taxes, the IRS would be able to send their name over to the passport office for suspension, provided that the IRS already either filed a public lien or a assessed a levy for the outstanding balance. The bill does provide a few exceptions though. For example, if a person has set up a payment plan (that they’re paying in a timely manner), is legitimately disputing the debt, or has an emergency situation or humanitarian reason and must travel internationally, they may be able to leave for a limited time despite their unpaid taxes.”
Stephen Levy @ Wired: Going With the Flow: Google’s Secret Switch to the Next Wave of Networking:
“If any company has potential to change the networking game, it is Google. The company has essentially two huge networks: the one that connects users to Google services (Search, Gmail, YouTube, etc.) and another that connects Google data centers to each other. It makes sense to bifurcate the information that way because the data flow in each case has different characteristics and demand. The user network has a smooth flow, generally adopting a diurnal pattern as users in a geographic region work and sleep. The performance of the user network also has higher standards, as users will get impatient (or leave!) if services are slow. In the user-facing network you also need every packet to arrive intact — customers would be pretty unhappy if a key sentence in a document or e-mail was dropped.
The internal backbone, in contrast, has wild swings in demand — it is “bursty” rather than steady. Google is in control of scheduling internal traffic, but it faces difficulties in traffic engineering. Often Google has to move many petabytes of data (indexes of the entire web, millions of backup copies of user Gmail) from one place to another. When Google updates or creates a new service, it wants it available worldwide in a timely fashion — and it wants to be able to predict accurately how quickly the process will take.
“There’s a lot of data center to data center traffic that has different business priorities,” says Stephen Stuart, a Google distinguished engineer who specializes in infrastructure. “Figuring out the right thing to move out of the way so that more important traffic could go through was a challenge.”
But Google found an answer in OpenFlow, an open source system jointly devised by scientists at Stanford and the University of California at Berkeley. Adopting an approach known as Software Defined Networking (SDN), OpenFlow gives network operators a dramatically increased level of control by separating the two functions of networking equipment: packet switching and management. OpenFlow moves the control functions to servers, allowing for more complexity, efficiency and flexibility.”
Reuben Collins @ Streets.mn The Problem of Hiawatha Avenue