Hi Hans,
Do you know there is a "bug" in Android with IPv6?
I had to disable IPv6 in all my customers due to this issue.(*)
(*) https://code.google.com/p/android/issues/detail?id=79576
While IPv6 is not fully supported by the majority of the devices, it
cant be deployed.
Regards,
El 30/08/2015 a las 18:02, Hans Petter Holen escribió:
On 28.08.2015 15:13, Nick Hilliard wrote:
Anyone is free to suggest a better mechanism. If you have some ideas which
are better that what's already there, please feel free to write a proposal.
Maybe something along the lines of "you can have a second /22" after a
certain period of time if you only have a /22.
The rationale behind this could be that RIPE NCC got more address space
than anticipated when the last /8 was made.
According to
https://www.ripe.net/publications/ipv6-info-centre/about-ipv6/ipv4-exhaustion/ipv4-available-pool-graph
RIPE NCC currently have 17.7 M IPv4 addresses left - which is slightly
more than a /8
(https://www.ripe.net/publications/ipv6-info-centre/about-ipv6/ipv4-exhaustion/ipv4-available-pool-graph)
NRO June figures:
https://docs.google.com/viewer?url=https%3A%2F%2Fwww.nro.net%2Fwp-content%2Fuploads%2FNRO_Q2_2015.pdf
Afrinic: 2.7
RIPE NCC: 1.08
APNIC: 0,69
Lacnic: 0.16
Arin: 0.1 now down to 0.0015
So if somebody want to pursue this I suggest looking a t
https://www.ripe.net/publications/docs/ripe-642
and create a proposal using the Policy template in Appendix B
But it is really time to get serious about IPv6.
(Since you can do Google and Facebook on v6 - what more do you want:-)
