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

François Simon <fygsimon@gmail.com> Mon, 13 February 2017 15:33 UTC

Return-Path: <fygsimon@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 B91E712961D for <its@ietfa.amsl.com>; Mon, 13 Feb 2017 07:33:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 wv3F1ylv-bY7 for <its@ietfa.amsl.com>; Mon, 13 Feb 2017 07:33:14 -0800 (PST)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FA5012965A for <its@ietf.org>; Mon, 13 Feb 2017 07:33:14 -0800 (PST)
Received: by mail-qk0-x22f.google.com with SMTP id 11so96215611qkl.3 for <its@ietf.org>; Mon, 13 Feb 2017 07:33:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=0aFCKLd9hf+eu7Elg8NurxRJQlDYRSzYVV1Oa4eITp0=; b=KwUzk99JjYOj1dTnyyKDj+467J1qzcqOZ5qL09tf99yVu/S/OVoNLj9JrBslR+8pVE lEgTXfA5q2+pIcn0ydTz7VK5b2rHGyYPzogz2HNTTqQlQFjvy5/LLAQdwBQo2UqRK3Js 0ehnWQ0FdvuA6/+lERhlPKA9KEzkdccbGP4+13cd9AMwM5F+CbmjAit8+jEUP/B+WwYY v0sNujQTrUNzC0uzksCVP1s5H5mnw/26lDzgVZqulxyL7w1QgHgQ2hQMVmTEFEHzISQ6 HlbKGR7nvxFSpVuo1KwaPFCrmSA7+i9lr9KRpjsFOwHiNW8NTguEWDJlCOBYFbRkdjQQ Z17g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=0aFCKLd9hf+eu7Elg8NurxRJQlDYRSzYVV1Oa4eITp0=; b=s0jlSLjpHkQF/5WIjzQGNscwhypxh98zNu9pPZ7QAWmIExj7WpQJ+iPGgJ++4YaePe pwV2zzq5vtxgebED2O+xWHl1Z03bO01y52n1cvRLpfD8UO95uLuwnnOgWMnpM4+DadKI lY9ZZY8Kibh01+xX5rYSapKHnfyDQqoeaI26gAEjazIZ8ZcfCaML9x0WavHVPYNvaupO jZox7TiqZPaenrbntPCCc2EQmORgH/7V9220oJFpeFbeD+cd6cXCFDLZEM4LKY68QpNA DTSvlLDy6fHYGin3QCkjEmZplGmyfUdQ+B/xW65cGzL7hCof1VwHDS3Yisn/xm6zvANa v95w==
X-Gm-Message-State: AMke39leorZ7xzVD6c7yVnnm0Csz7ueYbL/cvScoeNUTU+le3tyutAsq8POFDhG4QfwLbg==
X-Received: by 10.55.133.130 with SMTP id h124mr23606395qkd.91.1486999993092; Mon, 13 Feb 2017 07:33:13 -0800 (PST)
Received: from FrancoisPC (pool-173-66-69-120.washdc.fios.verizon.net. [173.66.69.120]) by smtp.gmail.com with ESMTPSA id 11sm7703624qke.38.2017.02.13.07.33.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 07:33:11 -0800 (PST)
From: François Simon <fygsimon@gmail.com>
To: '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>
In-Reply-To: <b85e580b-5913-5c09-193f-f08545d1dd08@gmail.com>
Date: Mon, 13 Feb 2017 10:33:13 -0500
Message-ID: <006c01d2860e$7d6d1290$784737b0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_006D_01D285E4.94995480"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwKQowfUAakyEegCEiTzOwI/mWiqAS11jY6gITSQkA==
Content-Language: en-us
X-MS-TNEF-Correlator: 000000003F7DF41A30B2324180A278D67E8F76E80700C3B68E10F77511CEB4CD00AA00BBB6E600000000000D0000B6139B33E2635F4EADB76554EF628CAA000000000AE40000
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/LXn5oQkHL1FnYDSydexf8VcKGpA>
Cc: fygsimon@gmail.com, 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:33:18 -0000

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:

 

 

 

-----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 <mailto: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 <mailto: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
>>
>>
>