[ipwave] Some review comments for draft-ietf-ipwave-vehicular-networking-11
Charlie Perkins <charles.perkins@earthlink.net> Mon, 16 September 2019 04:08 UTC
Return-Path: <charles.perkins@earthlink.net>
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 F32661201E5 for <its@ietfa.amsl.com>; Sun, 15 Sep 2019 21:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.026
X-Spam-Level:
X-Spam-Status: No, score=-2.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
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 clC87igG7ASc for <its@ietfa.amsl.com>; Sun, 15 Sep 2019 21:08:25 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3D3512008D for <its@ietf.org>; Sun, 15 Sep 2019 21:08:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1568606905; bh=1AFBAslZYqTdr0MBVM/Ol+nwMSiQZF9+6hXB ddqQ80A=; h=Received:To:From:Subject:Message-ID:Date:User-Agent: MIME-Version:Content-Type:Content-Transfer-Encoding: Content-Language:X-ELNK-Trace:X-Originating-IP; b=FByk0IlKKlWjkUHu FfBfBvh/HBvIfoMRZZFdA0o1pzGn34xbh1e2n1Y82C+Sj5/9VXddSDIbrhnyAC+TCrO GTo+7KxQfVX0pmB8BwzA5ezQRm7/bYIQx1uTVyj5DjpWroAj+5F1qd4XzeQPEagJWWd RFBvURiABxGT1bTWu2/3E5XfMzLbLHc/o/x/+glGxBSKrKSSJ9rX52jL0GNtGleaTo3 B3ERnewNoqOqF7ldVa/kli7Sk7HtX7cWcvCVAhuippPvASbo/sxI7Ak3WZIhQ86kOs4 E15tynSkpMpVfCXijTgSCCcVcs/U0Vy4FqCu1QO6cC/0i7ANvcsF8KuZ8g==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=AfGJroUapj3wmPb1r1qFJg5uEvtqt1ZPxcB4CQP2z6RQYtSfPWY1Z8YpD24vVDrVDxmbjD0reiFGCkMX4J8M9icwQRJHVbSUnAwwl4WktAwlND6FRJ7qTbzAZ7ERD4PIjhoS/EZsfSzUgHCHwdKdwqyXxipIDrmD0uyNGXNkshSdFZL420wXzzzhnjRO1D8UYi8H+zz0FWfEPCLiKLTOZ4KYRNNyLH+RyuQcJJcbMKLZapueNMfh9N4n4XWkTnWTknUP2F3rNZXNLcAsL2q/wERqjXCemAckILMRvPJ8rP72BIt7qjmNNJFCzToSQyS/ijHxw6+z1vg+pmfR4g0GPA==; h=Received:To:From:Subject:Message-ID:Date:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4) (envelope-from <charles.perkins@earthlink.net>) id 1i9iJM-00096q-N9 for its@ietf.org; Mon, 16 Sep 2019 00:08:24 -0400
To: "its@ietf.org" <its@ietf.org>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <a93e3290-e31f-dbd2-a39c-2895026f59ee@earthlink.net>
Date: Sun, 15 Sep 2019 21:08:21 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c95bd548f6d386b1b7fc86112779284ccf3350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/qtbi6dOhQrG2sQB790sReuU-cQs>
Subject: [ipwave] Some review comments for draft-ietf-ipwave-vehicular-networking-11
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: Mon, 16 Sep 2019 04:08:28 -0000
Hello folks, I made a review of the document draft-ietf-ipwave-vehicular-networking-11.txt. Besides editorial comments, I had some other more substantive comments on the document, as follows. First, I thought that the document should contain an easily identifiable problem statement. Here is some text that I devised for that purpose, which could fit naturally at the beginning of Section 5. In order to specify protocols using the abovementioned architecture for VANETs, IPv6 core protocols have to be adapted to overcome certain challenging aspects of vehicular networking. Since the vehicles are likely to be moving at great speed, protocol exchanges need to be completed in a time relatively small compared to the lifetime of a link between a vehicle and an RSU, or between two vehicles. This has a major impact on IPv6 neighbor discovery. Mobility management is also vulnerable to disconnections that occur before the completion of identify verification and tunnel management. This is especially true given the unreliable nature of wireless communications. Finally, and perhaps most importantly, proper authorization for vehicular protocol messages must be assured in order to prevent false reports of accidents or other mishaps on the road, which would cause horrific misery in modern urban environments. ---------------------------------------------- Although geographic routing is mentioned early in the document, it is not discussed in later sections. This makes me wonder whether the early mention is really relevant. In fact, for fast moving objects, I think it is already questionable whether geographic routing has value. For the RSUs, it is a lot easier to imagine a good use for geographic routing, or perhaps some other use of geographic information to establish links between application endpoints. If geographic algorithms are mentioned at all, a lot more development is needed to establish relevance to the problem statement. --------------------------------------------- More description is needed for OCB in the Terminology section. It would also be a good idea to include definitions for "context-aware" and for platooning. class-based safety plan needs a definition and a list of classes. --------------------------------------------- As a general comment, it seems to me that a proposed architecture is usually considered to be part of the solution, not the problem statement. In the case of this document, the architecture is really a depiction of IPv6 as it might be normally considered to live in a multi-network deployment (e.g., between a lot of cars and RSUs). But anyway some care has to be taken so that the proposed architecture doesn't otherwise place strong limits on acceptable solutions. So, for example, in section 4.1, it needs to be clear whether or not a single subnet prefix can span multiple vehicles. This is an important choice. --------------------------------------------- In section 5.1.1., a claim is made that a new link model is required. I think this is a very ambitious claim, and I am not even quite sure what is meant. IPv6 already provides for "on-link" and "off-link" variations on subnet operation. Unless I am missing something here, the claim should be made much more clear (or else retracted). Similarly, the suggestion that VANETs need to be merging and partitioning as part of the problem statement seems at least ambitious and might present a very high bar that could disqualify otherwise suitable solutions. --------------------------------------------- It would be nice to have a citation about why current implementations of address pseudonyms are insufficient for the purposes described in section 5.1.2. --------------------------------------------- It seems to me that the discussion in section 5.1.3 lives almost entirely in solution space. --------------------------------------------- In section 5.1.4, it was not clear to me about why Neighbor Discovery really needs to be extended into being a routing protocol. -------------------------------------------- It seems to me that section 5.3 really belongs in section 6. Also, even a perfectly authorized and legitimate vehicle might be persuaded somehow to run malicious applications. I think that this point is not sufficiently covered in the current text. Regards, Charlie P. Blue Sky Networks
- [ipwave] Some review comments for draft-ietf-ipwa… Charlie Perkins
- Re: [ipwave] Some review comments for draft-ietf-… Alexandre Petrescu
- Re: [ipwave] Some review comments for draft-ietf-… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Some review comments for draft-ietf-… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Some review comments for draft-ietf-… CARLOS JESUS BERNARDOS CANO
- Re: [ipwave] Some review comments for draft-ietf-… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Some review comments for draft-ietf-… CARLOS JESUS BERNARDOS CANO
- Re: [ipwave] Some review comments for draft-ietf-… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Some review comments for draft-ietf-… CARLOS JESUS BERNARDOS CANO
- Re: [ipwave] Some review comments for draft-ietf-… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Some review comments for draft-ietf-… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Some review comments for draft-ietf-… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Some review comments for draft-ietf-… CARLOS JESUS BERNARDOS CANO
- Re: [ipwave] Some review comments for draft-ietf-… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Some review comments for draft-ietf-… Mr. Jaehoon Paul Jeong