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

Arashmid Akhavain <arashmid.akhavain@gmail.com> Wed, 23 February 2022 18:08 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 5395C3A10EB for <etosat@ietfa.amsl.com>; Wed, 23 Feb 2022 10:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.903
X-Spam-Level: **
X-Spam-Status: No, score=2.903 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, GB_SUMOF=5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 RAxidadxE2GB for <etosat@ietfa.amsl.com>; Wed, 23 Feb 2022 10:08:17 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 3F9153A1075 for <etosat@ietf.org>; Wed, 23 Feb 2022 10:08:17 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id d187so16109812pfa.10 for <etosat@ietf.org>; Wed, 23 Feb 2022 10:08:17 -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=idoZhfWMuVhCCDZc7cFOoMy05vJL5H1Hkoe0+zomZhk=; b=BjMjQRDHT1e9gtxv/PpiFxdoVF1aYpHmgjI5q1+DMIdnnUDNe4lr4Tbf2WmrCYyijo INTWUJkXiTUTOmXA3+5h3mDcq1tz4Z2Zo7mjHtO0vHc7AM9JVQBwnDiZCG7JpnpIE02Q J9ZmZzPzrXjH/3LNVqCj2ISw+7l16n4+hj/D21nDgw8GuxMSRk1yGAt8edHH77wJanv+ /lq/WWSN4I+e/mVvdrA3Aqj4Aee/MY3mWee+D+RzcAvgRG/6ylZb2mCIVLXjcNPkXapp 4K18f3Ass9Rk9AScTJ9ap4cK6aN5vMCUc6ZZ/IFpsupOZS+Pr0tVFDp81ZBahu8dabV8 +uUQ==
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=idoZhfWMuVhCCDZc7cFOoMy05vJL5H1Hkoe0+zomZhk=; b=2i7z2cE/RNRCxwqZTjfPh5VN77o3XSPSoZATHabwLmW1FfiCkLMiBxSKquWeseqqkY emBApEUnOVEi/7LJMq7oEftb/vfFK2Kl6IfT4L1GkVYgSYe1gKk62V8XhYOg55aj0cip vu3ADnrsSXkh+UvoTBqaUwQ5zhwxe6he24WMRJcf++0mY/T984vJlMK36ovhM7mF5cAb k6/nzyl2FXOeRNUdekYJksnED/RqIKaemF8x6Kd+s03mzToIemb9LUYCx3tW7u/HkXY8 pCtsvqB1ivEDfw06GvrAPbWd7GC1cpH1Tak+mpsBCsSa07jXHa2x4+K+GmDXtKtEnqQg diPQ==
X-Gm-Message-State: AOAM531A+FrhSh8LpkJsY4enAtUJe3hCbDszpST/THBgmnfh5+G98z8o 23ogBkVyUfwYSgpKqRG/thh2BF8wZe3vKeci2ov7rPm7BPQ=
X-Google-Smtp-Source: ABdhPJzHSQtWnG4ilffRrZ0Fk3JZW6vyTeePKIFKwlSq5Z63Uu2FyTx2vqwQR4bXBvK4wAupx3+B8STTxv/KmzhmqHc=
X-Received: by 2002:a63:ce48:0:b0:373:ac94:f489 with SMTP id r8-20020a63ce48000000b00373ac94f489mr628987pgi.622.1645639696264; Wed, 23 Feb 2022 10:08:16 -0800 (PST)
MIME-Version: 1.0
References: <CAC4j5ERK9D9QsoQeF=4CxJ0eJeNs+kN3Zq0+GPKPmnPFW=977w@mail.gmail.com> <f0210e6b-5519-44ff-c102-beaa91f8a9ad@oneunified.net> <CAC4j5ER6Pp6P3Ey4tminiDxkHwrX5161y66jhi5QWfy4Bfqung@mail.gmail.com> <edba36e1-af33-b57c-c1d1-7d2d0e655eac@oneunified.net>
In-Reply-To: <edba36e1-af33-b57c-c1d1-7d2d0e655eac@oneunified.net>
From: Arashmid Akhavain <arashmid.akhavain@gmail.com>
Date: Wed, 23 Feb 2022 13:08:04 -0500
Message-ID: <CAC4j5EQ-cpAjvtzz1VwWPW5NfEmuuDE8Eue9e6utY4pjeZynpw@mail.gmail.com>
To: Raymond Burkholder <ray@oneunified.net>
Cc: etosat@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008630fb05d8b359b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/Wup8m_I2ggiLF6NTX0EGweXINRs>
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: Wed, 23 Feb 2022 18:08:22 -0000

