Re: The Troubling Truth of Why It’s Still So Hard to Share Files Directly

[Note:  This comment comes from friend Bob Frankston.  DLH]

From: “Bob Frankston” <Bob19-0501@bobf.frankston.com>
Subject: RE: [Dewayne-Net] Re: The Troubling Truth of Why It’s Still So Hard to Share Files Directly
Date: June 28, 2014 at 23:08:50 EDT
To: dewayne@warpspeed.com

Let’s not blame the NATs — they are only symptoms.  We could’ve made them
V4/V6 routers long ago but instead of V6 from the edge we get V6 from them
middle which isn’t in the spirit of peer connectivity. 

Given that we’ve had Bit Torrent and Jabber and now BT Sync the question is
why are new services like DropBox so centralized? One reason is economic —
central dependencies can be monetized.

Another is that today’s Internet protocols don’t honor the end-to-end
principle in that you have to get your address from a centralized provider.
In that sense the Internet may have been designed to be peer-to-peer but it
wasn’t engineered for stable peer relationships without a third party in the
guise of an address provider and a name=>address mapper (/etc., DNS). 

We also route through a backbone. NATs are just the third layer: Backbone,
Local, Localer. We shouldn’t have layers — any subset of connectivity
should be perfectly valid with stable addresses and stable relationships.
Thanks to the backbone assumption if you’re on a plane, for example,
adjacent machines may not be able to connect unless you have a connection to
a ground-based server. 

The NATs do cause a problem — not as much because of address translation
but because we’ve gotten to depend on them as security perimeters and rather
than addressing the trust (security) issues of peer connectivity we rely on
awkwardness for security. We’ve accepted the idea that there are separate
physical networks rather than common connectivity.

We locked down Wi-Fi because of the dependence on perimeter security though
the copyright lobby does compound the problem by further limiting sharing
infrastructure outside the security perimeter.

Instead of talking about connectivity as a general concept we have separate
connectivity domains for the Internet, Bluetooth, 3G, Zigbee etc. etc. That
only adds to the problem.

So the answer to why is it hard — because just as another post cites the
Supreme Court Justices are prisoners of bad analogies — too many of the
stewards of today’s Internet accept bad analogies such as the Internet as a
network of networks. Twisting winding peering networks at that. 

Just wait for the first generation of IoT silos …

From: Michael Cheponis <michael.cheponis@gmail.com>
Subject: Fwd: [Dewayne-Net] The Troubling Truth of Why It’s Still So Hard to
Share Files Directly
Date: June 27, 2014 at 13:04:30 EDT
To: Dewayne Hendricks <wa8dzp@gmail.com>

Isn’t this called ‘sftp’ ?

The REAL problem is natting — by not having REAL, routable, IP addresses,
we’re forced to deal with any manner of firewalls or more.

The net was *designed* to permit & encourage ‘peer-to-peer’.  Oh, how far
we’ve fallen.

The Troubling Truth of Why It’s Still So Hard to Share Files Directly
By PARKER HIGGINS
Jun 27 2014
<http://www.wired.com/2014/06/the-troubling-truth-of-why-its-still-so-hard-t
o-share-files-directly/>

Comments closed.

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s