Re: [EToSat] New Version Notification for draft-lhan-problems-requirements-satellite-net-02.txt

Christian Huitema <huitema@huitema.net> Sat, 26 February 2022 01:55 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: etosat@ietfa.amsl.com
Delivered-To: etosat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3F353A0E11 for <etosat@ietfa.amsl.com>; Fri, 25 Feb 2022 17:55:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.603
X-Spam-Level:
X-Spam-Status: No, score=-2.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PV7_LyQv8Asw for <etosat@ietfa.amsl.com>; Fri, 25 Feb 2022 17:55:17 -0800 (PST)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 298CF3A1C31 for <EToSat@ietf.org>; Fri, 25 Feb 2022 17:49:15 -0800 (PST)
Received: from xse7.mail2web.com ([66.113.196.7] helo=xse.mail2web.com) by mx258.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nNmCr-000KXB-Qa for EToSat@ietf.org; Sat, 26 Feb 2022 02:49:12 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4K58h26jhcz8S4 for <EToSat@ietf.org>; Fri, 25 Feb 2022 17:49:06 -0800 (PST)
Received: from [10.5.2.14] (helo=xmail04.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nNmCo-0005rx-Qi for EToSat@ietf.org; Fri, 25 Feb 2022 17:49:06 -0800
Received: (qmail 14796 invoked from network); 26 Feb 2022 01:49:06 -0000
Received: from unknown (HELO [192.168.1.105]) (Authenticated-user:_huitema@huitema.net@[172.58.43.140]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <chenmeiling@chinamobile.com>; 26 Feb 2022 01:49:05 -0000
Message-ID: <f41687d2-765a-c11b-f63e-e6f87c37afd1@huitema.net>
Date: Fri, 25 Feb 2022 17:49:04 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Meiling Chen <chenmeiling@chinamobile.com>, Wesley Eddy <wes@mti-systems.com>
Cc: EToSat <EToSat@ietf.org>
References: <CAC4j5ERK9D9QsoQeF=4CxJ0eJeNs+kN3Zq0+GPKPmnPFW=977w@mail.gmail.com> <f0210e6b-5519-44ff-c102-beaa91f8a9ad@oneunified.net> <85aa1a9d30c745c08598384bb68bdcf9@dlr.de> <CAL0D2oRBmEF0J8=3OJ0UNi7TfLkKJudvhVVsGg9wAEw4H-V8RQ@mail.gmail.com> <CAC4j5ET9988rpnq0GrrGspY9HEnc+YoLRP0-1DdQmdTSPsjZ3w@mail.gmail.com> <BY5PR13MB314462E940D269AD6CBB74CAE93C9@BY5PR13MB3144.namprd13.prod.outlook.com> <CAPjWiCS-eY9hsyxb+6iEOr-OK9fK_8Oqd7c44GvrkUwiAYDhmg@mail.gmail.com> <BY5PR13MB31448E1CB932962E5E539302E93D9@BY5PR13MB3144.namprd13.prod.outlook.com> <2022022511051209402716@chinamobile.com> <CAC4j5ERvkG=+NVyO+tZT=vG67Sukz=9gc7ebW3KqOnjHdzN0tA@mail.gmail.com> <BY5PR13MB3144C20419E7B933BB89F7CEE93E9@BY5PR13MB3144.namprd13.prod.outlook.com> <c07d775d-3360-f012-2c90-e8423b1e2366@mti-systems.com> <2022022608231131759614@chinamobile.com>
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <2022022608231131759614@chinamobile.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: 66.113.196.7
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9WLQux0N3HQm8ltz8rnu+BPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5yAr+WYRc/KC8CsRm5mAUDe42UuDhyzVYcwl2RB+0Aaejkw i87rn37xI++djTFVlyMh55uqY3MhMgFAHq5BxPxPXn36fLqvhISQ5ykyqUZqUd1jhnM/Mbva2XLV /LIEzaL2KoAZhJekBPedneT7f6994ir+F2NBzC6Lcr3eWcqZV4PAgTtUp75uqlx0KezvZHU8jaTA 4gvoN3cy3ZS3bc6iWQaaSSaRcFTFxaRvADgOuFdAU5fRzM/QzQW9/IoH33AG8ECuCwECazCwODtO F78PiyQEs+dlGXUJLWZ+Gc08Nmllke3azHdKmySKNUVQl4ntlVxnbS8qIO7oudHyb2T1VQ58xe/l rqiRGalI3YPsxOTrFXToVyBmRCgQVX6zVyFUu8qzeMQP6uTHL0d9UjfY+eX5ZvcELCIKs663F/co VFYFvf25LVONYbYifH5OzZDcG6hsRQZiAIgw+z837AqgX7ewI8e1h7RITgN14BHmGVt/ReJ9Mfhz zmbKTH7wI9GEU1utNskUAORCV2WFZX0jVtchDyr/klHhR+7g04zYe6TeVLW3pB0Q/PTyowo5Afs5 3J0bYPT+nQaMiyXmLgKWCFXoGKtafvOtcW/mP16bynTCOInfd76oq4RH5afpA3RRyBl07OVp2D/S 9ogT8aIXFFAJD4J4PNvTX6bIpjkJrD7YamjHRhv3cMS1AR/bb8GyuLfHqAnAj7rgKH7+eCmmvhwW lQR7CzuQ15ZBxYkGF1ShcA6Xvva2QAVEjpqzANZUmhRJvFbdO1XaKeBsEtPNYbEEnKrR5rcsyhEw cDCoBB0sl4OFxBT1d23OUWLVuGpBtL9ewJnoHKUNLZpf7DfZK/JdWvgd2/FibEdMM0Jnxu/VcARR JJg0CPVGXFYA7xCx7SWZBpdAUArn/St00aGa08t44IPL25P8DLNzMDIRDLdvK/cKOEqlCIPGIfYQ DNLcNVwigJ23suxKKQl6t4RW
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/N-w4wNtUvI0gfcy4FOZg8s5yiI4>
Subject: Re: [EToSat] New Version Notification for draft-lhan-problems-requirements-satellite-net-02.txt
X-BeenThere: etosat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "The EToSat list is a non-WG mailing list used to discuss performance implications of running encrypted transports such as QUIC over satellite." <etosat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/etosat>, <mailto:etosat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/etosat/>
List-Post: <mailto:etosat@ietf.org>
List-Help: <mailto:etosat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/etosat>, <mailto:etosat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Feb 2022 01:55:20 -0000

On 2/25/2022 4:23 PM, Meiling Chen wrote:

> 3GPP has regarded satellite network as 5G NG-RAN infrastructure, Network Operators need and want to be able to use satellite networks to provide services, the owner of satellite network should use the technology provided by IETF instead of private technology which is used currently.

3GPP solves a specific problem: standardize the communication between 
mobile phone and wireless network so phones can work and roam on 
multiple networks. I don't think we are close to the point were 
satellite phones can be designed to work on multiple satellite networks. 
Of course if multiple satellite network operators and device make to the 
IETF and asked to develop such standards, the IETF would most probably 
hear them. But the satellite operators are certainly not doing that now.

EToSat has been addressing a different but related problem: make sure 
that end-to-end protocols like TCP, TLS, HTTP or QUIC work well on paths 
that include satellite links or satellite networks. Up to date, that 
work has mostly addressed the geostationary satellite, dealing with long 
latency. Constellations of low orbit satellites do not suffer too much 
from the long latency problem, but may introduce other issues such as 
maybe variable bit rate or variable latency -- I say maybe because this 
is just a guess. If there are such issues, we may need to improve 
transport protocols or their implementation. But I have not heard of 
specific requests to address that so far.

>   To develop, we need to change the stateof privatization. From the perspective of economy, satellite networks will be shared in the future. It is impossible for each Service Provider to send a large satellite network, sure you know that.  Therefore, the technology of satellite network should be dominated by IETF and 3GPP like the current Internet and wireless technology.

On the contrary, each existing provider is using their own set of 
satellites, be it Inmarsat, Iridium, Globalstar, SpaceX or their future 
competitors. The IETF is not in a position to regulate the industry and 
change that practice.

-- Christian Huitema