diff options
| author | erdgeist <> | 2006-12-15 15:01:06 +0000 |
|---|---|---|
| committer | erdgeist <> | 2006-12-15 15:01:06 +0000 |
| commit | 25e63d93d2d48d49799ec66f571b0457a3bd4345 (patch) | |
| tree | 8e5959d7606bb19cab0a6b847c3ef65452c0331a | |
| parent | 8d13a14584a50cb0f192456a6388c7299d67db43 (diff) | |
Cheap Excuses ;)
| -rw-r--r-- | README_v6 | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/README_v6 b/README_v6 new file mode 100644 index 0000000..72d25a3 --- /dev/null +++ b/README_v6 | |||
| @@ -0,0 +1,8 @@ | |||
| 1 | Q: Why is there no v6-support in opentracker? | ||
| 2 | |||
| 3 | A: Although I tried very hard, implementing v6 right now would be a terrible waste of bandwidth, there is no compact format for v6 addresses, so instead of | ||
| 4 | answering "d5:peers6:AAAAPPe" I'd have to send "d5:peersld2:ip39:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA4:port2:PPPPeee" for a single peer. Even if there was a | ||
| 5 | compact mode, v6 addresses still would eat up thrice the memory, v4 addresses take. This, however, wouldn't be a show stopper. | ||
| 6 | |||
| 7 | Other problems concern efficient peer selection for obviously v6-capable peers and how to select peers for non-v6 clients. v6 addresses eat up more memory on the | ||
| 8 | host, too ;) | ||