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

Rex Buddenberg <buddenbergr@gmail.com> Fri, 10 February 2017 18:52 UTC

Return-Path: <buddenbergr@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 C3360129A96 for <its@ietfa.amsl.com>; Fri, 10 Feb 2017 10:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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] 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 GbjLrsVxS4Jm for <its@ietfa.amsl.com>; Fri, 10 Feb 2017 10:52:42 -0800 (PST)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 BE05212958B for <its@ietf.org>; Fri, 10 Feb 2017 10:52:42 -0800 (PST)
Received: by mail-pf0-x236.google.com with SMTP id 189so11136782pfu.3 for <its@ietf.org>; Fri, 10 Feb 2017 10:52:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=bM6IET2T6Fxuf0/Q0a3iaEBhUUt12aU7jJiTrPfOBJ4=; b=UxF8PpKJzCAAiXQeiAuZ1nBuHOW0wen/H1wO9H7A1+9UPkoVFkhJN82i2ibGP/cifB myO7HlNH+1EXsfrJUO0/OqGiQ2N2EWt1j9wsFW6KDRGmX0ejPoMqPIQ1BPLBA0KzWQ3W Viv6TQJaiy5VnQqC50iIzVfFYxdsMY4EM/HQNzJHCbsQjGnNQtg3Jr+VXz0DsM7XsDIE IrmmO+cNdw56fQg5KKuiQZp1IvbfhvdmGIvMjW8awR8w/6TSfRvFmx/b/Xha2qN+qKyR lPJe5fabZoHXKKg9XIc/oI/UcF3INdJCTqIn5JykTeM7GTU7r67L/Jy74YX7Ft89QN2B OmaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=bM6IET2T6Fxuf0/Q0a3iaEBhUUt12aU7jJiTrPfOBJ4=; b=ejFEyzgEOBT8vq/9zqxznxnJD5r1OBgtpiNVk3PC9454sitUSnMTU4sL5Edl3tgP90 mIfWFCVLQmjynVA6LIMIHs4AUgqWGg2N8oc5GD+G3DEj+39BgQ7abGmj98WaUfA4gGAD RhP3QTRiauxA+Lv/WVMnxtwr2q6GdDyTzDaBvbl/612HrjTLNkTl2Sh24bXJR1rNm7B/ exEeGC4JikrDI2VjcSgg+urDuXSTPKTUfivEtsmtqYMIsuXAhA17rIoHTGZeZT2CQ52+ x8eiHsjSTk7lthATsuqKFSbaj872r4s3Z8jHfQ4fUiL2EHRs0jxN3c19bD4yCJfrrQFd dn+w==
X-Gm-Message-State: AMke39kNVWATHGczxfjyRgoL4lo/qLvxzI7dQUNPFtUU4fKB54OFE0iz57NfXDHePBYOcw==
X-Received: by 10.99.114.91 with SMTP id c27mr12588538pgn.163.1486752762313; Fri, 10 Feb 2017 10:52:42 -0800 (PST)
Received: from localhost.localdomain (c-71-198-163-21.hsd1.ca.comcast.net. [71.198.163.21]) by smtp.gmail.com with ESMTPSA id p15sm7067982pfk.58.2017.02.10.10.52.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 10:52:41 -0800 (PST)
Message-ID: <1486752760.2398.15.camel@gmail.com>
From: Rex Buddenberg <buddenbergr@gmail.com>
To: Jérôme Härri <jerome.haerri@eurecom.fr>, 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>, 'Michelle Wetterwald' <mlwetterwald@gmail.com>
Date: Fri, 10 Feb 2017 10:52:40 -0800
In-Reply-To: <011901d28393$c03d4e00$40b7ea00$@eurecom.fr>
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> <011901d28393$c03d4e00$40b7ea00$@eurecom.fr>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.18.5.2 (3.18.5.2-1.fc23)
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/qL8jz2Jr-hdv3BP4AiSyZe1CYq8>
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 18:52:45 -0000

Box <> function.

If you understand the fragility and warts in radionav systems (GPS,
Galileo, Glonass, Loran) then differential overlays to these systems
makes a lot of sense.  And the most attractive place to put the
differential reference receivers is in the roadside boxes.  The
reference receiver function is a sensor function, not a routing one.
But probably belongs in the same box.


On Fri, 2017-02-10 at 12:49 +0100, Jérôme Härri wrote:
> 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
> 
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its