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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 20 February 2017 15:51 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 B886F1296B3 for <its@ietfa.amsl.com>; Mon, 20 Feb 2017 07:51:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level:
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 8FsNwunL54IF for <its@ietfa.amsl.com>; Mon, 20 Feb 2017 07:51:55 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCDBF129550 for <its@ietf.org>; Mon, 20 Feb 2017 07:51:54 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id v1KFpqQ1014325 for <its@ietf.org>; Mon, 20 Feb 2017 16:51:52 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 2D3A920A1CC for <its@ietf.org>; Mon, 20 Feb 2017 16:51:52 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 23AA82035BB for <its@ietf.org>; Mon, 20 Feb 2017 16:51:52 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v1KFppx1010315 for <its@ietf.org>; Mon, 20 Feb 2017 16:51:52 +0100
To: its@ietf.org
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <d3cdd725-160f-b3cc-540b-00bbcec797c7@cea.fr> <CAF5de8t4TjMK5uLc4XK6O7WAsrd6LPCM29=UoNNg7VZS+6VVYQ@mail.gmail.com> <025701d283bd$c63f9900$52becb00$@gmail.com> <CAF5de8viG3ksKg-Kf=6-tRK9+C-xkrWYucdEsS94c8bkrNkPyQ@mail.gmail.com> <CAGFPJ8v4J94QkEbU393e4UAHcNBzpJHY4Wm_piJmDVNPQdMwRQ@mail.gmail.com> <005301d286d1$efd116b0$cf734410$@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <e7de52bf-4178-4937-4edf-ab8c6c38c13e@gmail.com>
Date: Mon, 20 Feb 2017 16:51:46 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <005301d286d1$efd116b0$cf734410$@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/l3GaREX7uhbMgOls2ArZqewVSRw>
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, 20 Feb 2017 15:51:58 -0000


Le 14/02/2017 à 15:52, François Simon a écrit :
> In this figure the router would be the item at the right-hand, bottom
> corner “Backhaul Local Communications”.   Fygs

In the boxes I work with the router is not only the 'backhaul router' 
but also the Road-Side Unit that is pictured in that figure.

That RSU has 1 ethernet interface and 2 802.11-OCB interfaces, and runs 
IP routing (not bridging) between these interfaces.

There are many scalability advantages and interference avoidance to 
using routing, and not bridging, in that RSU.

Alex

>
>
>
> *From:*Michelle Wetterwald [mailto:michelle.wetterwald@gmail.com]
> *Sent:* Tuesday, February 14, 2017 6:31 AM
> *To:* François Simon <fygsimon@gmail.com>
> *Subject:* Fwd: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term
>
>
>
> Hi François,
>
> Thank you for sending me this picture, but I cannot see any RSR.
>
> I can only see an RSU, which may host an RSR, as I mentioned to Alex in
> my email below.
>
> Can you help me locate the RSR?
>
> Thanks, Michelle
>
>
> Michelle Wetterwald
> michelle.wetterwald@gmail.com <mailto:michelle.wetterwald@gmail.com>
> ----
> Senior expert in networking and telecommunications
>
>
>
> ---------- Forwarded message ----------
> From: *Michelle Wetterwald* <mlwetterwald@gmail.com
> <mailto:mlwetterwald@gmail.com>>
> Date: Tue, Feb 14, 2017 at 12:27 PM
> Subject: Fwd: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term
> To: Michelle Wetterwald <michelle.wetterwald@gmail.com
> <mailto:michelle.wetterwald@gmail.com>>
>
>
>
> ---------- Forwarded message ----------
> From: *François Simon* <fygsimon@gmail.com <mailto:fygsimon@gmail.com>>
> Date: 2017-02-10 17:50 GMT+01:00
> Subject: RE: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term
> To: Michelle Wetterwald <mlwetterwald@gmail.com
> <mailto:mlwetterwald@gmail.com>>
>
> See one of US FHWA view of RSE. RSR in left-hand bottom corner.   fygs
>
>
>
> *From:*its [mailto:its-bounces@ietf.org <mailto:its-bounces@ietf.org>]
> *On Behalf Of *Michelle Wetterwald
> *Sent:* Friday, February 10, 2017 6:19 AM
> *To:* Alexandre Petrescu <alexandre.petrescu@gmail.com
> <mailto:alexandre.petrescu@gmail.com>>
> *Cc:* its@ietf.org <mailto:its@ietf.org>
> *Subject:* Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 RSU term
>
>
>
> 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
>
>
>
>
> --
>
> Michelle Wetterwald
>
> michelle.wetterwald@gmail.com <mailto:michelle.wetterwald@gmail.com>
>
>
>
>
> --
>
> Michelle Wetterwald
>
> michelle.wetterwald@gmail.com <mailto:michelle.wetterwald@gmail.com>
>
>
>
>
>
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its
>