Most likely they'll follow APNIC assignment policy recommendation.
http://www.apnic.net/policy/ipv6-address-policy

i see... i take it that is your plan then.

Or you could like... change your v6 IP between every web page request

1) We don't need even to consider much and make lots of assumptions. Every TM Streamyx/Unifi users have already come to much conclusion that even with IPv4, they are getting variable results with different ranges.Even myself I've got a range that day which was so crappy, it was not even getting me anywhere: 174.145.174.x. From local/Singaporean server latency to speed, everything was like crawling.

Why IPv6 should give a bit of hope? There are still less users today and chances that you're going to get the "premium-like" ip which most Streamyx users are on the look out for.

2) My stance is still that privacy is every individual's basic rights. With all the scrutinization of social networking sites and blogs going on in this country, the trend is not going to make any fears by the public subside. Of course authorities are not going to make it obvious with their surveilance, who doesn't work along "the wolf in sheep skin concept"? Today it's all about deception and hideous motives.

In attempt of this today people study hard  and gain as much knowledge as they can so that they can prevent loopholes as a line of defense and at the same time try to find ways of circumventing an unknown problem(exploit).

Basic human nature in their attempts to equal God.

What everyone should be afraid of is RIR policy that make ISPs that assign prefixes larger than /64 to their customers to also SWIP that customer information (usually billing address at the minimum) into the ISP's net-block WHOIS data.

As I prefer to use vanity IPv6 address with fancy reverse DNS entries (maybe wkkay can made it to be shown next to the pale blue IPv6 text?), this mean I have to disable the privacy extension (via netsh), disable router solicitation, set up other stateful config in my wireless adapter to 1, then set up a static IPv6 address and add a route to the wireless adapter. See how much work I have to do just to let other people data mining me? My postal address has already been published anyway for the /48 I used here...

Microsoft truly make using IPv6 by other means that isn't SLAAC to be difficult to the end user.

As for other people on the network that has default Windows installation, all I have to do is to advertise a prefix with radvd and everything will work just fine with them. They probably doesn't even know their connection is IPv6-enabled.