Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session Initialization Clarification with datagrams #458

Open
TimEvens opened this issue Jun 6, 2024 · 1 comment · May be fixed by #616
Open

Session Initialization Clarification with datagrams #458

TimEvens opened this issue Jun 6, 2024 · 1 comment · May be fixed by #616
Assignees
Labels
Handshake QUIC vs WebTransport, SETUP Message Needs PR

Comments

@TimEvens
Copy link

TimEvens commented Jun 6, 2024

Section 3.3 states "The first stream opened is a client-initiated bidirectional control stream where the peers exchange Setup messages (Section 6.2)" but does not state what we should do about datagrams being sent before the control stream as well as before CLIENT_SETUP/SERVER_SETUP.

Should the connection be closed by protocol violation if DATAGRAM is received matching any of the following conditions:

  • Control bi-dir stream not yet created; session hasn't been established
  • CLIENT_SETUP and SERVER_SETUP not compete; session hasn't been established
  • CLIENT_SETUP role is 0x02 SUBSCRIBER; publishing is not allowed
@afrind afrind added the Handshake QUIC vs WebTransport, SETUP Message label Jul 24, 2024
@ianswett
Copy link
Collaborator

If you get a Datagram or Unidirectional stream with Objects from a subscription or Fetch you've never made, then it's a protocol violation.

@TimEvens can you write a PR to this effect?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Handshake QUIC vs WebTransport, SETUP Message Needs PR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants