<div dir="auto">Hi folks,</div><div dir="auto"><br></div><div dir="auto">Adding some comments here - hopefully English is not a problem (feel free to reply in Spanish/Portuguese).</div><div dir="auto"><br></div><div dir="auto">I appreciate the tone in the draft touching upon some points that are critical, specially, at the moment, in this IETF generation. </div><div dir="auto"><br></div><div dir="auto">I mentioned some initiatives to Fernando such as the waiver for the remote meetings (that should imho be made permanent) and the shmoo doc that is a small water drop in a hot stone. The IETF could likewise put some budget aside to fund authors from the LAC region with docs to be present in a physical meeting (similarly to the funding available at IRTF/ANRP fronts).</div><div dir="auto"><br></div><div dir="auto">I appreciate the education part as well, as it usually depends on the on-site meetings for newcomers to give ppl a mentor but it doesn’t make the process of digesting the documents and understanding process better. You go once to this meeting and ... you are forgotten. Have fun digging out docs, emails and finding peers.</div><div dir="auto"><br></div><div dir="auto">Lastly, language: I have been in some meetings were the presenter was intimidated by the audience bcs of insufficient good English to catch in a discussion at the mic or even hostile language. Maybe the most vivid experience was a Japanese presenting about DCTCP and the TSV WG-chair did nothing to reduce the pressure on her. There is a certain tolerance to some behavior that would be otherwise reported if you belong to some silos. They seem to have a hard time believing that you (belonging to the silo) could be doing a bad job in the community and not just polishing your ego or backscratching your friends. I believe the IETF needs a committee that starts cleaning up this sort of bad language and/or behavior with power to ban a member or WG chair for meeting(s) or assuming any other function. </div><div dir="auto"><br></div><div dir="auto">Finally, people of the same organization holding tokens to others of the same organization and just moving chair among them, pulling the next one of the same or, when their term is over. It shouldn’t be allowed consecutive terms of people coming from the same affiliation.</div><div dir="auto"><br></div><div dir="auto">My2c. Saludos,</div><div dir="auto">Simone</div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 1 Mar 2021 at 10:55, Douglas Fischer <<a href="mailto:fischerdouglas@gmail.com">fischerdouglas@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="ltr"><div class="gmail_default" style="font-family:"courier new",monospace;font-size:small">¡Soy brasileño!<br>¡Así que ya sabes lo que voy a decir de Maradona!<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>¡Messi es mejor que Maradona!<br></div><div class="gmail_default" style="font-family:"courier new",monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:"courier new",monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:"courier new",monospace;font-size:small"><br></div></div><br><div class="gmail_quote"></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em dom., 28 de fev. de 2021 às 23:38, Fernando Gont <<a href="mailto:fgont@si6networks.com" target="_blank">fgont@si6networks.com</a>> escreveu:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"></blockquote></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Estimados/as,<br>
<br>
FYI: <a href="https://www.rfc-editor.org/info/rfc8981" rel="noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc8981</a><br>
(mas abajo podrán encontrar un resumen técnico)<br>
<br>
Hace un poco más de 20 años atrás, estaba todavia en el colegio <br>
secundario, y habia empezado a leer RFCs de IETF -- con algo de <br>
frustración al ver que no habían RFCs con autores de la región.<br>
<br>
Pasó mucho tiempo (y muchas cosas) desde ahí... desde empezar a escribir <br>
un primer internet-draft, a pedir dinero prestado para poder asistir a <br>
mi primera reunión, renunciar a trabajos para poder hacer ingenieria de <br>
Internet (con un futuro verdaderamente incierto :-) ), y otras tantas <br>
cosas más.<br>
<br>
Los tiempos luego cambiaron, pero algunas cosas no: las reglas y los <br>
obstacúlos para participar en IETF jamas fueron los mismos para quienes <br>
veniamos del c* del mundo -- o, mejor dicho, para quienes no <br>
pertenecemos a la comunidad dominante de IETF (ver <br>
<a href="https://datatracker.ietf.org/doc/html/draft-gont-diversity-analysis-00" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/html/draft-gont-diversity-analysis-00</a>).<br>
<br>
En todo este tiempo, Diego Maradona fue un motivador imprescindible... <br>
en particular ante situaciones adversas.<br>
<br>
<br>
A poco mas de tres meses de habernos dejado físicamente, mi guiño <br>
(<a href="https://www.rfc-editor.org/rfc/rfc8981.html#name-authors-addresses" rel="noreferrer" target="_blank">https://www.rfc-editor.org/rfc/rfc8981.html#name-authors-addresses</a> ) a <br>
quien fuera distinguido como "Maestro Inspirador de los Soñadores" <br>
[Oxford] [Forbes].<br>
<br>
La vida no es la misma sin el Diego.<br>
<br>
<br>
[Oxford] <br>
<a href="https://www.tiempoar.com.ar/nota/de-villa-fiorito-a-oxford-cuando-maradona-fue-maestro-inspirador-de-suenos-en-inglaterra" rel="noreferrer" target="_blank">https://www.tiempoar.com.ar/nota/de-villa-fiorito-a-oxford-cuando-maradona-fue-maestro-inspirador-de-suenos-en-inglaterra</a><br>
<br>
[Forbes] <br>
<a href="https://www.forbesargentina.com/today/murio-diego-maradona-hombre-invento-asi-mismo-llego-lo-mas-alto-convirtio-maestro-inspirador-sonadores-n4615" rel="noreferrer" target="_blank">https://www.forbesargentina.com/today/murio-diego-maradona-hombre-invento-asi-mismo-llego-lo-mas-alto-convirtio-maestro-inspirador-sonadores-n4615</a><br>
<br>
<br>
Saludos cordiales,<br>
Fernando Gont<br>
SI6 Networks<br>
<br>
<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: Fwd: RFC 8981 on Temporary Address Extensions for Stateless <br>
Address Autoconfiguration in IPv6<br>
Date: Sun, 28 Feb 2021 22:41:05 -0300<br>
From: Fernando Gont <<a href="mailto:fgont@si6networks.com" target="_blank">fgont@si6networks.com</a>><br>
To: IPv6 Hackers Mailing List <<a href="mailto:ipv6hackers@lists.si6networks.com" target="_blank">ipv6hackers@lists.si6networks.com</a>><br>
<br>
Folks,<br>
<br>
RFC 8981, entitled "Temporary Address Extensions for Stateless Address <br>
Autoconfiguration in IPv6", has finally been published: <br>
<a href="https://www.rfc-editor.org/info/rfc8981" rel="noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc8981</a><br>
<br>
It has been the product of over four years of work.<br>
<br>
It is revision of RFC4941 -- the so called "IPv6 temporary addresses", <br>
also known as "IPv6 Privacy Addresses".<br>
<br>
This revision does a number of interesting things, including:<br>
<br>
* It employs a different algorithms for generating the Interface <br>
Identifiers (IIDs)<br>
<br>
* Addresses issues present in RFC4941, such as re-using the same <br>
interface identifier across different prefixes<br>
<br>
* The lifetimes of temporary addresses are reduced, thus reducing the <br>
average number of addresses that may be in use at any given time.<br>
<br>
* The lifetime of addresses is randomized, such that it's harder to <br>
infer when addresses are re-generated.<br>
<br>
Thanks,<br>
Fernando<br>
<br>
<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: RFC 8981 on Temporary Address Extensions for Stateless Address <br>
Autoconfiguration in IPv6<br>
Date: Sun, 28 Feb 2021 13:29:06 -0800 (PST)<br>
From: <a href="mailto:rfc-editor@rfc-editor.org" target="_blank">rfc-editor@rfc-editor.org</a><br>
To: <a href="mailto:ietf-announce@ietf.org" target="_blank">ietf-announce@ietf.org</a>, <a href="mailto:rfc-dist@rfc-editor.org" target="_blank">rfc-dist@rfc-editor.org</a><br>
CC: <a href="mailto:drafts-update-ref@iana.org" target="_blank">drafts-update-ref@iana.org</a>, <a href="mailto:ipv6@ietf.org" target="_blank">ipv6@ietf.org</a>, <a href="mailto:rfc-editor@rfc-editor.org" target="_blank">rfc-editor@rfc-editor.org</a><br>
<br>
A new Request for Comments is now available in online RFC libraries.<br>
<br>
RFC 8981<br>
<br>
Title: Temporary Address Extensions for Stateless <br>
Address Autoconfiguration in IPv6 Author: F. Gont,<br>
S. Krishnan,<br>
T. Narten,<br>
R. Draves<br>
Status: Standards Track<br>
Stream: IETF<br>
Date: February 2021<br>
Mailbox: <a href="mailto:fgont@si6networks.com" target="_blank">fgont@si6networks.com</a>,<br>
<a href="mailto:suresh@kaloom.com" target="_blank">suresh@kaloom.com</a>,<br>
<a href="mailto:narten@cs.duke.edu" target="_blank">narten@cs.duke.edu</a>,<br>
<a href="mailto:richdr@microsoft.com" target="_blank">richdr@microsoft.com</a><br>
Pages: 20<br>
Obsoletes: RFC 4941<br>
<br>
I-D Tag: draft-ietf-6man-rfc4941bis-12.txt<br>
<br>
URL: <a href="https://www.rfc-editor.org/info/rfc8981" rel="noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc8981</a><br>
<br>
DOI: 10.17487/RFC8981<br>
<br>
This document describes an extension to IPv6 Stateless Address<br>
Autoconfiguration that causes hosts to generate temporary addresses<br>
with randomized interface identifiers for each prefix advertised with<br>
autoconfiguration enabled. Changing addresses over time limits the<br>
window of time during which eavesdroppers and other information<br>
collectors may trivially perform address-based network-activity<br>
correlation when the same address is employed for multiple<br>
transactions by the same host. Additionally, it reduces the window of<br>
exposure of a host as being accessible via an address that becomes<br>
revealed as a result of active communication. This document obsoletes<br>
RFC 4941.<br>
<br>
This document is a product of the IPv6 Maintenance Working Group of the <br>
IETF.<br>
<br>
This is now a Proposed Standard.<br>
<br>
STANDARDS TRACK: This document specifies an Internet Standards Track<br>
protocol for the Internet community, and requests discussion and suggestions<br>
for improvements. Please refer to the current edition of the Official<br>
Internet Protocol Standards (<a href="https://www.rfc-editor.org/standards" rel="noreferrer" target="_blank">https://www.rfc-editor.org/standards</a>) for <br>
the standardization state and status of this protocol. Distribution of <br>
this memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
<a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer" target="_blank">https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="https://www.rfc-editor.org/search" rel="noreferrer" target="_blank">https://www.rfc-editor.org/search</a><br>
For downloading RFCs, see <a href="https://www.rfc-editor.org/retrieve/bulk" rel="noreferrer" target="_blank">https://www.rfc-editor.org/retrieve/bulk</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org" target="_blank">rfc-editor@rfc-editor.org</a>. Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
<br>
<br>
--------------------------------------------------------------------<br>
IETF IPv6 working group mailing list<br>
<a href="mailto:ipv6@ietf.org" target="_blank">ipv6@ietf.org</a><br>
Administrative Requests: <a href="https://www.ietf.org/mailman/listinfo/ipv6" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br>
<br></blockquote></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
_______________________________________________<br>
LACNOG mailing list<br>
<a href="mailto:LACNOG@lacnic.net" target="_blank">LACNOG@lacnic.net</a><br>
<a href="https://mail.lacnic.net/mailman/listinfo/lacnog" rel="noreferrer" target="_blank">https://mail.lacnic.net/mailman/listinfo/lacnog</a><br>
Cancelar suscripcion: <a href="https://mail.lacnic.net/mailman/options/lacnog" rel="noreferrer" target="_blank">https://mail.lacnic.net/mailman/options/lacnog</a></blockquote></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><font size="2" style="color:rgb(0,0,0)"><span style="font-family:"courier new",monospace">Douglas Fernando Fischer</span><br style="font-family:"courier new",monospace"><span style="font-family:"courier new",monospace">Engº de Controle e Automação</span></font><div style="padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;text-align:left;line-height:130%;font-family:"courier new",monospace;color:black"></div></div>
_____________________________________________<br>
Ietf-lac mailing list<br>
<a href="mailto:Ietf-lac@lacnog.org" target="_blank">Ietf-lac@lacnog.org</a><br>
Cancelar suscripcion: <a href="mailto:ietf-lac-unsubscribe@lacnog.org" target="_blank">ietf-lac-unsubscribe@lacnog.org</a><br>
<br>
</blockquote></div></div>