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

Abdussalam Baryun <> Sat, 11 September 2021 22:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 724123A136F for <>; Sat, 11 Sep 2021 15:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id puCoA5T4uW04 for <>; Sat, 11 Sep 2021 15:51:04 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 20C953A136E for <>; Sat, 11 Sep 2021 15:51:04 -0700 (PDT)
Received: by with SMTP id d21so621220wra.12 for <>; Sat, 11 Sep 2021 15:51:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=yUuq+naNp3Co3NzmrPGNtWqLu2d1VDT0TXVY7yRGx94=; b=F0FTF9H1JUGZ4kdWKzbMNyINaBLrdgRNtkecVWQRITUpOTQbTg34C9m7PnFYbcUu0J OFeTi5PRthkbNA0pXJVbYFSxotYmp/9qW2Ainv1oX6BnPVpqbYV8ys7En+Ucnuj0JOw0 pM3sAuhrD8qgghqgGkOv5BT9ajWWDF0KtfyfxnS0hC9G6TasQfcvVgUh3I68uRz9ExE6 KWopI+8i0rRugdvjA0C3xAZupirwZzbyYZ/17KvSHJnmSxzR0pFbqbGTlxjawEiOnK+3 q4jO5twtpeZQf5h/5sWlQm+QtBUceXbxY/OrFWrmH45D9waqFoyM0vFpDEaBsvsmcmam 9gHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=yUuq+naNp3Co3NzmrPGNtWqLu2d1VDT0TXVY7yRGx94=; b=BoP5SWGOkIpoVP3N/rSyNo5dZJ8hENTkcL3bCt9JE9+Ew2+Inci6FbV14fPv6kBUOt MWUykhNlLF9gzby68GLDON8GwyRY6BYbOD4BOtI2R0J5QxisoF5tbcVuve0eK3368clF ZkWRo8DCXW8Kre6SbKScnbGy/wbqBRFX/8Yo7OUi3tyINQmNX0wt293QuHP/XlBKTiLw mLMpn5+UDFZKci785zwmfqYfvkg5h3t7LbXz9FcBhnigWNZzcCuCM6bA4HgzlR81rDpq xyi5ywTLkyWywhFbaz6We9tw7f1HF85IZBh5XntOc3NMNaUcJ+nXqKxbvQ6th+u+eNZ7 XRgw==
X-Gm-Message-State: AOAM533hg2PWaq2f/Dara390J0ctB07clAbdTgGLpsZpRoNvAeMJkNu6 Usplxp+TaIc9YJLJvSrYDsuG6VcsG4r152dk0apYwvc4d5Xneg==
X-Google-Smtp-Source: ABdhPJye47naqPtF1xl/l1F2D1Vv/AG1Yh1AvaNHuPc6uM0zdai4xiC0dqj+gF0jPyIYAuSHJk877BE1Sfz5DryLG6I=
X-Received: by 2002:a05:6000:1a52:: with SMTP id t18mr4813998wry.21.1631400661486; Sat, 11 Sep 2021 15:51:01 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Abdussalam Baryun <>
Date: Sun, 12 Sep 2021 00:42:32 +0200
Message-ID: <>
To: its <>
Content-Type: multipart/alternative; boundary="000000000000ea103c05cbc010cf"
Archived-At: <>
Subject: Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicular-networking-23.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 11 Sep 2021 22:51:10 -0000

Hi Paul,

In terminology section: please add
definition for: IPWave-Link, IPWAVE-node (capable of networking with all
IPWAVE-nodes), V-node (Vehicle IPWAVE-node with mobility).
The use case section needs to mention the possible ipwave-link protocols,
as IEEE802.11 , IEEE802.15.4 with 6lowpan, 802.11ad, VLC (Visible
Light Communications),
IrDA, LTE-D, LP-WAN (mentioned in WG charter) and other possible
used-standards if available. If we have then a routing protocol it should
work over those network links, or as daft mentioned cases for protocols
used in the section of routing. Also the draft needs to mention the issue
of mobility is not seriously similar to MANET use cases (only V2V links can
be similar), because the network nodes in IPWAVE are moving within at least
one connectivity coverage or to say that any V-node MUST have at least one
connect link as V2I per.
In MANET or in LLN there are possibilities of totally disconnected at any
time and for a period of time.

In abstract it mentioned the problem statement and use cases. I think they
are the same thing, but it is used in the draft differently, however, I
think the problem statement is like a Vehicle network challenges section.
This challenging section can focus on architecture, standards, protocols,
but should not be mentioning network-layers only if solved in the network
architecture section.

The VANET definition, in terminology, I think should be deleted, because
not all V2V MUST be VANET, we need to make V2V networking definition  may
have possibility  ad hoc or infrastructure modes as known in ieee802.11
standard and others.

Best Regards

On Fri, Sep 3, 2021 at 5:12 AM <> 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-23.txt
>         Pages           : 49
>         Date            : 2021-09-02
> 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, for
>    IPv6-based vehicular networks, it makes a gap analysis of current
>    IPv6 protocols (e.g., IPv6 Neighbor Discovery, Mobility Management,
>    and Security & Privacy), and then enumerates requirements for the
>    extensions of those IPv6 protocols for IPv6-based vehicular
>    networking.
> The IETF datatracker status page for this draft is:
> There is also an htmlized version available at:
> A diff from the previous version is available at:
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> its mailing list