Devices will create a local link address that starts with fe8, fe9, fea or feb - this is roughly analgous to the de-facto IPV4 standard of 169.x.x.x. (Includes FE80)
Teredo - I gather this allows people behind IPv4 network connections connect (directly, only) to web servers that are IPv6 - but you need a relay - which doesn't seem to be common. So... I'm not seeing this as useful outside of a campus environment.
Win7, and others, get a pseudo IPv6 IP and DNS servers through the Teredo adapter. This makes nslookup (command line) think the computer has IPv6 connectivity. Which makes it try to resolve IPv6 hosts in DNS. Which time out. But this is only supposed to affect nslookup. Hmm.
https://superuser.com/questions/720145/why-does-win7-sp7-64-bit-try-to-resolve-dns-agsint-ipv6-dns-servers
Web page shows BOTH IPV4 and IPV6 address, i.e. tests if you are on a dual-stack connection: http://whatismyipaddress.com/ds-check
Computer can have multiple IPv6 addresses. % sign tells which NIC it's on (kind of). Good read: https://superuser.com/questions/99746/why-is-there-a-percent-sign-in-the-ipv6-address
For database storage, it isn't that clear the proper length. Typical correct answer is 39 characters to store: ABCD:ABCD:ABCD:ABCD:ABCD:ABCD:ABCD:ABCD - but there's a weird IPV4 backwards compatible thing. Not sure if that's something you'll see in the wild - https://stackoverflow.com/questions/1076714/max-length-for-client-ip-address
tags: tcpip, network, internet, ipv6,