Vehicle Identification Number-Based Unique Local IPv6 Unicast Addresses (VULA)
draft-imadali-its-vinipv6-vula-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sofiane Imadali , Alexandre Petrescu , Christophe Janneteau | ||
| Last updated | 2013-08-22 (Latest revision 2013-02-18) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Vehicle Identification Number (VIN) is standardized in ISO-3779 and ISO-3780. The VIN is made of 17 alphanumeric characters code that uniquely identifies a vehicle worldwide. Some public information related to a vehicle can be obtained knowing its VIN code. This code may also be used to enable novel vehicular networking communications. RFC 4193 introduces a globally unique IPv6 unicast address format intended for local communications, usually inside of a site. These addresses (ULA) are not expected to be routable on the global Internet. This document introduces a method to build a VIN-based IPv6 Prefix that is intended for local communications involving more than one hop (VULA). The VIN-based generated prefix is assured to be unique among other VIN-based generated prefixes. Typically, in a scenario involving several vehicles, each single vehicle (in which one Mobile Router is in charge) is capable of generating its own unique infrastructure-independent globally-scoped VIN-based IPv6 prefix. This document also describes some use cases where VULA could be exploited.
Authors
Sofiane Imadali
Alexandre Petrescu
Christophe Janneteau
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)