<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 por la respuesta, si es necesario evaluar cada caso. <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> Thursday, April 5, 2018 11:32:39 AM<br>
<b>To:</b> lactf@lacnic.net<br>
<b>Subject:</b> LACTF Digest, Vol 169, Issue 21</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 18<br>
(Rafael Ignacio Sandoval Morales)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 5 Apr 2018 16:32:27 +0000<br>
From: Rafael Ignacio Sandoval Morales <rafael_ignacios@hotmail.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 169, Issue 18<br>
Message-ID:<br>
<BN6PR2201MB10921AFFE99339271B2AE77C9ABB0@BN6PR2201MB1092.namprd22.prod.outlook.com><br>
<br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Saludos Amancio, un poco ya concluida t? inquietud, pero me sumo a lo comentado por Jordi.<br>
<br>
Los ISP deben m?nimo entregar el /48 por cada punto de presencia a internet, es decir, cada sede conectada de forma directa desde donde se da el acceso directo e incluso se despliegan servicios publicados a internet. En el caso de que la entidad cuente con
redes extendidas y por ejemplo conectadas con MPLS, sugiero dejar dimensionado o reservado el uso de un /48 por cada sed para cu?ndo estas pasen hacer reales puntos directamente conectados y no LAN extendidas.<br>
<br>
Ya en el caso de un inmediato despliegue de toda la red del cliente, en la pr?ctica est?s sedes remotas requerir?n del desarrollo y del uso incluso del mismo o un ?nico /48, por ejemplo, dividi?ndolo en /56. Otro caso que me ha tocado , donde aplica el uso
de segmentaci?n de un mismo /48, es cuando el cliente tiene infraestructura compartida y por supuesto cuando no la tiene, es decir, en la pr?ctica est?n dentro del mismo /48.<br>
<br>
Son muy distintas los casos de negocios que se presentan y se deben mirar de forma particular las necesidades de cada uno para as? definir una estrategia de despliegue de IPv6.<br>
<br>
En los casos donde el ISP ofrezca tambi?n servicios internos en backend de la entidad y por ende el desarrollo del direccionamiento a toda la red de la entidad. Ejemplo: arrendamiento de infraestructura, reses extendidas, etc.<br>
<br>
Pero en suma, reiter?, y ya bien explicado por Jordi, la regla general es que el ISP debe entregar m?nimo el /48 para cada entidad.<br>
<br>
Bendiciones!<br>
<br>
Rafael Sandoval<br>
<br>
<br>
<br>
Get Outlook for iOS<<a href="https://aka.ms/o0ukef">https://aka.ms/o0ukef</a>><br>
________________________________<br>
From: LACTF <lactf-bounces@lacnic.net> on behalf of Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>
Sent: Thursday, April 5, 2018 10:35:07 AM<br>
To: lactf@lacnic.net<br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 18<br>
<br>
Gracias por la respuesta.<br>
<br>
Cordialmente ?,<br>
<br>
Amancio Mora<br>
<br>
________________________________<br>
From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
Sent: Thursday, April 5, 2018 10:28:14 AM<br>
To: lactf@lacnic.net<br>
Subject: LACTF Digest, Vol 169, Issue 18<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 169, Issue 16 (JORDI PALET MARTINEZ)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 05 Apr 2018 17:27:58 +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 16<br>
Message-ID: <4EE7C903-737B-4BAC-98AE-E40FC3F7E8A6@consulintel.es><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
As? es, seguramente LACNIC le podr? asignar un /48 contiguo.<br>
<br>
<br>
<br>
De este modo, si un d?a el operador es el mismo, podr?a sumarizar el anuncio de ambas sedes en un ?nico /47.<br>
<br>
<br>
<br>
Si tuviera mas sedes en el futuro, sucesivos /48 contiguos, y as? puede sumarizar a un /46, /45, /44, etc.<br>
<br>
<br>
Saludos,<br>
<br>
Jordi<br>
<br>
<br>
<br>
De: LACTF <lactf-bounces@lacnic.net> en nombre de Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>
Responder a: <lactf@lac.ipv6tf.org><br>
Fecha: jueves, 5 de abril de 2018, 17:24<br>
Para: "lactf@lacnic.net" <lactf@lacnic.net><br>
Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 16<br>
<br>
<br>
<br>
Ok, la opci?n es que el cliente deber?a solicitar a la Lacnic otra red /48 para la otra sede.<br>
<br>
<br>
Amancio Mora<br>
<br>
<br>
<br>
From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
Sent: Thursday, April 5, 2018 10:20:48 AM<br>
To: lactf@lacnic.net<br>
Subject: LACTF Digest, Vol 169, Issue 16<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 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 <jordi.palet@consulintel.es><br>
To: <lactf@lac.ipv6tf.org><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 13<br>
Message-ID: <A7B93B67-216B-4102-9730-B8966FB1F421@consulintel.es><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 <lactf-bounces@lacnic.net> en nombre de Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>
Responder a: <lactf@lac.ipv6tf.org><br>
Fecha: jueves, 5 de abril de 2018, 17:14<br>
Para: "lactf@lacnic.net" <lactf@lacnic.net>, "lactf@lacnic.net" <lactf@lacnic.net><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 <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
Sent: Thursday, April 5, 2018 10:10:22 AM<br>
To: lactf@lacnic.net<br>
Subject: LACTF Digest, Vol 169, Issue 13<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 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 <jordi.palet@consulintel.es><br>
To: <lactf@lac.ipv6tf.org><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 6<br>
Message-ID: <FCD28B92-B0BD-43B2-9CA5-27A5EE3750D4@consulintel.es><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 <lactf-bounces@lacnic.net> en nombre de "Jaris Aizpr?a B." <jarisaizprua@gmail.com><br>
Responder a: <lactf@lac.ipv6tf.org><br>
Fecha: jueves, 5 de abril de 2018, 17:07<br>
Para: <lactf@lac.ipv6tf.org><br>
CC: "lactf@lacnic.net" <lactf@lacnic.net><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 <mora_amancio@hotmail.com>:<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 <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
Sent: Thursday, April 5, 2018 9:52:49 AM<br>
To: lactf@lacnic.net<br>
Subject: LACTF Digest, Vol 169, Issue 6<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 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 <jordi.palet@consulintel.es><br>
To: <lactf@lac.ipv6tf.org><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 4<br>
Message-ID: <F3A7EC2A-565E-42C7-95FF-854E6058C84A@consulintel.es><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 <lactf-bounces@lacnic.net> en nombre de Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>
Responder a: <lactf@lac.ipv6tf.org><br>
Fecha: jueves, 5 de abril de 2018, 16:47<br>
Para: "lactf@lacnic.net" <lactf@lacnic.net><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 <lactf-bounces@lacnic.net> on behalf of 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>
<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 <mora_amancio@hotmail.com><br>
Responder a: <lactf@lac.ipv6tf.org><br>
Fecha: jueves, 5 de abril de 2018, 16:16<br>
Para: "lactf@lacnic.net" <lactf@lacnic.net>, "lactf@lacnic.net" <lactf@lacnic.net><br>
Asunto: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>
<br>
<br>
<br>
Buenos d?as,<br>
<br>
Ingenieros cual es la m?scara m?s peque?a en Ipv6 que podemos anunciar a Internet.<br>
<br>
Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.<br>
<br>
Cualquier inquietud con gusto.<br>
<br>
Cordialmente ?,<br>
<br>
<br>
Amancio Mora<br>
<br>
<br>
<br>
From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
Sent: Tuesday, March 27, 2018 10:00:01 AM<br>
To: lactf@lacnic.net<br>
Subject: LACTF Digest, Vol 168, Issue 17<br>
<br>
<br>
<br>
Send LACTF mailing list submissions to<br>
lactf@lacnic.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<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>
<br>
_______________________________________________ LACTF mailing list LACTF@lacnic.net
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a> Cancelar 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 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: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/c2dfe476/attachment-0001.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/c2dfe476/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 05 Apr 2018 16:33:09 +0200<br>
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es><br>
To: <lactf@lac.ipv6tf.org><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 2<br>
Message-ID: <CEAAA94B-C5D8-4377-8D03-AF9EFA0C54D0@consulintel.es><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Lo correcto es que cada end-site tenga su propio /48 y no hay mas discusi?n posible.<br>
<br>
<br>
<br>
Entiendo que adem?s es un cliente corporativo, as? que con mayor motivo!<br>
<br>
<br>
<br>
<br>
Saludos,<br>
<br>
Jordi<br>
<br>
<br>
<br>
De: LACTF <lactf-bounces@lacnic.net> en nombre de Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>
Responder a: <lactf@lac.ipv6tf.org><br>
Fecha: jueves, 5 de abril de 2018, 16:30<br>
Para: "lactf@lacnic.net" <lactf@lacnic.net><br>
Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 2<br>
<br>
<br>
<br>
Adicional si el cliente tiene dos sedes conectadas a diferente proveedor y solo tiene asignado una red /48, pero el quiere en cada sede recibir solo la default y anunciar un segmento /52. Cual ser?a la mejor opci?n de configuraci?n que se le da al cliente final.<br>
<br>
Amancio Mora<br>
<br>
<br>
<br>
From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
Sent: Thursday, April 5, 2018 9:18:19 AM<br>
To: lactf@lacnic.net<br>
Subject: LACTF Digest, Vol 169, Issue 2<br>
<br>
<br>
<br>
Send LACTF mailing list submissions to<br>
lactf@lacnic.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<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.namprd04.prod.outlook.com><br>
<br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
/48<br>
<br>
<br>
________________________________<br>
From: LACTF <lactf-bounces@lacnic.net> on behalf of Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>
Sent: Thursday, April 5, 2018 11:15:58 AM<br>
To: lactf@lacnic.net; lactf@lacnic.net<br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>
<br>
Buenos d?as,<br>
<br>
Ingenieros cual es la m?scara m?s peque?a en Ipv6 que podemos anunciar a Internet.<br>
<br>
Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.<br>
<br>
Cualquier inquietud con gusto.<br>
<br>
Cordialmente ?,<br>
<br>
<br>
<br>
Amancio Mora<br>
<br>
________________________________<br>
From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
Sent: Tuesday, March 27, 2018 10:00:01 AM<br>
To: lactf@lacnic.net<br>
Subject: LACTF Digest, Vol 168, Issue 17<br>
<br>
Send LACTF mailing list submissions to<br>
lactf@lacnic.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/attachment-0001.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 5 Apr 2018 14:18:08 +0000<br>
From: Alex Ojeda <alex@chilenetworks.com><br>
To: "lactf@lac.ipv6tf.org" <lactf@lac.ipv6tf.org>, "lactf@lacnic.net"<br>
<lactf@lacnic.net><br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>
Message-ID:<br>
<BY2PR0401MB167295CDFBD703887BD34459C3BB0@BY2PR0401MB1672.namprd04.prod.outlook.com><br>
<br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
/48<br>
<br>
<br>
________________________________<br>
From: LACTF <lactf-bounces@lacnic.net> on behalf of Amancio Mora Rodriguez <mora_amancio@hotmail.com><br>
Sent: Thursday, April 5, 2018 11:15:58 AM<br>
To: lactf@lacnic.net; lactf@lacnic.net<br>
Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17<br>
<br>
Buenos d?as,<br>
<br>
Ingenieros cual es la m?scara m?s peque?a en Ipv6 que podemos anunciar a Internet.<br>
<br>
Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.<br>
<br>
Cualquier inquietud con gusto.<br>
<br>
Cordialmente ?,<br>
<br>
<br>
<br>
Amancio Mora<br>
<br>
________________________________<br>
From: LACTF <lactf-bounces@lacnic.net> on behalf of lactf-request@lacnic.net <lactf-request@lacnic.net><br>
Sent: Tuesday, March 27, 2018 10:00:01 AM<br>
To: lactf@lacnic.net<br>
Subject: LACTF Digest, Vol 168, Issue 17<br>
<br>
Send LACTF mailing list submissions to<br>
lactf@lacnic.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/attachment-0002.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/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 2<br>
*************************************<br>
<br>
_______________________________________________ LACTF mailing list LACTF@lacnic.net
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a> Cancelar 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 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: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/66c6e448/attachment.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/66c6e448/attachment.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 4<br>
*************************************<br>
<br>
_______________________________________________ LACTF mailing list LACTF@lacnic.net
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a> Cancelar 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 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: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/9b5642b7/attachment.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/9b5642b7/attachment.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 6<br>
*************************************<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>
<br>
_______________________________________________ LACTF mailing list LACTF@lacnic.net
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a> Cancelar 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 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: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/251fa76e/attachment.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/251fa76e/attachment.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 13<br>
**************************************<br>
<br>
_______________________________________________ LACTF mailing list LACTF@lacnic.net
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a> Cancelar 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 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: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/3d2a4743/attachment.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/3d2a4743/attachment.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 16<br>
**************************************<br>
<br>
_______________________________________________ LACTF mailing list LACTF@lacnic.net
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a> Cancelar 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 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: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/b3a8e5b1/attachment.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/b3a8e5b1/attachment.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 18<br>
**************************************<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://mail.lacnic.net/pipermail/lactf/attachments/20180405/54745c95/attachment-0002.html">https://mail.lacnic.net/pipermail/lactf/attachments/20180405/54745c95/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 21<br>
**************************************<br>
<br>
</div>
</span></font>
</body>
</html>