<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hola Amancio,</p>
<p>Agregando algo a la sugerencia de Jordi, te comento que de
acuerdo a las políticas actuales de LACNIC, si comenzarás el
despliegue IPv6 y ves que el bloque inicialmente asignado por
LACNIC no es suficiente (el /48) para tu proyecto, puedes
solicitar por única vez una ampliación de este rango sin que ésto
genere un costo adicional. Puedes consultar esta política
accediendo al siguiente link, punto 4.5.4.3
<a class="moz-txt-link-freetext" href="http://www.lacnic.net/547/1/lacnic/">http://www.lacnic.net/547/1/lacnic/</a><br>
</p>
<p>Previendo que este escenario ocurra, LACNIC reserva espacio
contiguo al recibido inicialmente, así que podrás recibir el /48
contiguo para la otra sede. Inclusive, puedes prever una
proyección de crecimiento y solicitar mas de 1 /48 adicional ;). <br>
</p>
<p>Para solicitar la ampliación, es necesario que su cliente
contacte a <a class="moz-txt-link-abbreviated" href="mailto:hostmaster@lacnic.net">hostmaster@lacnic.net</a>. Puede mantenerle copiado en el
correo para darle seguimiento al caso.</p>
<p>Espero que la información otorgada le haya sido de utilidad.</p>
<p>Saludos!</p>
<p>Sergio. . .<br>
</p>
<p><br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">El 5/4/18 a las 12:27, JORDI PALET
MARTINEZ escribió:<br>
</div>
<blockquote type="cite"
cite="mid:4EE7C903-737B-4BAC-98AE-E40FC3F7E8A6@consulintel.es">
<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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="ES-TRAD">Así es, seguramente LACNIC le podrá asignar
un /48 contiguo.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="ES-TRAD"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="ES-TRAD">De este modo, si un día el operador es el
mismo, podría sumarizar el anuncio de ambas sedes en un
único /47.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="ES-TRAD"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="ES-TRAD">Si tuviera mas sedes en el futuro,
sucesivos /48 contiguos, y así puede sumarizar a un /46,
/45, /44, etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.5pt;color:black" lang="ES-TRAD"><br>
Saludos,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:10.5pt;color:black;mso-fareast-language:EN-US"
lang="ES-TRAD">Jordi<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="ES-TRAD"><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
<a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> en nombre de Amancio Mora
Rodriguez <a class="moz-txt-link-rfc2396E" href="mailto:mora_amancio@hotmail.com"><mora_amancio@hotmail.com></a><br>
<b>Responder a: </b><a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
<b>Fecha: </b>jueves, 5 de abril de 2018, 17:24<br>
<b>Para: </b><a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a><br>
<b>Asunto: </b>Re: [LAC-TF] LACTF Digest, Vol 169, Issue
16<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" moz-do-not-send="true"><span
style="font-family:"Arial",sans-serif;color:black">Ok,
la opción es que el cliente debería solicitar a la
Lacnic otra red /48 para la otra sede. <br>
<br>
<br>
<o:p></o:p></span></a></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"
style="margin-left:35.4pt;text-align:center" align="center"><span
style="mso-bookmark:_MailOriginalBody">
<hr size="0" align="center" width="96%"></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
<a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a>
<a class="moz-txt-link-rfc2396E" href="mailto:lactf-request@lacnic.net"><lactf-request@lacnic.net></a><br>
<b>Sent:</b> Thursday, April 5, 2018 10:20:48 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
<b>Subject:</b> LACTF Digest, Vol 169, Issue 16</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>
<a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-owner@lacnic.net">lactf-owner@lacnic.net</a><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 169, Issue 13 (JORDI PALET
MARTINEZ)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 05 Apr 2018 17:20:36 +0200<br>
From: JORDI PALET MARTINEZ
<a class="moz-txt-link-rfc2396E" href="mailto:jordi.palet@consulintel.es"><jordi.palet@consulintel.es></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 13<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:A7B93B67-216B-4102-9730-B8966FB1F421@consulintel.es"><A7B93B67-216B-4102-9730-B8966FB1F421@consulintel.es></a><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
No, eso es incorrecto.<br>
<br>
<br>
<br>
El cliente tiene un /48 para cada sede, pero deber?
utilizar /64 dentro de ese /48 para cada LAN, VLAN, etc.<br>
<br>
<br>
<br>
Es decir, tiene hasta 65.535 posibles LANs con un /48.<br>
<br>
<br>
<br>
Saludos,<br>
<br>
Jordi<br>
<br>
<br>
<br>
De: LACTF <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> en nombre de
Amancio Mora Rodriguez <a class="moz-txt-link-rfc2396E" href="mailto:mora_amancio@hotmail.com"><mora_amancio@hotmail.com></a><br>
Responder a: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Fecha: jueves, 5 de abril de 2018, 17:14<br>
Para: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a>,
<a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a><br>
Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 13<br>
<br>
<br>
<br>
Es proponerle lo correcto, dejando claro las opciones que
pueden existir. <br>
<br>
Me queda claro que a Internet solo debemos anunciar una
red /48, pero a nivel lan el cliente solo esta utilizando
una red /52 por sede. <br>
<br>
Amancio Mora<br>
<br>
<br>
<br>
From: LACTF <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf-request@lacnic.net"><lactf-request@lacnic.net></a><br>
Sent: Thursday, April 5, 2018 10:10:22 AM<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
Subject: LACTF Digest, Vol 169, Issue 13 <br>
<br>
<br>
<br>
Send LACTF mailing list submissions to<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-owner@lacnic.net">lactf-owner@lacnic.net</a><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 169, Issue 6 (JORDI PALET
MARTINEZ)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 05 Apr 2018 17:10:11 +0200<br>
From: JORDI PALET MARTINEZ
<a class="moz-txt-link-rfc2396E" href="mailto:jordi.palet@consulintel.es"><jordi.palet@consulintel.es></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 6<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:FCD28B92-B0BD-43B2-9CA5-27A5EE3750D4@consulintel.es"><FCD28B92-B0BD-43B2-9CA5-27A5EE3750D4@consulintel.es></a><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Aunque un /48 fuera suficiente para ?repartir entre ambas?
sedes, es incorrecto.<br>
<br>
<br>
<br>
Insisto, queremos recomendar lo correcto o cualquier cosa?<br>
<br>
<br>
Saludos,<br>
<br>
Jordi<br>
<br>
<br>
<br>
De: LACTF <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> en nombre de
"Jaris Aizpr?a B." <a class="moz-txt-link-rfc2396E" href="mailto:jarisaizprua@gmail.com"><jarisaizprua@gmail.com></a><br>
Responder a: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Fecha: jueves, 5 de abril de 2018, 17:07<br>
Para: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
CC: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a><br>
Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 6<br>
<br>
<br>
<br>
Pues depende si las sedes se conectan al mismo proveedor o
no; si no se conectan al mismo operador, pues necesitan un
direccionamiento Global Unicast por cada sede para que su
prefijo /48 sea visible en Internet, caso contrario un /48
es suficiente dentro del mismo ISP.<br>
<br>
<br>
<br>
2018-04-05 10:02 GMT-05:00 Amancio Mora Rodriguez
<a class="moz-txt-link-rfc2396E" href="mailto:mora_amancio@hotmail.com"><mora_amancio@hotmail.com></a>:<br>
<br>
Es claro pero las dos sedes est?n en diferentes sitios y
no se conectan entre ellas, y adicional, el tendr?a que
anunciar la red /48 en ambas sedes, pero si el quiere
llegar de una sede a otra no podr?a. <br>
<br>
Se le tendr?a que decir que tiene que interconectar
obligatoria mente las dos sedes por un ibgp, o debe
solicitar otra red /48 para la otra sede, o que le
solicite el direccionamiento Ipv6 a uno de sus proveedores
de internet. Ya que ni podr?a utilizar la misma red /48 en
sus dos sedes que est?n en diferentes sitios. <br>
<br>
Amancio Mora<br>
<br>
<br>
<br>
From: LACTF <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf-request@lacnic.net"><lactf-request@lacnic.net></a><br>
Sent: Thursday, April 5, 2018 9:52:49 AM<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
Subject: LACTF Digest, Vol 169, Issue 6 <br>
<br>
<br>
<br>
Send LACTF mailing list submissions to<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-owner@lacnic.net">lactf-owner@lacnic.net</a><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 169, Issue 4 (JORDI PALET
MARTINEZ)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 05 Apr 2018 16:52:08 +0200<br>
From: JORDI PALET MARTINEZ
<a class="moz-txt-link-rfc2396E" href="mailto:jordi.palet@consulintel.es"><jordi.palet@consulintel.es></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 4<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:F3A7EC2A-565E-42C7-95FF-854E6058C84A@consulintel.es"><F3A7EC2A-565E-42C7-95FF-854E6058C84A@consulintel.es></a><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
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 ?<br>
<br>
<br>
Saludos,<br>
<br>
Jordi<br>
<br>
<br>
<br>
De: LACTF <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> en nombre de
Amancio Mora Rodriguez <a class="moz-txt-link-rfc2396E" href="mailto:mora_amancio@hotmail.com"><mora_amancio@hotmail.com></a><br>
Responder a: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Fecha: jueves, 5 de abril de 2018, 16:47<br>
Para: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a><br>
Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 4<br>
<br>
<br>
<br>
Realmente, el cliente tiene su propio direccionamiento
Ipv60/48, pero el solo quiere utilizar una red /52 por
sede. <br>
<br>
Qu? se le tendr?a que decir al cliente final? Que
configuraci?n se le debe recomendar? <br>
<br>
Amancio Mora<br>
<br>
<br>
<br>
From: LACTF <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf-request@lacnic.net"><lactf-request@lacnic.net></a><br>
Sent: Thursday, April 5, 2018 9:33:19 AM<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
Subject: LACTF Digest, Vol 169, Issue 4 <br>
<br>
<br>
<br>
Send LACTF mailing list submissions to<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-owner@lacnic.net">lactf-owner@lacnic.net</a><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
<a class="moz-txt-link-rfc2396E" href="mailto:jordi.palet@consulintel.es"><jordi.palet@consulintel.es></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:1814AB46-668D-4B34-A7AD-921BD2C11946@consulintel.es"><1814AB46-668D-4B34-A7AD-921BD2C11946@consulintel.es></a><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/"
moz-do-not-send="true"><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"
moz-do-not-send="true"><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 <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> en nombre de
Amancio Mora Rodriguez <a class="moz-txt-link-rfc2396E" href="mailto:mora_amancio@hotmail.com"><mora_amancio@hotmail.com></a><br>
Responder a: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Fecha: jueves, 5 de abril de 2018, 16:16<br>
Para: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a>,
<a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a><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 <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf-request@lacnic.net"><lactf-request@lacnic.net></a><br>
Sent: Tuesday, March 27, 2018 10:00:01 AM<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
Subject: LACTF Digest, Vol 168, Issue 17 <br>
<br>
<br>
<br>
Send LACTF mailing list submissions to<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-owner@lacnic.net">lactf-owner@lacnic.net</a><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a>, Lista
para discusi?n de<br>
seguridad en redes y sistemas informaticos de la
regi?n<br>
<a class="moz-txt-link-rfc2396E" href="mailto:seguridad@lacnic.net"><seguridad@lacnic.net></a><br>
Subject: [LAC-TF] Fwd: Fwd: RFC4941bis<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:9d1dfd63-db99-75ad-a58c-e82e049fd3e3@si6networks.com"><9d1dfd63-db99-75ad-a58c-e82e049fd3e3@si6networks.com></a><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: IPv6 Hackers Mailing List
<a class="moz-txt-link-rfc2396E" href="mailto:ipv6hackers@lists.si6networks.com"><ipv6hackers@lists.si6networks.com></a><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
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>)<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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
Organization: SI6 Networks<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:6man@ietf.org">6man@ietf.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:6man@ietf.org"><6man@ietf.org></a><br>
CC: <a class="moz-txt-link-abbreviated" href="mailto:6man-chairs@tools.ietf.org">6man-chairs@tools.ietf.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:6man-chairs@tools.ietf.org"><6man-chairs@tools.ietf.org></a><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"
moz-do-not-send="true"><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"
moz-do-not-send="true"><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"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:fgont@si6networks.com">fgont@si6networks.com</a><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>
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: </span><a
href="https://www.ietf.org/mailman/listinfo/ipv6"
moz-do-not-send="true"><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a>, Lista
para discusi?n de<br>
seguridad en redes y sistemas informaticos de la
regi?n<br>
<a class="moz-txt-link-rfc2396E" href="mailto:seguridad@lacnic.net"><seguridad@lacnic.net></a><br>
Subject: [LAC-TF] Fwd: Requirements for IPv6 Temporary
Addresses<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:2dfac8a3-876a-3f9e-8ac8-727355baba76@si6networks.com"><2dfac8a3-876a-3f9e-8ac8-727355baba76@si6networks.com></a><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: IPv6 Hackers Mailing List
<a class="moz-txt-link-rfc2396E" href="mailto:ipv6hackers@lists.si6networks.com"><ipv6hackers@lists.si6networks.com></a><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"
moz-do-not-send="true"><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
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>)<br>
<br>
Thanks!<br>
<br>
Best regards,<br>
-- <br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a class="moz-txt-link-abbreviated" href="mailto:fgont@si6networks.com">fgont@si6networks.com</a><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>
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a><br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a><br>
<br>
<br>
------------------------------<br>
<br>
End of LACTF Digest, Vol 168, Issue 17<br>
**************************************<br>
<br>
_______________________________________________ LACTF
mailing list <a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a> </span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a> <br>
<br>
<br>
<br>
**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
</span><a href="http://www.consulintel.es"
moz-do-not-send="true"><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"
moz-do-not-send="true"><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
<a class="moz-txt-link-rfc2396E" href="mailto:jordi.palet@consulintel.es"><jordi.palet@consulintel.es></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 2<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:CEAAA94B-C5D8-4377-8D03-AF9EFA0C54D0@consulintel.es"><CEAAA94B-C5D8-4377-8D03-AF9EFA0C54D0@consulintel.es></a><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 <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> en nombre de
Amancio Mora Rodriguez <a class="moz-txt-link-rfc2396E" href="mailto:mora_amancio@hotmail.com"><mora_amancio@hotmail.com></a><br>
Responder a: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a><br>
Fecha: jueves, 5 de abril de 2018, 16:30<br>
Para: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a><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 <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf-request@lacnic.net"><lactf-request@lacnic.net></a><br>
Sent: Thursday, April 5, 2018 9:18:19 AM<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
Subject: LACTF Digest, Vol 169, Issue 2 <br>
<br>
<br>
<br>
Send LACTF mailing list submissions to<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-owner@lacnic.net">lactf-owner@lacnic.net</a><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 <a class="moz-txt-link-rfc2396E" href="mailto:alex@chilenetworks.com"><alex@chilenetworks.com></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org">"lactf@lac.ipv6tf.org"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a>,
<a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a><br>
<a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>
Message-ID:<br>
<a class="moz-txt-link-rfc2396E" href="mailto:BY2PR0401MB167295CDFBD703887BD34459C3BB0@BY2PR0401MB1672.namprd04.prod.outlook.com"><BY2PR0401MB167295CDFBD703887BD34459C3BB0@BY2PR0401MB1672.namprd04.prod.outlook.com></a><br>
<br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
/48<br>
<br>
<br>
________________________________<br>
From: LACTF <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
Amancio Mora Rodriguez <a class="moz-txt-link-rfc2396E" href="mailto:mora_amancio@hotmail.com"><mora_amancio@hotmail.com></a><br>
Sent: Thursday, April 5, 2018 11:15:58 AM<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a>; <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><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 <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf-request@lacnic.net"><lactf-request@lacnic.net></a><br>
Sent: Tuesday, March 27, 2018 10:00:01 AM<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
Subject: LACTF Digest, Vol 168, Issue 17<br>
<br>
Send LACTF mailing list submissions to<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-owner@lacnic.net">lactf-owner@lacnic.net</a><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a>, Lista
para discusi?n de<br>
seguridad en redes y sistemas informaticos de la
regi?n<br>
<a class="moz-txt-link-rfc2396E" href="mailto:seguridad@lacnic.net"><seguridad@lacnic.net></a><br>
Subject: [LAC-TF] Fwd: Fwd: RFC4941bis<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:9d1dfd63-db99-75ad-a58c-e82e049fd3e3@si6networks.com"><9d1dfd63-db99-75ad-a58c-e82e049fd3e3@si6networks.com></a><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: IPv6 Hackers Mailing List
<a class="moz-txt-link-rfc2396E" href="mailto:ipv6hackers@lists.si6networks.com"><ipv6hackers@lists.si6networks.com></a><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
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>)<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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
Organization: SI6 Networks<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:6man@ietf.org">6man@ietf.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:6man@ietf.org"><6man@ietf.org></a><br>
CC: <a class="moz-txt-link-abbreviated" href="mailto:6man-chairs@tools.ietf.org">6man-chairs@tools.ietf.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:6man-chairs@tools.ietf.org"><6man-chairs@tools.ietf.org></a><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"
moz-do-not-send="true"><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"
moz-do-not-send="true"><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"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:fgont@si6networks.com">fgont@si6networks.com</a><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>
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: </span><a
href="https://www.ietf.org/mailman/listinfo/ipv6"
moz-do-not-send="true"><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a>, Lista
para discusi?n de<br>
seguridad en redes y sistemas informaticos de la
regi?n<br>
<a class="moz-txt-link-rfc2396E" href="mailto:seguridad@lacnic.net"><seguridad@lacnic.net></a><br>
Subject: [LAC-TF] Fwd: Requirements for IPv6 Temporary
Addresses<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:2dfac8a3-876a-3f9e-8ac8-727355baba76@si6networks.com"><2dfac8a3-876a-3f9e-8ac8-727355baba76@si6networks.com></a><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: IPv6 Hackers Mailing List
<a class="moz-txt-link-rfc2396E" href="mailto:ipv6hackers@lists.si6networks.com"><ipv6hackers@lists.si6networks.com></a><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"
moz-do-not-send="true"><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
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>)<br>
<br>
Thanks!<br>
<br>
Best regards,<br>
--<br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a class="moz-txt-link-abbreviated" href="mailto:fgont@si6networks.com">fgont@si6networks.com</a><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>
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a><br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a><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"
moz-do-not-send="true"><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 <a class="moz-txt-link-rfc2396E" href="mailto:alex@chilenetworks.com"><alex@chilenetworks.com></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org">"lactf@lac.ipv6tf.org"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lac.ipv6tf.org"><lactf@lac.ipv6tf.org></a>,
<a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a><br>
<a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>
Message-ID:<br>
<a class="moz-txt-link-rfc2396E" href="mailto:BY2PR0401MB167295CDFBD703887BD34459C3BB0@BY2PR0401MB1672.namprd04.prod.outlook.com"><BY2PR0401MB167295CDFBD703887BD34459C3BB0@BY2PR0401MB1672.namprd04.prod.outlook.com></a><br>
<br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
/48<br>
<br>
<br>
________________________________<br>
From: LACTF <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
Amancio Mora Rodriguez <a class="moz-txt-link-rfc2396E" href="mailto:mora_amancio@hotmail.com"><mora_amancio@hotmail.com></a><br>
Sent: Thursday, April 5, 2018 11:15:58 AM<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a>; <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><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 <a class="moz-txt-link-rfc2396E" href="mailto:lactf-bounces@lacnic.net"><lactf-bounces@lacnic.net></a> on behalf of
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf-request@lacnic.net"><lactf-request@lacnic.net></a><br>
Sent: Tuesday, March 27, 2018 10:00:01 AM<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
Subject: LACTF Digest, Vol 168, Issue 17<br>
<br>
Send LACTF mailing list submissions to<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf@lacnic.net">lactf@lacnic.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-request@lacnic.net">lactf-request@lacnic.net</a><br>
<br>
You can reach the person managing the list at<br>
<a class="moz-txt-link-abbreviated" href="mailto:lactf-owner@lacnic.net">lactf-owner@lacnic.net</a><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a>, Lista
para discusi?n de<br>
seguridad en redes y sistemas informaticos de la
regi?n<br>
<a class="moz-txt-link-rfc2396E" href="mailto:seguridad@lacnic.net"><seguridad@lacnic.net></a><br>
Subject: [LAC-TF] Fwd: Fwd: RFC4941bis<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:9d1dfd63-db99-75ad-a58c-e82e049fd3e3@si6networks.com"><9d1dfd63-db99-75ad-a58c-e82e049fd3e3@si6networks.com></a><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: IPv6 Hackers Mailing List
<a class="moz-txt-link-rfc2396E" href="mailto:ipv6hackers@lists.si6networks.com"><ipv6hackers@lists.si6networks.com></a><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
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>)<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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
Organization: SI6 Networks<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:6man@ietf.org">6man@ietf.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:6man@ietf.org"><6man@ietf.org></a><br>
CC: <a class="moz-txt-link-abbreviated" href="mailto:6man-chairs@tools.ietf.org">6man-chairs@tools.ietf.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:6man-chairs@tools.ietf.org"><6man-chairs@tools.ietf.org></a><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"
moz-do-not-send="true"><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"
moz-do-not-send="true"><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"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:fgont@si6networks.com">fgont@si6networks.com</a><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>
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: </span><a
href="https://www.ietf.org/mailman/listinfo/ipv6"
moz-do-not-send="true"><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net">"lactf@lacnic.net"</a> <a class="moz-txt-link-rfc2396E" href="mailto:lactf@lacnic.net"><lactf@lacnic.net></a>, Lista
para discusi?n de<br>
seguridad en redes y sistemas informaticos de la
regi?n<br>
<a class="moz-txt-link-rfc2396E" href="mailto:seguridad@lacnic.net"><seguridad@lacnic.net></a><br>
Subject: [LAC-TF] Fwd: Requirements for IPv6 Temporary
Addresses<br>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:2dfac8a3-876a-3f9e-8ac8-727355baba76@si6networks.com"><2dfac8a3-876a-3f9e-8ac8-727355baba76@si6networks.com></a><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 <a class="moz-txt-link-rfc2396E" href="mailto:fgont@si6networks.com"><fgont@si6networks.com></a><br>
To: IPv6 Hackers Mailing List
<a class="moz-txt-link-rfc2396E" href="mailto:ipv6hackers@lists.si6networks.com"><ipv6hackers@lists.si6networks.com></a><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"
moz-do-not-send="true"><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
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>)<br>
<br>
Thanks!<br>
<br>
Best regards,<br>
--<br>
Fernando Gont<br>
SI6 Networks<br>
e-mail: <a class="moz-txt-link-abbreviated" href="mailto:fgont@si6networks.com">fgont@si6networks.com</a><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>
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a><br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a><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"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a><br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a><br>
<br>
<br>
------------------------------<br>
<br>
End of LACTF Digest, Vol 169, Issue 2<br>
*************************************<br>
<br>
_______________________________________________ LACTF
mailing list <a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a> </span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a> <br>
<br>
<br>
<br>
**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
</span><a href="http://www.consulintel.es"
moz-do-not-send="true"><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"
moz-do-not-send="true"><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>
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a><br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a><br>
<br>
<br>
------------------------------<br>
<br>
End of LACTF Digest, Vol 169, Issue 4<br>
*************************************<br>
<br>
_______________________________________________ LACTF
mailing list <a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a> </span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a> <br>
<br>
<br>
<br>
**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
</span><a href="http://www.consulintel.es"
moz-do-not-send="true"><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/9b5642b7/attachment.html"
moz-do-not-send="true"><span
style="mso-bookmark:_MailOriginalBody">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/9b5642b7/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>
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a><br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a><br>
<br>
<br>
------------------------------<br>
<br>
End of LACTF Digest, Vol 169, Issue 6<br>
*************************************<br>
<br>
<br>
_______________________________________________<br>
LACTF mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a><br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a><br>
<br>
<br>
<br>
_______________________________________________ LACTF
mailing list <a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a> </span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a> <br>
<br>
<br>
<br>
**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
</span><a href="http://www.consulintel.es"
moz-do-not-send="true"><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/251fa76e/attachment.html"
moz-do-not-send="true"><span
style="mso-bookmark:_MailOriginalBody">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/251fa76e/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>
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a><br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a><br>
<br>
<br>
------------------------------<br>
<br>
End of LACTF Digest, Vol 169, Issue 13<br>
**************************************<br>
<br>
_______________________________________________ LACTF
mailing list <a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a> </span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a> <br>
<br>
<br>
<br>
**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
</span><a href="http://www.consulintel.es"
moz-do-not-send="true"><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/3d2a4743/attachment.html"
moz-do-not-send="true"><span
style="mso-bookmark:_MailOriginalBody">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/3d2a4743/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>
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a><br>
</span><a
href="https://mail.lacnic.net/mailman/listinfo/lactf"
moz-do-not-send="true"><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: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a><br>
<br>
<br>
------------------------------<br>
<br>
End of LACTF Digest, Vol 169, Issue 16<br>
**************************************<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:35.4pt"><span
style="mso-bookmark:_MailOriginalBody">_______________________________________________
LACTF mailing list <a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a>
<a class="moz-txt-link-freetext" href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a> Cancelar
suscripcion: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a> </span><o:p></o:p></p>
</div>
<br>
**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a class="moz-txt-link-freetext" href="http://www.consulintel.es">http://www.consulintel.es</a><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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
LACTF mailing list
<a class="moz-txt-link-abbreviated" href="mailto:LACTF@lacnic.net">LACTF@lacnic.net</a>
<a class="moz-txt-link-freetext" href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a>
Cancelar suscripcion: <a class="moz-txt-link-abbreviated" href="mailto:lactf-unsubscribe@lacnic.net">lactf-unsubscribe@lacnic.net</a>
</pre>
</blockquote>
<br>
</body>
</html>