diff options
-rw-r--r-- | src/transport/gnunet-service-tng.c | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/src/transport/gnunet-service-tng.c b/src/transport/gnunet-service-tng.c index 1d6329c21..7d7d04375 100644 --- a/src/transport/gnunet-service-tng.c +++ b/src/transport/gnunet-service-tng.c | |||
@@ -33,6 +33,19 @@ | |||
33 | * transport-to-transport traffic) | 33 | * transport-to-transport traffic) |
34 | * | 34 | * |
35 | * Implement next: | 35 | * Implement next: |
36 | * - address validation: what is our plan here? | ||
37 | * #1 Peerstore only gets 'validated' addresses | ||
38 | * #2 transport needs another API to "trigger" validation! | ||
39 | * API may be used by core/application or communicators; | ||
40 | * => use yet another lib/MQ/connection? | ||
41 | * #3 transport should use validation to also establish | ||
42 | * effective flow control (for uni-directional transports!) | ||
43 | * #4 UDP broadcasting logic must be extended to use the new API | ||
44 | * #5 only validated addresses go to ATS for scheduling; that | ||
45 | * also ensures we know the RTT | ||
46 | * #6 to ensure flow control and RTT are OK, we always do the | ||
47 | * 'validation', even if address comes from PEERSTORE | ||
48 | * #7 | ||
36 | * - ACK handling / retransmission | 49 | * - ACK handling / retransmission |
37 | * - address verification | 50 | * - address verification |
38 | * - track RTT, distance, loss, etc. | 51 | * - track RTT, distance, loss, etc. |