From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F0C613B29E for ; Thu, 20 Apr 2023 12:14:31 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6C30B3898C; Thu, 20 Apr 2023 12:32:03 -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 FEc6tISOus_a; Thu, 20 Apr 2023 12:32:02 -0400 (EDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id A6C1A3898B; Thu, 20 Apr 2023 12:32:02 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1682008322; bh=RFR4e3hSWxxfrrvyjWXxSQlakTd7O6zrDs0zGxljzac=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=bbzmH592RVIUpK37Of9TQX2O2e+y/5VynvA0N2GeqSaLtY5BLyKdVJ9ONh5fer0eH F4t2NqGYMwFDWOai9LOrYvmkdxkq4WpVexsT8Q5uNTobfUo3wDmOzbC6BUjAn1vWRH yBuLmQ4QQcGP/uQiXo+QghKwtxZ3YDTsd9/EIvIWUfE/ueC4u3fXZa9xPrTbFcy0dP zwv0I9j+Ub8crm72OhI6cZUTOa6r6cBB+WB7EzG/hicu2VqrEnsIRpRWZDCiPzjYkP V0ZMuZZWdx5TkqR5s20J/erPuSTBT6LkeEMF/aVAxz74TFBaxrMJBg/3JGn7hUAGll B8ARxTN6X2oOA== Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E859D43C; Thu, 20 Apr 2023 12:14:29 -0400 (EDT) From: Michael Richardson To: =?us-ascii?Q?=3D=3FUTF-8=3FQ=3FDavid=5FFern=3DC3=3DA1ndez=3F=3D?= cc: starlink@lists.bufferbloat.net In-Reply-To: References: 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 Digest, Vol 25, Issue 28 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, 20 Apr 2023 16:14:32 -0000 David Fern=C3=A1ndez via Starlink wrote: > As we were discussing recently, maybe starting with anycast DNS > servers on satellites is a first step to consider, before embarking > any other type of cloud servers. For Starlink customers, having a DNS recursive cache on the satellite you a= re talking to certainly saves half a hop, if the cache is big enough. If the gateway part of the bent pipe suffers from bufferbloat, then having DNS queries from the client avoid that part seems like a win. Also, the recursive queries from the DNS recursive cache can be switched on= a different circuit to the gateway, or marked better to avoid the bufferbloat. {or, you know, you could fix the bloat. In the satellite to satellite laser circuits, I suspect that the bandwidth available will fluctuate wildly. Engineers will be reluctant to throw away delay tolerant packets in that ca= se} (I'm not sure we should call it an anycast DNS service, because even though it looks similiar to the clients to the things we do with BGP, its not real= ly the same. Also, squatting on/intersepting 8.8.8.8, etc. would be a very bad thing to do. It would have to be a new address. But, because we wouldn't be using BGP, it does not need to occupy an entire /24. ) -- ] 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 = [