[LAC-TF] LACTF Digest, Vol 169, Issue 16
Sergio Rojas. . .
sergio at lacnic.net
Thu Apr 5 13:49:53 BRT 2018
Hola Amancio,
Agregando algo a la sugerencia de Jordi, te comento que de acuerdo a las
políticas actuales de LACNIC, si comenzarás el despliegue IPv6 y ves que
el bloque inicialmente asignado por LACNIC no es suficiente (el /48)
para tu proyecto, puedes solicitar por única vez una ampliación de este
rango sin que ésto genere un costo adicional. Puedes consultar esta
política accediendo al siguiente link, punto 4.5.4.3
http://www.lacnic.net/547/1/lacnic/
Previendo que este escenario ocurra, LACNIC reserva espacio contiguo al
recibido inicialmente, así que podrás recibir el /48 contiguo para la
otra sede. Inclusive, puedes prever una proyección de crecimiento y
solicitar mas de 1 /48 adicional ;).
Para solicitar la ampliación, es necesario que su cliente contacte a
hostmaster at lacnic.net. Puede mantenerle copiado en el correo para darle
seguimiento al caso.
Espero que la información otorgada le haya sido de utilidad.
Saludos!
Sergio. . .
El 5/4/18 a las 12:27, JORDI PALET MARTINEZ escribió:
>
> Así es, seguramente LACNIC le podrá asignar un /48 contiguo.
>
>
>
> De este modo, si un día el operador es el mismo, podría sumarizar el
> anuncio de ambas sedes en un único /47.
>
>
>
> Si tuviera mas sedes en el futuro, sucesivos /48 contiguos, y así
> puede sumarizar a un /46, /45, /44, etc.
>
>
> Saludos,
>
> Jordi
>
>
>
> *De: *LACTF <lactf-bounces at lacnic.net> en nombre de Amancio Mora
> Rodriguez <mora_amancio at hotmail.com>
> *Responder a: *<lactf at lac.ipv6tf.org>
> *Fecha: *jueves, 5 de abril de 2018, 17:24
> *Para: *"lactf at lacnic.net" <lactf at lacnic.net>
> *Asunto: *Re: [LAC-TF] LACTF Digest, Vol 169, Issue 16
>
>
>
> Ok, la opción es que el cliente debería solicitar a la Lacnic otra red
> /48 para la otra sede.
>
>
> Amancio Mora
>
>
>
> ------------------------------------------------------------------------
>
> *From:*LACTF <lactf-bounces at lacnic.net> on behalf of
> lactf-request at lacnic.net <lactf-request at lacnic.net>
> *Sent:* Thursday, April 5, 2018 10:20:48 AM
> *To:* lactf at lacnic.net
> *Subject:* LACTF Digest, Vol 169, Issue 16
>
>
>
> Send LACTF mailing list submissions to
> lactf at lacnic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.lacnic.net/mailman/listinfo/lactf
> or, via email, send a message with subject or body 'help' to
> lactf-request at lacnic.net
>
> You can reach the person managing the list at
> lactf-owner at lacnic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of LACTF digest..."
>
>
> Today's Topics:
>
> 1. Re: LACTF Digest, Vol 169, Issue 13 (JORDI PALET MARTINEZ)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 05 Apr 2018 17:20:36 +0200
> From: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>
> To: <lactf at lac.ipv6tf.org>
> Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 13
> Message-ID: <A7B93B67-216B-4102-9730-B8966FB1F421 at consulintel.es>
> Content-Type: text/plain; charset="utf-8"
>
> No, eso es incorrecto.
>
>
>
> El cliente tiene un /48 para cada sede, pero deber? utilizar /64
> dentro de ese /48 para cada LAN, VLAN, etc.
>
>
>
> Es decir, tiene hasta 65.535 posibles LANs con un /48.
>
>
>
> Saludos,
>
> Jordi
>
>
>
> De: LACTF <lactf-bounces at lacnic.net> en nombre de Amancio Mora
> Rodriguez <mora_amancio at hotmail.com>
> Responder a: <lactf at lac.ipv6tf.org>
> Fecha: jueves, 5 de abril de 2018, 17:14
> Para: "lactf at lacnic.net" <lactf at lacnic.net>, "lactf at lacnic.net"
> <lactf at lacnic.net>
> Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 13
>
>
>
> Es proponerle lo correcto, dejando claro las opciones que pueden existir.
>
> 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.
>
> Amancio Mora
>
>
>
> From: LACTF <lactf-bounces at lacnic.net> on behalf of
> lactf-request at lacnic.net <lactf-request at lacnic.net>
> Sent: Thursday, April 5, 2018 10:10:22 AM
> To: lactf at lacnic.net
> Subject: LACTF Digest, Vol 169, Issue 13
>
>
>
> Send LACTF mailing list submissions to
> lactf at lacnic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.lacnic.net/mailman/listinfo/lactf
> or, via email, send a message with subject or body 'help' to
> lactf-request at lacnic.net
>
> You can reach the person managing the list at
> lactf-owner at lacnic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of LACTF digest..."
>
>
> Today's Topics:
>
> 1. Re: LACTF Digest, Vol 169, Issue 6 (JORDI PALET MARTINEZ)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 05 Apr 2018 17:10:11 +0200
> From: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>
> To: <lactf at lac.ipv6tf.org>
> Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 6
> Message-ID: <FCD28B92-B0BD-43B2-9CA5-27A5EE3750D4 at consulintel.es>
> Content-Type: text/plain; charset="utf-8"
>
> Aunque un /48 fuera suficiente para ?repartir entre ambas? sedes, es
> incorrecto.
>
>
>
> Insisto, queremos recomendar lo correcto o cualquier cosa?
>
>
> Saludos,
>
> Jordi
>
>
>
> De: LACTF <lactf-bounces at lacnic.net> en nombre de "Jaris Aizpr?a B."
> <jarisaizprua at gmail.com>
> Responder a: <lactf at lac.ipv6tf.org>
> Fecha: jueves, 5 de abril de 2018, 17:07
> Para: <lactf at lac.ipv6tf.org>
> CC: "lactf at lacnic.net" <lactf at lacnic.net>
> Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 6
>
>
>
> 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.
>
>
>
> 2018-04-05 10:02 GMT-05:00 Amancio Mora Rodriguez
> <mora_amancio at hotmail.com>:
>
> 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.
>
> 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.
>
> Amancio Mora
>
>
>
> From: LACTF <lactf-bounces at lacnic.net> on behalf of
> lactf-request at lacnic.net <lactf-request at lacnic.net>
> Sent: Thursday, April 5, 2018 9:52:49 AM
> To: lactf at lacnic.net
> Subject: LACTF Digest, Vol 169, Issue 6
>
>
>
> Send LACTF mailing list submissions to
> lactf at lacnic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.lacnic.net/mailman/listinfo/lactf
> or, via email, send a message with subject or body 'help' to
> lactf-request at lacnic.net
>
> You can reach the person managing the list at
> lactf-owner at lacnic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of LACTF digest..."
>
>
> Today's Topics:
>
> 1. Re: LACTF Digest, Vol 169, Issue 4 (JORDI PALET MARTINEZ)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 05 Apr 2018 16:52:08 +0200
> From: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>
> To: <lactf at lac.ipv6tf.org>
> Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 4
> Message-ID: <F3A7EC2A-565E-42C7-95FF-854E6058C84A at consulintel.es>
> Content-Type: text/plain; charset="utf-8"
>
> 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 ?
>
>
> Saludos,
>
> Jordi
>
>
>
> De: LACTF <lactf-bounces at lacnic.net> en nombre de Amancio Mora
> Rodriguez <mora_amancio at hotmail.com>
> Responder a: <lactf at lac.ipv6tf.org>
> Fecha: jueves, 5 de abril de 2018, 16:47
> Para: "lactf at lacnic.net" <lactf at lacnic.net>
> Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 4
>
>
>
> Realmente, el cliente tiene su propio direccionamiento Ipv60/48, pero
> el solo quiere utilizar una red /52 por sede.
>
> Qu? se le tendr?a que decir al cliente final? Que configuraci?n se le
> debe recomendar?
>
> Amancio Mora
>
>
>
> From: LACTF <lactf-bounces at lacnic.net> on behalf of
> lactf-request at lacnic.net <lactf-request at lacnic.net>
> Sent: Thursday, April 5, 2018 9:33:19 AM
> To: lactf at lacnic.net
> Subject: LACTF Digest, Vol 169, Issue 4
>
>
>
> Send LACTF mailing list submissions to
> lactf at lacnic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.lacnic.net/mailman/listinfo/lactf
> or, via email, send a message with subject or body 'help' to
> lactf-request at lacnic.net
>
> You can reach the person managing the list at
> lactf-owner at lacnic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of LACTF digest..."
>
>
> Today's Topics:
>
> 1. Re: LACTF Digest, Vol 168, Issue 17 (JORDI PALET MARTINEZ)
> 2. Re: LACTF Digest, Vol 169, Issue 2 (JORDI PALET MARTINEZ)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 05 Apr 2018 16:30:12 +0200
> From: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>
> To: <lactf at lac.ipv6tf.org>
> Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17
> Message-ID: <1814AB46-668D-4B34-A7AD-921BD2C11946 at consulintel.es>
> Content-Type: text/plain; charset="utf-8"
>
> En general si anuncias algo mas largo que /48, te lo van a filtrar.
>
>
>
> Porque estas asignando menos de un /48 ?
>
>
>
> Sugiero leer:
>
>
>
> https://datatracker.ietf.org/doc/draft-palet-v6ops-p2p-links/
>
>
>
> y
>
>
>
> https://www.ripe.net/publications/docs/ripe-690
>
>
>
>
> Saludos,
>
> Jordi
>
>
>
> De: LACTF <lactf-bounces at lacnic.net> en nombre de Amancio Mora
> Rodriguez <mora_amancio at hotmail.com>
> Responder a: <lactf at lac.ipv6tf.org>
> Fecha: jueves, 5 de abril de 2018, 16:16
> Para: "lactf at lacnic.net" <lactf at lacnic.net>, "lactf at lacnic.net"
> <lactf at lacnic.net>
> Asunto: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17
>
>
>
> Buenos d?as,
>
> Ingenieros cual es la m?scara m?s peque?a en Ipv6 que podemos anunciar
> a Internet.
>
> Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.
>
> Cualquier inquietud con gusto.
>
> Cordialmente ?,
>
>
> Amancio Mora
>
>
>
> From: LACTF <lactf-bounces at lacnic.net> on behalf of
> lactf-request at lacnic.net <lactf-request at lacnic.net>
> Sent: Tuesday, March 27, 2018 10:00:01 AM
> To: lactf at lacnic.net
> Subject: LACTF Digest, Vol 168, Issue 17
>
>
>
> Send LACTF mailing list submissions to
> lactf at lacnic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.lacnic.net/mailman/listinfo/lactf
> or, via email, send a message with subject or body 'help' to
> lactf-request at lacnic.net
>
> You can reach the person managing the list at
> lactf-owner at lacnic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of LACTF digest..."
>
>
> Today's Topics:
>
> 1. Fwd: Fwd: RFC4941bis (Fernando Gont)
> 2. Fwd: Requirements for IPv6 Temporary Addresses (Fernando Gont)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 26 Mar 2018 16:15:20 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: "lactf at lacnic.net" <lactf at lacnic.net>, Lista para discusi?n de
> seguridad en redes y sistemas informaticos de la regi?n
> <seguridad at lacnic.net>
> Subject: [LAC-TF] Fwd: Fwd: RFC4941bis
> Message-ID: <9d1dfd63-db99-75ad-a58c-e82e049fd3e3 at si6networks.com>
> Content-Type: text/plain; charset=windows-1252
>
> FYI
>
>
> -------- Forwarded Message --------
> Subject: Fwd: RFC4941bis
> Date: Mon, 26 Mar 2018 14:48:34 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: IPv6 Hackers Mailing List <ipv6hackers at lists.si6networks.com>
>
> Folks,
>
> As the subject implies, this is an effort to revise RFC4941 to fix the
> issues in it.
>
> Comments welcome... even more if sent to (or CC'ed to ipv6 at ietf.org)
>
> Thanks!
>
> Best regards,
> Fernando
>
>
>
>
> -------- Forwarded Message --------
> Subject: RFC4941bis
> Date: Mon, 26 Mar 2018 04:55:06 +0100
> From: Fernando Gont <fgont at si6networks.com>
> Organization: SI6 Networks
> To: 6man at ietf.org <6man at ietf.org>
> CC: 6man-chairs at tools.ietf.org <6man-chairs at tools.ietf.org>
>
> Folks,
>
> Based on the comments on the last 6man meeting, we have done the
> following:
>
> 1) We have asked the RFC Editor the xml source for RFC4941, applied the
> minimum changes to publish it as an I-D, and posted it as:
> <https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt>
>
> 2) We subsequently applied all the corresponding changes to arrive to
> something similar to what we had in draft-gont-6man-rfc4941bis-00
> (please note the slight difference in the filename), presented at the
> last 6man meeting.
>
> The resulting document is available at:
> <https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt>
>
> The diff between the RFC4941 and our rfc4941bis is available at:
> <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>>
>
>
> Note: we have also added the verified errata for RFC4941 (which we had
> not yet incorporated in the version presented at the last 6man meeting).
>
> Your comments will be very appreciated!
>
> Thanks!
>
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont at si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6 at ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 26 Mar 2018 16:15:38 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: "lactf at lacnic.net" <lactf at lacnic.net>, Lista para discusi?n de
> seguridad en redes y sistemas informaticos de la regi?n
> <seguridad at lacnic.net>
> Subject: [LAC-TF] Fwd: Requirements for IPv6 Temporary Addresses
> Message-ID: <2dfac8a3-876a-3f9e-8ac8-727355baba76 at si6networks.com>
> Content-Type: text/plain; charset=utf-8
>
> FYI
>
>
> -------- Forwarded Message --------
> Subject: Requirements for IPv6 Temporary Addresses
> Date: Mon, 26 Mar 2018 15:03:23 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: IPv6 Hackers Mailing List <ipv6hackers at lists.si6networks.com>
>
> Folks,
>
> FYI, we have published the IETF Internet-Draft "Recommendation on
> Temporary IPv6 Interface Identifiers"
> (<https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04>),
> which specifies requirements for temporary addresses (a la RFC8064).
>
> So we have:
>
> * RFC8064: Requirements for stable addresses
> * RFC7217: A recommended algorithm for stable addresses that complies
> with RFC8064
> * draft-gont-6man-non-stable-iids: Requirements for temporary addresses
> * /draft-fgont-6man-rfc4941bis: Some recommended algorithms for
> temporary addresses that comply with draft-gont-6man-non-stable-iids
>
> Comments welcome... even more if sent to (or CC'ed to ipv6 at ietf.org)
>
> Thanks!
>
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont at si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
> ------------------------------
>
> End of LACTF Digest, Vol 168, Issue 17
> **************************************
>
> _______________________________________________ LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactfCancelar suscripcion:
> lactf-unsubscribe at lacnic.net
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> 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.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://mail.lacnic.net/pipermail/lactf/attachments/20180405/c2dfe476/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 05 Apr 2018 16:33:09 +0200
> From: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>
> To: <lactf at lac.ipv6tf.org>
> Subject: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 2
> Message-ID: <CEAAA94B-C5D8-4377-8D03-AF9EFA0C54D0 at consulintel.es>
> Content-Type: text/plain; charset="utf-8"
>
> Lo correcto es que cada end-site tenga su propio /48 y no hay mas
> discusi?n posible.
>
>
>
> Entiendo que adem?s es un cliente corporativo, as? que con mayor motivo!
>
>
>
>
> Saludos,
>
> Jordi
>
>
>
> De: LACTF <lactf-bounces at lacnic.net> en nombre de Amancio Mora
> Rodriguez <mora_amancio at hotmail.com>
> Responder a: <lactf at lac.ipv6tf.org>
> Fecha: jueves, 5 de abril de 2018, 16:30
> Para: "lactf at lacnic.net" <lactf at lacnic.net>
> Asunto: Re: [LAC-TF] LACTF Digest, Vol 169, Issue 2
>
>
>
> 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.
>
> Amancio Mora
>
>
>
> From: LACTF <lactf-bounces at lacnic.net> on behalf of
> lactf-request at lacnic.net <lactf-request at lacnic.net>
> Sent: Thursday, April 5, 2018 9:18:19 AM
> To: lactf at lacnic.net
> Subject: LACTF Digest, Vol 169, Issue 2
>
>
>
> Send LACTF mailing list submissions to
> lactf at lacnic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.lacnic.net/mailman/listinfo/lactf
> or, via email, send a message with subject or body 'help' to
> lactf-request at lacnic.net
>
> You can reach the person managing the list at
> lactf-owner at lacnic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of LACTF digest..."
>
>
> Today's Topics:
>
> 1. Re: LACTF Digest, Vol 168, Issue 17 (Alex Ojeda)
> 2. Re: LACTF Digest, Vol 168, Issue 17 (Alex Ojeda)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 5 Apr 2018 14:18:08 +0000
> From: Alex Ojeda <alex at chilenetworks.com>
> To: "lactf at lac.ipv6tf.org" <lactf at lac.ipv6tf.org>, "lactf at lacnic.net"
> <lactf at lacnic.net>
> Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17
> Message-ID:
>
> <BY2PR0401MB167295CDFBD703887BD34459C3BB0 at BY2PR0401MB1672.namprd04.prod.outlook.com>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> /48
>
>
> ________________________________
> From: LACTF <lactf-bounces at lacnic.net> on behalf of Amancio Mora
> Rodriguez <mora_amancio at hotmail.com>
> Sent: Thursday, April 5, 2018 11:15:58 AM
> To: lactf at lacnic.net; lactf at lacnic.net
> Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17
>
> Buenos d?as,
>
> Ingenieros cual es la m?scara m?s peque?a en Ipv6 que podemos anunciar
> a Internet.
>
> Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.
>
> Cualquier inquietud con gusto.
>
> Cordialmente ?,
>
>
>
> Amancio Mora
>
> ________________________________
> From: LACTF <lactf-bounces at lacnic.net> on behalf of
> lactf-request at lacnic.net <lactf-request at lacnic.net>
> Sent: Tuesday, March 27, 2018 10:00:01 AM
> To: lactf at lacnic.net
> Subject: LACTF Digest, Vol 168, Issue 17
>
> Send LACTF mailing list submissions to
> lactf at lacnic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.lacnic.net/mailman/listinfo/lactf
> or, via email, send a message with subject or body 'help' to
> lactf-request at lacnic.net
>
> You can reach the person managing the list at
> lactf-owner at lacnic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of LACTF digest..."
>
>
> Today's Topics:
>
> 1. Fwd: Fwd: RFC4941bis (Fernando Gont)
> 2. Fwd: Requirements for IPv6 Temporary Addresses (Fernando Gont)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 26 Mar 2018 16:15:20 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: "lactf at lacnic.net" <lactf at lacnic.net>, Lista para discusi?n de
> seguridad en redes y sistemas informaticos de la regi?n
> <seguridad at lacnic.net>
> Subject: [LAC-TF] Fwd: Fwd: RFC4941bis
> Message-ID: <9d1dfd63-db99-75ad-a58c-e82e049fd3e3 at si6networks.com>
> Content-Type: text/plain; charset=windows-1252
>
> FYI
>
>
> -------- Forwarded Message --------
> Subject: Fwd: RFC4941bis
> Date: Mon, 26 Mar 2018 14:48:34 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: IPv6 Hackers Mailing List <ipv6hackers at lists.si6networks.com>
>
> Folks,
>
> As the subject implies, this is an effort to revise RFC4941 to fix the
> issues in it.
>
> Comments welcome... even more if sent to (or CC'ed to ipv6 at ietf.org)
>
> Thanks!
>
> Best regards,
> Fernando
>
>
>
>
> -------- Forwarded Message --------
> Subject: RFC4941bis
> Date: Mon, 26 Mar 2018 04:55:06 +0100
> From: Fernando Gont <fgont at si6networks.com>
> Organization: SI6 Networks
> To: 6man at ietf.org <6man at ietf.org>
> CC: 6man-chairs at tools.ietf.org <6man-chairs at tools.ietf.org>
>
> Folks,
>
> Based on the comments on the last 6man meeting, we have done the
> following:
>
> 1) We have asked the RFC Editor the xml source for RFC4941, applied the
> minimum changes to publish it as an I-D, and posted it as:
> <https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt>
>
> 2) We subsequently applied all the corresponding changes to arrive to
> something similar to what we had in draft-gont-6man-rfc4941bis-00
> (please note the slight difference in the filename), presented at the
> last 6man meeting.
>
> The resulting document is available at:
> <https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt>
>
> The diff between the RFC4941 and our rfc4941bis is available at:
> <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>>
>
>
> Note: we have also added the verified errata for RFC4941 (which we had
> not yet incorporated in the version presented at the last 6man meeting).
>
> Your comments will be very appreciated!
>
> Thanks!
>
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont at si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6 at ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 26 Mar 2018 16:15:38 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: "lactf at lacnic.net" <lactf at lacnic.net>, Lista para discusi?n de
> seguridad en redes y sistemas informaticos de la regi?n
> <seguridad at lacnic.net>
> Subject: [LAC-TF] Fwd: Requirements for IPv6 Temporary Addresses
> Message-ID: <2dfac8a3-876a-3f9e-8ac8-727355baba76 at si6networks.com>
> Content-Type: text/plain; charset=utf-8
>
> FYI
>
>
> -------- Forwarded Message --------
> Subject: Requirements for IPv6 Temporary Addresses
> Date: Mon, 26 Mar 2018 15:03:23 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: IPv6 Hackers Mailing List <ipv6hackers at lists.si6networks.com>
>
> Folks,
>
> FYI, we have published the IETF Internet-Draft "Recommendation on
> Temporary IPv6 Interface Identifiers"
> (<https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04>),
> which specifies requirements for temporary addresses (a la RFC8064).
>
> So we have:
>
> * RFC8064: Requirements for stable addresses
> * RFC7217: A recommended algorithm for stable addresses that complies
> with RFC8064
> * draft-gont-6man-non-stable-iids: Requirements for temporary addresses
> * /draft-fgont-6man-rfc4941bis: Some recommended algorithms for
> temporary addresses that comply with draft-gont-6man-non-stable-iids
>
> Comments welcome... even more if sent to (or CC'ed to ipv6 at ietf.org)
>
> Thanks!
>
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont at si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
> ------------------------------
>
> End of LACTF Digest, Vol 168, Issue 17
> **************************************
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 5 Apr 2018 14:18:08 +0000
> From: Alex Ojeda <alex at chilenetworks.com>
> To: "lactf at lac.ipv6tf.org" <lactf at lac.ipv6tf.org>, "lactf at lacnic.net"
> <lactf at lacnic.net>
> Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17
> Message-ID:
>
> <BY2PR0401MB167295CDFBD703887BD34459C3BB0 at BY2PR0401MB1672.namprd04.prod.outlook.com>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> /48
>
>
> ________________________________
> From: LACTF <lactf-bounces at lacnic.net> on behalf of Amancio Mora
> Rodriguez <mora_amancio at hotmail.com>
> Sent: Thursday, April 5, 2018 11:15:58 AM
> To: lactf at lacnic.net; lactf at lacnic.net
> Subject: Re: [LAC-TF] LACTF Digest, Vol 168, Issue 17
>
> Buenos d?as,
>
> Ingenieros cual es la m?scara m?s peque?a en Ipv6 que podemos anunciar
> a Internet.
>
> Existe alguna regla que bloque el anuncio de redes ejemplo /52 o /56.
>
> Cualquier inquietud con gusto.
>
> Cordialmente ?,
>
>
>
> Amancio Mora
>
> ________________________________
> From: LACTF <lactf-bounces at lacnic.net> on behalf of
> lactf-request at lacnic.net <lactf-request at lacnic.net>
> Sent: Tuesday, March 27, 2018 10:00:01 AM
> To: lactf at lacnic.net
> Subject: LACTF Digest, Vol 168, Issue 17
>
> Send LACTF mailing list submissions to
> lactf at lacnic.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.lacnic.net/mailman/listinfo/lactf
> or, via email, send a message with subject or body 'help' to
> lactf-request at lacnic.net
>
> You can reach the person managing the list at
> lactf-owner at lacnic.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of LACTF digest..."
>
>
> Today's Topics:
>
> 1. Fwd: Fwd: RFC4941bis (Fernando Gont)
> 2. Fwd: Requirements for IPv6 Temporary Addresses (Fernando Gont)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 26 Mar 2018 16:15:20 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: "lactf at lacnic.net" <lactf at lacnic.net>, Lista para discusi?n de
> seguridad en redes y sistemas informaticos de la regi?n
> <seguridad at lacnic.net>
> Subject: [LAC-TF] Fwd: Fwd: RFC4941bis
> Message-ID: <9d1dfd63-db99-75ad-a58c-e82e049fd3e3 at si6networks.com>
> Content-Type: text/plain; charset=windows-1252
>
> FYI
>
>
> -------- Forwarded Message --------
> Subject: Fwd: RFC4941bis
> Date: Mon, 26 Mar 2018 14:48:34 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: IPv6 Hackers Mailing List <ipv6hackers at lists.si6networks.com>
>
> Folks,
>
> As the subject implies, this is an effort to revise RFC4941 to fix the
> issues in it.
>
> Comments welcome... even more if sent to (or CC'ed to ipv6 at ietf.org)
>
> Thanks!
>
> Best regards,
> Fernando
>
>
>
>
> -------- Forwarded Message --------
> Subject: RFC4941bis
> Date: Mon, 26 Mar 2018 04:55:06 +0100
> From: Fernando Gont <fgont at si6networks.com>
> Organization: SI6 Networks
> To: 6man at ietf.org <6man at ietf.org>
> CC: 6man-chairs at tools.ietf.org <6man-chairs at tools.ietf.org>
>
> Folks,
>
> Based on the comments on the last 6man meeting, we have done the
> following:
>
> 1) We have asked the RFC Editor the xml source for RFC4941, applied the
> minimum changes to publish it as an I-D, and posted it as:
> <https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-00.txt>
>
> 2) We subsequently applied all the corresponding changes to arrive to
> something similar to what we had in draft-gont-6man-rfc4941bis-00
> (please note the slight difference in the filename), presented at the
> last 6man meeting.
>
> The resulting document is available at:
> <https://tools.ietf.org/id/draft-fgont-6man-rfc4941bis-01.txt>
>
> The diff between the RFC4941 and our rfc4941bis is available at:
> <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>>
>
>
> Note: we have also added the verified errata for RFC4941 (which we had
> not yet incorporated in the version presented at the last 6man meeting).
>
> Your comments will be very appreciated!
>
> Thanks!
>
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont at si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6 at ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 26 Mar 2018 16:15:38 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: "lactf at lacnic.net" <lactf at lacnic.net>, Lista para discusi?n de
> seguridad en redes y sistemas informaticos de la regi?n
> <seguridad at lacnic.net>
> Subject: [LAC-TF] Fwd: Requirements for IPv6 Temporary Addresses
> Message-ID: <2dfac8a3-876a-3f9e-8ac8-727355baba76 at si6networks.com>
> Content-Type: text/plain; charset=utf-8
>
> FYI
>
>
> -------- Forwarded Message --------
> Subject: Requirements for IPv6 Temporary Addresses
> Date: Mon, 26 Mar 2018 15:03:23 +0100
> From: Fernando Gont <fgont at si6networks.com>
> To: IPv6 Hackers Mailing List <ipv6hackers at lists.si6networks.com>
>
> Folks,
>
> FYI, we have published the IETF Internet-Draft "Recommendation on
> Temporary IPv6 Interface Identifiers"
> (<https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-04>),
> which specifies requirements for temporary addresses (a la RFC8064).
>
> So we have:
>
> * RFC8064: Requirements for stable addresses
> * RFC7217: A recommended algorithm for stable addresses that complies
> with RFC8064
> * draft-gont-6man-non-stable-iids: Requirements for temporary addresses
> * /draft-fgont-6man-rfc4941bis: Some recommended algorithms for
> temporary addresses that comply with draft-gont-6man-non-stable-iids
>
> Comments welcome... even more if sent to (or CC'ed to ipv6 at ietf.org)
>
> Thanks!
>
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont at si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
> ------------------------------
>
> End of LACTF Digest, Vol 168, Issue 17
> **************************************
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://mail.lacnic.net/pipermail/lactf/attachments/20180405/f6390d98/attachment-0002.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
> ------------------------------
>
> End of LACTF Digest, Vol 169, Issue 2
> *************************************
>
> _______________________________________________ LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactfCancelar suscripcion:
> lactf-unsubscribe at lacnic.net
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> 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.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://mail.lacnic.net/pipermail/lactf/attachments/20180405/66c6e448/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
> ------------------------------
>
> End of LACTF Digest, Vol 169, Issue 4
> *************************************
>
> _______________________________________________ LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactfCancelar suscripcion:
> lactf-unsubscribe at lacnic.net
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> 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.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://mail.lacnic.net/pipermail/lactf/attachments/20180405/9b5642b7/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
> ------------------------------
>
> End of LACTF Digest, Vol 169, Issue 6
> *************************************
>
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
>
> _______________________________________________ LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactfCancelar suscripcion:
> lactf-unsubscribe at lacnic.net
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> 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.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://mail.lacnic.net/pipermail/lactf/attachments/20180405/251fa76e/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
> ------------------------------
>
> End of LACTF Digest, Vol 169, Issue 13
> **************************************
>
> _______________________________________________ LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactfCancelar suscripcion:
> lactf-unsubscribe at lacnic.net
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> 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.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://mail.lacnic.net/pipermail/lactf/attachments/20180405/3d2a4743/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
> ------------------------------
>
> End of LACTF Digest, Vol 169, Issue 16
> **************************************
>
> _______________________________________________ LACTF mailing list
> LACTF at lacnic.net https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> 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.
>
>
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
> Cancelar suscripcion: lactf-unsubscribe at lacnic.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.lacnic.net/pipermail/lactf/attachments/20180405/12c035a9/attachment-0001.html>
More information about the LACTF
mailing list