Author Archives: Russ
Author Archives: Russ
Over at ipspace.net, Ivan is discussing using DNS to program firewall rules—
Could you use DNS names to translate human-readable rules into packet filters? The traditional answer was “no, because I don’t trust DNS”.
This has been a pet peeve of mine for some years—particularly after my time at Verisign Labs, looking at the DNS system, and its interaction with the control plane, in some detail. I’m just going to say this simply and plainly; maybe someone, somewhere, will pay attention—
The Domain Name System is a part of the IP networking stack.
Network engineers and application developers seem to treat DNS as some sort of red-headed-stepchild; it’s best if we just hide it in some little corner someplace, and hope someone figures out how to make it work, but we’re not going to act like it should or will work. We’re just going to ignore it, and somehow hope it goes away so we don’t have to deal with it.
Let’s look at some of the wonderful ideas this we’ll just ignore DNS has brought us over the years, like, “let’s embed the IP address in the packet someplace so we know who we’re talking to,” and “we Continue reading
The post Worth Reading: Predictive Policing appeared first on 'net work.
The post Worth Reading Digital Monoculture appeared first on 'net work.
The post Worth Reading: Elliptic Curve Cryptography and DNS appeared first on 'net work.
The post Worth Reading: Stop Trying to Change Users appeared first on 'net work.
The post Worth Reading: Why Google Gadgets are so Cheap appeared first on 'net work.
In last week’s post, the new BGP peer we’re tracing through the snaproute BGP code moved from open to openconfirmed by receiving, and processing, the open
message. In processing the open message, the list of AFIs this peer will support was built, the hold timer set, and the hold timer started. The next step is to move to established. RFC 4271, around page 70, describes the process as—
If the local system receives a KEEPALIVE message (KeepAliveMsg (Event 26)), the local system:
- restarts the HoldTimer and
- changes its state to Established.
In response to any other event (Events 9, 12-13, 20, 27-28), the local system:
- sends a NOTIFICATION with a code of Finite State Machine Error,
- sets the ConnectRetryTimer to zero,
- releases all BGP resources,
- drops the TCP connection,
- increments the ConnectRetryCounter by 1,
- (optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and
- changes its state to Idle.
For a bit of review (because this is running so long, you might forget how the state machine works), the way the snaproute code is written is as a state machine. The way the state machine works is Continue reading
The post Worth Reading: Creating a PCE Prototype appeared first on 'net work.
The post Worth Reading: Three great lies of cloud computing appeared first on 'net work.
The post Worth Reading: The fall of Theranos appeared first on 'net work.
A short note reminding the gentle readers who wander in to this site of the riches of information available in the main menu to the left of this post…
rule 11 reader takes you to a subscription form for the mailing list. The format and frequency of the mailing list is a little messed up right now, and I always mean to do more with it, but never seem to get around to it.
sixty books takes you to a list of books I’ve found particularly helpful or useful over the years. The title isn’t the number of books, strictly speaking, but rather a challenge to read sixty books this year. Not all of these are related to network engineering.
worth visiting is something of a blog role and interesting sites, not all related to network engineering.
author page takes you to a page listing all of my works. Right now this is on Amazon, but as not all my works are available on Amazon, I need to fix this. Yes, it’s already on my list of things to do.
network icons is a set of icons I use in public presentations not tied to a company, etc. These are Continue reading
The post Worth Reading: a troubling new chapter for the ‘net appeared first on 'net work.
The post Worth Reading: The telco quality transformation appeared first on 'net work.
Warning, some philosophy may have unintentionally slipped into this post…
There are few things in life that ever really change; rather, we are held captive to what appears to be a surprisingly small set of rules that have lasted at least as long as writing seems to have been around, and—if the history of humanity described in writing is any guide—as long as humans have existed (regardless of your thoughts on that particular topic). One of them, for instance, is that there’s nothing truly new; take these few lines, for instance—
A generation goes, and a generation comes,
but the earth remains forever.
The sun rises, and the sun goes down,
and hastens to the place where it rises.
The wind blows to the south
and goes around to the north;
around and around goes the wind,
and on its circuits the wind returns.
All streams run to the sea,
but the sea is not full;
to the place where the streams flow,
there they flow again.
All things are full of weariness;
a man cannot utter it;
the eye is not satisfied with seeing,
nor the ear filled with hearing.
What has been is what will be,
and what Continue reading