Re: [ipwave] Request for Review on IPWAVE PS Draft

["Mr. Jaehoon Paul Jeong" <[e-mail]>]

Alex,
I mean IP-based networking for V2V and V2I by IPWAVE protocols.
As you said, I agree we need an application protocol between a vehicle and
a traffic light either directly or via an RSU.
Right now, I am not sure which application protocol will be popularly used
for the traffic light controller.

Best Regards,
Paul

On Tue, Dec 4, 2018 at 7:00 PM Alexandre Petrescu <
[e-mail]> wrote:

> Hi Paul,
>
> Thank you for the reply.
>
> Le 04/12/2018 à 01:15, Mr. Jaehoon Paul Jeong a écrit :
> > Hi Alex,
> > In South Korea, people are aware of PRESTO (ISO 22951:2009)
> > for traffic light control for emergency vehicles, but it seems like
> > there is no standardized, implemented protocol in South Korea yet.
> > I guess that Korean people will try to implement the ISO's PRESTO in
> future.
> >
> > The PRESTO does not specify a specific delivery protocol, so
> > our IPWAVE will be a good candidate for this traffic light control, so
> > we can include this into our PS document as a use case.
>
> This initiative seems appropriate.
>
> I would need to understand what do you mean by IPWAVE.
>
> On my side, I think IP/OCB protocol developped by IPWAVE WG would be a
> good intermediary means to network IP packets between car and traffic
> light controller (other intermediary segment is Ethernet, with
> IP/Ethernet, within the IP-RSU box, and within the car).
>
> But there need to be IP routes between the car and the traffic light
> controller too.  To achieve that we need a mechanism.
>
> And there would need to be an application layer protocol (PRESTO?  SPAT?
>   DIASER?  SRM/SSM? HTTP?) between the car and the traffic light
> controller.
>
> Alex
>
> >
> > Thanks.
> >
> > Best Regards,
> > Paul
> >
> >
> >
> > On Wed, Nov 28, 2018 at 9:43 PM Alexandre Petrescu
> > <[e-mail] <mailto:[e-mail]>>
> wrote:
> >
> >     Hi Paul,
> >
> >     Thank you for the reply.
> >
> >     In this particular case, I am not asking to make modifications to
> >     the draft.
> >
> >     But, for my information, I would like to learn: what protocol is
> >     used in
> >     in S Korea to communicate with the traffic lights controller?
> >
> >     I need such a protocol in a use-case where the car may have the
> ability
> >     to ask, under certain circumstances, the traffic light to turn to
> >     green,
> >     or to learn how much time is left for red.
> >
> >     In France that protocol is called "DIASER" (it is an abbreviation for
> >     "DIAlogue Standard des Equipements de Régulation de trafic".)
> >
> >     At ISO, which is an International SDO, there is "PRESTO" (ISO
> >     22951:2009
> >     "Data dictionary and message sets for preemption and prioritization
> >     signal systems for emergency and public transport vehicles (PRESTO)).
> >
> >     Alex
> >
> >     Le 28/11/2018 à 02:28, Mr. Jaehoon Paul Jeong a écrit :
> >      > Hi Alex,
> >      > I will address your comments with other reviewers' comments for
> the
> >      > revision.
> >      >
> >      > Thanks.
> >      >
> >      > Best Regards,
> >      > Paul
> >      >
> >      > On Tue, Nov 27, 2018 at 11:00 PM Alexandre Petrescu
> >      > <[e-mail]
> >     <mailto:[e-mail]>
> >     <mailto:[e-mail]
> >     <mailto:[e-mail]>>> wrote:
> >      >
> >      >     Hi Paul,
> >      >
> >      >     I have a few comments to the draft that I would like to
> mention.
> >      >
> >      >     At this time, I do not request to modify the draft.  Thank
> you.
> >      >
> >      >     Here are my comments:
> >      >
> >      >     In the V2V section:
> >      >     - do not forget there is a funny typo: "obstables".
> >      >     - the 4 paragraphs in this section read good and make sense.
> >      >     - at ISO/TC204, there is recently an activity called
> >      >         "Vehicle to Vehicle Intersection Collision Warning System
> >     (VVICW)"
> >      >         The private Word document ISO 23376:20##(E) has 16 pages
> >     and I can
> >      >         discuss it in private with interested parties.
> >      >
> >      >     In the V2I section:
> >      >     - the three paragraphs read good.
> >      >
> >      >     - in addition, in my project, we consider V2I to also mean
> direct
> >      >         communication between the car and the nearby Traffic
> Lights
> >      >         Controller.
> >      >
> >      >         The communication between the car and the traffic lights
> >     controller
> >      >         can happen in two distinct V2I ways: from car to TCC and
> >     back to
> >      >         traffic lights controller, or from car to traffic traffic
> >     lights
> >      >         controller (not through TCC).
> >      >
> >      >         The end-to-end protocol between car and traffic lights
> >      >     controller can
> >      >         be the same protocol as the protocol between TCC and the
> >     traffic
> >      >         lights controller.  In France that protocol is called
> >     "DIASER".
> >      >     But,
> >      >         for international (maybe France - Netherlands) we also
> >     consider the
> >      >         ISO protocol called "PRESTO".  DIASER runs over IP (and
> >     on serial),
> >      >         but we wonder whether PRESTO runs over IP.
> >      >
> >      >     In section "5.1.2 Routing":
> >      >     - the section lists "VANET Geo Routing",
> >      >         but we do not use geographical routing.
> >      >     - the section lists
> >      >         "IPv6 Neighbor Discovery for IP-Based Vehicular Networks"
> >      >         for potential use for V2V communications.
> >      >         Instead, we use RFC4191 "More Specific Routes".
> >      >         This RFC4191 has a problem in that it is only for Hosts.
> >      >         We want RFC4191 to be for Routers as well.
> >      >         This RFC4191 is partially implemented in two alternatives
> >     in linux:
> >      >         (1) in the linux kernel and (2) in openwrt's odhcp6c.
> >     The latter
> >      >         needs a little bit of extension because by default it is
> >     not capable
> >      >         of doing _only_ "more specific routes", it wants to also
> >     do default
> >      >         route and address autoconfiguration.
> >      >
> >      >     Alex
> >      >
> >      >     Le 21/11/2018 à 05:27, Mr. Jaehoon Paul Jeong a écrit :
> >      >      > Hi Sri Gundavelli and Jung-Soo Park,
> >      >      > Thanks for your volunteering on the review of our IPWAVE
> >     PS draft:
> >      >      >
> >
> https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-07
> >      >      >
> >      >      > Could you share your review within this December?
> >      >      >
> >      >      > Once I get your comments, I will address yours along with
> the
> >      >     co-authors.
> >      >      >
> >      >      > Thanks again.
> >      >      >
> >      >      > Best Regards,
> >      >      > Paul
> >      >      > --
> >      >      > ===========================
> >      >      > Mr. Jaehoon (Paul) Jeong, Ph.D.
> >      >      > Associate Professor
> >      >      > Department of Software
> >      >      > Sungkyunkwan University
> >      >      > Office: [phone]
> >      >      > Email: [e-mail]
> >     <mailto:[e-mail]> <mailto:[e-mail]
> >     <mailto:[e-mail]>>
> >      >     <mailto:[e-mail]
> >     <mailto:[e-mail]> <mailto:[e-mail]
> >     <mailto:[e-mail]>>>,
> >      >      > [e-mail] <mailto:[e-mail]>
> >     <mailto:[e-mail] <mailto:[e-mail]>>
> >      >     <mailto:[e-mail] <mailto:[e-mail]>
> >     <mailto:[e-mail] <mailto:[e-mail]>>>
> >      >      > Personal Homepage:
> >     http://iotlab.skku.edu/people-jaehoon-jeong.php
> >      >      > <http://cpslab.skku.edu/people-jaehoon-jeong.php>
> >      >      >
> >      >      > _______________________________________________
> >      >      > its mailing list
> >      >      > [e-mail] <mailto:[e-mail]> <mailto:[e-mail]
> >     <mailto:[e-mail]>>
> >      >      > https://www.ietf.org/mailman/listinfo/its
> >      >      >
> >      >
> >      >     _______________________________________________
> >      >     its mailing list
> >      > [e-mail] <mailto:[e-mail]> <mailto:[e-mail]
> >     <mailto:[e-mail]>>
> >      > https://www.ietf.org/mailman/listinfo/its
> >      >
>