+.SH BUGS
+Currently, \fBpubTSP\fR does not use ICMP notifications at the IPv4
+level to provide smart feedback to an IPv6 client. It is undecided
+at this point if this would add value.
+.PP
+To be able to fallback to this TSP profile, an IPv6-only application
+needs to find a \fBpubTSP\fR or similar service. A general naming
+or numbering scheme is needed to make that straightforward. The
+\fBpubTSP\fR service could be setup privately and configured in
+individual IPv6-only nodes, but it could accelerate the introduction
+of IPv6-only nodes if this were organised by network providers.
+.PP
+Ideally, \fBpubTSP\fR would be near all heavily connected nodes
+of the Internet. There, they would improve connectivity without
+being a detour for the traffic. Alternatively, it would be located
+in various uplinks. To optimise routing, it is possible to assign
+a fixed IPv4 address and IPv6 prefix for \fBpubTSP\fR running
+anywhere; its stateless operation means that traffic going back and
+forth can go through different instances of \fBpubTSP\fR without
+posing problems.
+.PP
+The \fBpubTSP\fR daemon is a piece of highly efficient code,
+and it should be able to handle very high bandwidths. A stress
+test has not been conducted yet.