<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div>
<blockquote type="cite" class="">
<div class="">On 6 Mar 2017, at 12:26, Mikael Abrahamsson <<a href="mailto:swmike@swm.pp.se" class="">swmike@swm.pp.se</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">On Mon, 6 Mar 2017, Gert Doering wrote:<br class="">
<br class="">
<blockquote type="cite" class="">If a CPE has no v6 support, having it available on the DSLAM (in passive mode = do not start IPv6CP until the client initiates it) will not do harm.<br class="">
</blockquote>
<br class="">
The issue here isn't devices that do not support IPv6, it's the ones that do support IPv6 when it "suddenly" is turned on.<br class="">
<br class="">
<blockquote type="cite" class="">The mobile carriers nicely demonstrated how *not* to do it - by ignoring the mandate for IPv6 in 3G, and rolling out huge masses of v4-only handsets, they suddenly had a huge installed basis of, well, v4-only legacy devices
to deal with...<br class="">
</blockquote>
<br class="">
Most carriers do not control handsets anymore. Those days are long gone.<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">But the mobile situation is now becoming better, isn’t it? I read that >50% of the traffic to Facebook from the bigger US mobile operators is now IPv6. In the UK, we have at least one mobile operator with a growing deployment of over half a million
v6-only handsets - see <a href="https://indico.uknof.org.uk/event/38/contribution/8/material/slides/1.pdf" class="">https://indico.uknof.org.uk/event/38/contribution/8/material/slides/1.pdf</a>. </div>
<div class=""><br class="">
</div>
<div class="">tim</div>
</body>
</html>