Loose footnotes: bold-wrapped sup with trailing content
The protocol handles mobility transparently.1
Some care is needed to prevent session hijacking.2
There are several candidate protocols.3
In conclusion, the approach is promising.
1 Note 2024-01-15: This also works with legacy addressing and NAT traversal.
2 Note 2024-01-10: A simple challenge-response exchange during handshake is sufficient to prevent hijacking by outside attackers.
3 Note 2024-03-20: Besides the primary candidate, there are several other proposals with similar properties.
Update 2024-06-01: A follow-up discussion has been posted on the project blog.