[ppml] Those pesky EUI-64's causing a shortage of IPv6 space (Was: [address-policy-wg] Those pesky ULAs again)

A good example where EUI64 is needed or at least plausible. 

Setting manual addresses on your IPv6 door-knobs makes as much sense as 
setting jumpers and DIP switches for SCSI disk drive numbers.
The embedded realm is a huge territory for leveraging IP instead of 
inventing new protocols. It's also an area where the IP components may 
not even be visible to the consumer unless you look under the hood.

You want DHCP for your IPv6 door knobs? Probably a good feature, but 
maybe auto-registering with manufacturer installed certificates and well 
known addresses is better, and the EUI64 happens to be your S/N so you 
can correlate your asset tags, support contracts and inventory. Similar 
processes exist for IP phones and lightweight (centrally managed) 
wireless access points, although are IPv4/DHCP based.

But do you also want DHCP (static?) for the IPv6 link between the IPv6 
door knob's optical handle rotation sensors  and the actuators 
controlling the latch movement and tactile feedback?

Where does it stop? These are "silly" examples, but technology keeps 
creeping up and making them reality.



Paul_Vixie at isc.org wrote:
>> But why would anybody want  to 'ban' EUI-64 configured addresses?
>>     
>
> because if it remains in the standard, then everybody will have to support
> it and networks will have to be allocated on /64 boundaries for all of the
> yet-unborn IPv6 capable SNMP-monitorable door knobs.
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.arin.net/pipermail/ppml/attachments/20070604/c0eab238/attachment.html