I'm following this thread with interest.
Car will have multiple prefixes, for different usages. The car makers will probably allocate them an ULA (no decision made on this) for diagnostic purposes and remote software updates. In addition, another prefix will be alocated to the vehicle for a number of comfort/mobility services and traffic efficiency applications requiring Internet access, and that, following what is current written in ITS (Intelligent Transport Systems) standards for the vehicles (private automobiles but also trucks, buses, etc) would be handled by a permanent and global IPv6 prefix (allocated by car makers themselves, but more likely third parties) and mobility support standards (NEMO [RFC3963], MCoA [RFC5648]: see e.g. ISO TC204. At this stage, this is not yet widely supported by the automobile industry, though, also the Car-to-Car Communication Consortium and the Wave architecture do have IPv6 building blocks (not completely defined). At the time being, the automobile industry is more concerned about vehicle-vehicle (V2V) and vehicle-roadside (V2R) communications for time-critical road safety applications based on 802.11p and not using IP. But other stakeholders like road operators and road authorities concerned with traffic efficiency and non time-critical information for road safety have IPv6 in their roadmap. In addition, there is the second current which is in-vehicle telematics using cellular networks and LTE in particular, but these are not the same people within the automobile industry. Once they will all have to converge, and this convergence is initiated through the Cooperative ITS set of standards defined currently at ISO (TC204), CEN (TC278), ETSI (TC ITS). So, IPV6 is in a number of Cooperative ITS standards (see Cooperative ITS and more importantly the CALM standards ISO 21217 and ISO 21210 which defines the communication architecture and how IPv6 would fit in for Cooperative ITS). If you are up to buy IISO 21210, I would advice you to wait for a couple of months as a new version is going to be published (ISO standards are not for free). You may want to check: - these slides: https://www-roc.inria.fr/imara/dw/_media/ipv6-its/20101109-cvis-ipv6-m5-itst.pdf - or this paper: https://www-roc.inria.fr/imara/dw/_media/ipv6-its/20101109-cvis-ipv6-m5-itst-paper.pdf
So, the "next edition of the car" is on track. Any recommandation from the IETF would be welcome but should be based on the grounds of the ITS needs, scenarios, and their standards.
In addition, let me point out about aeronautics for which there exist IPv6 addressing scheme (the SANDRA project has delivered such a scheme but I don't know if it is public (yet or ever going to).
Regards, Thierry. On 27/09/11 17:23, Ray Hunter wrote:
Who are we trying to kid about there being no need for a connection to the Internet?FYI A consortium in the Netherlands have just announced a scheme that is planning to link in-car navigation systems with traffic control and information systems, and also public transport systems, so that if there's a traffic jam and it is going to be faster to take the train than drive, the car driver will be redirected to the nearest train station. The system should even being able to reserve a car parking spot on the fly in advance. They expect a prototype in October. The idea being that coordinated transport reduces the need for infrastructure spending. And I know of at least one group who have been experimenting with car-car and car-infra communication.regards, RayHMessage: 3 Date: Tue, 27 Sep 2011 15:36:31 +0200 From: Roland Bless<roland.bl...@kit.edu> To: 6man<ipv6@ietf.org> Subject: Centrally assigned "ULAs" for automotives and other environments Message-ID:<4e81d15f.6090...@kit.edu> Content-Type: text/plain; charset=ISO-8859-15 Hi, it seems that there is currently not much interest in ULA-Cs (centrally assigned ULAs). I came across several use cases, where manufacturers (e.g, those of cars, airplanes, or smart metering environments) would need internal/closed IPv6-based networks (maybe only for internal control and management), that have no connection to the Internet. Roland-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
<<attachment: thierry_ernst.vcf>>
-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
