Quoting Dave Crocker <[email protected]>:
If we -- the IETF community -- had a definition of privacy, that would
help, but we don't.
If we knew what it meant to 'enable privacy' (nevermind whether by
default), that would also help, but we don't.
So the idea of 'privacy by default' well could serve as a useful
catch-phrase, but at the moment, it lacks technical substance. We have
no shared, technical understanding of its meaning.
Here are something to understand what privacy means.
"Information privacy, or data privacy, is the relationship between
collection and dissemination of data, technology, the public
expectation of privacy, and the legal and political issues surrounding
them.
Privacy concerns exist wherever personally identifiable information is
collected and stored.
The challenge in data privacy is to share data while protecting
personally identifiable information." [1]
"Internet privacy involves the right or mandate of personal privacy
concerning the storing, repurposing, provision to third-parties, and
displaying of information pertaining to oneself via the Internet." [2]
"Personally identifiable information (PII), as used in US privacy law
and information security, is information that can be used on its own
or with other information to identify, contact, or locate a single
person, or to identify an individual in context." [3]
[1] http://en.wikipedia.org/wiki/Data_privacy
[2] http://en.wikipedia.org/wiki/Internet_privacy
[3] http://en.wikipedia.org/wiki/Personally_identifiable_information
ES.-
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
perpass mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/perpass
