commit f8a91e2a106ef30734344361f76b3d47de1e91db parent df07946be57e0a3c7a9d79da14fc7910cf26d11d Author: Martin Schanzenbach <schanzen@gnunet.org> Date: Fri, 8 Sep 2023 17:21:40 +0200 notes on r5n Diffstat:
| M | IETF118/r5n.tex | | | 7 | +++++-- |
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/IETF118/r5n.tex b/IETF118/r5n.tex @@ -27,13 +27,16 @@ \begin{frame}{Support for in restricted-route environments} \begin{itemize} \item Problem: Restricted routes: what is that? - \item Solution: Randomized routing + \item Some peers, which from the distance metric (XOR) may be close, may not be reachable (e.g. firewall). + \item This leads to multiple (local) minima wrt where data may be stored/can be retrieved. + \item Solution: Randomized routing before XOR-metric-based routing. "Escape" local minimum sink. + \item When we have a small world topolofy, such a random walk will cause us to land in a random spot in the network and we will find a random local minimum. \end{itemize} \end{frame} \begin{frame}{Route recording} \begin{itemize} - \item Problem: ? + \item Problem: Peer which is very close in routing space. You should be connected, but you cannot connect (e.g. firewall). \item Solution: TODO \end{itemize} \end{frame}