<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<style>
<!--
.EmailQuote
{margin-left:1pt;
padding-left:4pt;
border-left:#800000 2px solid}
-->
</style>
</head>
<body>
<div id="compose-container" itemscope="" itemtype="https://schema.org/EmailMessage" style="direction:ltr">
<span itemprop="creator" itemscope="" itemtype="https://schema.org/Organization"><span itemprop="name"></span></span>
<div>
<div>
<div style="direction:ltr">/48</div>
<div><br>
</div>
<div style="direction:ltr"></div>
</div>
<div><br>
</div>
<div class="acompli_signature"></div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> LACTF <lactf-bounces@lacnic.net> on behalf of Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>
<b>Sent:</b> Thursday, April 5, 2018 11:15:58 AM<br>
<b>To:</b> lactf@lacnic.net; lactf@lacnic.net<br>
<b>Subject:</b> Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17</font>
<div> </div>
</div>
<div>
<div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Buenos días,<br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Ingenieros cual es la máscara más pequeña en Ipv6 que podemos anunciar a Internet.
<br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.<br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Cualquier inquietud con gusto. <br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Cordialmente ñ, <br>
<br>
<br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Amancio Mora</div>
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
<b>Sent:</b> Tuesday, March 27, 2018 10:00:01 AM<br>
<b>To:</b> lactf@lacnic.net<br>
<b>Subject:</b> LACTF Digest, Vol 168, Issue 17</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:11pt">
<div class="PlainText">Send LACTF mailing list submissions to<br>
lactf@lacnic.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a><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>
<<a href="https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt">https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt</a>><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>
<<a href="https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt">https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt</a>><br>
<br>
The diff between the RFC4941 and our rfc4941bis is available at:<br>
<<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">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</a>><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: <a href="https://www.ietf.org/mailman/listinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><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>
(<<a href="https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04">https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04</a>>),<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>
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a><br>
Cancelar suscripcion: lactf-unsubscribe@lacnic.net<br>
<br>
<br>
------------------------------<br>
<br>
End of LACTF Digest, Vol 168, Issue 17<br>
**************************************<br>
</div>
</span></font></div>
</body>
</html>