From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp119.iad3a.emailsrvr.com (smtp119.iad3a.emailsrvr.com [173.203.187.119]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id E4B9A3B29E for ; Thu, 1 Sep 2022 17:08:45 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=evslin.com; s=20220608-p431o605; t=1662066525; bh=Qnh+CeDn8QWp5V6VASLOS/guiIs+F9SaDmtMe3+yHJU=; h=From:To:Subject:Date:From; b=jn7wh70LhTpaW4Rzv4yG3Iq+fF6Xhj9ycRG3SmBNc3QfqrjOtXfIuOCX5eGubVGG4 GgbYunsplC508SzwHju+PvCYwbUo6JPrZCMHeZ3a1NyCSuwGW0nIfnjbl579qzdkSk urBdXTseT0ACKdH3aX+9N5hpgrMWSlbZYw+Zi+kA= X-Auth-ID: tom@evslin.com Received: by smtp23.relay.iad3a.emailsrvr.com (Authenticated sender: tom-AT-evslin.com) with ESMTPSA id 50C7124EDD; Thu, 1 Sep 2022 17:08:45 -0400 (EDT) From: To: "'Michael Richardson'" , "'Ulrich Speidel'" , 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> <15408.1662062057@localhost> In-Reply-To: <15408.1662062057@localhost> Date: Thu, 1 Sep 2022 17:08:45 -0400 Message-ID: <778e01d8be47$061c67f0$125537d0$@evslin.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQIPRsMrjCLeIUrVvf24O402fV6ZjgFbka6sAgkRiRgCL1qAJAHrApp1AfCjI2cA4yqH9AGHa2ahAdOv9mYB2d64CAFE/QxeALG7RoOs0guXwA== Content-Language: en-us X-Classification-ID: b8beee83-5813-4d12-9447-5ca0ade7ca15-1-1 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 21:08:46 -0000 I think manufacturing orbital datacenters in space is absolutely = necessary. Then, at no point, is a heavy set of frames needed to hold = the weight of the boards. Producing the chips in a real vacuum no = gravity environment may also allow radically different design -----Original Message----- From: Starlink On Behalf Of = Michael Richardson via Starlink Sent: Thursday, September 1, 2022 3:54 PM To: Ulrich Speidel ; = starlink@lists.bufferbloat.net Subject: Re: [Starlink] Starlink "beam spread" 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.