From: Matthias Tafelmeier <matthias.tafelmeier@gmx.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] DC behaviors today
Date: Tue, 19 Dec 2017 18:55:18 +0100 [thread overview]
Message-ID: <614a9a1f-67a9-de9c-d906-589bb84eab4d@gmx.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1712180848460.8884@uplift.swm.pp.se>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 3334 bytes --]
>
>> What I actually wanted to posit in relation to that is that one could
>> get sooner a c-cabable backbone sibling by marrying two ideas: the
>> airborne concept ongoing as outlined plus what NASA is planning to
>> bring about for the space backbone, e.g [1][2]. It's laser based
>> instead of directed radio-wave only. Sure, both is in the speed range
>> of c, apparantely, laser transmission has in addition a significantly
>> higher bandwidth to offer. "10 to 100 times as much data at a time as
>> radio-frequency systems"[3]. Attenuations to photons in clean
>> atmospheric air are neglible (few mps - refractive index of about
>> 1.0003), so actually a neglible slowdown - easily competing with top
>> notch fibres (99.7% the vacuum speed of light). Sure, that's the
>> ideal case, though, if cleverly done from the procurement of
>> platforms and overall system steering perspective, might feasible.
>
> Todays laser links are in the few km per hop range, with is easily at
> least one magnitude shorter than radio based equivalents.
>
Hold on! This is a severe oversimplifcation, isn' it. The devices you're
probably referring to are in the low-end segment, dillentically and
maybe terrestrially operated only - to mention a few limiting factor
conceivable possibly being perceived.
Certainly, there are range limiting factors when fully submerged in the
near-ground atmospheric ranges. E.g. in the darkest snow storm, one
cannot expect optics to be reliablly working - admitting that.
Nothwithstanding, recent research[1] showed astounding achievements of
FSOs even in harsh atmospheric conditions - "up to 10 gigabits per
second" while in vivid movement, in heavy fog ... for a single pathed laser.
90% mass of the atmosphere is below 16 km (52,000 ft), therefore also
most of it's randomness[2]. Meaning, one only had to surpass this
distance to more decently unfold the capabilities of an airborne
backbone. Therefore, a hierarchy of airborne vessels might be necessary.
Might smaller, more numerous ones gatewaying the optics out of the dense
parts of the atmosphere to the actual backbone-net borne lasers, might
by doing this relaying not laser beam based. Far more mitigation
techniques are conceivable. From there on, the shortcomings appear
controllable.
> I don't know the physics behind it, but people who have better insight
> than I do tell me "it's hard" to run longer hops (if one wants any
> kind of high bitrate).
If one looks up what is achievable in space, where the conditions
shouldn't be too different from earth atmosphere over 16 km. Thousands
of kilometres for a single hop, single path. Now imagine a decent degree
of multipathing.
Physical intricacies are certainly a headache in this topic, though
shouldn't be decisive, I'd dare to categorize the largest complexity
compartment of such a system into the algorithmics for steering,
converging or stabilizing the airborne components, directing the optics
problerly and in time. The overall automatic or even autonomic
operations to abstract it.
Probably, me forming some papers wrapping this up would be worthwile.
[1]https://phys.org/news/2017-08-high-bandwidth-capability-ships.html
[2]https://arxiv.org/pdf/1705.10630.pdf
--
Besten Gruß
Matthias Tafelmeier
[-- Attachment #1.1.1.2: Type: text/html, Size: 4477 bytes --]
[-- Attachment #1.1.2: 0x8ADF343B.asc --]
[-- Type: application/pgp-keys, Size: 4806 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]
next prev parent reply other threads:[~2017-12-19 17:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw43M=dhPOFhMJo7f-qOq=k=kKS6ppq4o9=hsTEKoBdUpA@mail.gmail.com>
[not found] ` <92906bd8-7bad-945d-83c8-a2f9598aac2c@lackof.org>
[not found] ` <CAA93jw5pRMcZmZQmRwSi_1dETEjTHhmg2iJ3A-ijuOMi+mg4+Q@mail.gmail.com>
[not found] ` <CAKiAkGT54RPLQ4f1tzCj9wcW=mnK7+=uJfaotw9G+H_JEy_hqQ@mail.gmail.com>
2017-12-04 4:19 ` [Bloat] " Dave Taht
2017-12-04 9:13 ` [Bloat] [Cerowrt-devel] " Mikael Abrahamsson
2017-12-04 9:31 ` Joel Wirāmu Pauling
2017-12-04 10:18 ` Mikael Abrahamsson
2017-12-04 10:27 ` Joel Wirāmu Pauling
2017-12-04 10:43 ` Pedro Tumusok
2017-12-04 10:47 ` Joel Wirāmu Pauling
2017-12-04 10:57 ` Pedro Tumusok
2017-12-04 10:59 ` Joel Wirāmu Pauling
2017-12-04 12:44 ` Mikael Abrahamsson
2017-12-04 19:59 ` dpreed
2017-12-04 20:29 ` David Collier-Brown
2017-12-08 7:05 ` Mikael Abrahamsson
2017-12-12 15:09 ` Luca Muscariello
2017-12-12 18:36 ` Dave Taht
2017-12-12 22:53 ` dpreed
2017-12-12 23:20 ` Jonathan Morton
2017-12-13 10:20 ` Mikael Abrahamsson
2017-12-13 10:45 ` Luca Muscariello
2017-12-13 15:26 ` Neil Davies
2017-12-13 16:41 ` Jonathan Morton
2017-12-13 18:08 ` dpreed
2017-12-13 19:55 ` Neil Davies
2017-12-13 21:06 ` Jonathan Morton
2017-12-14 8:22 ` Mikael Abrahamsson
2017-12-17 21:37 ` Benjamin Cronce
2017-12-18 8:11 ` Mikael Abrahamsson
2017-12-17 11:52 ` Matthias Tafelmeier
2017-12-18 7:50 ` Mikael Abrahamsson
2017-12-19 17:55 ` Matthias Tafelmeier [this message]
2017-12-27 15:15 ` Matthias Tafelmeier
2018-01-20 11:55 ` Joel Wirāmu Pauling
2017-12-04 12:41 ` Mikael Abrahamsson
2017-12-04 10:56 ` [Bloat] Linux network is damn fast, need more use XDP (Was: DC behaviors today) Jesper Dangaard Brouer
2017-12-04 17:00 ` Dave Taht
2017-12-04 20:49 ` Joel Wirāmu Pauling
2017-12-07 8:43 ` Jesper Dangaard Brouer
2017-12-07 8:49 ` Jesper Dangaard Brouer
2017-12-04 17:19 ` Matthias Tafelmeier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=614a9a1f-67a9-de9c-d906-589bb84eab4d@gmx.net \
--to=matthias.tafelmeier@gmx.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox