Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 absence of addressing the multi-channel service of 802.11 OCB

Jérôme Härri <jerome.haerri@eurecom.fr> Sat, 11 February 2017 13:18 UTC

Return-Path: <jerome.haerri@eurecom.fr>
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 C1DFB12961D for <its@ietfa.amsl.com>; Sat, 11 Feb 2017 05:18:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 jvqZlmlq0aE5 for <its@ietfa.amsl.com>; Sat, 11 Feb 2017 05:18:09 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp3.eurecom.fr [193.55.113.213]) by ietfa.amsl.com (Postfix) with ESMTP id 1486B12978B for <its@ietf.org>; Sat, 11 Feb 2017 05:18:08 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,146,1484002800"; d="scan'208";a="5760905"
Received: from waha.eurecom.fr (HELO smtps.eurecom.fr) ([10.3.2.236]) by drago2i.eurecom.fr with ESMTP; 11 Feb 2017 14:18:06 +0100
Received: from xerus29 (LFbn-1-6946-250.w90-116.abo.wanadoo.fr [90.116.128.250]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtps.eurecom.fr (Postfix) with ESMTPSA id 8ADD483B; Sat, 11 Feb 2017 14:18:07 +0100 (CET)
From: Jérôme Härri <jerome.haerri@eurecom.fr>
To: 'François Simon' <fygsimon@gmail.com>, its@ietf.org
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <3046d8b9-0079-99f0-9e9a-f5f88c9c8f5a@cea.fr> <012301d28394$4c0a7d40$e41f77c0$@eurecom.fr> <02bc01d283d8$c7a5eb80$56f1c280$@gmail.com>
In-Reply-To: <02bc01d283d8$c7a5eb80$56f1c280$@gmail.com>
Date: Sat, 11 Feb 2017 14:18:06 +0100
Organization: EURECOM
Message-ID: <00ab01d28469$48d35e50$da7a1af0$@eurecom.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwGpzVvTAW+TjdkBYR2VCqBH2aSQ
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/rf-WA3Kdt2MJDy7ni2wBlep6edU>
Cc: 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 absence of addressing the multi-channel service of 802.11 OCB
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.17
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, 11 Feb 2017 13:18:11 -0000

Dear François,

Totally agree. But this is neither DSRC nor 802.11 OCB. This is the IEEE
WAVE stack IEEE 1609.4, which as far as I understand this IETF WG does not
assume to use (and neither the ETSI ITS stack). 

But actually, It is very simple to use different channels using OCB. As
there is no BSS (or IBSS), you can change channel simply by indicating to
the OCB a new channel...as there is no further process required to transmit
on the new channel. 

Yet, the challenge is to be sure that the 'receivers' are also on the
'other' channel, as otherwise, we will transmit and nobody will be there to
receive. That was the objective of the work done in IEEE 1609.4. But such
coordination can also be done purely on an IP(v6) stack, as both Tx and Rx
could be notified on the right channel to get the right message...
A simple indication to OCB on which channel to move would be enough. Even a
multi-channel monitoring can be done using IP(v6) stack, where a
higher-layer service would ask OCB to periodically switch between channel
and monitor  'something'. 

Well, long story short, I do not think multi-channel 'operation' should be
part of this draft. But we could describe how IPv6 can 'request' a channel
switch to OCB. That could indeed be worth mentioning this explicitly. 

BR,

Jérôme

 
-----Original Message-----
From: François Simon [mailto:fygsimon@gmail.com] 
Sent: Friday 10 February 2017 21:04
To: 'Jérôme Härri'
Cc: 'Alexandre Petrescu'; fygsimon@gmail.com
Subject: RE: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 absence of
addressing the multi-channel service of 802.11 OCB

Multi-channel means that a single device is capable of maintaining multiple
"conversations" quasi-simultaneously.  In the US, the MAC extension (IEEE
1609.4) allows you to support multiple channels under the control of CCH (Ch
178) - TDM.  The problem with this, is you limit your actual overall
transmission rate.  The accepted practice in the US,  is that one radio is
dedicated to a permanent channel to get the maximum data rate (e.g. CH 172)
and used for high-priority applications (i.e. Safety).  Another radio, for
lower priority applications, is allowed to switch channels.  In addition,
each channel can support up to four EDCA parameter sets.  Very "nifty" but
hell to maintain all the state machines!

Fygs



-----Original Message-----
From: its [mailto:its-bounces@ietf.org] On Behalf Of Jérôme Härri
Sent: Friday, February 10, 2017 6:53 AM
To: 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>; its@ietf.org
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 absence of
addressing the multi-channel service of 802.11 OCB

Hello Alex,

What do you mean with multi-channel? OCB does not provide any multi-channel
service. Higher-layer services do (IEEE WAVE or ETSI)...OCB only assume that
the frequency to be used is 'known', so using OCB actually means knowing a
set of channels where to send OCB-related packets...I am not sure if this
could be called a multi-channel service...

However, we should mention that IPv6 would intend to offer such a
service...if this is what you meant, I agree with you.

Best Regards.

Jérôme

-----Original Message-----
From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre Petrescu
Sent: Friday 10 February 2017 12:13
To: its@ietf.org
Subject: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 absence of
addressing the multi-channel service of 802.11 OCB

draft-ietf-ipwave-ipv6-over-80211ocb-00
absence of addressing the multi-channel service of 802.11 OCB

Hello IPWAVErs,

We received a comment stating that this document does not really address the
multi-channel service that 802.11 OCB is capable of providing.

I agree with the comment.

I have not seen other IPv6-over-foo documents addressing channel issues.

There is no IPv6-over-WiFi RFC, which could address them.

In vehicular networks implementations there is often a careful planning of
channel allocation to avoid interference.  Dynamic channel use schemes
exist.

Yours,

Alex



_______________________________________________
its mailing list
its@ietf.org
https://www.ietf.org/mailman/listinfo/its