From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 5450A3B29D for ; Tue, 19 Sep 2023 09:35:04 -0400 (EDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 38JDZ0Gi007983; Tue, 19 Sep 2023 15:35:00 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5BF5920633D; Tue, 19 Sep 2023 15:35:00 +0200 (CEST) Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 49BAE2061F9; Tue, 19 Sep 2023 15:35:00 +0200 (CEST) Received: from [10.14.6.168] ([10.14.6.168]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 38JDZ0iH038129; Tue, 19 Sep 2023 15:35:00 +0200 Message-ID: <67f956f8-898f-4be0-8981-1adf412b314a@gmail.com> Date: Tue, 19 Sep 2023 15:35:00 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: fr To: Hesham ElBakoury , David Lang Cc: Dave Taht via Starlink References: <2d05e701-7556-8ae4-122c-e2f2d23feff2@gmail.com> <4o116qp9-6108-91r8-pn91-o37o6629npqo@ynat.uz> <2012b68c-2e15-4b5c-b36b-3b1d7eff12b4@gmail.com> <0q3n1sp5-09r5-5pqn-3p9p-opq883305s1s@ynat.uz> <340fd78d-39eb-e9af-c15a-7ca87b173e4e@auckland.ac.nz> <40da3b55-38ad-4e02-8c58-afea2bd02279@gmail.com> <2sp89904-o460-976s-4rsq-55nn6ps84464@ynat.uz> From: Alexandre Petrescu In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Starlink] Main hurdles against the Integration of Satellites and Terrestial Networks 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, 19 Sep 2023 13:35:04 -0000 Le 19/09/2023 à 01:32, Hesham ElBakoury a écrit : > Given the discussions in this email thread, what IETF should standardize > in priority order  for the integrated NTN terrestrial networks? Maybe make the NTN networks run IP, and preferably IPv6. It would be a good step towards integrating with the IP flat networks on the ground. (yes, I know, many will say that starlink does support IP and even IPv6, but I believe there is no IP in the sats; or maybe I have to read more). Alex > > Thanks, > Hesham > > On Sun, Sep 17, 2023, 12:59 PM David Lang via Starlink > > > wrote: > > it's very clear that there is a computer in the dishy that you are > talking to. > You get the network connection while the dishy is not connected to the > satellites (there's even a status page and controls, stowing and > unstowing for > example) > > I think we've seen that the dishy is running linux (I know the > routers run an > old openwrt), but I don't remember the details of the dishy software. > > David Lang > >   On Sun, 17 Sep 2023, Alexandre Petrescu via Starlink wrote: > > > Date: Sun, 17 Sep 2023 19:21:50 +0200 > > From: Alexandre Petrescu via Starlink > > > > Reply-To: Alexandre Petrescu > > > To: starlink@lists.bufferbloat.net > > > Subject: Re: [Starlink] Main hurdles against the Integration of > Satellites and > >      Terrestial Networks > > > > > > Le 16/09/2023 à 01:32, Ulrich Speidel via Starlink a écrit : > >> On 16/09/2023 5:52 am, David Lang wrote: > >>> > >>> In addition to that Ulrich says, the dishy is a full computer, > it's > >>> output is ethernet/IP and with some adapters or cable changes, you > >>> can plug it directly into a router. > >> > >> We've done that with the Yaosheng PoE Dishy adapter - actually > plugged > >> a DHCP client straight in - and it "works" but with a noticeably > >> higher rate of disconnects. > > > > It is good to know one can plug a DHCP client into the Ethernet > of the > > DISHY and receive DHCP replies. > > > > But that would be only a lead into what kind of DHCPv4 is > supported, or not. > > > > I would ask to know whether the DHCP server runs on the DISHY, or > > whether it is on the ground network of starlink, i.e. the reply > to DHCP > > request comes after 50ms, or after 500microseconds (timestamp > difference > > can be seen in the wireshark run on that Ethernet). > > > > This (DHCP server daemon on dishy or on ground segment) has an > impact of > > how IPv6  can be, or is, made to work. > > > > This kind of behaviour of DHCP - basically asking who allocates an > > address - has seen a continous evolution in 3GPP cellular > networks since > > they appeared.  Nowadays the DHCP behaviour is very complex in a > 3GPP > > network; even in a typical smartphone there are intricacies about > where > > and how the DHCP client and server works. With it comes the > problem of > > /64 in cellular networks (which some dont call a problem, but I do). > > > > So, it would be interesting to see whether starlink has the same /64 > > problem as 3GPP has, or is free of it (simply put: can I connect > several > > Ethernet subnets in my home to starlink, in native IPv6 that is, > or not?). > > > > Alex > > > > _______________________________________________ > > Starlink mailing list > > Starlink@lists.bufferbloat.net > > > https://lists.bufferbloat.net/listinfo/starlink > > >_______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > >