Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicular-networking-14.txt

Jung-Soo Park <fnumber@gmail.com> Wed, 01 April 2020 11:26 UTC

Return-Path: <fnumber@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 E90283A0ACC for <its@ietfa.amsl.com>; Wed, 1 Apr 2020 04:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 1MYX8oq9f_7z for <its@ietfa.amsl.com>; Wed, 1 Apr 2020 04:26:33 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (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 F1EB83A0AC2 for <its@ietf.org>; Wed, 1 Apr 2020 04:26:32 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id v13so2579270pjb.0 for <its@ietf.org>; Wed, 01 Apr 2020 04:26:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3YchkCaxAn1ne2t2QU4nlYzR/+17Bdkh3NFbcafp2bQ=; b=jReMfcVyJVFTYB8id4qqJVJxuTjvsiwxNPlkt+6/ByRG8AAhsN6rK7lALoM3F2IBZc tEXkUcllp7JHJXOXZ8xUZv3wsD2HqGkEURpbAadXWAjvznUbaec9TIR5uR0EoPdCDzZ9 Qp4etL8uXONEJLKYU12c4Rc+onBBrSWciLO0AAex2KS0nH5WPlUdfAaZRmZaX18aVj+G 71Ty6p0UcqVs1eY3tRqbsnvxlgGa4qSTColosZ6M+8toVQYZlp7PrHStdg4YB7lyC0Be Xq0jCnQVpcRjAirkU8ycLYaUfPv7kmN9ODEInDxbK95ltxrapfCTUBAso3/CfvE/+s/z IJwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3YchkCaxAn1ne2t2QU4nlYzR/+17Bdkh3NFbcafp2bQ=; b=RiEd2O3FIGBWL0L/vBjSR+CJYzZnBySgWJAyer7j1nelyCC5jr4UdDLBKPLE2EbX7u sfv07Yj6x6+PqY6oPTQewENLNUXHA+MCD401PU2IwrREG8Y5ycmB/DqV51gXYd2U2lue yPEDHa03ewYaTMtxhg9BOBYGIWF0X9fwVrxi1nu8F7WNbUku42/No5PW4V5fP9zIpNpP YpJZ72adCgbqQgBEBlkXrpHsKK0mYxrcA0AfPN8BJ1gFN5VZyMksZ3mpr+0BmdbMzcWz xZKmiRP9OqmAFrtIcI7jNGvKDLDXN40jcrB9nWz8v+D4qYb2u1wfrV1AsX8vtTmciyW6 uPQA==
X-Gm-Message-State: AGi0PuYIh7i4CYMEseB6nrtzR9e1BfTtrQab9K3Z5Dhhq8pjdarsZMOs wGIL8hoS7oLiC1gCJJwxFypcAfYOHbwOa5T/E1eO52urfM0=
X-Google-Smtp-Source: APiQypJVL9Z3CEgHOe+uewU93v+V2lBk6uN3oPS12NEHLIspB1MaWIEfGGc8HByYYS9OGHsBZxfmr/m8ZC6Z1XI1ehc=
X-Received: by 2002:a17:90a:cb0e:: with SMTP id z14mr4225344pjt.156.1585740392168; Wed, 01 Apr 2020 04:26:32 -0700 (PDT)
MIME-Version: 1.0
References: <158377782203.5503.9266337240401588359@ietfa.amsl.com> <BEA2C0D4-E700-4A91-BCBA-881DB4339523@vigilsec.com> <CAE9rxx4W6VGy4_xJQrMm7OEspxP=VqSgW7crNEeSfRhkx7YWrw@mail.gmail.com> <3F98FF11-12D8-4A6F-A269-6B8EC50BA9DE@vigilsec.com>
In-Reply-To: <3F98FF11-12D8-4A6F-A269-6B8EC50BA9DE@vigilsec.com>
From: Jung-Soo Park <fnumber@gmail.com>
Date: Wed, 01 Apr 2020 20:26:21 +0900
Message-ID: <CAE9rxx4eSOATu59=KF6qj0wkyxPufL9Ww5=dpQVJYS=mNGxUZA@mail.gmail.com>
To: "its@ietf.org" <its@ietf.org>
Cc: Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es>
Content-Type: multipart/alternative; boundary="000000000000c7fefd05a238f45a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/l9Xl6e6N23rWb2A-n_8Fn0p8Vx8>
Subject: Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicular-networking-14.txt
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 01 Apr 2020 11:26:35 -0000

Hi, all.

I reviewed IPWAVE draft and wrote down the humble comments.


---

#Clause 1.

At the third paragraph, my proposal is adding new reference,
[ISO-ITS-IPv6-Amd1].

“Along with these WAVE standards, IPv6 …

For Land Mobile (CALM) [ISO-ITS-IPv6], [ISO-ITS-IPv6-Amd1].



#Clause 2.

-New term, V2X should be added.

Generally speaking, vehicle-to-everything (V2X)  term is including V2I and
V2V.

So, new term should be define in Clause 2 (Terminology) with a sentence
excluding V2I and V2V use cases like a description of the first paragraph
of Clause 3. And this term should also include the V2P and V2D use cases.



-About Edge Network (EN),  “In” is changed to “It”.



-About IP-OBU,

This term is currently focused on a vehicle.

In case of a Device or Pedestrian, I want to know whether the IP-OBU
functionality is supported in them or not. I think this issue is solved in
this term.



-About Vehicle Detection Loop (i.e., Loop Detector),

This term is only used to define TCC in this document.

So, I think this term is useless.



#Clause 3,

-In Clause 3.1 V2V

In the first paragraph of Clause 3.1, these are four use cases of V2V
networking.

The second “cruise control” use case is described for urban environment.

The third “platooning” is also described for the highway.

So, I suggest that “in an urban roadway” and “in a highway” is redundant at
the second and third bullet  points.



-In Clause 3.1

In “Cooperative-environment-sensing” use case, describing the reward
system  is better. For more active cooperation, the supporter of
information should have   the benefit.



-In Clause 3.3 V2X

V2I2X is not described in upper part.



#Clause 4,

-In the fourth paragraph on page 12

We suggest like this;

“In the host-based mobility scheme, an IP-RSU plays a role of a home

  agent.”  We propose just deleting the “in a visited network”.



-In Clause 4.2 V2I-based Internetworking

In Figure 2, the internal network of Vehicle1 is constructed using wired
and wireless. So, the internal network of Vehicle1 should be changed
including two types of arrows (wired and wireless link) unlike EN1.



-In Figure 4,

It just comments. I think the Figure 4 can be used in Platooning
environment.

In that case, a Host has a role of leading vehicle with driver’s operation.
Others will be a driverless vehicles. So, star topology will be also used.



#Clause 6

-In the second paragraph of Clause 6,

“Also, in-vehicle devices (e.g., ECU) and mobile devices (e.g., smartphone)
in a vehicle need to …in another vehicle,”

I think that “mobile devices” can be existed out of the vehicle, just near
the vehicle. And the pedestrian also has them. So, this sentence should be
extended to include others such as pedestrian.





#Clause 7



[ISO-ITS-IPv6-Amd1]

ISO/TC 204, Intelligent transport systems - Communications access for

Land mobiles (CALM) - IPv6 Networking Amendment 1, September 2017.


Thanks.

Jungsoo, PARK

On Thu, Mar 19, 2020 at 12:42 AM Russ Housley <housley@vigilsec.com> wrote:

> We look forward to your review.  Please post it to the mail list.
>
> Russ
>
>
> On Mar 18, 2020, at 7:20 AM, Jung-Soo Park <fnumber@gmail.com> wrote:
>
> Hi All,
>
> I'm volunteer for reviewing.
> I hope giving a good response in the IPv6 networking and security aspects.
>
> Best Regards,
> JungSoo
>
> On Tue, Mar 10, 2020 at 4:46 AM Russ Housley <housley@vigilsec.com> wrote:
>
>> Paul believes that he has addressed all comments in revision:
>> https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-14
>>
>> I think we need to let at least five reviewers.  Could you do a review of
>> this revision?  Please respond to the WG mail list.
>>
>> Thanks,
>>   Russ
>>
>>
>> On Mar 9, 2020, at 2:17 PM, internet-drafts@ietf.org wrote:
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the IP Wireless Access in Vehicular
>> Environments WG of the IETF.
>>
>>        Title           : IPv6 Wireless Access in Vehicular Environments
>> (IPWAVE): Problem Statement and Use Cases
>>        Author          : Jaehoon Paul Jeong (editor)
>> Filename        : draft-ietf-ipwave-vehicular-networking-14.txt
>> Pages           : 32
>> Date            : 2020-03-09
>>
>> Abstract:
>>   This document discusses the problem statement and use cases of
>>   IPv6-based vehicular networking for Intelligent Transportation
>>   Systems (ITS).  The main scenarios of vehicular communications are
>>   vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and
>>   vehicle-to-everything (V2X) communications.  First, this document
>>   explains use cases using V2V, V2I, and V2X networking.  Next, it
>>   makes a problem statement about key aspects in IPv6-based vehicular
>>   networking, such as IPv6 Neighbor Discovery, Mobility Management, and
>>   Security & Privacy.  For each key aspect, this document specifies
>>   requirements for IPv6-based vehicular networking.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-ipwave-vehicular-networking/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-14
>> <https://tools.ietf..org/html/draft-ietf-ipwave-vehicular-networking-14>
>>
>> https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-vehicular-networking-14
>>
>> A diff from the previous version is available at:
>>
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-ipwave-vehicular-networking-14
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>>
>> _______________________________________________
>> 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
>>
>
>
> --
> Dr. JungSoo PARK
> -----------------
> Smart Infra Standardization Team
> Electronics and Telecommunications Research Institute (ETRI), Korea
> Tel:+82-42-860-6514, Fax:861-5404
> MSN: fnumber@msn.com, E-mail : pjs@etri.re.kr <pjs@etri..re.kr>
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its
>
>
>

-- 
Dr. JungSoo PARK
-----------------
Smart Infra Standardization Team
Electronics and Telecommunications Research Institute (ETRI), Korea
Tel:+82-42-860-6514, Fax:861-5404
MSN: fnumber@msn.com, E-mail : pjs@etri.re.kr