<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Gracias, vamos a realizar la sumarizacion de la red /48 en uno de los Isp. <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> Thursday, April 5, 2018 9:59:16 AM<br>
<b>To:</b> lactf@lacnic.net<br>
<b>Subject:</b> LACTF Digest, Vol 169, Issue 8</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. Re: LACTF Digest, Vol 169, Issue 4 (Jaris Aizpr?a B.)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 5 Apr 2018 09:59:09 -0500<br>
From: Jaris Aizpr?a B. <jarisaizprua@gmail.com><br>
To: lactf@lac.ipv6tf.org<br>
Cc: "lactf@lacnic.net" <lactf@lacnic.net><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 4<br>
Message-ID:<br>
<CAF4x_n+k+M_E39cPmOpsnDTegGCRk7rpLhY8D6Yhu2rt6wzrMw@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
En alg?n punto de la red del operador, ejemplo equipos de borde, deber?n<br>
sumarizar/agregar las subredes del cliente (/52 /56 etc.) y anunciar hacia<br>
Internet solamente el prefijo /48.<br>
<br>
2018-04-05 9:46 GMT-05:00 Amancio Mora Rodriguez <mora_amancio@hotmail.com>:<br>
<br>
> Realmente, el cliente tiene su propio direccionamiento Ipv60/48, pero el<br>
> 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<br>
> recomendar?<br>
><br>
> Amancio Mora<br>
><br>
> ------------------------------<br>
> *From:* LACTF <lactf-bounces@lacnic.net> on behalf of<br>
> lactf-request@lacnic.net <lactf-request@lacnic.net><br>
> *Sent:* Thursday, April 5, 2018 9:33:19 AM<br>
> *To:* lactf@lacnic.net<br>
> *Subject:* LACTF Digest, Vol 169, Issue 4<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>
> <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. 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>
> <a href="https://datatracker.ietf.org/doc/draft-palet-v6ops-p2p-links/">https://datatracker.ietf.org/doc/draft-palet-v6ops-p2p-links/</a><br>
><br>
><br>
><br>
> y<br>
><br>
><br>
><br>
> <a href="https://www.ripe.net/publications/docs/ripe-690">https://www.ripe.net/publications/docs/ripe-690</a><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 <<br>
> 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" <<br>
> 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<br>
> 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<br>
> 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>
> <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=""></a>https://tools.ietf.org//rfcdiff?url1=https://tools.<br>
> ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt&url2=https:/<br>
> /tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt><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>
><br>
> _______________________________________________ LACTF mailing list<br>
> LACTF@lacnic.net <a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a> Cancelar<br>
> suscripcion: lactf-unsubscribe@lacnic.net<br>
><br>
><br>
><br>
> **********************************************<br>
> IPv4 is over<br>
> Are you ready for the new Internet ?<br>
> <a 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<br>
> confidential. The information is intended to be for the exclusive use of<br>
> the individual(s) named above and further non-explicilty authorized<br>
> disclosure, copying, distribution or use of the contents of this<br>
> information, even if partially, including attached files, is strictly<br>
> prohibited and will be considered a criminal offense. If you are not the<br>
> intended recipient be aware that any disclosure, copying, distribution or<br>
> use of the contents of this information, even if partially, including<br>
> attached files, is strictly prohibited, will be considered a criminal<br>
> offense, so you must reply to the original sender to inform about this<br>
> communication and delete it.<br>
><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<a href=""></a>https://mail.lacnic.net/pipermail/lactf/attachments/<br>
> 20180405/c2dfe476/attachment-0001.html><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<br>
> 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 <<br>
> 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<br>
> solo tiene asignado una red /48, pero el quiere en cada sede recibir solo<br>
> la default y anunciar un segmento /52. Cual ser?a la mejor opci?n de<br>
> 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<br>
> 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>
> <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. 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.<br>
> 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<br>
> 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<br>
> 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<br>
> 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>
> <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=""></a>https://tools.ietf.org//rfcdiff?url1=https://tools.<br>
> ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt&url2=https:/<br>
> /tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt><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>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<a href=""></a>https://mail.lacnic.net/pipermail/lactf/attachments/<br>
> 20180405/f6390d98/attachment-0001.html><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.<br>
> 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<br>
> 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<br>
> 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<br>
> 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>
> <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=""></a>https://tools.ietf.org//rfcdiff?url1=https://tools.<br>
> ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt&url2=https:/<br>
> /tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt><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>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<a href=""></a>https://mail.lacnic.net/pipermail/lactf/attachments/<br>
> 20180405/f6390d98/attachment-0002.html><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 169, Issue 2<br>
> *************************************<br>
><br>
> _______________________________________________ LACTF mailing list<br>
> LACTF@lacnic.net <a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a> Cancelar<br>
> suscripcion: lactf-unsubscribe@lacnic.net<br>
><br>
><br>
><br>
> **********************************************<br>
> IPv4 is over<br>
> Are you ready for the new Internet ?<br>
> <a 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<br>
> confidential. The information is intended to be for the exclusive use of<br>
> the individual(s) named above and further non-explicilty authorized<br>
> disclosure, copying, distribution or use of the contents of this<br>
> information, even if partially, including attached files, is strictly<br>
> prohibited and will be considered a criminal offense. If you are not the<br>
> intended recipient be aware that any disclosure, copying, distribution or<br>
> use of the contents of this information, even if partially, including<br>
> attached files, is strictly prohibited, will be considered a criminal<br>
> offense, so you must reply to the original sender to inform about this<br>
> communication and delete it.<br>
><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<a href=""></a>https://mail.lacnic.net/pipermail/lactf/attachments/<br>
> 20180405/66c6e448/attachment.html><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 169, Issue 4<br>
> *************************************<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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/cec97096/attachment-0002.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/cec97096/attachment-0002.html</a>><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 169, Issue 8<br>
*************************************<br>
</div>
</span></font>
</body>
</html>