From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (045-059-245-186.biz.spectrum.com [45.59.245.186]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 144FA3CB37 for ; Wed, 13 Dec 2023 13:27:11 -0500 (EST) Received: from dlang-mobile (unknown [10.2.2.69]) by mail.lang.hm (Postfix) with ESMTP id A2B4C1BC998; Wed, 13 Dec 2023 10:27:09 -0800 (PST) Date: Wed, 13 Dec 2023 10:27:09 -0800 (PST) From: David Lang To: Alexandre Petrescu cc: Sebastian Moeller , Steven , starlink@lists.bufferbloat.net In-Reply-To: Message-ID: <4rooss86-p114-8qp1-38r8-rn4302n99or4@ynat.uz> References: <361ee9d0d01da491a6e2b132317d170b@ausics.net> <8a807397-edef-4dcc-bfa6-f9c1598cbc77@gmail.com> <69da68cf-8746-45f8-9537-8fd8252de115@gmail.com> <7a20ea4f-4f16-4584-9f53-1ee3c72afd6f@app.fastmail.com> <26abce66-300f-405e-ad18-cc32695580fa@gmail.com> <4d0cd8c6-9de7-4976-8d46-ef159ea06c58@gmail.com> <21b2df7e-23c6-4c84-980f-635f41483c29@app.fastmail.com> <19c3c701-7c1a-4f04-a35f-bbec3055a54b@app.fastmail.com> <9d67c201-e759-4730-aa0c-e1c1a7186f84@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="228850167-130691884-1702492029=:5207" Subject: Re: [Starlink] Info on IP country ranges 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: Wed, 13 Dec 2023 18:27:11 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --228850167-130691884-1702492029=:5207 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT On Wed, 13 Dec 2023, Alexandre Petrescu via Starlink wrote: > A tunnel within 3GPP network (GTP) is used, among other reasons, to > support mobility.  The 'mobility', among some interpretations, is to > maintain a constant IP address for a moving end user. > > Surprisingly, the URL > https://support.starlink.com/?topic=1192f3ef-2a17-31d9-261a-a59d215629f4 > explains that that kind of mobility is not supported in starlink, i.e. > the end user might get another IP address if going to some other area.  > It is surprising in that in other starlink.com URLs they offer starlink > service for automobiles, and these typically move a lot.  Maybe the > starlink-connected automobiles do change their IP addresses a lot, but > the end users dont care that much. > > To support mobility within a starlink network - maintain constant all IP > addresses in a car - maybe one would try the DHCPv6 CONFIRM message to > try to maintain the same allocated /56 but it another area.  Maybe the > starlink DHCPv6-PD server will satisfy that CONFIRM, or maybe not. > > Or maybe there is a need of some other protocol in starlink, or in user > equipment connected to starlink (Dishy, third party router), to offer > that mobility.  But without adding new latency, of course. > > (this mobility aspect is on topic of the IP country ranges - > cross-border areas would ideally not break connectivity). There are two types of keeping your address. One is to have the same address all the time, the other is to keep your address during a session. Even if you get a public address, it can change from time to time (just like DHCP addresses could on landline ISPs), but that doesn't mean that your address will change during a session (i.e. while you are powered up and connected) even while moving around. If you get a public IP, that IP will change like a DHCP address would on a landline ISP, rarely and mostly when equipment at one end or another was restarted, but not every time you do a new satellite handoff David Lang --228850167-130691884-1702492029=:5207--