Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term

Jérôme Härri <jerome.haerri@eurecom.fr> Mon, 13 February 2017 15:42 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 D29FE1296E3 for <its@ietfa.amsl.com>; Mon, 13 Feb 2017 07:42:03 -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 zEa0jZh0bQex for <its@ietfa.amsl.com>; Mon, 13 Feb 2017 07:42:01 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp3.eurecom.fr [193.55.113.213]) by ietfa.amsl.com (Postfix) with ESMTP id 7529F1296EC for <its@ietf.org>; Mon, 13 Feb 2017 07:41:59 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,156,1484002800"; d="dat'59?scan'59,208,59";a="5769050"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago2i.eurecom.fr with ESMTP; 13 Feb 2017 16:41:57 +0100
Received: from xerus29 (xerus29.eurecom.fr [172.17.31.38]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by monza.eurecom.fr (Postfix) with ESMTPSA id 8FE8BB53; Mon, 13 Feb 2017 16:41:57 +0100 (CET)
From: Jérôme Härri <jerome.haerri@eurecom.fr>
To: 'François Simon' <fygsimon@gmail.com>, 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <d3cdd725-160f-b3cc-540b-00bbcec797c7@cea.fr> <01fa01d283b8$74b02e10$5e108a30$@gmail.com> <64f02795-96fe-03c3-c139-eb438c16a87e@gmail.com> <034301d283fe$0d319210$2794b630$@gmail.com> <b85e580b-5913-5c09-193f-f08545d1dd08@gmail.com> <006c01d2860e$7d6d1290$784737b0$@gmail.com>
In-Reply-To: <006c01d2860e$7d6d1290$784737b0$@gmail.com>
Date: Mon, 13 Feb 2017 16:41:57 +0100
Organization: EURECOM
Message-ID: <004001d2860f$b591ac20$20b50460$@eurecom.fr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0041_01D28618.17561420"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwKQowfUAakyEegCEiTzOwI/mWiqAS11jY6gITSQkIAAAm5g
Content-Language: en-us
X-MS-TNEF-Correlator: 00000000B6880C6704F327408FB89A844E48C913070044581432800C7847B83418086494B56000000000010B000044581432800C7847B83418086494B560000000BE8FC30000
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/zrIfN0ERGp_LPF0HhiUfsO3MfV8>
Cc: its@ietf.org
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term
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: Mon, 13 Feb 2017 15:42:04 -0000

Following your feedback,

Whereas a full MIMO remains arguable at this stage (my personal view I have
to admit), as one would need to orient the beams and learn the channel state
which is constantly moving (basically tracking a vehicle), a key benefit of
having two antennas on a RSU (and actually on a OBU) could be antenna
diversity with space-time coding (e.g. 2x1). Unfortunately, OCB does not
allow this (and neither MIMO). So, multi-antennas so far can only be used
for multi-transceivers as far as I know. 

But as we aim at beyond DAY 2, we never know what the future holds...so,
having multiple antennas, with different patterns might be expected in the
future. We should leave it open. 

BR,

Jérôme
_____________________________________________
From: its [mailto:its-bounces@ietf.org] On Behalf Of François Simon
Sent: Monday 13 February 2017 16:33
To: 'Alexandre Petrescu'
Cc: fygsimon@gmail.com; its@ietf.org
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term


Two Antennae: Multiple Input Multiple Output (MIMO) technology - The
antennas at each end of the communications circuit are combined to minimize
errors and optimize data speed.

Non-intersection RSUs:

 << File: Untitled attachment 00062.txt >> 

 << OLE Object: Picture (Device Independent Bitmap) >> 

 << OLE Object: Picture (Device Independent Bitmap) >> 

-----Original Message-----
From: Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com] 
Sent: Saturday, February 11, 2017 3:42 AM
To: François Simon <fygsimon@gmail.com>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term



Le 11/02/2017 à 01:30, François Simon a écrit :
> Both are arguable.
>
> a) Antennas:  Depend on applications.  In the picture, this is mostly 
> for intersections where OBE's transmissions comes from all directions.  
> An omni-directional is more appropriate for tolling applications.

If this is for intersection, then why are there _two_ antennas, each omni?
IT should be 180deg for each.  It makes no sense to put 2 omnis. 
One omni would be sufficient.

And do they have a figure which is _not_ for intersection? (i.e. for along
the road?)

Alex

> b) boosters on surge-suppressor......; I do not see the point.  I miss 
> the point.
> Fygs
>
> -----Original Message-----
> From: Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com]
> Sent: Friday, February 10, 2017 11:28 AM
> To: François Simon <fygsimon@gmail.com>
> Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term
>
> Thanks for the note.
>
> As a side note, note that omni antennas dont make much sense on pole 
> along roads - should be sector antennas.  This is a common mistake at many
sites.
>
> In addition to surge-suppressors one should use boosters too, to 
> extend reach.
>
> Le 10/02/2017 à 17:12, François Simon a écrit :
>> I would be very careful to replace RSU with RSR systematically 
>> (global change).  The figure below shows how, in the US, FHWA sees 
>> the implementation (one of several):
>>
>>
>> In this figure, the RSR is in the left hand bottom corner.
>>
>> Fygs
>>
>>
>>
>> -----Original Message-----
>> From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre 
>> Petrescu
>> Sent: Friday, February 10, 2017 5:34 AM
>> To: its@ietf.org
>> Subject: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term
>>
>> draft-ietf-ipwave-ipv6-over-80211ocb-00
>> RSU term
>>
>> Hello IPWAVErs,
>>
>> We received multiple comments about the RSU term.  The strongest 
>> issue is that apparently there are conflicts between our assumption 
>> of RSU to be a router and FHWA(?) thinking RSU is more like an 
>> interface to a router, or something like a master-RSU controlling
(slave?) RSUs.
>> Unless FHWA tells us they agree RSU is a router, I will modify the
>> following:
>>
>> Old:
>>> 2.  Terminology
>> [...]
>>> RSU: Road Side Unit.
>>
>> New:
>>> RSR: Road Side Router; an IP router equipped with, or connected to, 
>>> at least one interface that is 802.11 and that is an interface that 
>>> operates in OCB mode.
>>
>> and substitute RSR for RSU throughout.
>>
>> This old 'RSU' term, now RSR, is absolutely needed in the draft when 
>> discussing IP handovers and Mobile IP.
>>
>> Alex
>>
>>
> << OLE Object: Picture (Device Independent Bitmap) >>