Re: [ipwave] Higher bandwidth is a requirement, not a number to avoid
Alexandre Petrescu <alexandre.petrescu@gmail.com> Sat, 22 June 2019 15:37 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 899FC120058 for <its@ietfa.amsl.com>; Sat, 22 Jun 2019 08:37:00 -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 pgHo52KW1keP for <its@ietfa.amsl.com>; Sat, 22 Jun 2019 08:36:58 -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 63FD212004F for <its@ietf.org>; Sat, 22 Jun 2019 08:36:57 -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 x5MFaoQX040689; Sat, 22 Jun 2019 17:36:50 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C72FD20183C; Sat, 22 Jun 2019 17:36:50 +0200 (CEST)
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 B1D1D200D12; Sat, 22 Jun 2019 17:36:50 +0200 (CEST)
Received: from [132.166.86.2] ([132.166.86.2]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x5MFanYL003688; Sat, 22 Jun 2019 17:36:49 +0200
To: dickroy@alum.mit.edu, 'Jérôme Härri' <jerome.haerri@eurecom.fr>, 'John Kenney' <jkenney@us.toyota-itc.com>
Cc: 'its' <its@ietf.org>
References: <24309460-0172-60f1-f2e8-7cc57d152167@gmail.com> <00b601d521c6$7038a7a0$50a9f6e0$@eurecom.fr> <CAP6QOWQJwz9TFxhyaon4OMAjKHbjoqqpQKgkabU5GEWX38+n6Q@mail.gmail.com> <01de01d5276f$00911960$01b34c20$@eurecom.fr> <cf78903c-2fad-4203-f557-d613575e0ab7@gmail.com> <FAF38084B8CB4CD7A5B839173C68CADA@SRA6> <5776cb65-4194-60bf-ab6c-14d458f15c08@gmail.com> <A10EF784197244F5A0C6946F0BC3DFD9@SRA6>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <d47308ef-46d3-8921-3b40-e9ace4ba9099@gmail.com>
Date: Sat, 22 Jun 2019 17:36:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <A10EF784197244F5A0C6946F0BC3DFD9@SRA6>
Content-Type: multipart/alternative; boundary="------------D425D01557DCB588D4647DB5"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/7lWuPQBbTd6MKwH0o3-E1ShGoZ4>
Subject: Re: [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: Sat, 22 Jun 2019 15:37:01 -0000
When people write apps they need to know the bandwidth they could afford. E.g. I could be brave and try write skype with HD video and 192KHz audio but that would never work on 56Kbit/s bandwidth modem. Remark I am saying HD video, and people understand approximately what kind of bandwidth is needed, assuming a certain encoder ranging from no compression to high performance H. something. I am also saying 192KHz which is a sampling rate (not bandwidth) but people understand what kind od bandwidth that would request, depending on the encoder used ranging from RAW (no compression) to high quality open source compression in Ogg. Avoiding numbers of bandwidth available for IPv6 on ITS-G5 for high-quality chipsets means that probably the high quality chipsets never tried to send IPv6 on it. OTherwise they could have seen the bandwidth. On another hand, the bandwidth afforded by IPv6 iperf command on an open source DOT11a/10MHz driver is approximately 7mbit/s. This is why there is where the focus of a standard should be: on the open source DOT11a/10MHz basis, not on the high-quality chipsets. Of course, there are also the theoretical numbers (1Mbit/s, 2, 5, 16, 48, etc). They are obtained from calculations on numbers, not from experimenting. These numbers are theoretical upper limits of actual banwidth. It is well known these limits are never reached. Le 21/06/2019 à 22:09, Dick Roy a écrit : > > “What is the bandwidth afforded by an application using TCP/IPv6 on > > ITS-G5/DSRC?” > > Applications don’t have bandwidths. They may have information (aka > data) rate requirements often specified in [G/M/K]bits per second, not > in Hertz. Whether or not any particular network and transport layer > technology is used is irrelevant. Not sure what you are asking. > > RR > > -----Original Message----- > From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre Petrescu > Sent: Friday, June 21, 2019 2:30 AM > To: dickroy@alum.mit.edu; 'Jérôme Härri'; 'John Kenney' > Cc: 'its' > Subject: Re: [ipwave] Higher bandwidth is a requirement, not a number > to avoid > > Le 20/06/2019 à 16:49, Dick Roy a écrit : > > > -----Original Message----- > > > From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre Petrescu > > > Sent: Thursday, June 20, 2019 7:13 AM > > > To: Jérôme Härri; 'John Kenney' > > > Cc: 'its' > > > Subject: Re: [ipwave] Higher bandwidth is a requirement, not a number to > > > avoid > > > > > > Le 20/06/2019 à 15:49, Jérôme Härri a écrit : > > > > > > [...] > > > > > >> as they do not really represent > > > > > >> what an automotive-grade ITS-G5/DSRC is really capable of doing. > > > > > > What is the bandwidth of IPv6 demonstrated on ITS-G5/DSRC? > > > > > > */[RR] IPV6 does not “have a bandwidth”. The ITS-G5/DSRC access layers > > > currently have 10MHz (and 20MHz in the US)bandwidth channels specified > > > if that’s your question./* > > What is the bandwidth afforded by an application using TCP/IPv6 on > > ITS-G5/DSRC? > > Alex > > > > > > Alex > > > > > > _______________________________________________ > > > > > > its mailing list > > > > > > its@ietf.org > > > > > > https://www.ietf.org/mailman/listinfo/its > > > > > _______________________________________________ > > its mailing list > > its@ietf.org > > https://www.ietf.org/mailman/listinfo/its >
- [ipwave] Higher bandwidth is a requirement, not a… Alexandre Petrescu
- Re: [ipwave] Higher bandwidth is a requirement, n… Jérôme Härri
- Re: [ipwave] Higher bandwidth is a requirement, n… John Kenney
- Re: [ipwave] Higher bandwidth is a requirement, n… Jérôme Härri
- Re: [ipwave] Higher bandwidth is a requirement, n… Alexandre Petrescu
- Re: [ipwave] Higher bandwidth is a requirement, n… Alexandre Petrescu
- Re: [ipwave] Higher bandwidth is a requirement, n… Jérôme Härri
- Re: [ipwave] Higher bandwidth is a requirement, n… Alexandre Petrescu
- Re: [ipwave] Higher bandwidth is a requirement, n… Alexandre Petrescu
- Re: [ipwave] Higher bandwidth is a requirement, n… Alexandre Petrescu