Hi, Bob,

On 08/12/2013 04:59 PM, Bob Hinden wrote:
> 
> Pseudo-Random Per-Subnet Interface Identifiers
> 
> They are pseudo-random and intended to be used on a single subnet.
> 
> Personally, I would prefer something like these titles because
> "privacy" is once of several characteristics and the privacy
> characteristic depend a lot on how they are used and other factors
> like if they are put in the DNS, shared at the application layer, the
> prefix remains constant, etc.

IMHO, I think we're over-..thinking(?) the title.

For instance, the same arguments that have been made about the use of
the term "privacy" could be done about terms such as "secret" (in
"secret key") -- we shouldn't not be able to say "secret key" because it
all depends on whether you disclose or publish the key.

In this case, theses addresses have the following properties:

* They don't leak information about the underlying NIC manufacturer
* They don't disclose information about node identity
* They don't disclose any information about patterns employed by IPv6
addresses in the local subnet


You might use this addresses for incoming connections without affecting
the above properties. And you might set up temporary names (and publish
the addresses there) without affecting any of some of the above
properties. In any case, if you hurt their privacy properties at any
other layer, it's a similar case of someone leaking a secret key above
(but we still call them "secret").


The best thing a reader of this document can do is read the I-D we're
co-authoring with Dave and Alissa. Whatever title we were to chose won't
help the reader avoid the ned to do that.

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to