Re: [ipwave] Some review comments for draft-ietf-ipwave-vehicular-networking-11

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 16 September 2019 13:26 UTC

Return-Path: <alexandre.petrescu@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 E2869120046 for <its@ietfa.amsl.com>; Mon, 16 Sep 2019 06:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
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 Q5M5PqMTL3Qx for <its@ietfa.amsl.com>; Mon, 16 Sep 2019 06:26:55 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 E7EDA12006A for <its@ietf.org>; Mon, 16 Sep 2019 06:26:54 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8GDQr5A047292 for <its@ietf.org>; Mon, 16 Sep 2019 15:26:53 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3DE0420696B for <its@ietf.org>; Mon, 16 Sep 2019 15:26:53 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 342FF202BD1 for <its@ietf.org>; Mon, 16 Sep 2019 15:26:53 +0200 (CEST)
Received: from [10.11.240.27] ([10.11.240.27]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8GDQqvi023285 for <its@ietf.org>; Mon, 16 Sep 2019 15:26:53 +0200
To: its@ietf.org
References: <a93e3290-e31f-dbd2-a39c-2895026f59ee@earthlink.net>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <e9d3f1ff-deac-0930-2b2a-ad5affed03ff@gmail.com>
Date: Mon, 16 Sep 2019 15:26:52 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <a93e3290-e31f-dbd2-a39c-2895026f59ee@earthlink.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/XoPIMJDZLyRlOmrieTUCa6ymZys>
Subject: Re: [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 13:26:57 -0000



Le 16/09/2019 à 06:08, Charlie Perkins a écrit :
[...]

> 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.

I do not know what particular aspect is little clear about why ND really
needs to be extended into being a routing protocol?

On my side, I can try to clarify, as I support ND for vehicular networks
encompassing multiple subnets.

A routing protocol is something very heavy, designed to adapt to very
many dynamic graphs.  For example, I think of the number of subnets in a
Enterprise, coupled to several ISPs simultaneously and with branches
overseas, and some cellular network subscriptions.

On another hand, in vehicular lines like convoys, or in car-to-traffic
lights situations, or even in 2-dimensional car plus drones and air taxi
situations, the IP paths are much simpler than in the above cited
dynamic graphs.

For these situations one would need simpler protocols, like ND.  But ND
has only very primitive forms of routing.

Alex

> 
> --------------------------------------------
> 
> 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
> 
> 
> 
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its