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

Arashmid Akhavain <arashmid.akhavain@gmail.com> Wed, 23 February 2022 15:46 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 B6C833A10D8 for <etosat@ietfa.amsl.com>; Wed, 23 Feb 2022 07:46:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 i7zFNM1P11qe for <etosat@ietfa.amsl.com>; Wed, 23 Feb 2022 07:46:10 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 BB7533A10E0 for <etosat@ietf.org>; Wed, 23 Feb 2022 07:46:10 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id 27so15122753pgk.10 for <etosat@ietf.org>; Wed, 23 Feb 2022 07:46:10 -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=vSwdtqSC8m8hafKKnjV3zAv93nVMR3GWwL75v0KWvoY=; b=YrwqntY4Vhguv+yrWqqKwWHKea9ucqlfK9Z82Ee45sdxkVIK9S+3Vf+dAMlQyYkrw/ DhH6tLeDeJf7Qgg/GLKE3Y1fNIdhPEBlDxqvsL7tSrM6V71LZelnysYSvOPkiOS2Wp7C F7F1C/WZ+HwSnZiRb8HyZtYh0gEoRzjh1Qe9GiBG7xqXygcJg4K1xKeGGq6I6ZWA3mXx dbVdAnHU8sQmhs+2+aauZMDm8ymoLa/QlV5Ajh+FVK8eOUVSKqddeeP9u0xjpmpPJB0H BRHYZamA20r4WzuDhgqb/5EIwa8GkYx784hKVE/TUfikDXvJx7FR5TvG9Zjfm0vd13b6 8tKA==
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=vSwdtqSC8m8hafKKnjV3zAv93nVMR3GWwL75v0KWvoY=; b=ps3NCWnkqQ+/AhILvY46da0zGX0YdXeOH2IndM4homU3kPnj5yLP+nyzmRpSxVWv/q R6KhSDBGd0AEk1JJZEq7Sw3R0ZUL8mI/wG1CmZgR+SI7DY/G4Ba3tL3aiQw20tq3X8V/ TOoMS7qCFUzi1vfdp3SH2NDEBjSC6cEFDVgLaUz3+RjSf/LZQOSGgQkVrLttC04NJouC vwVCttAyf4k0vYovfIv2cPidIL8WT11qureiTLVZj4zE7c3FvnIob7X6xjEiuwwblHzR HZeaLjPNPZpGHgsU5KWSUZzIpaKewCdaV14ds8E1qBpFA4k3IoSCp82nM7v7O/E8Q2rP g+zA==
X-Gm-Message-State: AOAM532qFBK8j/TRYHGoF7trI2MICrDOci9hEIlzJ6v7wbJ1tNyWnN/0 kB8uYjmW3X0/JfmXKoLjK8s1547F5X7Db0/W4ts=
X-Google-Smtp-Source: ABdhPJzmtENxyQKVhQVU8PzNqWVj5CeJGyN/x8I9V8eOgEF/q0qNcGAh8R1ajUg1aS/ejWz0UjWXf9taxfUCsIkw4AM=
X-Received: by 2002:a65:6d85:0:b0:373:79c6:9f15 with SMTP id bc5-20020a656d85000000b0037379c69f15mr106689pgb.335.1645631169577; Wed, 23 Feb 2022 07:46:09 -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>
In-Reply-To: <85aa1a9d30c745c08598384bb68bdcf9@dlr.de>
From: Arashmid Akhavain <arashmid.akhavain@gmail.com>
Date: Wed, 23 Feb 2022 10:45:57 -0500
Message-ID: <CAC4j5ETBZX316rQsxjSk5VbOki3S0-BFrW-9GjO+zzUaKZL+_w@mail.gmail.com>
To: Tomaso.deCola@dlr.de
Cc: ray@oneunified.net, etosat@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004b48de05d8b15da1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/uOpNEGQaSrG6vgSAmVzW4Vb9lhc>
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 15:46:16 -0000

Thank you Tomaso,
I will have a look. Pure geographical routing works well when there is no
link down, but it faces issues when the link to the next closer node goes
down. I am interested to see whether the paper you mentioned addresses
those issues.

Best regards,
Arashmid

On Wed, Feb 23, 2022 at 4:33 AM <Tomaso.deCola@dlr.de> wrote:

> If of any interest or support to the discussion on routing for LEO,
> colleagues of mine at DLR published the following paper last year:
>
>
>
> Roth, M, Brandt, H, Bischl, H. Implementation of a geographical routing
> scheme for low Earth orbiting satellite constellations using intersatellite
> links. *Int J Satell Commun Network*. 2021; 39: 92– 107.
> https://doi.org/10.1002/sat.1361
>
>
>
> Then we are now working on SDN in space as enabler for new concepts of
> routing and network management, as part of an ESA-funded project.
>
>
>
> Best Regards,
>
>
>
> Tomaso de Cola
>
>
>
>
>
> ————————————————————————
>
> *Deutsches Zentrum für Luft- und Raumfahrt* (DLR)
> German Aerospace Center
> Institute of Communications and Navigation | Satellite Networks |
> Oberpfaffenhofen | 82234 Wessling | Germany
>
> *Tomaso de Cola, Ph.D.*
> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
> tomaso.decola@dlr.de <sandro.scalise@dlr.de>
> http://www.dlr.de/kn/institut/abteilungen/san
>
>
>
>
>
>
>
> *From:* EToSat <etosat-bounces@ietf.org> *On Behalf Of *Raymond Burkholder
> *Sent:* Mittwoch, 23. Februar 2022 04:07
> *To:* etosat@ietf.org
> *Subject:* Re: [EToSat] New Version Notification for
> draft-lhan-problems-requirements-satellite-net-02.txt
>
>
>
> 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 list
>
> EToSat@ietf.org
>
> https://www.ietf.org/mailman/listinfo/etosat
>
>
> _______________________________________________
> EToSat mailing list
> EToSat@ietf.org
> https://www.ietf.org/mailman/listinfo/etosat
>