Re: [ipwave] 回复:Re: RSU minor textual issue

François Simon <fygsimon@gmail.com> Thu, 18 May 2017 17:36 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 745CB127B31 for <its@ietfa.amsl.com>; Thu, 18 May 2017 10:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 w5t4w1o-qXiD for <its@ietfa.amsl.com>; Thu, 18 May 2017 10:36:17 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 69C8E128BB7 for <its@ietf.org>; Thu, 18 May 2017 10:30:37 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id f55so39916870qta.3 for <its@ietf.org>; Thu, 18 May 2017 10:30:37 -0700 (PDT)
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=TIOQ/ECfIT09gD/Q/7qvUYywjBPyOBqSAeGi3kkT4Ag=; b=LjVYAYvFmKhq3dlJghKS8smXNqKmJfDJKZgjekvJPrsTiJyV1dayshWP0uGlTxo7tS P+zik3oGt4NAWXNZldYWj9Z6uHf965ePimjKThrUVZmmRW94usEopR8hDEDrYQoUIc7W NrWB/LqE749vp0mM7XE8DD2PpPRn5gGasqhorAgLSAgfXO1W+e3GKOykZHLg2xcoIlRI KcnT+7wLTH/Q/UL2K9Rx+PkWMe7M2ylLmCQfh90tRsVAgZPMw3ycoLWjnjCKoUC3wte1 D/Kj1SuZhKJfniVT/kt03F7XcnnZ5y6R1jEY3ngaaoPd60UxptjsClIwNn058gIAZkEf xu2A==
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=TIOQ/ECfIT09gD/Q/7qvUYywjBPyOBqSAeGi3kkT4Ag=; b=NV0K9F7dUEoN+aq6KXQjMdvuglS+zUtZau/Y+iZuHMDu/GhWN01oWUmyhDZcjI/08Q rndB5EY7Y1Ohh6j+6mPz/3rn4ktBPqZbDbreX/cZqQz9Vb8V9xuWj9y5SS5itfwV7n07 Pe2vcb5IQuBTNFkKHoKqR6x6p1iccZA4Q0TGDu7jI/4VygbZAYQTzGlax7iTp/WZbzBh E7dDLNfc2lcQ/BgYbkltBjYRQMkG1wYH7csHL7T89vVVRBdpjpJgG9+PJ4atkYnKSI94 5+ZPZYw5Qz1T3TrI2I8qcDzCKQ9Jm++pk5Oztzq3LrJ9VrYvNv37Pyxc5ybFR9fJ1Wv/ SLfQ==
X-Gm-Message-State: AODbwcBeEi/WXCkWmEFgEb0vu2YcCrDA1DFtKxamM1LFRoDOLmMKyL6Z gSEqLemghfcB+A==
X-Received: by 10.200.38.227 with SMTP id 32mr4752774qtp.275.1495128636536; Thu, 18 May 2017 10:30:36 -0700 (PDT)
Received: from FrancoisPC (pool-108-48-182-247.washdc.fios.verizon.net. [108.48.182.247]) by smtp.gmail.com with ESMTPSA id 29sm4245506qkz.38.2017.05.18.10.30.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 May 2017 10:30:35 -0700 (PDT)
From: François Simon <fygsimon@gmail.com>
To: langziwumingzhimi@sina.com
Cc: its@ietf.org
References: <20170518172151.DF44940097@webmail.sinamail.sina.com.cn>
In-Reply-To: <20170518172151.DF44940097@webmail.sinamail.sina.com.cn>
Date: Thu, 18 May 2017 13:30:33 -0400
Message-ID: <01ad01d2cffc$74e10d60$5ea32820$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AE_01D2CFDA.EDDC65B0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQII2sauNVGQjzqHIG+YJr7kANVbzqGOQhJw
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/0D_3PkYQAHHh5DPJ2_zk5R7yhfI>
Subject: Re: [ipwave] 回复:Re: RSU minor textual issue
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 18 May 2017 17:36:19 -0000

It is any nodes outside the DSRC network which can provides the RSU with information it needs for its applications (monetary transactions, traveling information,  maps, weather, etc.).

 

From: langziwumingzhimi@sina.com [mailto:langziwumingzhimi@sina.com] 
Sent: Thursday, May 18, 2017 1:22 PM
To: François_Simon <fygsimon@gmail.com>; 'Russ Housley' <housley@vigilsec.com>
Cc: its <its@ietf.org>
Subject: 回复:Re: [ipwave] RSU minor textual issue

 

By viewing this discussion, I would like to raise a question for V2I, which I stands for infrastructure. And RSU is a kind of infrastructure.

 

My question is: Is that infrastructure means transportation infrastructure, or Internet infrastructure?

 

If it is transportation infrastructure,  RSU should not be considered as a router. 

 

BRs,

Minpeng

 

 

 

----- 原始邮件 -----
发件人:François_Simon <fygsimon@gmail.com <mailto:fygsimon@gmail.com> >
收件人:"'Russ Housley'" <housley@vigilsec.com <mailto:housley@vigilsec.com> >
抄送人:fygsimon@gmail.com <mailto:fygsimon@gmail.com> , its@ietf.org <mailto:its@ietf.org> 
主题:Re: [ipwave] RSU minor textual issue
日期:2017年05月19日 00点28分

 

In the US, RSUs ARE NOT ROUTERS. There are logical boundaries between RSU and functions accessing the infrastructure (when required):

 

FHWA Definition: 

“1.6. Roadside Units

DSRC enables communication between vehicles and roadside equipment, but does not

generate data necessary to provide warnings and advisories from infrastructure to drivers. To

support V2I applications, DSRC must be integrated with existing traffic equipment, such as

Signal Controllers and backhaul connections to Traffic Management Centers (TMCs). DSRC

devices that serve as the demarcation component between vehicles and other mobile devices

and existing traffic equipment will be referred to DSRC Roadside Units (RSU) in this document.”

 

RSU - A connected device that is only allowed to operate from a fixed position

(which may in fact be a permanent installation or from temporary

equipment brought on-site for a period of time associated with an

incident, road construction, or other event). Some RSEs may have

connectivity to other nodes or the Internet.

 

 

 

From: its [mailto:its-bounces@ietf.org] On Behalf Of Russ Housley
Sent: Thursday, May 18, 2017 9:34 AM
To: Alexandre Petrescu <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com> >
Cc: its@ietf.org <mailto:its@ietf.org> 
Subject: [ipwave] RSU minor textual issue

 

 

On May 18, 2017, at 5:39 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com> > wrote:

 

OLD:

RSU: Road Side Unit. 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.


A comment was made stating that an RSU is not a router, and that an RSU
may be connected to a router via an interface, e.g. Ethernet, to access
the infrastructure if required.

But I think that some Road Side Units are indeed IP routers and they
access the infrastructure and the Internet.  This is an important point
when using the IP protocol - be connected.

I think I keep that text that way at this time.

End issue.

 

Alex:

 

Some RSUs will be routers, but others will not.  For example, an RSU that sends messages to vehicles about foggy conditions does not need to be a router.  I think the definition should allow both cases.

 

Russ

 

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