From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 60EFD3B29E for ; Tue, 26 Oct 2021 13:51:54 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 1967E1801E; Tue, 26 Oct 2021 13:52:56 -0400 (EDT) Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27AvqZ8p_sId; Tue, 26 Oct 2021 13:52:55 -0400 (EDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0F3121800D; Tue, 26 Oct 2021 13:52:55 -0400 (EDT) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B945E112B; Tue, 26 Oct 2021 13:51:51 -0400 (EDT) From: Michael Richardson To: Mike Puchol , starlink@lists.bufferbloat.net, Dave Taht , Mark Handley In-Reply-To: References: X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Subject: Re: [Starlink] thinking about the laser links again X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2021 17:51:54 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mike Puchol wrote: > I could bore you to death but here=E2=80=99s a quick test you can do:= grab a > laser pointer and try to keep it on a target the size of the laser dot > on a wall 10-15 meters away. You=E2=80=99ll quickly see why doing tha= t at I fail, because the cat attacks me :-) (our cats somehow know when we get the laser pointers out, even if the batteries are dead...) > The logical thing to start with would be to keep every shell > interconnected, but not to try to cross-link shells. For this, > ground-to-satellite links come into play. Or they could interconnect using microwaves, couldn't they? It's all just different parts of the EM spectrum after all :-) > How do you make capacities in the petabits per second around your spa= ce > segment useful? You need to deliver to the ground eventually. IMHO the > only way this will hapen is ground-to-satellite links, with the ground > stations either in a few, as cloudless as possible locations, or many > stations in as geographically diverse configuration as possible, so > that at least some will not have cloud cover. > Once you have the ground links to each shell, they can be used to > offload to internet backbones, or you can relay data between shells, > without complicating your pointing & tracking on the satellites. What about going the other way? Interconnect via GEO? Or something resonant to the earth that is not quite so far? > Mark Handley makes a very good job at explaining in this video (and > others he has posted):=C2=A0https://www.youtube.com/watch?v=3DQEIUdMi= ColU Thnk you for the link. =2D- ] Never tell me the odds! | ipv6 mesh network= s [ ] Michael Richardson, Sandelman Software Works | IoT architect = [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails = [ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmF4QDcACgkQgItw+93Q 3WVTqAgAqwJpvOvxB3ER515Tkpe0wLWtzxkXn0xsp/4Hkw+hEHYFTeFPwOU6Bp8q v0mKTciD291SEfmz3JMnoiv7XygL5ikYiFuaMJK37cyuq2eMBFR/Z1YbgnP6DxN4 IGtqsOR5FsZJ1D5tzWYojvC93cfbaFyGFYj5niMirFq86IfAVE5T1KhiMjOqkyhA U0RADS41DWkP3Jvulauo/nEcO2zniJ+S5AYqtW4tUQvn6JAnZjQZeGNAZTgf/0Ia fdcfHeceDGZYtNyLyL0eEiFiyPQaHn0thXZCNKwFX+nzixS7FvY3NgMVfrywPv9i ui/ngaFSj/syN50rxn4ZsKVpiZEf4w== =fZgL -----END PGP SIGNATURE----- --=-=-=--