search

GrumpyOldTroll / draft-jholland-quic-multicast

Work in progress to propose a multicast extension to quic.
Other
6 stars 6 forks source link

Add channel state diagram #56

Closed MaxF12 closed 2 years ago

MaxF12 commented 2 years ago

Only from the client point of view for now, I think server side might not actually be necessary because its very similar? (Basically just switch send/receive in front of the frames I think)

Closes #50

MaxF12 commented 2 years ago

I guess a question would be where "declined join" goes, does it just return to unjoined or does it retire the channel (probably not)?

MaxF12 commented 2 years ago

I also didn't include "Held down" as a state since I didn't see what interaction would make it transition back to "unjoined", so it seemed redundant

MaxF12 commented 2 years ago

Only have two states, joined and unjoined, remove timeout triggers, have transition from unjoined to unjoined after receiving a leave

MaxF12 commented 2 years ago

On thinking about it more, didn't add the reflexive arrow for unjoined since the same would also be required for joined when a join arrives and initialized when both join or leave arrive. I think that would make the diagram unnecessarily crowded, this way only action that actually lead to a state change are pictured which I think is consistent.

Also added text to deal with retiring a channel better since it feels relevant to the diagram (closes #58)