<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><br><div dir="ltr">Sent from my iPad</div><div dir="ltr"><br><blockquote type="cite">On Oct 3, 2019, at 12:14 PM, Stephen Satchell <list@satchell.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>On 10/3/19 8:42 AM, Fred Baker wrote:</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Oct 3, 2019, at 9:51 AM, Stephen Satchell <list@satchell.net> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Someone else mentioned that "IPv6 has been around for 25 years, and why</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>is it taking so long for everyone to adopt it?" I present as evidence</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>the lack of a formally-released requirements RFC for IPv6. It suggests</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>that the "science" of IPv6 is not "settled" yet. That puts the</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>deployment of IPv6 in the category of "experiment" and not "production".</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>And, of course, we now have companies like T-Mobile and others</span><br></blockquote><blockquote type="cite"><span>turning IPv4 off. If that's an experiment, wow.</span><br></blockquote><span>The cellular data industry appears to have embraced IPv6 in one form or</span><br><span>another. I would expect that the network engineers have done some work</span><br><span>to keep IPv4 off their *internal* networks, but provide IPv4 access at</span><br><span>the edge. (Isn't a netblock within IPv6 intended to enable bridging to</span><br><span>IPv4?) The applications on the phon could be configured to search DNS</span><br><span>for AAAA addresses first.</span><br></div></blockquote><div><br></div>T-Mobile documented what they are doing at <a href="https://tools.ietf.org/html/rfc6877">https://tools.ietf.org/html/rfc6877</a>.<div><br><blockquote type="cite"><div dir="ltr"><span>My AT&T cell phone has both IPv4 and IPv6 addresses. The IPv4 address</span><br><span>is from my access point; the IPv6 address appears to be a public address.</span><br></div></blockquote><div><br></div>So does my T-Mobile phone. It got the IPv4 address from my friendly neighborhood WiFi. </div><div><br><blockquote type="cite"><div dir="ltr"><span>I would like to move to IPv6. I just don't want to shoot myself in the</span><br><span>foot, or cause trouble for other people, by being sure my edge router</span><br><span>"follows all the rules."</span><br></div></blockquote></div></body></html>