Re: [ipwave] Adaptive RESTful Real-time Live Streaming for Things (A-REaLiST)'
Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 24 January 2019 11:17 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91CEC1310EB for <its@ietfa.amsl.com>; Thu, 24 Jan 2019 03:17:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, 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 Kn3HpdJas4ZW for <its@ietfa.amsl.com>; Thu, 24 Jan 2019 03:17:51 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E401B130E13 for <its@ietf.org>; Thu, 24 Jan 2019 03:17:50 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x0OBHmfP054685 for <its@ietf.org>; Thu, 24 Jan 2019 12:17:48 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7B9B0204B1C for <its@ietf.org>; Thu, 24 Jan 2019 12:17:48 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 6F867200CFF for <its@ietf.org>; Thu, 24 Jan 2019 12:17:48 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x0OBHm7R032759 for <its@ietf.org>; Thu, 24 Jan 2019 12:17:48 +0100
To: its@ietf.org
References: <OF3CBB4EB2.92610A3E-ON6525838C.0016A8F0-6525838C.0016B40C@tcs.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <08d7924f-55c5-f89a-c2f6-cccb3fa4d071@gmail.com>
Date: Thu, 24 Jan 2019 12:17:48 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <OF3CBB4EB2.92610A3E-ON6525838C.0016A8F0-6525838C.0016B40C@tcs.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/HZsFi2OzuV6EjCJcIYSVeMrGppU>
Subject: Re: [ipwave] Adaptive RESTful Real-time Live Streaming for Things (A-REaLiST)'
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2019 11:17:54 -0000
Le 24/01/2019 à 05:07, Abhijan Bhattacharyya a écrit : > Dear list, > We submitted a draft in CoRE with a technical proposal for efficient > transfer of time-series stream and presented in IETF Bangkok. The > immediate use case that we considered was to transfer First Person View > (FPV) video from a remote drone to a control unit over IP based > infrastructure. We built it on CoAP leveraging some of CoAP's unique > features. Hi, Thank you for the message. I have seen another drone from DLR that communicates with a van, but not using CoAP. It uses TCP/IP family of protocols. I understand the need to transfer video (First-Person View, FPV), but I do not understand how CoAP helps with video. Video over IPv6 over OCB works fine between vehicles. In the future, with the hopeful development of 802.11-NGV (Next Generation Vehicular), I expect latencies in the order of hundreds of micro-seconds, and 1Gbps bandwidths. I think video over IP, and lidar streams over IP, would take advantage of that. Why CoAP? > The ambition is to create a protocol stack that would be > equally good in sending small sporadic bytes (sensor data) as well as > streaming infinite time-series (like live video) while ensuring good QoE > despite being low on resource consumption. But such a multi-feature protocol is also claimed by Google with QUIC protocol. Why not QUIC? > The draft is available here: > https://tools.ietf.org/html/draft-bhattacharyya-core-a-realist-00 > > Probably, the use case that we had in mind and the technology we > proposed, both can be extended to the purview of this WG. > > Requesting your views on this draft please.. If relevant then we can > present this draft in Prague. I can look at the draft, but I need to understand why CoAP? Video per se is not a sufficient reason to use CoAP, I think. (and yes, I do agree there are strong IP requirements for video in drones, like multi-cameras, multiple laser, infrared, and others) Alex > > Here is the abstract for your ready reference: > > This draft presents extensions to Constrained Application Protocol > (CoAP) to enable RESTful Real-time Live Streaming for improving the > Quality of Experience (QoE) for delay-sensitive Internet of Things > (IoT) applications. The overall architecture is termed ''Adaptive > RESTful Real-time Live Streaming for Things (A-REaLiST)''. It is > particularly designed for applications which rely on real-time > augmented vision through live First Person View (FPV) feed from > constrained remote agents like Unmanned Aerial Vehicle (UAV), etc. > These extensions provide the necessary hooks to help solution > designers ensure low-latency transfer of streams and, for contents > like video, a quick recovery from freeze and corruption without > incurring undue lag. A-REaLiST is an attempt to provide an > integrated approach to maintain the balance amongst QoE, resource- > efficiency and loss resilience. It provides the necessary hooks to > optimize system performance by leveraging contextual intelligence > inferred from instantaneous information segments in flight. These > extensions equip CoAP with a standard for efficient RESTful > streaming for Internet of Things (IoT) contrary to HTTP-streaming in > conventional Internet. > > > > > Thank you. Looking forward. > > P.S. The work has been accepted and presented in Wi-UAV workshop in > Globecom, Dec, 2018. The public link to the paper is yet to be available. > > With Best Regards > Abhijan Bhattacharyya > Consultant / Scientist, > {Internet Protocols | 5G | Standardization}, > TCS Research, > Tata Consultancy Services > Building 1B,Ecospace > Plot - IIF/12 ,New Town, Rajarhat, > Kolkata - 700160,West Bengal > India > Ph:- +91 33 66884691 > Cell:- +919830468972 | +918583875003 > Mailto: abhijan.bhattacharyya@tcs.com <mailto:abhijan.bhattacharyya@tcs.com> > Website: http://www.tcs.com > ____________________________________________ > Experience certainty. IT Services > Business Solutions > Consulting > ____________________________________________ > > =====-----=====-----===== > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > > > _______________________________________________ > its mailing list > its@ietf.org > https://www.ietf.org/mailman/listinfo/its >
- [ipwave] Adaptive RESTful Real-time Live Streamin… Abhijan Bhattacharyya
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Alexandre Petrescu
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Michael Richardson
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Abhijan Bhattacharyya
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Alexandre Petrescu
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Carsten Bormann
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Abhijan Bhattacharyya
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Alexandre Petrescu
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Abhijan Bhattacharyya
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Alexandre Petrescu
- Re: [ipwave] Adaptive RESTful Real-time Live Stre… Abhijan Bhattacharyya