<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">As far as I know ULA was deprecated in 9/2004 however worse yet it isn’t routable period so it isn’t of much use since IPv6 to IPv6 NAT isn’t permitted officially.
I know that Cisco proposed IPv6 to IPv6 NAT but last I checked it wasn’t accepted. Much of the IPv6 production equipment won’t handle a statically configured IPv6 address such as the FE80/10 address and then still be able to use SLAAC or DHCPv6 to obtain
a routable IPv6 address. This gets us to the problem. As far as I know IPv6 is supposed to be globally routable by definition and while ULAs are a great idea for completely offline networks I don’t think at this point are a good solution for regular networks
connected to the internet. As we add IoT equipment to local networks IPv6 is going to become very important to our community. When local networks go from dozens of devices to thousands IPv4 becomes unusable without network segmentation that most customers
do not have the experience to handle. Think of it this way, a home network has a thousand IoT devices that will attempt to register their name with the local DNS server but because a lot of the local inexpensive consumer routers can’t handle DNS registration
this creates a major problem. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Kristian McColm <Kristian.McColm@rci.rogers.com>
<br>
<b>Sent:</b> Wednesday, October 23, 2019 7:35 AM<br>
<b>To:</b> Michael Sturtz <Michael.Sturtz@PACCAR.com>; ipv6-ops@lists.cluenet.de<br>
<b>Subject:</b> Re: ipv6-ops Digest, Vol 159, Issue 1<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Isn't that what ULA's are for?<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
<a href="mailto:ipv6-ops-bounces+kristian.mccolm=rci.rogers.com@lists.cluenet.de">
ipv6-ops-bounces+kristian.mccolm=rci.rogers.com@lists.cluenet.de</a> <<a href="mailto:ipv6-ops-bounces+kristian.mccolm=rci.rogers.com@lists.cluenet.de">ipv6-ops-bounces+kristian.mccolm=rci.rogers.com@lists.cluenet.de</a>> on behalf of Michael Sturtz <<a href="mailto:Michael.Sturtz@PACCAR.com">Michael.Sturtz@PACCAR.com</a>><br>
<b>Sent:</b> October 23, 2019 10:26 AM<br>
<b>To:</b> <a href="mailto:ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de</a> <<a href="mailto:ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de</a>><br>
<b>Subject:</b> RE: ipv6-ops Digest, Vol 159, Issue 1</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">I have found more problems with the DHCPv6-PD. The issue is on many home networks where people are using server type hardware such as Windows(TM) networks where DNS is used to locate and secure the network
the renumbering event creates major problems as the on premises DHCPv6 server has no way to understand that a renumber event has occurred. People are very used to the IPv4 RFC 1918 static addressing where nothing on their local internal network will change
without notice. The fact that ISPs can randomly change the internal delegated address without notice is a major problem. That will confuse people and cause problems especially where a customer has equipment such as Windows or Linux servers or other equipment
that requires static addressing or DHCPv6. I understand that for certain operational reasons ISPs need to renumber addresses however I suggest we discourage the practice. We also could modify the RFC to require a message to be sent by CPE to all downstream
network devices that a network renumber event is being scheduled. This can be sent as a multicast message that encodes the date that the renumbering will occur. I realize that we need to understand the security implications of this. This is just one idea
that could smooth the renumbering events when then have to happen for some operational reason.
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ipv6-ops-bounces+michael.sturtz=paccar.com@lists.cluenet.de">
ipv6-ops-bounces+michael.sturtz=paccar.com@lists.cluenet.de</a> <<a href="mailto:ipv6-ops-bounces+michael.sturtz=paccar.com@lists.cluenet.de">ipv6-ops-bounces+michael.sturtz=paccar.com@lists.cluenet.de</a>> On Behalf Of
<a href="mailto:ipv6-ops-request@lists.cluenet.de">ipv6-ops-request@lists.cluenet.de</a><br>
Sent: Wednesday, October 23, 2019 3:00 AM<br>
To: <a href="mailto:ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de</a><br>
Subject: ipv6-ops Digest, Vol 159, Issue 1<br>
<br>
Send ipv6-ops mailing list submissions to<br>
<a href="mailto:ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.cluenet.de%2Fmailman%2Flistinfo%2Fipv6-ops&data=02%7C01%7CMichael.Sturtz%40PACCAR.com%7C0e31b7525c36472bb9e708d757c625c6%7Ce201abf9c5a343f88e29135d4fe67e6b%7C0%7C0%7C637074380867557710&sdata=XSlETXdVmXDZmb14C6uDMEU6Fl8wPKE4xPG0MG%2Fongw%3D&reserved=0">
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.cluenet.de%2Fmailman%2Flistinfo%2Fipv6-ops&amp;data=02%7C01%7Cmichael.sturtz%40paccar.com%7Ce0b1f347a5cf432a761e08d7579fc9b3%7Ce201abf9c5a343f88e29135d4fe67e6b%7C0%7C1%7C637074216137461832&amp;sdata=jmfELsU1SabFN%2BnPssOkByWoExIqjKfLhJCotAe40FA%3D&amp;reserved=0</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:ipv6-ops-request@lists.cluenet.de">ipv6-ops-request@lists.cluenet.de</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:ipv6-ops-owner@lists.cluenet.de">ipv6-ops-owner@lists.cluenet.de</a><br>
<br>
When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6-ops digest..."<o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal">This communication is confidential. We only send and receive email on the basis of the terms set out at
<a href="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rogers.com%2Fweb%2Fcontent%2Femailnotice&data=02%7C01%7CMichael.Sturtz%40PACCAR.com%7C0e31b7525c36472bb9e708d757c625c6%7Ce201abf9c5a343f88e29135d4fe67e6b%7C0%7C0%7C637074380867557710&sdata=AgOc1x%2Fe%2BD4rLITDmg%2BoHaa41spxWeRIlj7yacu6bHY%3D&reserved=0">
www.rogers.com/web/content/emailnotice</a><br>
<br>
<br>
<br>
Ce message est confidentiel. Notre transmission et réception de courriels se fait strictement suivant les modalités énoncées dans l’avis publié à
<a href="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rogers.com%2Faviscourriel&data=02%7C01%7CMichael.Sturtz%40PACCAR.com%7C0e31b7525c36472bb9e708d757c625c6%7Ce201abf9c5a343f88e29135d4fe67e6b%7C0%7C0%7C637074380867567668&sdata=Ep%2B56ciyDF4%2BVQsXWtLmbjAtExyEfICqfOplyYhQERQ%3D&reserved=0">
www.rogers.com/aviscourriel </a><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
</div>
</body>
</html>