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

Marie-Jose Montpetit <marie@mjmontpetit.com> Thu, 24 February 2022 01:41 UTC

Return-Path: <marie@mjmontpetit.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 4CA1D3A128E for <etosat@ietfa.amsl.com>; Wed, 23 Feb 2022 17:41:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=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=mjmontpetit-com.20210112.gappssmtp.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 ot1-M2PPkSMm for <etosat@ietfa.amsl.com>; Wed, 23 Feb 2022 17:41:38 -0800 (PST)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 71B583A1289 for <etosat@ietf.org>; Wed, 23 Feb 2022 17:41:38 -0800 (PST)
Received: by mail-lf1-x133.google.com with SMTP id u20so1374357lff.2 for <etosat@ietf.org>; Wed, 23 Feb 2022 17:41:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20210112.gappssmtp.com; s=20210112; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=Vpy811nbwwcoiksMb0bR2GuaHvLpwGaZ4BFA5XuURXw=; b=BoP72yxai8taWa+T4Xgt1KwmzIbkygeJ9WWHn/a8gHS5oVOOSdaYt6ll/vt9Wg1vJ1 N+4BbH2t2amqHUPmhKpcK3EazeG4zRT8PSNrD5nSDYIf8BZWBqrVUoSIxpH9+E5PJH2L yb/sCxAd6VYI38CQiyv+8+Z2oR0YlvsQqpXZCHEMJ5nNJ/9vGV4uolWnsHuvqtF3l+qH bF19A9A1awaBHbEmADSHC3q8TyjdnVVCVtjLg84uJ5bhT4jpU7/FObXFlhMSw800Zi/p TWXrhZWKCkHDCH4kq6IijJLG8Zzus2L2/q/YvaTKM13nkPwtZLsGIYwrhy08wZi3veOk cLYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=Vpy811nbwwcoiksMb0bR2GuaHvLpwGaZ4BFA5XuURXw=; b=sFvIUPfNzRKneU4vqFDjw0/8mX00CsoPH7ynsCgACDDGEBOW/1pHtj+qplz7BwZ9Py wXv9N/BKQUsm61a4i5PiQy01AzWS7jY9awyFow0HTD8vtQcxqb104f+b4H+hbsHsbgyv tScfqoAr4hZY0gBJndR83mSnZN5pSaP5XvtN6EkkHrb2yvORqkl3qeDj3PXljretC9lp tsuYzwhFx7ZXWxM/epU1LMqutKqaxq621cO7jTw595jx/lwGR8Br/ulAJTOCsSRkryc4 W8h08S7CRunFtpO/9mH1IhrmR8hyqNUlt1XyifpyZElSnHiGe3z9WQW2v/4ji0jKdZlL jKcw==
X-Gm-Message-State: AOAM532Si9/hgChtdLjL8yo9Fe2//fbHwlpwNMGZ33NdrSjjH648VX88 f3kvsyjukQLDR68qNHN+J4qc4MMVfP8Yt+55d8t8jAgbZcM=
X-Google-Smtp-Source: ABdhPJypMsh10anTn42+Vt920L3kv2QGbnbdBOGoiNxNdOAkWLLTk3LBEgITbl73VcdQNlPuo17CwmpJbyu9/7pMB6g=
X-Received: by 2002:ac2:48b0:0:b0:443:1bb5:374c with SMTP id u16-20020ac248b0000000b004431bb5374cmr354019lfg.236.1645666895898; Wed, 23 Feb 2022 17:41:35 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 23 Feb 2022 17:41:35 -0800
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
In-Reply-To: <BY5PR13MB314462E940D269AD6CBB74CAE93C9@BY5PR13MB3144.namprd13.prod.outlook.com>
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>
MIME-Version: 1.0
Date: Wed, 23 Feb 2022 17:41:35 -0800
Message-ID: <CAPjWiCS-eY9hsyxb+6iEOr-OK9fK_8Oqd7c44GvrkUwiAYDhmg@mail.gmail.com>
To: Nicolas Kuhn <nicolas.kuhn.ietf@gmail.com>, Lin Han <lin.han@futurewei.com>, Arashmid Akhavain <arashmid.akhavain@gmail.com>
Cc: "etosat@ietf.org" <etosat@ietf.org>, "Tomaso.deCola@dlr.de" <tomaso.decola@dlr.de>, "ray@oneunified.net" <ray@oneunified.net>
Content-Type: multipart/alternative; boundary="000000000000bfbf3905d8b9ae7f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/6ji0kiroB1FzsJ8wmlrh-3RJsGM>
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: Thu, 24 Feb 2022 01:41:45 -0000

Where do you intend to present at 113?

Marie-José Montpetit, Ph.D.
marie@mjmontpetit.com



From: Lin Han <lin.han@futurewei.com> <lin.han@futurewei.com>
Reply: Lin Han <lin.han@futurewei.com> <lin.han@futurewei.com>
Date: February 23, 2022 at 5:15:16 PM
To: Arashmid Akhavain <arashmid.akhavain@gmail.com>
<arashmid.akhavain@gmail.com>, Nicolas Kuhn <nicolas.kuhn.ietf@gmail.com>
<nicolas.kuhn.ietf@gmail.com>
Cc: etosat@ietf.org <etosat@ietf.org> <etosat@ietf.org>,
Tomaso.deCola@dlr.de <tomaso.decola@dlr.de> <tomaso.decola@dlr.de>,
ray@oneunified.net <ray@oneunified.net> <ray@oneunified.net>
Subject:  Re: [EToSat] New Version Notification for
draft-lhan-problems-requirements-satellite-net-02.txt

Good question. Actually this has been studied by 3gpp. 3gpp has proposed
the Satellite-based NG-RAN architectures in TR38.821. In this architecture,
satellite network is an infrastructure for 5G. In its proposed
“Regenerative payload” mode, satellite network (with ISL) should provide
the IP connectivity for wireless access and NTN integration. Different SP
is able to use satellite as wireless access network. From this expectation,
satellite network will be access and backhaul network for wireless, the
standardized protocol/methods are expected.

I will have a slide in the next IETF meeting to explain more details about
the problems.



Regards



Lin



*From:* Arashmid Akhavain <arashmid.akhavain@gmail.com>
*Sent:* Wednesday, February 23, 2022 12:36 PM
*To:* Nicolas Kuhn <nicolas.kuhn.ietf@gmail.com>
*Cc:* Tomaso.deCola@dlr.de; etosat@ietf.org; ray@oneunified.net
*Subject:* Re: [EToSat] New Version Notification for
draft-lhan-problems-requirements-satellite-net-02.txt



That could be another alternative.

The question that I have been struggling with is whether and how satellite
networks can benefit from standardisations. These networks are proprietary
(at least for the time being). It is difficult to imagine satellites in a
multi-vendor ecosystem.



That's why I asked what the authors of this draft intended to do.



Arashmid



On Wed, Feb 23, 2022 at 3:12 PM Nicolas Kuhn <nicolas.kuhn.ietf@gmail.com>
wrote:

Thanks Tomaso for the interesting pointer.



This kind of work is very useful when it comes to design routing strategies
for mega constellation systems.

If there are any public outputs of the SDN approach, I would be very
interested in having a look.



What I think would be also very interesting to discuss in terms of IETF
perspective is to assess whether existing routing mechanisms (OSPF,
SegmentRouting) require specific changes for the use case.



Nico



On Wed, Feb 23, 2022 at 10: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

_______________________________________________
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