Transport properties / peer state for transport information, etc

[oskarth]

Problem

A client might only have certain transports available. To sync messages, the clients need to know how to reach each other over which transports.

Acceptance criteria

A spec and proof of concept for a data sync client that allows:

• storing of transport information
• switching of preferred way of being contacted

Notes

See https://code.briarproject.org/briar/briar/wikis/Transport-Properties-Client

Also see protocol negotiation in libp2p.

Example: Whisper / MANET / USB sync

[decanus]

Would this make sense to fall into a more broad handshake type thing @oskarth?

[oskarth]

See https://forum.vac.dev/t/transport-agnostic-waku/28/3 for some ideas here

[decanus]

yeah @oskarth, I believe this becomes relevant for compatibility.

[oskarth]

cc @jm-clius for awareness

[oskarth]

Generic message follows

I'm going to go ahead and close this discussion as:

1. It is quite old and we are moving away from GH discussions (in favor of either forum.vac.dev or normal issues)

2. Existing discussion has evolved and is captured in more targeted issues already

If you feel like this is in error, please create a thread on Vac forum or a new issue.