|
|
Yes, I reached out a couple of weeks back, but have yet to hear back.
Chris
Swish Fibre Team I have just raised it in TTTS to see if it can be progressed subject to any checks/verification
Hi Chris, looks like you have now been elevated. Keep up the good work 
Appreciate your help dect =)
Edited by Swish_Fibre (Mon 14-Feb-22 17:08:08)
|
|
The above post has been made by an ISP REPRESENTATIVE (although not necessarily the ISP being discussed in the post).
|
|
|
The problem is content providers are not the problem, broadband isps are
I see it the other way round. Right now, there are plenty of big content providers that are IPv4-only (like the BBC for example). As a result, this forces the ISP to provide IPv4 (or dual-stack). And dual-stack doesn't give you access to any additional significant part of the Internet, so most ISPs are stilll IPv4.
However, once *all* the important content is dual-stack, then it starts to become plausible that people will go to IPv6-only broadband connections.
Interesting that you really dont like the idea. You not even neutral on it, which has me curious. 
Which idea? I don't the idea of forcibly repatriating IPv4 blocks from one ISP to another, because it can't be done, and even if it could it wouldn't solve the problem.
IPv6 on the other hand I'm all in favour of - home network is very happily dual-stacked. But then I'm a techie so like playing with this stuff.
|
|
|
Right now, there are plenty of big content providers that are IPv4-only (like the BBC for example). That's what I thought, but:
ping6 bbc.co.uk
PING6(56=40+8+8 bytes) {my IP} --> 2a04:4e42::81
16 bytes from 2a04:4e42::81, icmp_seq=0 hlim=58 time=8.237 ms
16 bytes from 2a04:4e42::81, icmp_seq=1 hlim=58 time=8.474 ms
16 bytes from 2a04:4e42::81, icmp_seq=2 hlim=58 time=8.500 ms
16 bytes from 2a04:4e42::81, icmp_seq=3 hlim=58 time=15.239 ms
16 bytes from 2a04:4e42::81, icmp_seq=4 hlim=58 time=8.525 ms
16 bytes from 2a04:4e42::81, icmp_seq=5 hlim=58 time=8.035 ms
16 bytes from 2a04:4e42::81, icmp_seq=6 hlim=58 time=8.216 ms
16 bytes from 2a04:4e42::81, icmp_seq=7 hlim=58 time=8.239 ms
???
Bill
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
Is it the same for www.bbc.co.uk ?
I ask as I thought www is hosted by a CDN, when bbc.co.uk without the www is different. I recall that iplayer is on the www URL for browsers. No idea where SmartTVs go.
(I don't have IPv6 on VM).
22 years of broadband connectivity since 1999 trial - Live BQM
Edited by jchamier (Tue 15-Feb-22 10:22:06)
|
|
|
Is it the same for www.bbc.co.uk ? Nope:
ping6 www.bbc.co.uk
ping6: getaddrinfo -- nodename nor servname provided, or not known
I don't know enough about these things to have any idea what may be inferred from that, I'll leave it to others who may be interested!
Bill
|
|
|
Thanks.
22 years of broadband connectivity since 1999 trial - Live BQM
|
|
|
That's what I thought, but:
ping6 bbc.co.uk
PING6(56=40+8+8 bytes) {my IP} --> 2a04:4e42::81
16 bytes from 2a04:4e42::81, icmp_seq=0 hlim=58 time=8.237 ms
16 bytes from 2a04:4e42::81, icmp_seq=1 hlim=58 time=8.474 ms
bbc.co.uk is accessible via IPv6, but it does *nothing* except issue a redirect to www.bbc.co.uk. And www.bbc.co.uk is *not* accessible by IPv6.
| Text | 1
23
45
6 | $ curl -v https://bbc.co.uk
* Trying 2a04:4e42::81:443...* Connected to bbc.co.uk (2a04:4e42::81) port 443 (#0)
...< HTTP/2 301
< location: https://www.bbc.co.uk/ |
So they are basically cheating to get a green tick on some "IPv6-ready" tester for their domain.
Edited by candlerb (Tue 15-Feb-22 11:21:54)
|
|
|
So they are basically cheating to get a green tick on some "IPv6-ready" tester for their domain. Sneaky
Thanks 👍
Bill
|
|
|
The problem is content providers are not the problem, broadband isps are
I see it the other way round. Right now, there are plenty of big content providers that are IPv4-only (like the BBC for example). As a result, this forces the ISP to provide IPv4 (or dual-stack). And dual-stack doesn't give you access to any additional significant part of the Internet, so most ISPs are stilll IPv4.
However, once *all* the important content is dual-stack, then it starts to become plausible that people will go to IPv6-only broadband connections.
Interesting that you really dont like the idea. You not even neutral on it, which has me curious.
Which idea? I don't the idea of forcibly repatriating IPv4 blocks from one ISP to another, because it can't be done, and even if it could it wouldn't solve the problem.
IPv6 on the other hand I'm all in favour of - home network is very happily dual-stacked. But then I'm a techie so like playing with this stuff.
Content providers going dual stack would give absolutely no motivation to broadband providers to rollout IPv6, going single stack IPV6 on the other hand.....
Some isp's evidently are not going to bother until they forced to by a regulator or there is a fiancial gain from it.
Edited by Chrysalis (Thu 17-Feb-22 15:16:25)
|
|
|
Some isp's evidently are not going to bother until they forced to by a regulator or there is a fiancial gain from it. Sadly I think Virgin Media is in this bracket. With no sign of any altnet, I'm stuck with VM or trying to sort out an HE tunnel (not easy with a dynamic WAN IP).
The customers of the AltNets that have to use CGNAT for IPv4 I hope would be the ones that have IPv6 as standard and will benefit from the content providers moving to v6 / dual stack.
22 years of broadband connectivity since 1999 trial - Live BQM
|
Pages in this thread: 
Print Thread
