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

Hi Alex,

> -----Original Message-----
> From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre Petrescu
> Sent: Sunday, December 23, 2018 8:31 AM
> To: its@ietf.org
> Subject: Re: [ipwave] Route Information Options in IPv6 Neighbor Discovery
> 
> 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.

OK. It would be good to use an established IPv6 ND option if we can and
RIO is already available. That is the basis of the draft.

We are also using the option for aerial vehicles (manned and unmanned);
so far in Boeing-internal trials, but we are starting to talk about it in the
broader industry.

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

It is the same way for airplanes and unmanned air vehicles. The vehicle
has a prefix that has been pre-assigned before first use. For manned
aircraft, the proposal is to use a /32 IPv6 prefix followed by a 24-bit
aircraft serial number that is assigned to the aircraft by ICAO. So,
each aircraft has a /56 prefix that is pre-assigned.

We call it a "delegated prefix" though because it has been assigned
to the aircraft (i.e., delegated) and must be injected into the routing
system the same way that a DHCPv6 delegated prefix would be. But,
there is no requirement to use DHCPv6 PD in all scenarios. You might
also be interested to read 'draft-templin-v6ops-pdhost' and also
draft-templin-6man-dhcpv6-ndopt' which talk about prefix delegation
services other than DHCPv6 (including pre-assigned administratively
configured).

Happy Holidays, everyone.

Fred

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