[tor-commits] [torspec/master] mention the uint32_t -> tor_addr_t transition too

[arma@xxxxxxxxxxxxxx]

commit ab2e389479d5db84f9a7de5f0e2cf279934d19c6
Author: Roger Dingledine <arma@xxxxxxxxxxxxxx>
Date:   Tue Mar 15 17:38:28 2011 -0400

    mention the uint32_t -> tor_addr_t transition too
---
 proposals/ideas/xxx-ipv6-plan.txt |   11 +++++++++--
 1 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/proposals/ideas/xxx-ipv6-plan.txt b/proposals/ideas/xxx-ipv6-plan.txt
index 26a0359..f88c0b0 100644
--- a/proposals/ideas/xxx-ipv6-plan.txt
+++ b/proposals/ideas/xxx-ipv6-plan.txt
@@ -41,8 +41,15 @@ What needs to change:
    dual stack of both IPv4 and IPv6 for interconnection seems like a
    reasonable step towards a fully hybrid v4/v6 Tor network.
 
-   Of course, more issues may be discovered as we develop solutions for these
-   issues, some of which may need to take priority.
+   One implementation hurdle that will need to get resolved alongside
+   these changes is to convert uint32_t to tor_addr_t in many more places
+   in the Tor code, so we can handle addresses being either IPv4 or IPv6.
+   There are a few cases, e.g. the local router list, where we'll want
+   to think harder about the resource requirements of keeping tens of
+   thousands of larger addresses in memory.
+
+   More issues may of course also be discovered as we develop solutions
+   for these issues, some of which may need to take priority.
 
 Designs that we will need to do:
 

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits