[ipwave] Higher bandwidth is a requirement, not a number to avoid

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 12 June 2019 18:05 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 7D248120075 for <its@ietfa.amsl.com>; Wed, 12 Jun 2019 11:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] 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 2V72OTq--FJx for <its@ietfa.amsl.com>; Wed, 12 Jun 2019 11:05:30 -0700 (PDT)
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 5B44A120025 for <its@ietf.org>; Wed, 12 Jun 2019 11:05:30 -0700 (PDT)
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 x5CI5SCP175389 for <its@ietf.org>; Wed, 12 Jun 2019 20:05:28 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 106952045CA for <its@ietf.org>; Wed, 12 Jun 2019 20:05:28 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 054982037EF for <its@ietf.org>; Wed, 12 Jun 2019 20:05:28 +0200 (CEST)
Received: from [10.8.68.66] ([10.8.68.66]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x5CI5Rgd010862 for <its@ietf.org>; Wed, 12 Jun 2019 20:05:27 +0200
To: "its@ietf.org" <its@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <24309460-0172-60f1-f2e8-7cc57d152167@gmail.com>
Date: Wed, 12 Jun 2019 20:05:27 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------FB2DB0FAB8B41B2AC62CAF7D"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/CEKWdLEzz_081YlozBoi9aJWw6I>
Subject: [ipwave] Higher bandwidth is a requirement, not a number to avoid
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: Wed, 12 Jun 2019 18:05:33 -0000

Hi,

With respect to the channel width 20MHz capability, which would probably 
offer higher bandwidth and less latency.

I received in private several replies from at least 4 people.  I also 
had a face to face meeting with our partners.

I want to say something so I am better understood: it is a _requirement_ 
to get higher bandwidth; it is not a number to avoid.

If the app people send 10000 RTMAPS 1480byte sized IP messages per 
second then it is so because they need it.  Yes, that is 10KHz messages, 
and not 20Hz; yes, that is 1428byte IP message and not CAM/BSM 633byte.  
And yes, that must be satisfied.  We should not tell these people to 
reduce their outputs.  Reducing their outputs will indeed guarantee 
better latency for ping, but they will be less able to transmit valuable 
data.

We should not tell app people to throttle (reduce) their output down to 
20 messages per second (20Hz).  That is nonsense out of standard 
documents.  The 20Hz/10Hz/1Hz is data relevant out of GPS chipsets - GPS 
has nothing to do with OCB.

If in the first platooning tests it worked with less data transmitted, 
also the convoy was less performing.  We need rich data transmitted, not 
poor data.  We need lidar data out of the lidar directly on OCB, and 
similar other things.

Alex