Re: [ipwave] Route Information Options in IPv6 Neighbor Discovery

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sun, 23 December 2018 16:30 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 BADD8124B0C for <its@ietfa.amsl.com>; Sun, 23 Dec 2018 08:30:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 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_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 NpF98DitfrR3 for <its@ietfa.amsl.com>; Sun, 23 Dec 2018 08:30:50 -0800 (PST)
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 B567212426A for <its@ietf.org>; Sun, 23 Dec 2018 08:30:50 -0800 (PST)
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 wBNGUm63041294 for <its@ietf.org>; Sun, 23 Dec 2018 17:30:48 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CCDA42015E9 for <its@ietf.org>; Sun, 23 Dec 2018 17:30:48 +0100 (CET)
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 C2B45200C16 for <its@ietf.org>; Sun, 23 Dec 2018 17:30:48 +0100 (CET)
Received: from [10.8.68.10] ([10.8.68.10]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id wBNGUm6C029527 for <its@ietf.org>; Sun, 23 Dec 2018 17:30:48 +0100
To: its@ietf.org
References: <7492e4cc1b2140f09b37071b3e85d549@boeing.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <746b0b3c-5a8e-a832-3c73-26e8029c3b71@gmail.com>
Date: Sun, 23 Dec 2018 17:30:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <7492e4cc1b2140f09b37071b3e85d549@boeing.com>
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/KJZtdVJiBzoubTt0HpaZjqL41ks>
Subject: Re: [ipwave] Route Information Options in IPv6 Neighbor Discovery
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: Sun, 23 Dec 2018 16:30:53 -0000

Fred, I will read this.
We implement something like RIO ND options in vehicle-to-vehicle 
communications.  The first trial in cars on dedicated track is on 
January 8th.

Le 23/12/2018 à 17:23, Templin (US), Fred L a écrit :
> Here is a draft on including Route Information Options in IPv6 Neighbor
> Discovery Messages:
> 
> https://datatracker.ietf.org/doc/draft-templin-6man-rio-redirect/
> 
> It allows for including Route Information Options (RIOs) in IPv6 ND
> messages other than RAs. This is useful for vehicular nodes when the
> node needs to inform neighbors of its delegated prefixes using NS

I will look at it.

I have a doubt why they are called 'delegated' prefixes, because the 
prefixes we put in RIOs are not delegated: they are hardcoded in cars. 
(they dont pre-arrive by DHCPv6PD).

Alex

> and NA messages (and sometimes also RS and Redirect). With this
> method, an established IPv6 ND option is used for carrying routing
> information without having to define a new IPv6 ND option type.
> The draft also allows for the inclusion of "attributes" with the route
> in case the RIO needs to include ancillary information besides just
> prefix and prefix length.
> 
> We use this for our AERO proposal which has been discussed
> widely for use in Unmanned Aerial Vehicles but also have
> obvious implications for other vehicular applications. Please
> review the draft and post any comments or insights.
> 
> Thanks - Fred
> 
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its
>