From c9085a5562d7e7a7a6a975d4a1b133ee6392b4b3 Mon Sep 17 00:00:00 2001
From: swillden <>
Date: Wed, 9 Nov 2011 14:37:59 +0000
Subject: [PATCH] [Imported from Trac: page Summit2Day1, version 2]

---
 Summit2Day1.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/Summit2Day1.md b/Summit2Day1.md
index bc6578f..7eb08b5 100644
--- a/Summit2Day1.md
+++ b/Summit2Day1.md
@@ -52,7 +52,10 @@ expected vs required vs known, k-of-N, H, points, understandability
     - Brian says client/gateway should expect user to teach it what sort of
       grid they expect, so it can bail when expectations aren't met
     - Shawn would prefer scheme where client measures reliability itself,
-      chooses k/N/H to meet certain speed/cost/reliability goals
+      sets N to the number of servers currently accepting shares, sets H
+      slightly below N (to improve upload availability) and computes and
+      uses a k that maximizes performance (or minimizes cost) while achieving
+      a target reliability.
 
 ## encrypted git, or revision control on tahoe
     - Zack(?) is thinking about revision control on top of Tahoe, will