Some comments about the scope of the wikipedia problem

svn:r3432

diff --git a/doc/design-paper/challenges.tex b/doc/design-paper/challenges.tex
index f6d3b0dd3597d17fd21fb70118db862f84c4c364..032ddf55229c1ad880f2d3fab57b862e8665e3c9 100644 (file)
--- a/doc/design-paper/challenges.tex
+++ b/doc/design-paper/challenges.tex
@@ -270,6 +270,25 @@ snipe them?
 Takedowns and efnet abuse and wikipedia complaints and irc
 networks.
 
+This is potentially a bigger problem than it may appear. 
+On the one hand, if people want to refuse connections from you on
+their servers it would seem that they should be allowed to.  But, a
+possible major problem with the blocking of Tor is that it's not just
+the decision of the individual server administrator whose deciding if
+he wants to post to wikipedia from his Tor node address or allow
+people to read wikipedia anonymously through his Tor node. If e.g.,
+s/he comes through a campus or corporate NAT, then the decision must
+be to have the entire population behind it able to have a Tor exit
+node or write access to wikipedia. This is a loss for both of us (Tor
+and wikipedia). We don't want to compete for (or divvy up) the NAT
+protected entities of the world.
+
+Squishy IP based ``authentication'' and ``authorization'' is a reality
+we must contend with. We should say something more about the analogy
+with SSNs.
+
+
+
 \subsection{Other}
 
 Tor's scope: How much should Tor aim to do? Applications that leak