> >>>>> Alain Durand <[EMAIL PROTECTED]> said: > >>> => again this is inadequate and stresses the previous issue. > >>> This MUST must not move to the standard track part. > >>> Note my environment suggestion works well for this case because > >>> daemons (which want the public address) run with another userID > >>> than applications of physical users (which want a temporary address). > >>> We really need soemthing tunable from the outside, not a new switch > >>> in every applications... > >> > >> I tend to agree. I previously said a per-node switch is better for > >> privacy purposes (though some disagreed), but more accurately, a > >> per-user switch is better. > > > The same user may want to use privacy when browsing > > the wild wild web and application robustness when > > accessing data on a file server. > > I like Francis suggestion of an environment switch. > > But in my understanding the environment switch can be inherited to > "descendents" (e.g. child processes). (If the understanding of the > switch on this point is the same between us) so the switch has > basically the same defect as the per-node switch; we cannot perfectly > prevent a user from creating an "environment" from which a user's > application may suffer. I don't get why you like the environment > switch while you (probably) dislike the per-node switch...
A per-node switch probably doesn't make sense because it would have an affect on both the "server-like" applications as well as the "client-like" applications. However, an environmental switch could make more sense because each user could throw that environmental setting into their .shellrc file and be assured that no application that they launch from that shell would ever use a non-temporary address by default. I.e., the inheritance is a feature. > Anyway...I still believe if I were a privacy conscious user (who needs > a RFC3041-like privacy mechanism) I would rather choose the possible > pitfalls than the leakage of privacy. However, I know some other guys > disagree on this view and I actually do not have a strong opinion on > the switch, I'll not insist on this point. Similarly, I'm just clarifying the argument, without necessarily trying to express an opinion. Best Regards, -jj -- Real programmers don't draw flowcharts. Flowcharts are, after all, the illiterate's form of documentation. Cavemen drew flowcharts; look how much good it did them. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
