<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=utf-8"><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: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;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
border:none;
padding:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EstiloCorreo19
{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><!--[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=ES link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=ES-TRAD style='mso-fareast-language:EN-US'>Pues le diría que lea bien esos documentos y que, además, si se empeña en usar algo diferente del /48, no será visible en buena parte del mundo …<o:p></o:p></span></p><div><p class=MsoNormal><span lang=ES-TRAD style='font-size:10.5pt;color:black'><br>Saludos,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=ES-TRAD style='font-size:10.5pt;color:black;mso-fareast-language:EN-US'>Jordi<o:p></o:p></span></p></div><p class=MsoNormal><span lang=ES-TRAD style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='margin-left:35.4pt'><b><span style='font-size:12.0pt;color:black'>De: </span></b><span style='font-size:12.0pt;color:black'>LACTF <lactf-bounces@lacnic.net> en nombre de Amancio Mora Rodriguez <mora_amancio@hotmail.com><br><b>Responder a: </b><lactf@lac.ipv6tf.org><br><b>Fecha: </b>jueves, 5 de abril de 2018, 16:47<br><b>Para: </b>"lactf@lacnic.net" <lactf@lacnic.net><br><b>Asunto: </b>Re: [LAC-TF] LACTF Digest, Vol 169, Issue 4<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><a name="_MailOriginalBody"><span style='font-family:"Arial",sans-serif;color:black'>Realmente, el cliente tiene su propio direccionamiento Ipv60/48, pero el solo quiere utilizar una red /52 por sede. <o:p></o:p></span></a></p></div><div><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><span style='mso-bookmark:_MailOriginalBody'><span style='font-family:"Arial",sans-serif;color:black'>Qué se le tendría que decir al cliente final? Que configuración se le debe recomendar? <o:p></o:p></span></span></p></div><div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='mso-bookmark:_MailOriginalBody'><span style='font-family:"Arial",sans-serif;color:black'>Amancio Mora<o:p></o:p></span></span></p></div><p class=MsoNormal style='margin-left:35.4pt'><span style='mso-bookmark:_MailOriginalBody'><span style='font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></span></p></div><div class=MsoNormal align=center style='margin-left:35.4pt;text-align:center'><span style='mso-bookmark:_MailOriginalBody'><hr size=0 width="96%" align=center></span></div><div id="x_divRplyFwdMsg"><p class=MsoNormal style='margin-left:35.4pt'><span style='mso-bookmark:_MailOriginalBody'><b><span style='color:black'>From:</span></b></span><span style='mso-bookmark:_MailOriginalBody'><span style='color:black'> LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br><b>Sent:</b> Thursday, April 5, 2018 9:33:19 AM<br><b>To:</b> lactf@lacnic.net<br><b>Subject:</b> LACTF Digest, Vol 169, Issue 4</span></span><span style='mso-bookmark:_MailOriginalBody'> <o:p></o:p></span></p><div><p class=MsoNormal style='margin-left:35.4pt'><span style='mso-bookmark:_MailOriginalBody'> <o:p></o:p></span></p></div></div></div><div><p class=MsoNormal style='margin-left:35.4pt'><span style='mso-bookmark:_MailOriginalBody'>Send LACTF mailing list submissions to<br> lactf@lacnic.net<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> </span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>or, via email, send a message with subject or body 'help' to<br> lactf-request@lacnic.net<br><br>You can reach the person managing the list at<br> lactf-owner@lacnic.net<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of LACTF digest..."<br><br><br>Today's Topics:<br><br> 1. Re: LACTF Digest, Vol 168, Issue 17 (JORDI PALET MARTINEZ)<br> 2. Re: LACTF Digest, Vol 169, Issue 2 (JORDI PALET MARTINEZ)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 05 Apr 2018 16:30:12 +0200<br>From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es><br>To: <lactf@lac.ipv6tf.org><br>Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>Message-ID: <1814AB46-668D-4B34-A7AD-921BD2C11946@consulintel.es><br>Content-Type: text/plain; charset="utf-8"<br><br>En general si anuncias algo mas largo que /48, te lo van a filtrar.<br><br> <br><br>Porque estas asignando menos de un /48 ?<br><br> <br><br>Sugiero leer:<br><br> <br><br></span><a href="https://datatracker.ietf.org/doc/draft-palet-v6ops-p2p-links/"><span style='mso-bookmark:_MailOriginalBody'>https://datatracker.ietf.org/doc/draft-palet-v6ops-p2p-links/</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br><br> <br><br>y<br><br> <br><br></span><a href="https://www.ripe.net/publications/docs/ripe-690"><span style='mso-bookmark:_MailOriginalBody'>https://www.ripe.net/publications/docs/ripe-690</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br><br> <br><br><br>Saludos,<br><br>Jordi<br><br> <br><br>De: LACTF <lactf-bounces@lacnic.net> en nombre de Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>Responder a: <lactf@lac.ipv6tf.org><br>Fecha: jueves, 5 de abril de 2018, 16:16<br>Para: "lactf@lacnic.net" <lactf@lacnic.net>, "lactf@lacnic.net" <lactf@lacnic.net><br>Asunto: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br><br> <br><br>Buenos d?as,<br><br>Ingenieros cual es la m?scara m?s peque?a en Ipv6 que podemos anunciar a Internet. <br><br>Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.<br><br>Cualquier inquietud con gusto. <br><br>Cordialmente ?, <br><br><br>Amancio Mora<br><br> <br><br>From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>Sent: Tuesday, March 27, 2018 10:00:01 AM<br>To: lactf@lacnic.net<br>Subject: LACTF Digest, Vol 168, Issue 17 <br><br> <br><br>Send LACTF mailing list submissions to<br> lactf@lacnic.net<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> </span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>or, via email, send a message with subject or body 'help' to<br> lactf-request@lacnic.net<br><br>You can reach the person managing the list at<br> lactf-owner@lacnic.net<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of LACTF digest..."<br><br><br>Today's Topics:<br><br> 1. Fwd: Fwd: RFC4941bis (Fernando Gont)<br> 2. Fwd: Requirements for IPv6 Temporary Addresses (Fernando Gont)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 26 Mar 2018 16:15:20 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: "lactf@lacnic.net" <lactf@lacnic.net>, Lista para discusi?n de<br> seguridad en redes y sistemas informaticos de la regi?n<br> <seguridad@lacnic.net><br>Subject: [LAC-TF] Fwd: Fwd: RFC4941bis<br>Message-ID: <9d1dfd63-db99-75ad-a58c-e82e049fd3e3@si6networks.com><br>Content-Type: text/plain; charset=windows-1252<br><br>FYI<br><br><br>-------- Forwarded Message --------<br>Subject: Fwd: RFC4941bis<br>Date: Mon, 26 Mar 2018 14:48:34 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com><br><br>Folks,<br><br>As the subject implies, this is an effort to revise RFC4941 to fix the<br>issues in it.<br><br>Comments welcome... even more if sent to (or CC'ed to ipv6@ietf.org)<br><br>Thanks!<br><br>Best regards,<br>Fernando<br><br><br><br><br>-------- Forwarded Message --------<br>Subject: RFC4941bis<br>Date: Mon, 26 Mar 2018 04:55:06 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>Organization: SI6 Networks<br>To: 6man@ietf.org <6man@ietf.org><br>CC: 6man-chairs@tools.ietf.org <6man-chairs@tools.ietf.org><br><br>Folks,<br><br>Based on the comments on the last 6man meeting, we have done the following:<br><br>1) We have asked the RFC Editor the xml source for RFC4941, applied the<br>minimum changes to publish it as an I-D, and posted it as:<br><</span><a href="https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>2) We subsequently applied all the corresponding changes to arrive to<br>something similar to what we had in draft-gont-6man-rfc4941bis-00<br>(please note the slight difference in the filename), presented at the<br>last 6man meeting.<br><br>The resulting document is available at:<br><</span><a href="https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>The diff between the RFC4941 and our rfc4941bis is available at:<br><</span><a href="https://tools.ietf.org/rfcdiff?url1=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt&url2=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org//rfcdiff?url1=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt&url2=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br><br>Note: we have also added the verified errata for RFC4941 (which we had<br>not yet incorporated in the version presented at the last 6man meeting).<br><br>Your comments will be very appreciated!<br><br>Thanks!<br><br>Best regards,<br>-- <br>Fernando Gont<br>SI6 Networks<br>e-mail: fgont@si6networks.com<br>PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br><br><br><br><br>--------------------------------------------------------------------<br>IETF IPv6 working group mailing list<br>ipv6@ietf.org<br>Administrative Requests: </span><a href="https://www.ietf.org/mailman/listinfo/ipv6"><span style='mso-bookmark:_MailOriginalBody'>https://www.ietf.org/mailman/listinfo/ipv6</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>--------------------------------------------------------------------<br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 26 Mar 2018 16:15:38 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: "lactf@lacnic.net" <lactf@lacnic.net>, Lista para discusi?n de<br> seguridad en redes y sistemas informaticos de la regi?n<br> <seguridad@lacnic.net><br>Subject: [LAC-TF] Fwd: Requirements for IPv6 Temporary Addresses<br>Message-ID: <2dfac8a3-876a-3f9e-8ac8-727355baba76@si6networks.com><br>Content-Type: text/plain; charset=utf-8<br><br>FYI<br><br><br>-------- Forwarded Message --------<br>Subject: Requirements for IPv6 Temporary Addresses<br>Date: Mon, 26 Mar 2018 15:03:23 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com><br><br>Folks,<br><br>FYI, we have published the IETF Internet-Draft "Recommendation on<br>Temporary IPv6 Interface Identifiers"<br>(<</span><a href="https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>>),<br>which specifies requirements for temporary addresses (a la RFC8064).<br><br>So we have:<br><br>* RFC8064: Requirements for stable addresses<br>* RFC7217: A recommended algorithm for stable addresses that complies<br>with RFC8064<br>* draft-gont-6man-non-stable-iids: Requirements for temporary addresses<br>* /draft-fgont-6man-rfc4941bis: Some recommended algorithms for<br>temporary addresses that comply with draft-gont-6man-non-stable-iids<br><br>Comments welcome... even more if sent to (or CC'ed to ipv6@ietf.org)<br><br>Thanks!<br><br>Best regards,<br>-- <br>Fernando Gont<br>SI6 Networks<br>e-mail: fgont@si6networks.com<br>PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br><br><br><br><br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>LACTF mailing list<br>LACTF@lacnic.net<br></span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>Cancelar suscripcion: lactf-unsubscribe@lacnic.net<br><br><br>------------------------------<br><br>End of LACTF Digest, Vol 168, Issue 17<br>**************************************<br><br>_______________________________________________ LACTF mailing list LACTF@lacnic.net </span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'> Cancelar suscripcion: lactf-unsubscribe@lacnic.net <br><br><br><br>**********************************************<br>IPv4 is over<br>Are you ready for the new Internet ?<br></span><a href="http://www.consulintel.es"><span style='mso-bookmark:_MailOriginalBody'>http://www.consulintel.es</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</span><a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/c2dfe476/attachment-0001.html"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/pipermail/lactf/attachments/20180405/c2dfe476/attachment-0001.html</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>------------------------------<br><br>Message: 2<br>Date: Thu, 05 Apr 2018 16:33:09 +0200<br>From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es><br>To: <lactf@lac.ipv6tf.org><br>Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 2<br>Message-ID: <CEAAA94B-C5D8-4377-8D03-AF9EFA0C54D0@consulintel.es><br>Content-Type: text/plain; charset="utf-8"<br><br>Lo correcto es que cada end-site tenga su propio /48 y no hay mas discusi?n posible.<br><br> <br><br>Entiendo que adem?s es un cliente corporativo, as? que con mayor motivo!<br><br> <br><br><br>Saludos,<br><br>Jordi<br><br> <br><br>De: LACTF <lactf-bounces@lacnic.net> en nombre de Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>Responder a: <lactf@lac.ipv6tf.org><br>Fecha: jueves, 5 de abril de 2018, 16:30<br>Para: "lactf@lacnic.net" <lactf@lacnic.net><br>Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 2<br><br> <br><br>Adicional si el cliente tiene dos sedes conectadas a diferente proveedor y solo tiene asignado una red /48, pero el quiere en cada sede recibir solo la default y anunciar un segmento /52. Cual ser?a la mejor opci?n de configuraci?n que se le da al cliente final. <br><br>Amancio Mora<br><br> <br><br>From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>Sent: Thursday, April 5, 2018 9:18:19 AM<br>To: lactf@lacnic.net<br>Subject: LACTF Digest, Vol 169, Issue 2 <br><br> <br><br>Send LACTF mailing list submissions to<br> lactf@lacnic.net<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> </span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>or, via email, send a message with subject or body 'help' to<br> lactf-request@lacnic.net<br><br>You can reach the person managing the list at<br> lactf-owner@lacnic.net<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of LACTF digest..."<br><br><br>Today's Topics:<br><br> 1. Re: LACTF Digest, Vol 168, Issue 17 (Alex Ojeda)<br> 2. Re: LACTF Digest, Vol 168, Issue 17 (Alex Ojeda)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 5 Apr 2018 14:18:08 +0000<br>From: Alex Ojeda <alex@chilenetworks.com><br>To: "lactf@lac.ipv6tf.org" <lactf@lac.ipv6tf.org>, "lactf@lacnic.net"<br> <lactf@lacnic.net><br>Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>Message-ID:<br> <BY2PR0401MB167295CDFBD703887BD34459C3BB0@BY2PR0401MB1672.namprd04.prod.outlook.com><br> <br>Content-Type: text/plain; charset="iso-8859-1"<br><br>/48<br><br><br>________________________________<br>From: LACTF <lactf-bounces@lacnic.net> on behalf of Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>Sent: Thursday, April 5, 2018 11:15:58 AM<br>To: lactf@lacnic.net; lactf@lacnic.net<br>Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br><br>Buenos d?as,<br><br>Ingenieros cual es la m?scara m?s peque?a en Ipv6 que podemos anunciar a Internet.<br><br>Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.<br><br>Cualquier inquietud con gusto.<br><br>Cordialmente ?,<br><br><br><br>Amancio Mora<br><br>________________________________<br>From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>Sent: Tuesday, March 27, 2018 10:00:01 AM<br>To: lactf@lacnic.net<br>Subject: LACTF Digest, Vol 168, Issue 17<br><br>Send LACTF mailing list submissions to<br> lactf@lacnic.net<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> </span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>or, via email, send a message with subject or body 'help' to<br> lactf-request@lacnic.net<br><br>You can reach the person managing the list at<br> lactf-owner@lacnic.net<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of LACTF digest..."<br><br><br>Today's Topics:<br><br> 1. Fwd: Fwd: RFC4941bis (Fernando Gont)<br> 2. Fwd: Requirements for IPv6 Temporary Addresses (Fernando Gont)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 26 Mar 2018 16:15:20 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: "lactf@lacnic.net" <lactf@lacnic.net>, Lista para discusi?n de<br> seguridad en redes y sistemas informaticos de la regi?n<br> <seguridad@lacnic.net><br>Subject: [LAC-TF] Fwd: Fwd: RFC4941bis<br>Message-ID: <9d1dfd63-db99-75ad-a58c-e82e049fd3e3@si6networks.com><br>Content-Type: text/plain; charset=windows-1252<br><br>FYI<br><br><br>-------- Forwarded Message --------<br>Subject: Fwd: RFC4941bis<br>Date: Mon, 26 Mar 2018 14:48:34 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com><br><br>Folks,<br><br>As the subject implies, this is an effort to revise RFC4941 to fix the<br>issues in it.<br><br>Comments welcome... even more if sent to (or CC'ed to ipv6@ietf.org)<br><br>Thanks!<br><br>Best regards,<br>Fernando<br><br><br><br><br>-------- Forwarded Message --------<br>Subject: RFC4941bis<br>Date: Mon, 26 Mar 2018 04:55:06 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>Organization: SI6 Networks<br>To: 6man@ietf.org <6man@ietf.org><br>CC: 6man-chairs@tools.ietf.org <6man-chairs@tools.ietf.org><br><br>Folks,<br><br>Based on the comments on the last 6man meeting, we have done the following:<br><br>1) We have asked the RFC Editor the xml source for RFC4941, applied the<br>minimum changes to publish it as an I-D, and posted it as:<br><</span><a href="https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>2) We subsequently applied all the corresponding changes to arrive to<br>something similar to what we had in draft-gont-6man-rfc4941bis-00<br>(please note the slight difference in the filename), presented at the<br>last 6man meeting.<br><br>The resulting document is available at:<br><</span><a href="https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>The diff between the RFC4941 and our rfc4941bis is available at:<br><</span><a href="https://tools.ietf.org/rfcdiff?url1=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt&url2=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org//rfcdiff?url1=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt&url2=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br><br>Note: we have also added the verified errata for RFC4941 (which we had<br>not yet incorporated in the version presented at the last 6man meeting).<br><br>Your comments will be very appreciated!<br><br>Thanks!<br><br>Best regards,<br>--<br>Fernando Gont<br>SI6 Networks<br>e-mail: fgont@si6networks.com<br>PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br><br><br><br><br>--------------------------------------------------------------------<br>IETF IPv6 working group mailing list<br>ipv6@ietf.org<br>Administrative Requests: </span><a href="https://www.ietf.org/mailman/listinfo/ipv6"><span style='mso-bookmark:_MailOriginalBody'>https://www.ietf.org/mailman/listinfo/ipv6</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>--------------------------------------------------------------------<br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 26 Mar 2018 16:15:38 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: "lactf@lacnic.net" <lactf@lacnic.net>, Lista para discusi?n de<br> seguridad en redes y sistemas informaticos de la regi?n<br> <seguridad@lacnic.net><br>Subject: [LAC-TF] Fwd: Requirements for IPv6 Temporary Addresses<br>Message-ID: <2dfac8a3-876a-3f9e-8ac8-727355baba76@si6networks.com><br>Content-Type: text/plain; charset=utf-8<br><br>FYI<br><br><br>-------- Forwarded Message --------<br>Subject: Requirements for IPv6 Temporary Addresses<br>Date: Mon, 26 Mar 2018 15:03:23 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com><br><br>Folks,<br><br>FYI, we have published the IETF Internet-Draft "Recommendation on<br>Temporary IPv6 Interface Identifiers"<br>(<</span><a href="https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>>),<br>which specifies requirements for temporary addresses (a la RFC8064).<br><br>So we have:<br><br>* RFC8064: Requirements for stable addresses<br>* RFC7217: A recommended algorithm for stable addresses that complies<br>with RFC8064<br>* draft-gont-6man-non-stable-iids: Requirements for temporary addresses<br>* /draft-fgont-6man-rfc4941bis: Some recommended algorithms for<br>temporary addresses that comply with draft-gont-6man-non-stable-iids<br><br>Comments welcome... even more if sent to (or CC'ed to ipv6@ietf.org)<br><br>Thanks!<br><br>Best regards,<br>--<br>Fernando Gont<br>SI6 Networks<br>e-mail: fgont@si6networks.com<br>PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br><br><br><br><br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>LACTF mailing list<br>LACTF@lacnic.net<br></span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>Cancelar suscripcion: lactf-unsubscribe@lacnic.net<br><br><br>------------------------------<br><br>End of LACTF Digest, Vol 168, Issue 17<br>**************************************<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</span><a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/attachment-0001.html"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/attachment-0001.html</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>------------------------------<br><br>Message: 2<br>Date: Thu, 5 Apr 2018 14:18:08 +0000<br>From: Alex Ojeda <alex@chilenetworks.com><br>To: "lactf@lac.ipv6tf.org" <lactf@lac.ipv6tf.org>, "lactf@lacnic.net"<br> <lactf@lacnic.net><br>Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>Message-ID:<br> <BY2PR0401MB167295CDFBD703887BD34459C3BB0@BY2PR0401MB1672.namprd04.prod.outlook.com><br> <br>Content-Type: text/plain; charset="iso-8859-1"<br><br>/48<br><br><br>________________________________<br>From: LACTF <lactf-bounces@lacnic.net> on behalf of Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>Sent: Thursday, April 5, 2018 11:15:58 AM<br>To: lactf@lacnic.net; lactf@lacnic.net<br>Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br><br>Buenos d?as,<br><br>Ingenieros cual es la m?scara m?s peque?a en Ipv6 que podemos anunciar a Internet.<br><br>Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.<br><br>Cualquier inquietud con gusto.<br><br>Cordialmente ?,<br><br><br><br>Amancio Mora<br><br>________________________________<br>From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>Sent: Tuesday, March 27, 2018 10:00:01 AM<br>To: lactf@lacnic.net<br>Subject: LACTF Digest, Vol 168, Issue 17<br><br>Send LACTF mailing list submissions to<br> lactf@lacnic.net<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> </span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>or, via email, send a message with subject or body 'help' to<br> lactf-request@lacnic.net<br><br>You can reach the person managing the list at<br> lactf-owner@lacnic.net<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of LACTF digest..."<br><br><br>Today's Topics:<br><br> 1. Fwd: Fwd: RFC4941bis (Fernando Gont)<br> 2. Fwd: Requirements for IPv6 Temporary Addresses (Fernando Gont)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 26 Mar 2018 16:15:20 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: "lactf@lacnic.net" <lactf@lacnic.net>, Lista para discusi?n de<br> seguridad en redes y sistemas informaticos de la regi?n<br> <seguridad@lacnic.net><br>Subject: [LAC-TF] Fwd: Fwd: RFC4941bis<br>Message-ID: <9d1dfd63-db99-75ad-a58c-e82e049fd3e3@si6networks.com><br>Content-Type: text/plain; charset=windows-1252<br><br>FYI<br><br><br>-------- Forwarded Message --------<br>Subject: Fwd: RFC4941bis<br>Date: Mon, 26 Mar 2018 14:48:34 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com><br><br>Folks,<br><br>As the subject implies, this is an effort to revise RFC4941 to fix the<br>issues in it.<br><br>Comments welcome... even more if sent to (or CC'ed to ipv6@ietf.org)<br><br>Thanks!<br><br>Best regards,<br>Fernando<br><br><br><br><br>-------- Forwarded Message --------<br>Subject: RFC4941bis<br>Date: Mon, 26 Mar 2018 04:55:06 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>Organization: SI6 Networks<br>To: 6man@ietf.org <6man@ietf.org><br>CC: 6man-chairs@tools.ietf.org <6man-chairs@tools.ietf.org><br><br>Folks,<br><br>Based on the comments on the last 6man meeting, we have done the following:<br><br>1) We have asked the RFC Editor the xml source for RFC4941, applied the<br>minimum changes to publish it as an I-D, and posted it as:<br><</span><a href="https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>2) We subsequently applied all the corresponding changes to arrive to<br>something similar to what we had in draft-gont-6man-rfc4941bis-00<br>(please note the slight difference in the filename), presented at the<br>last 6man meeting.<br><br>The resulting document is available at:<br><</span><a href="https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>The diff between the RFC4941 and our rfc4941bis is available at:<br><</span><a href="https://tools.ietf.org/rfcdiff?url1=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt&url2=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org//rfcdiff?url1=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt&url2=https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br><br>Note: we have also added the verified errata for RFC4941 (which we had<br>not yet incorporated in the version presented at the last 6man meeting).<br><br>Your comments will be very appreciated!<br><br>Thanks!<br><br>Best regards,<br>--<br>Fernando Gont<br>SI6 Networks<br>e-mail: fgont@si6networks.com<br>PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br><br><br><br><br>--------------------------------------------------------------------<br>IETF IPv6 working group mailing list<br>ipv6@ietf.org<br>Administrative Requests: </span><a href="https://www.ietf.org/mailman/listinfo/ipv6"><span style='mso-bookmark:_MailOriginalBody'>https://www.ietf.org/mailman/listinfo/ipv6</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>--------------------------------------------------------------------<br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 26 Mar 2018 16:15:38 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: "lactf@lacnic.net" <lactf@lacnic.net>, Lista para discusi?n de<br> seguridad en redes y sistemas informaticos de la regi?n<br> <seguridad@lacnic.net><br>Subject: [LAC-TF] Fwd: Requirements for IPv6 Temporary Addresses<br>Message-ID: <2dfac8a3-876a-3f9e-8ac8-727355baba76@si6networks.com><br>Content-Type: text/plain; charset=utf-8<br><br>FYI<br><br><br>-------- Forwarded Message --------<br>Subject: Requirements for IPv6 Temporary Addresses<br>Date: Mon, 26 Mar 2018 15:03:23 +0100<br>From: Fernando Gont <fgont@si6networks.com><br>To: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com><br><br>Folks,<br><br>FYI, we have published the IETF Internet-Draft "Recommendation on<br>Temporary IPv6 Interface Identifiers"<br>(<</span><a href="https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04"><span style='mso-bookmark:_MailOriginalBody'>https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>>),<br>which specifies requirements for temporary addresses (a la RFC8064).<br><br>So we have:<br><br>* RFC8064: Requirements for stable addresses<br>* RFC7217: A recommended algorithm for stable addresses that complies<br>with RFC8064<br>* draft-gont-6man-non-stable-iids: Requirements for temporary addresses<br>* /draft-fgont-6man-rfc4941bis: Some recommended algorithms for<br>temporary addresses that comply with draft-gont-6man-non-stable-iids<br><br>Comments welcome... even more if sent to (or CC'ed to ipv6@ietf.org)<br><br>Thanks!<br><br>Best regards,<br>--<br>Fernando Gont<br>SI6 Networks<br>e-mail: fgont@si6networks.com<br>PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br><br><br><br><br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>LACTF mailing list<br>LACTF@lacnic.net<br></span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>Cancelar suscripcion: lactf-unsubscribe@lacnic.net<br><br><br>------------------------------<br><br>End of LACTF Digest, Vol 168, Issue 17<br>**************************************<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</span><a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/attachment-0002.html"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/attachment-0002.html</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>LACTF mailing list<br>LACTF@lacnic.net<br></span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>Cancelar suscripcion: lactf-unsubscribe@lacnic.net<br><br><br>------------------------------<br><br>End of LACTF Digest, Vol 169, Issue 2<br>*************************************<br><br>_______________________________________________ LACTF mailing list LACTF@lacnic.net </span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'> Cancelar suscripcion: lactf-unsubscribe@lacnic.net <br><br><br><br>**********************************************<br>IPv4 is over<br>Are you ready for the new Internet ?<br></span><a href="http://www.consulintel.es"><span style='mso-bookmark:_MailOriginalBody'>http://www.consulintel.es</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</span><a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/66c6e448/attachment.html"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/pipermail/lactf/attachments/20180405/66c6e448/attachment.html</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'>><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>LACTF mailing list<br>LACTF@lacnic.net<br></span><a href="https://mail.lacnic.net/mailman/listinfo/lactf"><span style='mso-bookmark:_MailOriginalBody'>https://mail.lacnic.net/mailman/listinfo/lactf</span><span style='mso-bookmark:_MailOriginalBody'></span></a><span style='mso-bookmark:_MailOriginalBody'><br>Cancelar suscripcion: lactf-unsubscribe@lacnic.net<br><br><br>------------------------------<br><br>End of LACTF Digest, Vol 169, Issue 4<br>*************************************<o:p></o:p></span></p></div><p class=MsoNormal style='margin-left:35.4pt'><span style='mso-bookmark:_MailOriginalBody'>_______________________________________________ LACTF mailing list LACTF@lacnic.net https://mail.lacnic.net/mailman/listinfo/lactf Cancelar suscripcion: lactf-unsubscribe@lacnic.net </span><o:p></o:p></p></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.consulintel.es<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>