Re: [LOOPS] draft-li-tsvwg-loops-problem-opportunities and use-cases.

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Wed, 29 July 2020 11:25 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: loops@ietfa.amsl.com
Delivered-To: loops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3814B3A092F for <loops@ietfa.amsl.com>; Wed, 29 Jul 2020 04:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 VEU9xmQ4jEq3 for <loops@ietfa.amsl.com>; Wed, 29 Jul 2020 04:25:29 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 7863E3A092D for <loops@ietf.org>; Wed, 29 Jul 2020 04:25:29 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id AECEC1B0019B; Wed, 29 Jul 2020 12:25:07 +0100 (BST)
To: mohamed.boucadair@orange.com, loops <loops@ietf.org>
References: <fb709277-50a8-26ad-b925-38f153805d70@erg.abdn.ac.uk> <13424_1596003270_5F2113C6_13424_401_1_787AE7BB302AE849A7480A190F8B9330315069E6@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <1fe93d0a-6765-1fa8-1627-1aea91e0b40d@erg.abdn.ac.uk>
Date: Wed, 29 Jul 2020 12:25:00 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <13424_1596003270_5F2113C6_13424_401_1_787AE7BB302AE849A7480A190F8B9330315069E6@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/8l3U6Ccf2dNaTpTxW2tuG2WO85c>
Subject: Re: [LOOPS] draft-li-tsvwg-loops-problem-opportunities and use-cases.
X-BeenThere: loops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Local Optimizations on Path Segments <loops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/loops>, <mailto:loops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/loops/>
List-Post: <mailto:loops@ietf.org>
List-Help: <mailto:loops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/loops>, <mailto:loops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2020 11:25:33 -0000

Hi med,

On 29/07/2020 07:14, mohamed.boucadair@orange.com wrote:
> Hi Gorry,
>
> I guess you are referring to this text:
>
>     Similar issues and optimizations
>     may be helpful in other deployments such as enhancing the reliability
>     of data transfer when a fleet of drones are used for specific
>     missions (e.g., site inspection, live streaming, and emergency
>     service).  Captured data should be reliably transmitted via paths
>     involving radio connections.
>
> Actually, this is an old text. The main point we wanted to convey here is that when a swarm of drones is collaborating for example to provide connectivity, multiple drones (seen ad as forwarders) will be solicited till packets are (hopefully) delivered to a network where the fleet of drones is grafted (can be a 3GPP core network). The idea we had in mind is that LOOPS can be enabled in such mutli-hop wireless network (composed of drones) for the sake of performance optimization.
>
> Cheers,
> Med

So this use case probably needs more text. I think you're saying drones 
are an example of a network with continuously changing paths. To me, 
mitigating the impacts of handover likely does expose some interesting 
constraints on the designs for LOOPS as well as on the performance.  I 
haven't though about what that means wrt to using ECN and path information.

Gorry

>> -----Message d'origine-----
>> De : LOOPS [mailto:loops-bounces@ietf.org] De la part de Gorry
>> Fairhurst
>> Envoyé : lundi 27 juillet 2020 17:22
>> À : loops <loops@ietf.org>
>> Objet : [LOOPS] draft-li-tsvwg-loops-problem-opportunities and use-
>> cases.
>>
>> Thank you for the scenarios update in
>> draft-li-tsvwg-loops-problem-opportunities, I see you have updated the
>> text relating to satellite network segments. I now have some more
>> questions on scenarios based on the what is said in the most recent
>> ID:
>>
>>
>> (4) I see you also mention in the latest rev adds a use case for a
>> "fleet of drones" - I'm not quite sure what this is describing, maybe
>> you could expand how this works, and add some text to the draft.
>>
>> Gorry
>>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>