[Ietf-lac] [lacnog] RFC8981 y el maradonianismo (Fwd: Fwd: RFC 8981 on Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6)

Mon Mar 1 06:55:37 -03 2021

¡Soy brasileño!
¡Así que ya sabes lo que voy a decir de Maradona!

¡Messi es mejor que Maradona!

Em dom., 28 de fev. de 2021 às 23:38, Fernando Gont <fgont at si6networks.com>
escreveu:

> Estimados/as,
>
> FYI: https://www.rfc-editor.org/info/rfc8981
> (mas abajo podrán encontrar un resumen técnico)
>
> Hace un poco más de 20 años atrás, estaba todavia en el colegio
> secundario, y habia empezado a leer RFCs de IETF -- con algo de
> frustración al ver que no habían RFCs con autores de la región.
>
> Pasó mucho tiempo (y muchas cosas) desde ahí... desde empezar a escribir
> un primer internet-draft, a pedir dinero prestado para poder asistir a
> mi primera reunión, renunciar a trabajos para poder hacer ingenieria de
> Internet (con un futuro verdaderamente incierto :-) ), y otras tantas
> cosas más.
>
> Los tiempos luego cambiaron, pero algunas cosas no: las reglas y los
> obstacúlos para participar en IETF jamas fueron los mismos para quienes
> veniamos del c* del mundo -- o, mejor dicho, para quienes no
> pertenecemos a la comunidad dominante de IETF (ver
> https://datatracker.ietf.org/doc/html/draft-gont-diversity-analysis-00).
>
> En todo este tiempo, Diego Maradona fue un motivador imprescindible...
> en particular ante situaciones adversas.
>
>
> A poco mas de tres meses de habernos dejado físicamente, mi guiño
> (https://www.rfc-editor.org/rfc/rfc8981.html#name-authors-addresses ) a
> quien fuera distinguido como "Maestro Inspirador de los Soñadores"
> [Oxford] [Forbes].
>
> La vida no es la misma sin el Diego.
>
>
> [Oxford]
>
> https://www.tiempoar.com.ar/nota/de-villa-fiorito-a-oxford-cuando-maradona-fue-maestro-inspirador-de-suenos-en-inglaterra
>
> [Forbes]
>
> https://www.forbesargentina.com/today/murio-diego-maradona-hombre-invento-asi-mismo-llego-lo-mas-alto-convirtio-maestro-inspirador-sonadores-n4615
>
>
> Saludos cordiales,
> Fernando Gont
> SI6 Networks
>
>
>
>
> -------- Forwarded Message --------
> Subject: Fwd: RFC 8981 on Temporary Address Extensions for Stateless
> Address Autoconfiguration in IPv6
> Date: Sun, 28 Feb 2021 22:41:05 -0300
> From: Fernando Gont <fgont at si6networks.com>
> To: IPv6 Hackers Mailing List <ipv6hackers at lists.si6networks.com>
>
> Folks,
>
> RFC 8981, entitled "Temporary Address Extensions for Stateless Address
> Autoconfiguration in IPv6", has finally been published:
> https://www.rfc-editor.org/info/rfc8981
>
> It has been the product of over four years of work.
>
> It is revision of RFC4941 -- the so called "IPv6 temporary addresses",
> also known as "IPv6 Privacy Addresses".
>
> This revision does a number of interesting things, including:
>
> * It employs a different algorithms for generating the Interface
> Identifiers (IIDs)
>
> * Addresses issues present in RFC4941, such as re-using the same
> interface identifier across different prefixes
>
> * The lifetimes of temporary addresses are reduced, thus reducing the
> average number of addresses that may be in use at any given time.
>
> * The lifetime of addresses is randomized, such that it's harder to
> infer when addresses are re-generated.
>
> Thanks,
> Fernando
>
>
>
>
> -------- Forwarded Message --------
> Subject: RFC 8981 on Temporary Address Extensions for Stateless Address
> Autoconfiguration in IPv6
> Date: Sun, 28 Feb 2021 13:29:06 -0800 (PST)
> From: rfc-editor at rfc-editor.org
> To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
> CC: drafts-update-ref at iana.org, ipv6 at ietf.org, rfc-editor at rfc-editor.org
>
> A new Request for Comments is now available in online RFC libraries.
>
>                  RFC 8981
>
>          Title:      Temporary Address Extensions for Stateless
>    Address Autoconfiguration in IPv6         Author:     F. Gont,
>                      S. Krishnan,
>                      T. Narten,
>                      R. Draves
>          Status:     Standards Track
>          Stream:     IETF
>          Date:       February 2021
>          Mailbox:    fgont at si6networks.com,
>                      suresh at kaloom.com,
>                      narten at cs.duke.edu,
>                      richdr at microsoft.com
>          Pages:      20
>          Obsoletes:  RFC 4941
>
>          I-D Tag:    draft-ietf-6man-rfc4941bis-12.txt
>
>          URL:        https://www.rfc-editor.org/info/rfc8981
>
>          DOI:        10.17487/RFC8981
>
> This document describes an extension to IPv6 Stateless Address
> Autoconfiguration that causes hosts to generate temporary addresses
> with randomized interface identifiers for each prefix advertised with
> autoconfiguration enabled. Changing addresses over time limits the
> window of time during which eavesdroppers and other information
> collectors may trivially perform address-based network-activity
> correlation when the same address is employed for multiple
> transactions by the same host. Additionally, it reduces the window of
> exposure of a host as being accessible via an address that becomes
> revealed as a result of active communication. This document obsoletes
> RFC 4941.
>
> This document is a product of the IPv6 Maintenance Working Group of the
> IETF.
>
> This is now a Proposed Standard.
>
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and
> suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for
> the standardization state and status of this protocol.  Distribution of
> this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>    https://www.ietf.org/mailman/listinfo/ietf-announce
>    https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6 at ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
> _______________________________________________
> LACNOG mailing list
> LACNOG at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lacnog
> Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
>

-- 
Douglas Fernando Fischer
Engº de Controle e Automação
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.lacnic.net/pipermail/ietf-lac/attachments/20210301/3866e43f/attachment-0001.htm>