Protocol Engineering Swarm #332
Conversation
oskarth
force-pushed
the
311-status-protocol
branch
from
c915797
to
1983bae
Compare
311-status-protocol.md
Outdated
|
|
||
| ## Goals | ||
|
|
||
| 1. Create a set of open protocol(s) for secure messaging that reflects our |
There was a problem hiding this comment.
a small inconsistency: "secure messaging" here, "communication protocol" in other places
311-status-protocol.md
Outdated
| requires, what it provides, under what threat models, and with what | ||
| trade-offs. | ||
|
|
||
| 5. Enable implementation of clients to participate in the Stauts Network, and |
There was a problem hiding this comment.
typo: should be "Status Network"
| 5. Reasonable Bandwidth | ||
| 6. Adaptable Anonymity | ||
| 7. Scalable | ||
| 8. No specialized Services |
There was a problem hiding this comment.
I would still want to add that it should be designed with mobile in mind: internet connection is unstable an mostly missing, CPU resources are limited, we can't stay in background for a long time and we are behind very strict firewalls that makes it hard for NAT to pass through.
Maybe it is already incorporated in these requirements, but I just want to reiterate :-P
There was a problem hiding this comment.
Good point, w3f/messaging#18
There was a problem hiding this comment.
Is NAT a problem for UDP in general?
I'm assuming mixnet nodes must be specialized into "relays" and "clients" for numerous reasons.
311-status-protocol.md
Outdated
| likely the scope will be limited, at least initially, to ensure solid progress | ||
| in the most fruitful direction and avoid scope creep. | ||
|
|
||
| Expect the precise scope and requirements to change soemwhat as we get more |
There was a problem hiding this comment.
typo, should be "somewhat"
| – as well as anonymity/secure p2p specific (Tor, Briar, etc) | ||
| 2. Sketch out rough layers of concerns | ||
| 3. Team formation and collaboration with others in the space | ||
| 4. Do write-up of lessons learned so far |
There was a problem hiding this comment.
I would love a presentation about lessons learned and the landscape on the Town Hall or a separate meeting, sounds super interesting to me (though I'm not ready to dig through all the papers myself atm).
|
Thanks! Addressed comments. |
oskarth
force-pushed
the
311-status-protocol
branch
from
1983bae
to
ed86d38
Compare
RFC.