QUOTE(wKkaY @ Jan 20 2012, 03:35 PM)
Well last I checked, IPv6 doesn't make you declare your assets in the packet header. Please explain convincingly your analogy between them?
As for IP addresses letting you be tracked to your individual device through the MAC address, consider this. I've made a few forum posts here recently with IPv6 and out-of-the-box Windows 7. Vista's behavior is the same AFAIK, not sure about XP.
These are my IPs:
2405:4600:3004:0:5e8:764e:6c64:88ba
2405:4600:3004:0:78bc:d939:b11e:50fb
2405:4600:3004:0:e962:c9a9:8620:d8a
2405:4600:3004:0:f52e:9644:9144:45a7
2405:4600:3004:3:b091:165b:3c98:db0c
Questions:
1) Can you derive my MAC address?
2) Why does my IP keep changing throughout the week?
Temporary IPv6 Address Cloaking per RFC 3041?
My stance is still that IPv6 should only be used by people who KNOWS what they're doing with their setup.
The DCOMS engineers who are network administrators/ISP are the ones who knows the way around these things.
All these will put the end user at great risk of exposure if they are NOT properly INFORMED and EDUCATED about
EUI-64 implementation of IPv6.
Here's why and how they plan to merge your device's MAC into IPv6 with EUI-64. This will be used to assign unique static IP in future instead of manually mapping them with MAC IDs.

Noticed that your sets of Manufacturer ID and Device IDs from your MAC are cleverly integrated into your IPv6 by reserving the last 8 bytes? If you do not cloak your IPv6 address carefully, what device you're using can be discovered by authorities at your location.Even worst your mobile device such as smartphones will even record all your movement into a secret log like what Apple did last time?
Concerns About IPv6 and Its BackgroundQUOTE
The division of IPv6 addresses into distinct topology and interface identifier portions raises an issue new to IPv6 in that a fixed portion of an IPv6 address (i.e., the interface identifier) can contain an identifier that remains constant even when the topology portion of an address changes (e.g., as the result of connecting to a different part of the Internet). In IPv4, when an address changes, the entire address (including the local part of the address) usually changes. It is this new issue that this document addresses.
A more troubling case concerns mobile devices (e.g., laptops, PDAs, etc.) that move topologically within the Internet. Whenever they move (in the absence of technology such as mobile IP [MOBILEIP]), they form new addresses for their current topological point of attachment. This is typified today by the "road warrior" who has Internet connectivity both at home and at the office. While the node's address changes as it moves, however, the interface identifier contained within the address remains the same (when derived from an IEEE Identifier). In such cases, the interface identifier can beused to track the movement and usage of a particular machine.
For example, a server that logs usage information together with a source addresses, is also recording the interface identifier since it is embedded within an address. Consequently, any data-mining technique that correlates activity based on addresses could easily be extended to do the same using the interface identifier. This is of particular concern with the expected proliferation of next-generation network-connected devices (e.g.PDAs, cell phones, etc.) in which large numbers of devices are inpractice associated with individual users (i.e., not shared). Thus, the interface identifier embedded within an address could be used to track activities of an individual, even as they move topologically within the internet.
Source:
https://tools.ietf.org/html/rfc3041Is this clear enough?
Most of the regular users don't even know what is DHCP and hex-binary conversions, they are in for big trouble if they choose to use IPv6 blindly.
Added on January 21, 2012, 5:26 pmQUOTE(wKkaY @ Jan 20 2012, 04:04 PM)
I see why you're thinking that way. You think that $ISP will set aside dedicated copper/wavelengths for IPv6 traffic. I think they'll dual-stack existing links, so congestion that affects an IPv4 user will also affect an IPv6 user traversing the same path.
It's not I "think", it's by observation and experience.
Why is Streamyx assigning some unusable range of IPs around which differs greatly to some regular ones?
So much that they give awfully bad results to certain server locations and are not standardized?
Hey not fair^^
How come I can't post twice like you above but instead my posts got merged?
This post has been edited by iipohbee: Jan 21 2012, 05:29 PM