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

Arashmid Akhavain <arashmid.akhavain@gmail.com> Mon, 28 February 2022 16:16 UTC

Return-Path: <arashmid.akhavain@gmail.com>
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 5CD7A3A1367 for <etosat@ietfa.amsl.com>; Mon, 28 Feb 2022 08:16:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ZVATwVs8wZsL for <etosat@ietfa.amsl.com>; Mon, 28 Feb 2022 08:16:19 -0800 (PST)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C119F3A1335 for <EToSat@ietf.org>; Mon, 28 Feb 2022 08:16:18 -0800 (PST)
Received: by mail-pl1-x635.google.com with SMTP id s1so11126953plg.12 for <EToSat@ietf.org>; Mon, 28 Feb 2022 08:16:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gkJt7EpOxxd3wyIf4gbv3XaYJWUHniw0Xw0MKxkh9io=; b=q1wTvLF8/dvZFfmfss+SReoRDR54N1FGoeeRoNDgJcM+8LgWnRASQ4jrIQsmOwhBoB tIBxrszuQy5Ywn1BY36+lv10J0GmAlNFPnv/xGwxFGHPKr6Pi/mBEF8pXMAQHsh0Al3J Tj8avYpzx+e0DHUPHESnLtZ17RqYUpGbJlw0iBGrM4Ssk/mUwELiFeTdMJgy9jm7sq2I P4YI9rsk6n0RF6+UZFraS/HlQgA/Z/zUBUNazqACRnrHF4XHJXWGYtFvVSgy+1fp3rhe ZuUZTFrKdlL47Zo6xCIxKjNZtKZWCW2spbBwTCZ+WvuhhfKE5RIlwhK8A3GW7ue+pdNt fsHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gkJt7EpOxxd3wyIf4gbv3XaYJWUHniw0Xw0MKxkh9io=; b=ox/ZJNQtAH+EG8Q8KRfF7txJVk+fjc1cg/+xh5ZuVpDnp7c9rZhPxpAB4Xvq3NcbDG kCBz/HlSf57UIkO3pg/I7Y4AsLsQmohIfe0n4lr5/aS/Ac/UAaO1QLmkdUjnYw24ZOq5 SeIAT9AHXDAy2A5yHAAbMvsZI1yKzJoUFs8t/zMp0CWsk8to8P8rCT9xT721t2wIHZpP 9o5ByjDPljXwiF/fcGV3YmBEuo1fkjLBDQ5MHui0/1bEGO6wdtRTjyEFNiqsX3Q381Cj GS7k2hc7+0BUXmQ+tcNE04ERpjpN7EkbS4q9D5eoqZ8zZQ5UOIvzErupq4/MCCcpmQzQ otkA==
X-Gm-Message-State: AOAM5313F7QAt6uemWwbq2w/pkyOcilsH1IsDeRk4iP6EWNmCzfJZc96 OwjbDptuZvzJ/nW9ylWu19TPfgBM5z4P6OcyWmI=
X-Google-Smtp-Source: ABdhPJyuXotgSHw/gEM2L6wQxNWZYJzOcJcmiOparvncz38JfSe9wv4FV6OP9Y1MwI88Qq2M7CKWxyHBmtYr/cvsMag=
X-Received: by 2002:a17:90b:1a81:b0:1bc:ec26:40a6 with SMTP id ng1-20020a17090b1a8100b001bcec2640a6mr17565109pjb.0.1646064977537; Mon, 28 Feb 2022 08:16:17 -0800 (PST)
MIME-Version: 1.0
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> <f41687d2-765a-c11b-f63e-e6f87c37afd1@huitema.net>
In-Reply-To: <f41687d2-765a-c11b-f63e-e6f87c37afd1@huitema.net>
From: Arashmid Akhavain <arashmid.akhavain@gmail.com>
Date: Mon, 28 Feb 2022 11:16:05 -0500
Message-ID: <CAC4j5ET19WLABJ7S9gcFTjdmmJ6axgxx2VWdShJ7NTD4LZYa-Q@mail.gmail.com>
To: Christian Huitema <huitema@huitema.net>
Cc: Meiling Chen <chenmeiling@chinamobile.com>, Wesley Eddy <wes@mti-systems.com>, EToSat <EToSat@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000436f1d05d9165ebf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/EVfx_zabJeXzIdHMo7zMqPH7eAs>
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: Mon, 28 Feb 2022 16:16:30 -0000

In addition to standardising the communications between the UEs and the
mobile network, 3GPP defines every single aspect of the overlay network
from its required NFs to the specifications of all the protocols and
interfaces. Communications between RAN and mobile core is handled through a
specific set of 3GPP defined protocols which up to now assumed a stable and
reliable transport underlay. The data plane for example uses GPRS (GTP is
carried in UDP) to connect user plane functions (UPFs). I do believe that
there are routing and forwarding challenges when it comes to mega
constellations.

Having said that however, as per my comment earlier, I share Christian's
point of view. Satellite networks, at least for now, are close ecosystems.
Existing satellite providers employ their own proprietary mechanisms to
connect their satellites to one another. There is no
interoperability requirement between satellite operators so far. Well...at
least I haven't seen one yet. Without such requirements, there won't be any
need for standardisation.

Now, when I raised this concern earlier, our colleague, Raymond Burkholder
in his reply wrote











*"In the not too distant future (as in, it is being worked on right
now),some operators will be carrying the traffic of other operators.
ie,backbone operators in the sky will have a good foot print of
groundstations, and will be providing backbone operations to
satelliteoperators who don't have a large ground footprint (this is the sky
tosky to ground scenario, vs the broadband up-down scenario).There then
needs to be some sort of interoperability of the carrier vsthe end-user in
terms of how to get a endnode-satellite's dataencapsulated across a
carrier's satellite network down to the ground andthen over to the
subscriber's site in a real-time fashion."*

This operation/business model is interesting from the standardisation point
of view and something we should perhaps find out more about.

@ Raymond Burkholder: Do you have any pointers you can share?

Best regards,
Arashmid

On Fri, Feb 25, 2022 at 8:57 PM Christian Huitema <huitema@huitema.net>
wrote:

> 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
>
>
> _______________________________________________
> EToSat mailing list
> EToSat@ietf.org
> https://www.ietf.org/mailman/listinfo/etosat
>