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

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 <
alexandre.petrescu@gmail.com> 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: +82-31-299-4957
> > Email: jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>,
> > pauljeong@skku.edu <mailto:pauljeong@skku.edu>
> > Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
> > <http://cpslab.skku.edu/people-jaehoon-jeong.php>
> >
> > _______________________________________________
> > 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
>

-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Software
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>