<html 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=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><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;}
@font-face
{font-family:"Times New Roman \(Cuerpo en alfa";
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EstiloCorreo18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=ES link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>If you’re receiving the messages is because YOU subscribed to the list.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>If you subscribed to the list, you know how to unsubscribe.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>If you don’t know it, you should be smart enough to look into the email header and you will find how to do it.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Just in case you don’t know how to do it, here is it for you:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>List-Unsubscribe: <http://lists.cluenet.de/mailman/listinfo/ipv6-ops>,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'> <mailto:ipv6-ops-request@lists.cluenet.de?subject=unsubscribe><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'>Regards,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>Jordi<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>@jordipalet<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>El 1/4/20 6:08, "Sunita Badiga" <<a href="mailto:ipv6-ops-bounces+jordi.palet=consulintel.es@lists.cluenet.de">ipv6-ops-bounces+jordi.palet=consulintel.es@lists.cluenet.de</a> en nombre de <a href="mailto:indrules@aol.com">indrules@aol.com</a>> escribió:<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'>STOP FUCKING EMAILING ME <o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>UNSUBSCRIBE<o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-left:35.4pt'>On Mar 31, 2020, at 8:35 PM, james machado <<a href="mailto:hvgeekwtrvl@gmail.com">hvgeekwtrvl@gmail.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>The real problem is there are distinct use cases for both SLAAC and DHCPv6 and the people in charge of DHCPv6 keep screwing up. It should be possible to run either SLAAC/RA or DHCPv6 and have each offering provide the required information without having to run additional services just to get basic feature parity to IPv4. This is slowing implementation in enterprise networks.<o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>james<o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div></div></div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>On Tue, Mar 31, 2020 at 3:24 PM Brian E Carpenter <<a href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'>On 31-Mar-20 23:17, Mark Tinka wrote:<br>> <br>> <br>> On 31/Mar/20 12:09, <a href="mailto:sthaug@nethelp.no" target="_blank">sthaug@nethelp.no</a> wrote:<br>> <br>>> Note that there have been multiple requests for DHCPv6 to do this but<br>>> every attempt has been shot down.<br>> <br>> Yep - thankfully, we have an option.<br>> <br>> Operating two address assignment protocols is just silly.<br>> <br>> At my house, I don't even bother with DHCPv6 for DNS. I just use the<br>> IPv4 ones and let SLAAC assign IPv6 addresses to my devices. Just about<br>> done with the purist madness around this.<br><br>There's purism (which I don't understand) and there's also historical<br>baggage that is incredibly hard to get rid of. As I have reminded from<br>time to time, SLAAC was designed and implemented for IPv6 *before* DHCP<br>became a proven technology for IPv4 (i.e. many of us were still running<br>around manually assigning IPv4 addresses to newly installed Suns and<br>NCDs and the like). DHCPv6 was an afterthought.<br><br>Unfortunately, the purism has made it impossible to have a rational<br>discussion about engineering our way out of this historical duplication.<br><br>On 01-Apr-20 05:01, Gert Doering wrote:<br><br>...<br>> As soon as you have a larger routed network, mDNS falls short, and <br>> (unless you have a windows domain) there are no existing mechanisms<br>> to put a SLAAC v6 address into DNS...<br><br>I think there's no *deployed* mechanism. DynDNS is said to work in the<br>lab. There's also some hope that DNS-SD will alleviate this problem, <br>but only if it gets deployed.<br><br>> Yes, thanks, IETF. Well done.<br><br>It's not because nobody has tried. But the bridge between theory and<br>operations seems to be hard to cross.<br><br>On 01-Apr-20 07:21, James R Cutler wrote:<br><br>...<br>> Wouldn’t it be more cost effect in the long term to simply make SLAAC and DHCPv6 cooperative and complementary attributes of end-to-end networking? <br><br>Well, duh. What we need is more people with real operational smarts<br>able to spend a lot of time and patience in the IETF. Yes, I know<br>why that is hard. (I had operation smarts once; no longer.) But that<br>is the only way we we can get a pragmatic approach into RFC text.<br><br>Don't worry about the travel budget, because the IETF is going to<br>have to do much more of its work remotely for the next couple of years<br>anyway. But the time and patience investment is substantial.<br><br>Stay well,<br> Brian Carpenter<br><br><br><o:p></o:p></p></blockquote></div></div></blockquote></div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
<br>
</body></html>