org/meetings/2014WinterDevMeeting/notes/GuardDesign.md

-= Guard nodes =
+# Guard nodes
 
-'''Abstract:''' What is to be done?
+**Abstract:** What is to be done?
 
-== Minutes ==
+## Minutes
 
-=== One guard / guard sets ===
+### One guard / guard sets
 
 - Perhaps we should go to 1 guard by default.
 - Alternatively, we could go with "guard sets" and similar ideas, but those have deep gaps and unanswered questions.
@@ -15,7 +15,7 @@
   - ...the smallest guard is not too slow
 - Could there be a user parameter to raise guard bw threshold
 
-=== Guards and identity ===
+### Guards and identity
 
 - Hey, should there be a different set of guards per identity?
 - Or a different tor state per identity
@@ -30,7 +30,7 @@
   - But it would be cool to separate hidden services from other stuff
   - And it would be cool to allow separation via different socksports, etc
 
-=== How many guard are used at once? ===
+### How many guard are used at once?
 
 - Limit how many guards a user gets/tries at one time?
   - If you get a whole bunch of guards, probably your connection is down...
@@ -41,27 +41,27 @@
   - fingers to pick next guard from a small set?
   - decide these fingers based on unpredictable shuffle of net?
 
-=== When are guards chosen? ===
+### When are guards chosen?
 
 When to choose sets of guards?
 
 - option 1: choose more guards, use one at a time.  (Needs coding)
 - option 2: choose next guard at time of first-guard failure.
 
-=== Missing proposals ===
+### Missing proposals
 
 - Limit how many guards can go down (see sniper attack)
 - Should guard rotation period be consensus parameter?
 - New proposal: "i couldn't consense" statement.  Anybody could write.
 - New proposal: "consensus hash chain".  Anybody could write.
 
-=== Guard enumeration ===
+### Guard enumeration
 
 Guard enumeration, maybe 9 months is far easier then 2 months.  Especially if Tor is used infrequently. We need a solution for guard enumeration:
  - 2-hop cascades?
  - pathsel is an abstraction layer.
 
-=== arma matters ===
+### arma matters
 
 arma blocks unless we have a way to say that the users don't mostly get shoved onto shitty guards.
 
@@ -70,7 +70,7 @@ Open questions:
  - why does arma have so many guards in his state file?
  - why are his guards not in sequential order????????
 
-=== Next steps ===
+### Next steps
 
 Next steps: