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

선경재 <gomjae@dcn.ssu.ac.kr> Thu, 12 March 2020 06:48 UTC

Return-Path: <gomjae@dcn.ssu.ac.kr>
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 05F233A119B for <its@ietfa.amsl.com>; Wed, 11 Mar 2020 23:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=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=dcn-ssu-ac-kr.20150623.gappssmtp.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 Q309yWpO4kll for <its@ietfa.amsl.com>; Wed, 11 Mar 2020 23:48:27 -0700 (PDT)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 BB72A3A119A for <its@ietf.org>; Wed, 11 Mar 2020 23:48:25 -0700 (PDT)
Received: by mail-ed1-x52f.google.com with SMTP id h62so6002206edd.12 for <its@ietf.org>; Wed, 11 Mar 2020 23:48:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcn-ssu-ac-kr.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=IXAxQkHSC6RzLASBdcG7Lm8fmukq/OY6qJkmIv+Vtbc=; b=gR5KAqr/JNHKQZbwpFzKqZaRuxBXJ4UU/LOgxjl8/u85Plb5+Hl7PnKVMaUj9bzc01 KFpvU5QYV3wb7bgeWp3YRQaDnhBWwxqa9jQW6L5pqaaCpKv4aFYnGnY1aU9zP7ZEZSdD B43+0I7nPmvZI1WpUjOmtypixXMiwiRQlI1wTQX65KUlBrfnTPMxAxPbG7Tf2RcJX0Zp VXLrTq+qWMlO3gNF3ppKVp6T+d86fJnC3tkvxc1y0tqCJmCzlkZYkTel7l5rNGzAsWyE F+XS1SgQTNz6SOsm/u3c/xQnNIF76P/Y6yDhTUGTdpRgtB1IOD/Nvd0Fh7f9pjHWitmb nHkw==
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:content-transfer-encoding; bh=IXAxQkHSC6RzLASBdcG7Lm8fmukq/OY6qJkmIv+Vtbc=; b=Yw7TGHozQRJthPmleBZaypHZ3TWn1KeDvEQ07Cqi2aQPg1dqrBSvBy+b80styvNuoL 9Db7iKAgCZOxKtyZjLIQ4ARxGxAI7kFQT+ATv86owV9rf+tK81qDRv8qErm2gtjdWZh0 lLy8ey5RNPhOApr9sfcwwFZNkYtkhnyeWHRQCw8opt6/3bLc4oYPfbeogNBbRCbIZYwT WcBazaGbmKSzQvojjs2tMdqzhI1WFB2DKS0HV7WRPG2gZfCI9wQE5JqnG/PzJXB8wFSH ak6q+eFoVuWWi2B3RWj/O5J5IjNANcN2BufvO5PH/WCwBq0wXFog8/F1Qws2OrfKZ6nS kZuQ==
X-Gm-Message-State: ANhLgQ3pqac46xJ93F5niwyYO4BJ0J8nV62DYBb1xnklsl9XFkOujDmt V58D3ayPRqcBNpSWM3YJE1iw3Idjd1sOkuXwFGwWJU5pI58=
X-Google-Smtp-Source: ADFU+vssmWEVicvKIwr5XlUvNdm5QGEDdzy9CGght872/idYY0W0ayDaHVaOMdnqDT1eeFUf8jQcGlDsobYfcABDgfA=
X-Received: by 2002:a17:906:aad1:: with SMTP id kt17mr5654940ejb.86.1583995703845; Wed, 11 Mar 2020 23:48:23 -0700 (PDT)
MIME-Version: 1.0
References: <158377782203.5503.9266337240401588359@ietfa.amsl.com>
In-Reply-To: <158377782203.5503.9266337240401588359@ietfa.amsl.com>
From: 선경재 <gomjae@dcn.ssu.ac.kr>
Date: Thu, 12 Mar 2020 15:48:11 +0900
Message-ID: <CAND-M=ctQ54prdt5O+ekjRHSvKdaNWCgvRaWY0KSX0MpmmGOMg@mail.gmail.com>
To: its <its@ietf.org>
Cc: Russ Housley <housley@vigilsec.com>, 정재훈 <jaehoon.paul@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/v6f7C9cp7JX4ABorL559QDyXIkU>
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: Thu, 12 Mar 2020 06:48:29 -0000

Hi, Paul

I reviewed your revised draft. Check my comments below.


1) In "2. Terminology", '[RFC7429]' was not hyperlinked. it is the
only reference which is not hyperlinked.

2) In 3.1, position of paragraph starting with "The existing IPv6
protocol does not.." may not suitable. I suggest to move this
paragraph in front of last paragraph. For the same reason, similar
paragraphs in 3.2 and 3.3 are suggested to move position.

3) In 3.2, when "TCC" is written firstly, there is no explanation for
this abbreviation.

4) In 3.3, you explained about V2I2V use case. Can we say that the
scenario you mentioned in the third paragraph is correct to define
'IP-RSU relaying'? If an edge computing is running and processing
between vehicle and pedestrian, it seems to be two separated V2I
communications between edge and two nodes.

5) I suggest to move figure 1 under the chapter 4 because this figure
was explained in chapter 4.1. For the same reason, Figure 2 can be
placed under the chapter 4.2, and Figure 3 under the chapter 4.3.

6) In fifth paragraph of 4.1, I think that "which are part of a
Vehicular Cloud." is not necessary. Also, "which is a controller for
the mobility management of vehicles." is not necessary because it
seems to duplicate meaning for previous sentence.

7) In the first paragraph of 4.1, "However, some components..." is
suggested to change in the way like "These components are not
mandatory and there can be deployed in various ways".

8) Second paragraph 4.1 seems to be specified PMIPv6 as a default
mobility management protocol. If not, I suggest this paragraph to
modify or remove.

9) In 4.1, SDN concept pops up in sudden and it is used for mobility
management. If you want to add CP/DP separation concept for mobility
management, I think that CP/DP separation definition and explanation
which is defined in the DMM WG will be better. In
"draft-ietf-dmm-fpc-cpdp", they defined Forwarding Policy
Configuration (FPC) architecture which adapts CP/DP separation. I
think this document can be helpful.

Best Regards,

KJ.


====================================================================

선경재 / KJ Sun


연구원 / 인터넷인프라시스템 기술연구센터

Researcher / Internet Infrastructure System Technology Research Center

Office : +82-2-820-0841    Phone : +82-10-3643-5627

Email : gomjae@dcn.ssu.ac.kr

====================================================================

2020년 3월 10일 (화) 오전 3:18, <internet-drafts@ietf.org>님이 작성:
>
>
> 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://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