OK, I’ll go ahead and do an -01 with a better introduction, which is clearly needed. Interested to hear what others think of Robin’s privacy/confidentiality distinction.
On Sun, Mar 15, 2015 at 4:00 AM, Dave Crocker <d...@dcrocker.net> wrote: > On 3/14/2015 2:27 AM, Tim Bray wrote: > > This draft is trying to make general points that are orthogonal to any > > particular technology, including: > > > > - Positive & negative privacy failures are asymmetrically harmful > > - the right choices are hard to make, so just don't ask inexpert uses to > > make them, > > - the cost of privacy technologies is monotonically falling > > > +1 to the nature and direction of this document. > > Especially for topics that are complex, poorly understood and/or are > controversial, it can greatly help to discuss issues and tradeoffs in > higher-level, non-technical terms. I usually cast this as needing > statement about functional benefits and detriments for users (end-users, > operators, etc.) > > The summary bullets Tim provided, above, are worth adding to the > document early, with the rest of document providing substance to them. > > If there is enough community difficulty in readily seeing the nature and > benefit of this exercise -- I usually assume that when any one > reasonable reader has that sort of problem, others will too -- we should > probably find an example to add that distinguishes between this level of > discussion and the lower-level type that IETF work typical deals with -- > and that ought to derive from these higher-level points. > > There might be an line of discussion to add to the document, namely > tradeoffs and limitations of various technical approaches, especially > popular ones. For example, transport-level encryption has notable > benefits, but the deficiencies seem to be absent from most IETF > discussions, leaving very large holes in the creator/consumer path. > > d/ > > -- > Dave Crocker > Brandenburg InternetWorking > bbiw.net > -- - Tim Bray (If you’d like to send me a private message, see https://keybase.io/timbray)
_______________________________________________ perpass mailing list perpass@ietf.org https://www.ietf.org/mailman/listinfo/perpass
