Updates, clarifying what we mean by "local area network" which was too generic, hence just using the actual name is fine "The People's Open Network" which indeed is "(local)"

Also updated the Relay Node description, replacing "Virtual Private Network" with the term "Virtual Public Network" or VPuN, which has roots in GNUnet https://gnunet.org/gnunet-vpn and is situated in this historical piece http://www.isaca.org/Journal/Past-Issues/2001/Volume-3/Pages/Virtual-Private-Networking-Confidentiality-on-Public-Networks.aspx

I also updated the language to denote Relay Nodes as "Tunnel Server & Client" because this is accurate based on the software used on these servers, an IP tunnel package developed by WLAN-Slovenija folks: TunnelDigger.

While TunnelDigger technically qualifies as "Virtual Private Network" software (with a major lapse in not actually providing access control mechanisms as is the point of most VPN software), this label is actually more generic than what we need (see https://en.wikipedia.org/wiki/VPN#Unencrypted_tunnels), especially when there is a socially and historically situated alternative that is both more descriptive and mission-consistent with sudo mesh's work: Virtual Public Network (VPuN). 

So, who wants to write the Wikipedia article on Virtual Public Networks? ;)

Many thanks to Marc, Mitar, and everyone for drawing this out, I think we have a good labeling system and sufficient justification for all names.

Cheers!

// Matt


On Sun, Mar 23, 2014 at 11:14 PM, Matthew Senate <mattsenate@gmail.com> wrote:
I think everyone's comments have been helpful. Attached is an updated version of the diagram, though you can see that there are really only minor tweaks and not a major reorganization. I decided that for the purposes of this diagram, since the eye comes across it more or less from the top that the primary focal point should be the Local Area Network, even if emotionally we know it to be a bottom-up concept. Graphically, having the internet at the top doesn't come off as legible to me without other elements, say dirt, grass and such. The subtlety is that essentially, outside the LAN bubble of this diagram is the open space of other networks, namely including connections that go to and include the global internet.

I think what Chris points out is helpful too since we can basically shake this diagram from any particular node, in order to orient our view toward a particular topic, purpose, point of view, end user, developer, etc. However, that can take place in additional diagrams, and I really want this to be a basic reference. As for the end users, I completely agree and plan to make a diagram from the perspective of the home router, showing how traffic passes into and out of your home. I think the pair of these diagrams tells a whole story: how I fit in at home, and how the network functionally works on a fundamental level.

Any diagrams to explain the rest of the internet itself would be swell. Any links? This one is a bit much: https://upload.wikimedia.org/wikipedia/commons/b/bd/Internet_map_1024_-_transparent.png this one not enough: http://www.overthinkingit.com/wp-content/uploads/2008/11/tubes.jpg

// Matt


On Sat, Mar 22, 2014 at 7:45 PM, Marc Juul <juul@labitat.dk> wrote:
All of this up or down discussion doesn't make much sense to me.

Network diagrams are either completely abstract with no up or down, or
they relate to real-world topographies as seen from above, usually
with the top being North.

On Sat, Mar 22, 2014 at 5:58 PM, Chris Jefferies <chris@freeranger.com> wrote:
> That would be a simple top to bottom flip of the image, right?
>
> Another way to imagine it would be that the home (the individual) is at the
> top.  Each individual personal connection is at the top and below it is all
> the infrastructure.
>
> The node near my house is in the sky, but as soon as it connects to the
> internet it's going underground in fiber tubes buried next to the highways
> that criss-cross the nation and the world.
>
> I suppose that in a pure wifi-mesh system, unconnected to the internet, it
> could be considered an air only, connected from above, system.
>
> However we look at it, I think it is important that we find a way to impart
> a meaningful, shared conceptual model of what we're building.  Only with a
> model that people can understand quickly and at a high level will it get
> traction.  We don't want to mislead or pander only to the lowest common
> denominator but we want it to be right sized, if you will, to our goal of
> educating the public.
>
> I think, that when we are looking for the balance of high level abstractions
> to low level technical details, that we should ere a bit on the side of
> technical.  I know I get frustrated with descriptions of technology that use
> a false abstraction in an attempt to make a challenging idea accessible to
> those who are unfamiliar with those ideas.
>
> My 4c...  ;)
>
>
>
> --
> Chris Jefferies
> (510) 409-0003 - mobile
>
>
>
> On Sat, Mar 22, 2014 at 11:42 AM, Jenny Ryan <tunabananas@gmail.com> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Fri 21 Mar 2014 09:43:30 PM PDT, Somebody wrote:
>> > In my mind see the Mesh Network come from ground up, from the home's
>> > walls and roofs showering the streets and then taking off to the sky.
>> >
>> > Well, that is how my mind sees the Mesh. :)
>> >
>>
>> <3 Gotta concur with somebody, here :)
>> from the bottom up!
>>
>> Jenny
>> http://jennyryan.net
>> http://sudomesh.org
>> http://thevirtualcampfire.org
>> http://technomadic.tumblr.com
>>
>> `~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
>> "Technology is the campfire around which we tell our stories."
>> - -Laurie Anderson
>>
>> "Storytelling reveals meaning without committing the error of defining
>> it."
>>  -Hannah Arendt
>>
>> "To define is to kill. To suggest is to create."
>> - -Stéphane Mallarmé
>> ~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.14 (GNU/Linux)
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iQEcBAEBAgAGBQJTLdmOAAoJEHTWWpBUSeDhIcQH/idtsQ4X5c7fIO+HW8A6Nw80
>> QRWVOluP/lRVJaKMIqOchUq9uem4V92e7sNswHJjOF8OMGfJhssNk0V0BSgCkWAW
>> ddVhI0iK4YQS+I1zCpEFGr/rOw5VuRXxQLGZUv344923/qsEdOwOyg45yZXN8l6O
>> SgOteIWC5YIWXmXIitwpYbNXelLtcFzmpW1I3O3NV46EEllrXwgEBBSIIbT5/Amg
>> 3JHRNkYnzTa3BG45asYbqgQvag5lciwDDH5Okb/jrjMoAvRri/9NuHfGLDEG3gvt
>> X/JfhBcjHhFL5Pmg4eoAKWP9zcDykkcXuzoV6ndK8oPUC2HrToRSH0NvFexQwRI=
>> =rgYV
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> mesh mailing list
>> mesh@lists.sudoroom.org
>> https://lists.sudoroom.org/listinfo/mesh
>
>
>
> _______________________________________________
> mesh mailing list
> mesh@lists.sudoroom.org
> https://lists.sudoroom.org/listinfo/mesh
>
_______________________________________________
mesh mailing list
mesh@lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh