From: Hal Murray <hmurray@megapathdsl.net>
To: bloat@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Cc: hmurray@megapathdsl.net
Subject: [Cerowrt-devel] Fiber bandwidth vs distance
Date: Tue, 19 Dec 2017 04:45:20 -0800 [thread overview]
Message-ID: <20171219124520.16C4340605C@ip-64-139-1-69.sjc.megapath.net> (raw)
> 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).
The buzzword is dispersion. The speed of the photon varies slightly with
color. All the photons in a pulse are not the same color. The farther they
go, the more they spread out. If they spread out far enough, they overlap
neighboring bits and the receiver can't sort things out.
You would like all the photons in a pulse to be the same color. Lasers are
close. Just not close enough.
The dimension of quality for fibers used to be megabit*miles. (actually
megabits/second) That probably assumed a specific bandwidth of the light.
For a given transmitter, you could go X miles at Y bits/sec, or 2*X at Y/2...
Sample data sheet:
https://www.corning.com/media/worldwide/coc/documents/Fiber/SMF-28%20Ultra.p
df
Dispersion is the next to bottom section on the right of the first page.
> Todays laser links are in the few km per hop range, with is easily at least
> one magnitude shorter than radio based equivalents.
What's the bandwidth of those radio links?
--
These are my opinions. I hate spam.
reply other threads:[~2017-12-19 12:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171219124520.16C4340605C@ip-64-139-1-69.sjc.megapath.net \
--to=hmurray@megapathdsl.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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