Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

transport protocol specification #471

Merged
merged 8 commits into from
Nov 16, 2021
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions content/docs/rfcs/31/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
slug: 31
title: 31/WAKU2-TRANSPORT
rshiv marked this conversation as resolved.
Show resolved Hide resolved
name: Waku v2 Transport Specification
status: draft
editor: Reeshav Khan <reeshav@status.im>
contributors:
---

`31/WAKU2-TRANSPORT` describes the specification for Protocols supported by Waku v2. While Waku v2 strives to be transport agonistic, however any underlying transport layer MUST be IETF standardized transport protocol, this document underlines the baseline for interoperability between different Waku v2 clients.
rshiv marked this conversation as resolved.
Show resolved Hide resolved

# Transport Protocol Specification

Waku client implementations MUST support the TCP transport, and it MUST be enabled for both dialing and listening even if other transports are available. During negotiation upgrade protocol MAY be chosen over TCP.
rshiv marked this conversation as resolved.
Show resolved Hide resolved
The underlying transports SHOULD support websocket and secure websockets for bidirectional communication streams and browser applications.
rshiv marked this conversation as resolved.
Show resolved Hide resolved


# Copyright

Copyright and related rights waived via
[CC0](https://creativecommons.org/publicdomain/zero/1.0/).