In 1974 a specification was developed that would, eventually, launch what we
know of as "The Internet." That specification was TCP and though it is often
overshadowed by HTTP as the spark that lit the fire under the Internet,
without TCP HTTP wouldn't have a (transport) leg to stand on.
Still, it would take 10 years before the Internet (all 1000 hosts of it)
converted en masse to using TCP/IP for its messaging. Once that adoption had
occurred, it was a much shorter leap for the development of HTTP to occur and
then, well, your refrigerator or toaster can probably tell you the rest at
That makes TCP 40 years old this year. And despite the old adage you can't
teach an old dog new tricks, TCP has continued to evolve right along with the
needs of the applications that rely so heavily on its reliable transport
Consider the additions, modifications... (more)
It's that time of the year, when resolutions promising grand changes in our
lives are made - and more often than we'd like to admit, broken. Along with
the resolutions comes advice on how to make them "stick." In other words, how
to make them habitual.
Many folks still cite the old "21 days to form a habit" wisdom that has, in
more recent research, been proven to be less than accurate. Turns out it
takes longer than that for most people, with only a few actually able to form
a habit that quickly. Unless it's something bad for us*. Then it seems to
become a habit in under 2 days.... (more)
Pundits, owing to SDN still being very young and not widely adopted, continue
to put forth treatise upon treatise as to why organizations should be falling
over themselves to go out and get themselves some SDN. Now. Not tomorrow,
One of the compelling reasons to adopt is to address a variety of operational
issues that arise from complexity and differentiation in network elements.
The way SDN addresses this - as do a variety of other options - is
standardization. Note this is standardization with a little "s", not the
capital "S" that might imply industry-agreed-upon-and-g... (more)
The original RFC for TCP (793) was written in September of 1981. Let's pause
for a moment and reflect on that date.
When TCP was introduced applications on "smart" devices was relegated to
science fiction and the use of the Internet by your average consumer was
still more than two decades away.
Yet TCP remains, like IP, uncontested as "the" transport protocol of ...
New application architectures, networks, and devices all introduce challenges
with respect to how TCP behaves. Over the years it's become necessary to
tweak the protocol with new algorithms designed to ad... (more)
A lot of security-minded folks immediately pack up their bags and go home
when you start talking about automating anything in the security
infrastructure. Automating changes to data center firewalls, for example,
seem to elicit a reaction akin not unlike that to a suggestion to putting an
unpatched Windows machine directly on the public Internet.
At RSA yesterday I happened to see a variety of booths with a focus on ..
.logs. That isn't surprising as log analysis is used across the data center
and across domains for a variety of reasons. It's one of the ways databases
are replic... (more)