Article development led by
some benefit from the work done—to
tune the bandwidth and round-trip
time estimators—that will exist in the
nodes sending and receiving the data.
Your network is point-to-point,
which means you do not think you
care about routing. But unless all the
work is always going to be carried out
at one or the other end of this link,
you are eventually going to have to
worry about addressing and routing.
It turns out that someone thought
The company I work for has decided to use a wireless network link
to reduce latency, at least when the
weather between the stations is good.
It seems to me that for transmission
over lossy wireless links we will want
our own transport protocol that sits
directly on top of whatever the radio
provides, instead of wasting bits on IP
and TCP or UDP headers, which, for a
point-to-point network, are not really
I completely agree that the best way
to roll out a new networking service
is to ignore 30 years of research in the
area. Good luck.
Second only to operating system
developers—all of whom want to rewrite the scheduler (see “Bugs and
Bragging Rights,” second letter, at
http://bit.ly/1yGXHV9)—are the networking engineers and developers
who want to write their own protocol.
“If only we could go at it with a clean
sheet of paper, we could do so much
better than the ARPANET, since that
was designed for old, crappy hardware, and ours is shiny and new.”
That statement is both true and false,
and you had better be damned sure
about which side of the Boolean logic
your idea lies before you write a single
line of new code.
The Internet protocols are not the
be all and end all of networking, but
they have had more research and test-
ing time applied to them than any
other network protocols currently in
existence. You say you are building a
wireless network with—I am sure—
the highest-quality gear you can buy.
Wireless networks are notoriously
lossy, at least in comparison to wired
networks. And it turns out there has
been a lot of research done on TCP in
lossy environments. So although you
will pay an extra 40 bytes per packet to
transport data over TCP, you might get
Relevance and repeatability.