10/WAKU2: Update #125
10/WAKU2: Update #125
Conversation
There was a problem hiding this comment.
Approved, as these changes certainly improve the spec. Main open question is whether (or how) we can stop using the slightly clumsy "Waku v2" everywhere. I also think Research should add this spec to its backlog for a thorough review, as the state of the art looks very different now from when this spec was first compiled. Thanks!
| @@ -14,37 +14,37 @@ contributors: | |||
|
|
|||
| ## Abstract | |||
|
|
|||
| Waku v2 is family of modular peer-to-peer protocols for secure communication. | |||
| Waku v2 is a family of modular peer-to-peer protocols for secure communication. | |||
There was a problem hiding this comment.
Mmm, I realise now I forgot to comment about this while reviewing the WAKU2-MESSAGE spec, but we've generally stopped referring to "Waku v2" and simply use "Waku". The "v2" seems to confuse people, as v1 (now usually just "legacy Waku") is implemented nowhere, difficult to find specifications for and not actively developed. We do want to acknowledge though that this spec introduced a newly designed Waku stack. Perhaps it's possible to drop the "Waku v2" but add a single comment at the top to explain that this suite of protocols were previously referred to as "Waku v2" in order to distinguish it from the obsolete legacy Waku protocol stack?
There was a problem hiding this comment.
Wouldn't this affect all Waku RFCs and RFC IDs? Also may need consensus from the other contributors named in this spec if that is the case. I think the only conflict may be with the stable spec 11/WAKU2-RELAY which only mention Waku v2 in the name within the header (stable specs can not be updated).
The way 11/WAKU2-RELAY is written may be an alternative approach where Waku is used throughout the spec, but v2 is only mentioned in the name within the header. This would still require an update of other spec but doable. @jm-clius
waku/standards/core/10/waku2.md
Outdated
|
|
||
| ### Request/Reply domain | ||
| ### Request/Reply Domain |
There was a problem hiding this comment.
I think we've since opted for "Request/Response" instead of .../Reply
Co-authored-by: Hanno Cornelius <[email protected]>
Updates include changing links, removing deprecated specs, and adding updated specs.