From 8eb826c08bbfe573970c6d8b4419d8081191ff42 Mon Sep 17 00:00:00 2001 From: Jim Newsome Date: Tue, 14 Nov 2023 13:40:20 -0600 Subject: flashflow: escape `*`s While mdbook seems to handle them ok, other parsers (such as vim's) get confused. --- proposals/316-flashflow.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'proposals') diff --git a/proposals/316-flashflow.md b/proposals/316-flashflow.md index 4a1fa15..6acdd0d 100644 --- a/proposals/316-flashflow.md +++ b/proposals/316-flashflow.md @@ -317,7 +317,7 @@ values. They are: with the target relay. We suggest s=160 based on the FF paper. - The bandwidth multiplier, m. Given an existing capacity estimate for a relay, z, the coordinator will instruct the measurers to, in - aggregate, send m*z Mbit/s to the target relay. We recommend m=2.25. + aggregate, send m\*z Mbit/s to the target relay. We recommend m=2.25. - The measurement duration, d. Based on the FF paper, we recommend d=30 seconds. @@ -419,7 +419,7 @@ slot for it. It picks slot 3. The coordinator takes the next largest, ``` The coordinator takes the next largest, 250, and randomly picks slot 2. -Slot 2 already has 600 Mbit/s of measurer capacity reserved (300*m); +Slot 2 already has 600 Mbit/s of measurer capacity reserved (300\*m); given just 1000 Mbit/s of total measurer capacity, there is just 400 Mbit/s of spare capacity while this relay requires 500 Mbit/s. There is not enough room in slot 2 for this relay. The coordinator picks a new @@ -825,7 +825,7 @@ will have (49/50)^(2*146) or 0.2% odds of success, which is quite low. Wanting a <1% chance that a 10 Mbit/s relay can successfully cheat results in a bucket size of approximately 125: -- 10*30 = 300 Mbit of traffic during 30s measurement. 37.5 million +- 10\*30 = 300 Mbit of traffic during 30s measurement. 37.5 million bytes. - 37,500,000 bytes / 514 bytes/cell = ~73,000 cells - bucket_size of 125 cells means 73,000 / 125 = 584 buckets -- cgit v1.2.3-54-g00ecf