Skip to content
This repository was archived by the owner on Oct 23, 2024. It is now read-only.

Commit 8e3ae51

Browse files
committed
Server sends transport ID to client after authentication.
1 parent 48aacad commit 8e3ae51

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc/design/quic-transport-payload-format.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,4 +41,4 @@ After creating a WebTransport, a stream with session 0 should be created for aut
4141

4242
## Authentication
4343

44-
If signaling messages are transmitted over WebTransport, authentication follows the regular process defined by [Client-Portal Protocol](https://github.com/open-webrtc-toolkit/owt-server/blob/master/doc/Client-Portal%20Protocol.md). Otherwise, client sends a token for WebTransport as a signaling message. WebTransport token is issued during joining a conference.
44+
If signaling messages are transmitted over WebTransport, authentication follows the regular process defined by [Client-Portal Protocol](https://github.com/open-webrtc-toolkit/owt-server/blob/master/doc/Client-Portal%20Protocol.md). Otherwise, client sends a token for WebTransport as a signaling message. WebTransport token is issued during joining a conference. If token is valid, server sends a 128 bit length transport ID to client. The transport ID should be same as the one included in token.

0 commit comments

Comments
 (0)