this is the largest wrong myth about IPv6 stateless address autoconfiguration. there is no requirement, at all, to use MAC/EUI64 address for the lowermost 64 bits.
the requirement is to have the following properties: - the value should be stable across reboots - there is very low likelyhood to make collisions
so good candidate would be MD5(hostname) or something alike.
noone can escape from OS fingerprinting other than OpenBSD-like "randomize every field" aproach.
itojun # ipv6samurais.com: Saving the World with Code and Sword
::ffff:10.1.1.1 type of syntax is just for use inside IPv6-capable node, so that programs that runs on IPv6 socket can manipulate IPv4 connection on the wire.
Transition issues are discussed in IETF ngtrans working group, so it may be useful if you check IETF drafts named "draft-ngtrans-*".
If you write domain name in URL, you do not need to say "ipv6". For example, www.kame.net has both A and AAAA records and you can just specify http://www.kame.net/, and you'll connect to either of them (just like when a web server have multiple IPv4 addresses).
Numeric IPv6 address is little trickier because they have colon inside. for this there are several draft submitted in IETF.
QoS still needs big discussion until put into real wide area use. So, IPv6 reserves necessary header field for future use by some-QoS-protocol-deployed. This is the best thing IPv6 guys can do at this moment, I believe.
Slashdot Mirror
this is the largest wrong myth about IPv6 stateless address autoconfiguration.
there is no requirement, at all, to use MAC/EUI64 address for the lowermost 64 bits.
the requirement is to have the following properties:
- the value should be stable across reboots
- there is very low likelyhood to make collisions
so good candidate would be MD5(hostname) or something alike.
noone can escape from OS fingerprinting other than OpenBSD-like "randomize every field" aproach.
itojun
# ipv6samurais.com: Saving the World with Code and Sword
those who are very vocal are not using IPv6 daily. they are from ivoly towers.
itojun
# ipv6samurais.com: Saving the World with Code and Sword
::ffff:10.1.1.1 type of syntax is just for use inside IPv6-capable node, so that programs that runs on IPv6 socket can manipulate IPv4 connection on the wire.
Transition issues are discussed in IETF ngtrans working group, so it may be useful if you check IETF drafts named "draft-ngtrans-*".
If you write domain name in URL, you do not need to say "ipv6". For example, www.kame.net has both A and AAAA records and you can just specify http://www.kame.net/, and you'll connect to either of them (just like when a web server have multiple IPv4 addresses).
Numeric IPv6 address is little trickier because they have colon inside. for this there are several draft submitted in IETF.
QoS still needs big discussion until put into real wide area use. So, IPv6 reserves necessary header field for future use by some-QoS-protocol-deployed. This is the best thing IPv6 guys can do at this moment, I believe.
In the past proposal address was variable-length, but this was rejected in standardization process because it gets harder to code.