Le 04/04/2013 21:56, Manfredi, Albert E a écrit :
-----Original Message----- From: Alexandru Petrescu
[mailto:alexandru.petre...@gmail.com]
Some applications involving the use of VIN may have been
discussed.
One requirement may come from V2V communications when
infrastructure is not available: how to know the IP address of the
seen vehicle when DNS is unavailable.
If these comms are tactical, I would go to something more like
802.11 ad-hoc network, and do the comms at layer 2.
YEs, the link between egress WiFi interfaces of each vehicle (not their
ingress WiFi interfaces - in-car), could form a typical 802.11 ad-hoc
network.
The communications on that link may be layer but could also be IP.
Alternatively, the vehicle can use its assigned IPv6 /64 prefix
(which need not be related to anything specific like a VIN),
A /64 inside a vehicle may not be used to be assigned on the link
_between_ vehicles, because there is a Router between the inside and the
outside of the vehicle. This inside-vehicle prefix could be 'announced'
to the other vehicle, but not assigned on that adhoc network.
About the non-VIN aspect: the inside-vehicle IPv6 /64 prefix may indeed
be tightly related to that vehicle, without using VIN. For example, it
could be dynamically configured using DHCP: the MR in vehicle runs
Mobile IP and then executes DHCP Prefix Delegation to its Home Agent.
The prefix thus obtained is for that particular vehicle.
When doing so, one may be interested to dynamicall configure always same
prefix for that particular vehicle. That could be realized by using MAC
address: do DHCP and put the MAC address of the requesting interface.
But many egress interfaces (such as LTE) don't have MAC addresses. One
may then put a NAI (Network Access Identifier). But NAI is under the
form "u...@example.com". But here there is no particular human user -
it's the MR of a car (Mobile Router).
Otherwise, one may do an address plan for all vehicles of one
manufacturer and stamp the IPv6 /64 into one vehicle. That poses some
questions about revoking addresses after 10year use, or whether they are
Provider-Independent or Provider-Dependent.
and then use MANET. Seems built to order for MANET, no?
In general yes, it looks much as MANET is well adapted for this
vehicle-to-vehicle communications.
However, there may be some difficulties that could be analyzed (which
MANET protocol? and how does it do address configuration?).
Other requirement of using parts of the VIN would be remote
software update: extract the field of the VIN which represents
Manufacturer ID, make an IPv6 multicast group of it, and send the
update accordingly.
For that, I would way prefer using the VIN as part of a DNS name,
which is then mapped to the IP address of the vehicle. This makes
the problem more amenable to flexible solutions, like allowing the
IP address prefix to be changed periodically, or allowing the vehicle
ID to be associated in any number of ways, other than just a VIN.
I tend to agree. A solution could be devised where the VIN may be
mapped into a DNS name and make place for more flexible solutions.
There may also be some problems with relying on DNS when the vehicle is
disconnected from the infrastructure.
Or have a DNS server in a vehicle but make sure it's disconnected very
often ('autonomous' mode of operation). I am not sure how this could be
made to work.
By the way, this vehicle application of IPv6 is another example that
makes me kringe about the waste of even IPv6 address space, when we
continue to discourage the use of longer than 64-bit prefixes.
I agree. I think address planning should consider avoid potential
waste, and the way in which vehicle industry looks at vehicle lifetime
planning (which is different than the typical computer lifetime planning).
Alex
Bert
These are just ideas having been floated in various contexts.
VIN-to-IPv6-InterfaceIdentifier is just one little thing which
could or not could not work.
Alex
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
