<div dir="ltr">Me refiero a los últimos 64bits.</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">Atentamente,<div>Erick Lobo</div><div><br></div><div>lgD</div></div></div>
<br><br><div class="gmail_quote">2014-05-09 16:01 GMT-06:00 Erick Lobo Marín <span dir="ltr"><<a href="mailto:erick.lobo@cgr.go.cr" target="_blank">erick.lobo@cgr.go.cr</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Fernando: ¿Qué tan aceptado es el método que ha implementado Microsoft en sus sistemas operativos Windows de generación aleatoria de la dirección IPv6 sobre el tiempo?<div><div>Considerando entre las razones de su uso el evitar el tracking de la dirección IP.</div>
</div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">Atentamente,<div>Erick Lobo</div><div><br></div><div>lgD</div></div></div>
<br><br><div class="gmail_quote">2014-04-30 17:52 GMT-06:00 Fernando Gont <span dir="ltr"><<a href="mailto:fgont@si6networks.com" target="_blank">fgont@si6networks.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Estimados,<br>
<br>
FYI: <<a href="http://www.rfc-editor.org/rfc/rfc7217.txt" target="_blank">http://www.rfc-editor.org/rfc/rfc7217.txt</a>><br>
<br>
Esto es parte fundamental para mejorar la resistencia a ataques de<br>
escaneo de direcciones, y otras cosas tales como "host-tracking".<br>
<br>
P.S.: El "concepto" fue "separar el espacio de direcciones", al estilo<br>
RFC6528.<br>
<br>
Saludos, y gracias!<br>
Fernando<br>
<br>
<br>
<br>
<br>
-------- Original Message --------Subject: RFC 7217 on A Method for<br>
Generating Semantically Opaque Interface Identifiers with IPv6 Stateless<br>
Address Autoconfiguration (SLAAC)<br>
Date: Wed, 30 Apr 2014 14:05:39 -0700 (PDT)<br>
From: <a href="mailto:rfc-editor@rfc-editor.org" target="_blank">rfc-editor@rfc-editor.org</a><br>
Reply-To: <a href="mailto:ietf@ietf.org" target="_blank">ietf@ietf.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>
<br>
RFC 7217<br>
<br>
Title: A Method for Generating Semantically<br>
Opaque Interface Identifiers with IPv6 Stateless<br>
Address Autoconfiguration (SLAAC)<br>
Author: F. Gont<br>
Status: Standards Track<br>
Stream: IETF<br>
Date: April 2014<br>
Mailbox: <a href="mailto:fgont@si6networks.com" target="_blank">fgont@si6networks.com</a><br>
Pages: 19<br>
Characters: 48497<br>
Updates/Obsoletes/SeeAlso: None<br>
<br>
I-D Tag: draft-ietf-6man-stable-privacy-addresses-17.txt<br>
<br>
URL: <a href="http://www.rfc-editor.org/rfc/rfc7217.txt" target="_blank">http://www.rfc-editor.org/rfc/rfc7217.txt</a><br>
<br>
This document specifies a method for generating IPv6 Interface<br>
Identifiers to be used with IPv6 Stateless Address Autoconfiguration<br>
(SLAAC), such that an IPv6 address configured using this method is<br>
stable within each subnet, but the corresponding Interface Identifier<br>
changes when the host moves from one network to another. This method<br>
is meant to be an alternative to generating Interface Identifiers<br>
based on hardware addresses (e.g., IEEE LAN Media Access Control<br>
(MAC) addresses), such that the benefits of stable addresses can be<br>
achieved without sacrificing the security and privacy of users. The<br>
method specified in this document applies to all prefixes a host may<br>
be employing, including link-local, global, and unique-local prefixes<br>
(and their corresponding addresses).<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 Internet<br>
Official Protocol Standards (STD 1) for the standardization state and<br>
status of this protocol. Distribution of 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="http://www.ietf.org/mailman/listinfo/ietf-announce" target="_blank">http://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
<a href="http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" target="_blank">http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="http://www.rfc-editor.org/search" target="_blank">http://www.rfc-editor.org/search</a><br>
For downloading RFCs, see <a href="http://www.rfc-editor.org/rfc.html" target="_blank">http://www.rfc-editor.org/rfc.html</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>
<br>
--<br>
Fernando Gont<br>
e-mail: <a href="mailto:fernando@gont.com.ar" target="_blank">fernando@gont.com.ar</a> || <a href="mailto:fgont@si6networks.com" target="_blank">fgont@si6networks.com</a><br>
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
LACTF mailing list<br>
<a href="mailto:LACTF@lacnic.net" target="_blank">LACTF@lacnic.net</a><br>
<a href="https://mail.lacnic.net/mailman/listinfo/lactf" target="_blank">https://mail.lacnic.net/mailman/listinfo/lactf</a><br>
Cancelar suscripcion: <a href="mailto:lactf-unsubscribe@lacnic.net" target="_blank">lactf-unsubscribe@lacnic.net</a><br>
</blockquote></div><br></div>
</blockquote></div><br></div>