Networking → [ipv6] How to know progress of an ISP reqarding IPv6?

Quote from my ISP.

quote:

---

We'll have IPv6 routing capability within our core network by the end of 2013 and plan to give IPv6 addresses by end of 2014.

---

Besides asking the ISP, how does one know the status/progress of the core network?

Thank you

[root@dns2 ~]# dig ptd.net

; > DiG 9.2.4 > ptd.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER- opcode: QUERY, status: NOERROR, id: 21540
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 12

;; QUESTION SECTION:
;ptd.net. IN A

;; ANSWER SECTION:
ptd.net. 2703 IN A 209.50.150.195

;; AUTHORITY SECTION:
ptd.net. 20342 IN NS dns5.ptd.net.
ptd.net. 20342 IN NS dns6.ptd.net.
ptd.net. 20342 IN NS dns1.ptd.net.
ptd.net. 20342 IN NS dns2.ptd.net.
ptd.net. 20342 IN NS dns3.ptd.net.
ptd.net. 20342 IN NS dns4.ptd.net.

;; ADDITIONAL SECTION:
dns1.ptd.net. 20342 IN A 204.186.0.201
dns1.ptd.net. 20342 IN AAAA 2606:9400:0:a:204:186:0:201
dns2.ptd.net. 20342 IN A 207.44.96.129
dns2.ptd.net. 20342 IN AAAA 2606:9400:0:b:207:44:96:129
dns3.ptd.net. 20342 IN A 204.186.0.203
dns3.ptd.net. 20342 IN AAAA 2606:9400:0:a:204:186:0:203
dns4.ptd.net. 20342 IN A 207.44.0.1
dns4.ptd.net. 20342 IN AAAA 2606:9400:0:b:207:44:0:1
dns5.ptd.net. 20342 IN A 204.186.80.169
dns5.ptd.net. 20342 IN AAAA 2606:9400:0:c:204:186:80:169
dns6.ptd.net. 20342 IN A 204.186.80.249
dns6.ptd.net. 20342 IN AAAA 2606:9400:0:d:204:186:80:249

;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Mar 28 08:21:16 2014
;; MSG SIZE rcvd: 419

by using public data to trace down any possible ways into network via IPv6... I found an IPv6 block of 2606:9400::/32 for Penteledata in ptd.net DNS records, that i misses last time... however the router is NOT in IPv6 BGP tables of my working IPv6 border router (which is probably how i missed it), indicating block is not routing properly on IPv6 internet, and so shouldn't be in their DNS records....as this will cause issues.

none of their IPv6 DNS server addresses below are reachable... ARIN shows the block belongs to "PTD" assigned in 2010, which appears to be when they started their migration.

I'm not sure why you care (about the core).

I will just say I found out v6 was finally available to me by noticing RAs were being multicasted and I would try occasionally with wide-dhcpv6 (in debug foreground mode, so I could see whether it was timing out or actually getting an address or prefix).