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

Jérôme Härri <jerome.haerri@eurecom.fr> Fri, 10 February 2017 11:49 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 7D02A1295ED for <its@ietfa.amsl.com>; Fri, 10 Feb 2017 03:49:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 ga0qD_l8j-Zg for <its@ietfa.amsl.com>; Fri, 10 Feb 2017 03:49:37 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp3.eurecom.fr [193.55.113.213]) by ietfa.amsl.com (Postfix) with ESMTP id DFA871289C4 for <its@ietf.org>; Fri, 10 Feb 2017 03:49:36 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,141,1484002800"; d="scan'208";a="5756054"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago2i.eurecom.fr with ESMTP; 10 Feb 2017 12:49:35 +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 93AD01A44; Fri, 10 Feb 2017 12:49:35 +0100 (CET)
From: Jérôme Härri <jerome.haerri@eurecom.fr>
To: 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>, 'Michelle Wetterwald' <mlwetterwald@gmail.com>
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <d3cdd725-160f-b3cc-540b-00bbcec797c7@cea.fr> <CAF5de8t4TjMK5uLc4XK6O7WAsrd6LPCM29=UoNNg7VZS+6VVYQ@mail.gmail.com> <9fe84c68-897b-d5e3-ec5f-ba4e5af62f78@gmail.com>
In-Reply-To: <9fe84c68-897b-d5e3-ec5f-ba4e5af62f78@gmail.com>
Date: Fri, 10 Feb 2017 12:49:35 +0100
Organization: EURECOM
Message-ID: <011901d28393$c03d4e00$40b7ea00$@eurecom.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwKQowfUAiMWYkYC07H/MKAtzGUw
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/b6wKYQq47VZiUiXbxlby4-kmYKc>
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: Fri, 10 Feb 2017 11:49:39 -0000

Hi Alex,

It could actually be two different terms, depending of what we want to say in the draft. The RSU is no longer a pure C-ITS name, as even LTE-V2X adopted the LTE-UE operating in RSU mode for LTE-V2V communications (meaning you do not need to be a eNB/base station to be a RSU). 
I would tend to think that the RSU is more a function/service than an actual technology...but as I think the debate could be complex and suggest to follow Michelle suggestion to keep the RSU as a 'bigger' entity, and if you need it, a RSR as a potential sub-set of a RSU. As Michelle said, a RSU is not a router  by default...

BR,

Jérôme

-----Original Message-----
From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre Petrescu
Sent: Friday 10 February 2017 12:37
To: Michelle Wetterwald
Cc: its@ietf.org
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term

Hi Michelle,

Thank you for the suggestion.

But making RSR a component of RSU is different than making RSU a component of RSR, right?

Despite the widespread belief that RSU would have something to do with IP and Internet, rarely if ever was there an RSU connected to Internet that forwarded IP packets - most RSUs are disconnected from the Internet (the supposedly 'slaves' at FHWA) and the ones that are connected to the Internet (supposedly the 'masters' at FHWA) are so only in order to be SNMP-managed remotely, but not to forward.

If we know of some RSU which has this 'forwarding' flag set to 1, then we should talk about it, and call it a Router.

The "ITS station" term is not a term at IETF.  We could re-use the term "ITS station", but I would like to know whether "ITS Station" is a Router or a Host?

Yours,

Alex

Le 10/02/2017 à 12:18, Michelle Wetterwald a écrit :
> Hi Alex,
>
> Actually, an RSU is generally more than an RSR as it is an ITS station 
> per se and may contain upper (e.g. service or even
> application) layers. I suggest to keep the definition of RSU in the 
> text, as it is a widely used term, but clarify that an RSR could be 
> one of the components of an RSU.
>
> Best regards, Michelle
>
> 2017-02-10 11:34 GMT+01:00 Alexandre Petrescu 
> <alexandre.petrescu@gmail.com
> <mailto:alexandre.petrescu@gmail.com>>:
>
> 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
>
>
> _______________________________________________ its mailing list 
> its@ietf.org <mailto:its@ietf.org> 
> https://www.ietf.org/mailman/listinfo/its
> <https://www.ietf.org/mailman/listinfo/its>
>
>
>
>
> -- Michelle Wetterwald michelle.wetterwald@gmail.com 
> <mailto:michelle.wetterwald@gmail.com>

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