[LAC-TF] LACTF Digest, Vol 169, Issue 2

Amancio Mora Rodriguez mora_amancio at hotmail.com
Thu Apr 5 11:29:43 BRT 2018


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>


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>


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
*************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.lacnic.net/pipermail/lactf/attachments/20180405/e1260266/attachment-0001.html>


More information about the LACTF mailing list