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 412663B29E for ; Thu, 1 Sep 2022 15:54:19 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 74224181D2; Thu, 1 Sep 2022 16:14:50 -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 8qNpmwfTU1u3; Thu, 1 Sep 2022 16:14:49 -0400 (EDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id D0656181B1; Thu, 1 Sep 2022 16:14:49 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1662063289; bh=B+eOfa8PQZ3RySdcj3Y2WO3MEZv83NCpXgpGzOTwBIA=; h=From:To:Subject:In-Reply-To:References:Date:From; b=8VNL2O9t4qFMMkiOGLhorunFpREUF6+rP6V9ljjnDspI8+t3U1+aPKnt976litrC8 ORaXDlFpJbjaJLGx9f13cG8S0IkuK1lKfoCV996qSbIPotUTfHj5Rx4ZsDXVBI3bbj Ex9jBTuEPLEvRgec9K8oLS0r0C8FjhvQlLaIPgRO1jY2eRkf0oN+Dsku5zOJoOIg8s RDtFyUr0AqxcWVwO4ns9BzDt061Ob7OOl02xKER1CrO/RaMwuDX2pIaYBfDB4PWa3m K2hw4tNdQUfPbhEr/7MOwOkZm+RVphDQOcB/sgXIsET8olC4w9tgZvpfjaZ8ze0hu7 YhIoQUI3OLu8g== Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DBEAB7F7; Thu, 1 Sep 2022 15:54:17 -0400 (EDT) From: Michael Richardson To: Ulrich Speidel , starlink@lists.bufferbloat.net In-Reply-To: References: <1661878433.14064713@apps.rackspace.com> <6p5n9262-3745-pq31-5636-1rnon987o255@ynat.uz> <20220830220710.GA2653@sunf10.rd.bbc.co.uk> <15982a40-2b34-7ed1-bfa3-bced03fc3839@auckland.ac.nz> <9CE05D69-FC37-4C97-9D8D-D46B2DF6DE16@gmx.de> <2321be3b-957f-2d1f-c335-119c8e76efe5@auckland.ac.nz> <8978587-42op-q175-2o41-qq9p4491459s@ynat.uz> <56e56b0f-07bd-fe0c-9434-2663ae9d4404@auckland.ac.nz> <63B8B233-DF84-4D60-884F-8A83B3ED7607@gmx.de> X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.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] Starlink "beam spread" 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: Thu, 01 Sep 2022 19:54:19 -0000 --=-=-= Content-Type: text/plain Is there any orbit other than GEO that would make CDNs in space useful? While current Starlink don't have lasers that could reach up to higher orbits, maybe a subsequent generation could have such a thing. Maybe there could even be a standard which OneWeb/StarLink/??? could all agree to, and CDN satellites (with bigger solar panels and longer service lifetimes) could be built to. Having said all of this, it sure seems that the better place today for CDNs is within satellite serviced villages. Some may even remember the Internet Cache Protocol (ICP), which never really got anywhere (RFC2186). There are perhaps energy arguments for moving datacenters to space, but stuff just isn't reliable enough, and I'm sure it's a fail until you manufacture in space. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFFBAEBCgAvFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmMRDekRHG1jckBzYW5k ZWxtYW4uY2EACgkQgItw+93Q3WWgywgAvsM3hgWS/tkd5VUDOfxkOXDujsrCy0pX drFtSux/JVSygLmwPzGtQuP036fcHakHYbliv9vXk7dyFyVe69u9yz1uPJigtQoq 6x8Qe1uaXCPUwbczPz59LJTisOLdo2BBUVKa+zLRwSPS88ImDDNtTwQdsmjHHbIV DtqFfMT4reXvDbCM6QLfvNHThKvpXL+NoJwx4Wyz9sxjIiFvH6Khh/NsyhDzTTOb V4igqRk31CpnhsDeczky8fMgslPg6V3oxxmXlTnDgbWAqOkRrFIkKyKAOoUVr3PQ AZfRmUjQXen2eOqLdJydoKpK87O7tCGlxBTI30Co3LK6ojWtR9dzWQ== =Dmyz -----END PGP SIGNATURE----- --=-=-=--