Do you mean as an open source initiative? Or more like a formal discussion
in an IETF WG?
I have been looking into LEO/vLEO networks from two point of views:
1- General internet connectivity
2- Integration with mobile networks.

Ad-Hoc networking might be a relevant forum in IETF. We might want to talk
to Alvaro or Erik Kline at some point and seek their opinions when we have
more concrete proposals. IETF Hackathon might be a good venue from a
prototyping point of view.

As for integration with mobile networks, 3GPP started some ongoing work in
this area at the end of its release 16 (I don't quite remember, it could be
release 17) . They do have a long way to go though; as in some of the
proposals they are planning to place a gNB in the satellite. The more
immediate scenario which is also simpler to tackle is RAN to mobile core
connectivity via the LEO network.

Best regards,
Arashmid

On Wed, Feb 23, 2022 at 11:17 AM Raymond Burkholder <ray@oneunified.net>
wrote:

> On 2022-02-23 8:38 a.m., Arashmid Akhavain wrote:
>
> This sounds like an interesting approach. The routing system has to deal
> with both predictable (majority) and unpredictable link events. Traditional
> SDN systems might not be able to perform as the number of nodes goes up
> drastically. Is this work public, or proprietary?
>
>
> Their implementation is proprietary, but many of the concepts are common
> knowledge:
>
>    - based upon TLE information, ground stations can compute satellite
>    feasible neighbors
>    - using network flow algorithms, feasible paths can be computed
>    - there is now enough satellite-local compute available such that
>    multiple ground stations can compute these paths and advertise upwards, and
>    satellites pick the 'best' suggestion for paths to ground (based upon local
>    awareness of rf and link capability/capacity)
>    - the flow calculations take in to consideration the sum of path
>    latencies on the ground, earth-sky, and satellite-satellite
>    - multiple ground stations perform the computation as not all are
>    connected upwards at all times
>
> Is there a 'forum' where some of this could be developed in public?
>
>
> On Tue, Feb 22, 2022 at 10:07 PM Raymond Burkholder <ray@oneunified.net>
> wrote:
>
>> On 2022-02-22 1:27 p.m., Arashmid Akhavain wrote:
>>
>> I agree that existing IP routing protocols can face convergence issues
>> when it comes to satellite networks. IP and existing routing protocols rely
>> on hierarchy to minimise the impact of link events. Establishing hierarchy
>> in satellite networks can be very complex due to various movements
>> especially when it comes to massive constellations.
>>
>> In polar constellations, the movement at the poles, and the seam plane
>> will be problematic for existing routing protocols. The issue of course
>> gets exacerbated in the Walker Delta constellation as the seam effect
>> exists between every other orbit.
>>
>> A new method of routing might be required to address this issue. What are
>> your plans w.r.t to this draft? Have you discussed some of these issues
>> with any of the working groups?
>>
>> Using standard routing protocols are problematic as they are reactive.
>> And due to inter-satellite delays, can take time to re-converge.  I was
>> working with a company to come up with an SDN solution where we used TLE
>> (Two Line Elements) to compute satellite nearness and then pre-populate
>> neighbor entries for installation at pre-arranged times.
>>
>> In addition, to do this properly, these neighbor entries and routing
>> table entries need to be populated based upon distributed path computation
>> capabilities (due to the fact that the same ground stations are not always
>> in view, and paths need to be adjusted as necessary).
>>
>>
>> Best regards,
>> Arashmid
>>
>>
>> _______________________________________________
>> EToSat mailing listEToSat@ietf.orghttps://www.ietf.org/mailman/listinfo/etosat
>>
>>
>> _______________________________________________
>> EToSat mailing list
>> EToSat@ietf.org
>> https://www.ietf.org/mailman/listinfo/etosat
>>
>
>