>>>>> "Alexandru" == Alexandru Petrescu <[email protected]> writes: Alexandru> 2 - the prefixes obtained from Registries, or from ISP (which one Alexandru> should I try first?) may come with a price tag. The more vehicles, Alexandru> the pricier the allocation.
Depending upon the way in which the VIN->subnet ID is formed, it might
be that each manufacturer should actually go and acquire a /28 or
something from their local RIR. That would be one way.
The RIRs might find that they want to adjust their policies and talk to
IANA, allocate this out of a Non-Connected Network space.
That would be, from the IETF point of view, the easiest way to do this.
Creating the subnetID could in fact be manufacturer proprietary, and the
document would just be a BCP on how not to do it wrong.
It would likely be, from the RIR and automotive industry, a complex way,
because I think neither RIR community nor automative community
knows or understands each other.
A different way would be for the IETF to instruct IANA to create a NCN
space, and designate the VIN-mapping as a part of it. This would be
harder for the IETF to do, but would I think, lead to a better world.
Alexandru> 3 - prefixes which are provider-assigned and/or provider
independent
Alexandru> may introduce routing churn in the core of the Internet - if
these
Alexandru> prefixes are numerous.
you have confused globally routable with globally unique.
These prefixes are simply *NOT* going to be announced in the core of the
Internet. If they *are*, it will be a manufacturer doing so, and and
using one of many tunneling technologies to get the packets to the right
place (whether it be IPsec, IPIP, MobileIPV6, GRE, or IP-over-Acoutistic
Carrier).
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
pgp2aeXBy6BZw.pgp
Description: PGP signature
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
