There seem to be a number of assumptions, some of which I suspect I am misunderstanding, in the case being described.

I tend to make two assumptions:
1) Even low end intra-automotive devices can cope with multiple addresses
2) Even low end automotive-internal devices will need to communicate externally.

From what you have described, it seems that all such extenral communication (whether to another vehicle, to a trusted monitoring entity, or to the Internet, will have to go through what you describe as a "proxy" which will deal with changing the IPv6.
Put differently, the only application communication will be via an ALG.

Based on our experience, that seems to be a very bad design target.
And it seems unnecessary for the goal of having stable itnernal addresses for internal communication.

Yours,
Joel M. Halpern

On 9/28/2011 3:57 PM, Roland Bless wrote:
Hi David,

On 28.09.2011 20:24, David Farmer wrote:
Yes, OUI exhaustion isn't and shouldn't be a problem unless we make
it one.

My point was if you implement your proposal without doing a more
classic ULA-C also, you will create demand for OUIs from the
enterprise world just so they can get registered ULAs.  There are not
enough OUIs to satisfy that demand, and it would be a waste, too.

So if you do an ULA-M you need to also do ULA-C to prevent those that
would be happy with ULA-C from consuming vast numbers of OUIs only
for the purpose of obtaining ULA.

I see your point now and agree. My intent was not to replace ULA-Cs,
but to propose something that fits more the intended use cases.

Regards,
  Roland
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to